unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: raid5atemyhomework via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: "53043@debbugs.gnu.org" <53043@debbugs.gnu.org>
Subject: bug#53043: Dash To Dock 71 not working properly with Gnome Shell 41
Date: Fri, 07 Jan 2022 06:15:52 +0000	[thread overview]
Message-ID: <MCau22Wi7A7UruA0YoavCp3ptgzavv4QGt_g0GoJlDD70_Uf0ipzSwpyJICuSC4Sz-N47obBb2wUc5RId5YSHDjiJgXhNpcnfvTH5K9INCw=@protonmail.com> (raw)
In-Reply-To: <cdc422111fea6ee21d94ebab8678f63f11f030fd.camel@gmail.com>

Hello,

> Hi,
>
> Am Freitag, dem 07.01.2022 um 03:56 +0000 schrieb raid5atemyhomework:
>
> > Hello Liliana,
> > [...]
> > It may be a related bug, but this may also be unique to how Guix
> > packages both programs. So I want to know if other users on Guix are
> > seeing the same thing as well.
>
> We don't do rigorous integration tests for GNOME Shell extensions and
> to my knowledge you are the first one to report that bug.

It's probably because "Use built-in theme" is default-enabled and this bug seems to appear with this setting disabled.  Disabling the setting lets me set up some more settings for the dock which is why I prefer this setting disabled.

> > Given the default `(service gnome-desktop-service-type)`, where does
> > `gnome-shell` put its logs?
> > There are no logs for Gnome Shell specifically on `/var/log`, it does
> > not print anything in `/var/log/Xorg.0.log`, and `info guix` does not
> > describe any log output directory for `gnome-desktop-configuration`,
> > so I don't know where Gnome Shell on Guix puts its logs.  Does it
> > just get printed to console?
>
> There's your ~/.local/share/xorg logs that you haven't mentioned yet,
> but I doubt something like an extension misbehaving (i.e. not even
> raising an error that GNOME Shell detects) would end up there. I'm not
> aware of any other GNOME-specific logs and their locations, but since
> it's either /var/log or somewhere in your $HOME/.something, I don't
> think Guix would do anything to manipulate the output path. You could
> try checking for logs in GDM's home as well, which requires sudo to ls.


The github issue you linked to asks for logs as well, so presumably they print *something* on the logs that might help them.

Nothing in my normal user `~/.local/share/` has xorg in it, and `root` has no `~root/.local`.  My user has `~/.local/share/gnome-shell` but it has no logs either.  I also looked into `~/.cache` and `~/.local` for both my user and `root` -- no dice.

I don't use GDM since it keeps wanting to suspend the computer, and the computer is intended to be a fileserver and printserver, the Gnome Shell is just there for ease-of-use since the printer is a scanner/printer and you can't really remotely use the scanner usefully since you have to feed the papers to scan into it one by one anyway.

Looking at my console, flipping the "Use built-in theme" shows a bunch of error messages on the console.  Sigh.  Looks like `gnome-shell` on Guix prints its logs to console, which makes it a headache to copy-paste messages off for bug reports.

Re:

> but I doubt something like an extension misbehaving (i.e. not even
> raising an error that GNOME Shell detects) would end up there.

It's JavaScript.  If you have a browser and open its console while browsing most websites, you'll see a fair number of error messages there, even though the site may be operating perfectly well as far as you can tell --- errors don't cause a typical JavaScript application to crash because an error will just send it back to the event mainloop and it will keep on going on despite bunches of JavaScript errors.  That's why logs for `gnome-shell` are fairly vital, and it's getting thrown into the console where they are not recorded.  Sigh.  More coding to do to make Guix useful.

Thanks
raid5atemyhomework




  reply	other threads:[~2022-01-07  6:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06  4:35 bug#53043: Dash To Dock 71 not working properly with Gnome Shell 41 raid5atemyhomework via Bug reports for GNU Guix
2022-01-06  6:59 ` Liliana Marie Prikler
2022-01-07  3:56   ` raid5atemyhomework via Bug reports for GNU Guix
2022-01-07  5:23     ` Liliana Marie Prikler
2022-01-07  6:15       ` raid5atemyhomework via Bug reports for GNU Guix [this message]
2022-10-23 17:27         ` Liliana Marie Prikler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='MCau22Wi7A7UruA0YoavCp3ptgzavv4QGt_g0GoJlDD70_Uf0ipzSwpyJICuSC4Sz-N47obBb2wUc5RId5YSHDjiJgXhNpcnfvTH5K9INCw=@protonmail.com' \
    --to=bug-guix@gnu.org \
    --cc=53043@debbugs.gnu.org \
    --cc=liliana.prikler@gmail.com \
    --cc=raid5atemyhomework@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).