02-26-2020, 08:00 AM
(This post was last modified: 02-26-2020, 09:44 AM by tophneal.)
I'll check into mine this evening (I forgot my Gnome install SDs at home today.) If I can get my Arch install resized enough to install GNome, today, I'll try then if the problem exists there, too.
EDIT: Just tried this
Code: $ grep -r '/dev\|dri\|gpu' /etc/dbus-1 /usr/share/dbus-1
on a fresh Arch install, and got an error that /etc/dbus-1 did not exist. Checked with ls, and it was, in fact, not there. No dbus folder was, even after installing dbus.
(02-26-2020, 08:00 AM)tophneal Wrote: I'll check into mine this evening (I forgot my Gnome install SDs at home today.) If I can get my Arch install resized enough to install GNome, today, I'll try then if the problem exists there, too.
EDIT: Just tried this
Code: $ grep -r '/dev[^i]\|dri\|gpu' /etc/dbus-1 /usr/share/dbus-1
on a fresh Arch install, and got an error that /etc/dbus-1 did not exist. Checked with ls, and it was, in fact, not there. No dbus folder was, even after installing dbus.
What about this (on a system with broken GNOME)?
Code: $ for d in {/etc,/usr/share}/{dbus-1,polkit-1,pam.d}; do [ -d $d ] && sudo grep -ri '/dev[^i]\|dri[^v]\|gpu' $d; done
tophneal
(02-24-2020, 03:20 PM)pjsf Wrote: (02-24-2020, 02:22 PM)tophneal Wrote: Last week on Manjaro I got a whole stack of updates to GNOME and some system packages. After rebooting, both gdm and GNOME give me black screens with cursors, journalctl /usr/bin/gnome-shell gives me a bunch of errors:
Code: Failed to open gpu '/dev/dri/card0':
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Operation not permitted
Installed Budgie a little earlier to get another DE going, and to see if it'd run since it shares a lot with Gnome. It runs without any issue.
Have any other GNOME3 users experienced similar issues from the most recent updates?
yes. it broke for me in both an Xorg and wayland session, so far I've tried falling back from nesa-git to mesa with no change, going to try re-installing Gnome=shell next.
Thanks for your feedback! Have you found any indication to what happened?
Don;t hold your breath on reinstalling gnome-shell  Ive reinstalled the entire gnome DE and still cant get into a usable DE.
It's a gnome-shell coredump for me/
log.txt (Size: 18.98 KB / Downloads: 361)
02-27-2020, 09:48 PM
(This post was last modified: 02-27-2020, 09:50 PM by tophneal.)
Same thing for me on Mankato and Arch. I think someone has this issue on fedora, too.
Have you tried running the command in post before yours? I haven't had a chance yet. We’ve certainly stumbled across something we should submit as an issue, but it's hard to tell what.
I wanna metoo these gdm/gnome-shell errors. After getting a replacment DE running I thought I could debug this a bit, but did not get very far.
I tried upgrading the Manjaro packages to the archlinuxarm upstream ones, but that did not help. Still, there are no reports on their forum, which leads me to conclude that either a) the issue does not exist there b) the forums are not very active c) hardly anyone uses GNOME there.
(02-27-2020, 02:59 AM)icecream95 Wrote: Code: $ for d in {/etc,/usr/share}/{dbus-1,polkit-1,pam.d}; do [ -d $d ] && sudo grep -ri '/dev[^i]\|dri[^v]\|gpu' $d; done
This does not result in any output for me.
I tried checking the logs of gdm and its subprocesses. GDM does not yield any unusual output, until it is stopped, when it says that a child process already was dead:
Code: Feb 28 12:22:28 buddy systemd[1]: Starting GNOME Display Manager...
Feb 28 12:22:28 buddy systemd[1]: Started GNOME Display Manager.
Feb 28 12:31:06 buddy systemd[1]: Stopping GNOME Display Manager...
Feb 28 12:31:07 buddy gdm[1417]: Child process -1464 was already dead.
Feb 28 12:31:07 buddy gdm[1417]: GdmDisplay: Session never registered, failing
Feb 28 12:31:07 buddy gdm[1417]: GLib: g_hash_table_foreach: assertion 'version>
Feb 28 12:31:07 buddy systemd[1]: gdm.service: Succeeded.
Feb 28 12:31:07 buddy systemd[1]: Stopped GNOME Display Manager.
The only unusual thing in the Xorg output is
Code: Feb 28 12:23:22 buddy /usr/lib/gdm-x-session[1466]: (II) AIGLX: Suspending AIGLX clients for VT switch
but I don't think that is the source of the error. The suggested fix that I found on some BSD forum did not help anyway.
One last note-worthy thing, I found that gnome-control-center won't start either, failing at an assertion for visibility of a panel.
Code: ERROR:../gnome-control-center/shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Bail out! ERROR:../gnome-control-center/shell/cc-shell-model.c:458:cc_shell_model_set_panel_visibility: assertion failed: (valid)
Aborted (core dumped)
(02-27-2020, 09:48 PM)tophneal Wrote: Same thing for me on Mankato and Arch. I think someone has this issue on fedora, too.
Have you tried running the command in post before yours? I haven't had a chance yet. We’ve certainly stumbled across something we should submit as an issue, but it's hard to tell what. This is what I get. nothing there that look significantly different to my desktop machine.
/usr/share/dbus-1/interfaces/org.gnome.Shell.PadOsd.xml: @device_node: device node file, usually in /dev/input/...
/usr/share/dbus-1/interfaces/org.freedesktop.UPower.Device.xml: <doc:term>6</doc:term><doc:definition>Nickel metal hydride</doc:definition>
/usr/share/polkit-1/actions/org.freedesktop.UDisks2.policy: <!-- NOTE: this is not a DoS because we are using /dev/loop-control -->
/usr/share/polkit-1/actions/org.gnome.settings-daemon.plugins.power.policy: <description xml:lang="da">Ændring af den bærbares lysstyrke</description>
/usr/share/polkit-1/actions/org.gnome.settings-daemon.plugins.power.policy: <message xml:lang="da">Ændring af den bærbares lysstyrke kræver godkendelse</message>
/usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy: <message xml:lang="sv">Systemets policy förhindrar ändring av personliga nätverksinställningar</message>
/usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy: <message xml:lang="sv">Systemets policy förhindrar ändring av nätverksinställningar för alla användare</message>
/usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy: <message xml:lang="da">Systempolitikken forhindrer ændring af det faste systemværtsnavn</message>
/usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy: <message xml:lang="sv">Systemets policy förhindrar ändring av bestående värdnamn för systemet</message>
/usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy: <message xml:lang="sv">Systemets policy förhindrar ändring av bestående global DNS-konfiguration</message>
/usr/share/polkit-1/actions/org.gnome.settings-daemon.plugins.wacom.policy: <message xml:lang="da">Ændring af den tændte LED på en Wacom-tegneplade kræver godkendelse</message>
/usr/share/polkit-1/actions/org.opensuse.cupspkhelper.mechanism.policy: <description xml:lang="tr">Bir yazıcıyı etkinleştir/devre dışı bırak</description>
(02-28-2020, 07:52 PM)pjsf Wrote: (02-27-2020, 09:48 PM)tophneal Wrote: Same thing for me on Mankato and Arch. I think someone has this issue on fedora, too.
Have you tried running the command in post before yours? I haven't had a chance yet. We’ve certainly stumbled across something we should submit as an issue, but it's hard to tell what. This is what I get. nothing there that look significantly different to my desktop machine.
/usr/share/dbus-1/interfaces/org.gnome.Shell.PadOsd.xml: @device_node: device node file, usually in /dev/input/...
/usr/share/dbus-1/interfaces/org.freedesktop.UPower.Device.xml: <doc:term>6</doc:term><doc:definition>Nickel metal hydride</doc:definition>
/usr/share/polkit-1/actions/org.freedesktop.UDisks2.policy: <!-- NOTE: this is not a DoS because we are using /dev/loop-control -->
/usr/share/polkit-1/actions/org.gnome.settings-daemon.plugins.power.policy: <description xml:lang="da">Ændring af den bærbares lysstyrke</description>
It looks like you have a different issue to the original on this thread, which was related to DBus configuration.
Maybe try submitting a bug on the GNOME bug tracker:
https://gitlab.gnome.org/GNOME/gnome-shell/issues
03-03-2020, 10:46 AM
(This post was last modified: 03-03-2020, 11:15 AM by tophneal.)
(02-27-2020, 02:59 AM)icecream95 Wrote: What about this (on a system with broken GNOME)?
Code: $ for d in {/etc,/usr/share}/{dbus-1,polkit-1,pam.d}; do [ -d $d ] && sudo grep -ri '/dev[^i]\|dri[^v]\|gpu' $d; done
Here's the output I get from that. Nothing seems too telling, but I may also have no idea what I'm talking about (always a likely scenario.)
Code: /usr/share/dbus-1/interfaces/org.gnome.Shell.PadOsd.xml: @device_node: device node file, usually in /dev/input/...
/usr/share/dbus-1/interfaces/org.freedesktop.portal.Flatpak.xml: Share the gpu access with the caller.
/usr/share/dbus-1/interfaces/org.freedesktop.UPower.Device.xml: <doc:term>6</doc:term><doc:definition>Nickel metal hydride</doc:definition>
/usr/share/polkit-1/actions/org.gnome.settings-daemon.plugins.power.policy: <description xml:lang="da">Ændring af den bærbares lysstyrke</description>
/usr/share/polkit-1/actions/org.gnome.settings-daemon.plugins.power.policy: <message xml:lang="da">Ændring af den bærbares lysstyrke kræver godkendelse</message>
/usr/share/polkit-1/actions/org.opensuse.cupspkhelper.mechanism.policy: <description xml:lang="tr">Bir yazıcıyı etkinleştir/devre dışı bırak</description>
/usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy: <message xml:lang="sv">Systemets policy förhindrar ändring av personliga nätverksinställningar</message>
/usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy: <message xml:lang="sv">Systemets policy förhindrar ändring av nätverksinställningar för alla användare</message>
/usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy: <message xml:lang="da">Systempolitikken forhindrer ændring af det faste systemværtsnavn</message>
/usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy: <message xml:lang="sv">Systemets policy förhindrar ändring av bestående värdnamn för systemet</message>
/usr/share/polkit-1/actions/org.freedesktop.NetworkManager.policy: <message xml:lang="sv">Systemets policy förhindrar ändring av bestående global DNS-konfiguration</message>
/usr/share/polkit-1/actions/org.freedesktop.UDisks2.policy: <!-- NOTE: this is not a DoS because we are using /dev/loop-control -->
/usr/share/polkit-1/actions/org.gnome.settings-daemon.plugins.wacom.policy: <message xml:lang="da">Ændring af den tændte LED på en Wacom-tegneplade kræver godkendelse</message>
BTW, thanks for your efforts in helping troubleshoot this!
EDIT: Just booted up one of my broken installs, and decided to try editing GDM's custom.conf to disable it using wayland, and the autologin I setup to put me into Budgie. Now I get some more telling output on boot: "failed to startload kernel module drm" That repeats with a similar error from logind, and cupsd, then stops.
At this point I think it might be worth it to just wait for GNOME Shell 3.36 to be made available in the repos and hope that that will fix these issues.
03-05-2020, 07:19 AM
(This post was last modified: 03-06-2020, 07:32 AM by tophneal.)
(03-05-2020, 05:59 AM)p3732 Wrote: At this point I think it might be worth it to just wait for GNOME Shell 3.36 to be made available in the repos and hope that that will fix these issues.
I agree. I can't really hope to fix my broken Gnome installs, now anyway. Both my Manjaro and Arch SDs became corrupted, or refused to boot (and for some reason my Manjaro turned half the system folders into files. )
Gnome does seem to be working well on Fedora, though. Maybe they've held back the faulty update? nope, I just forgot to check for updates. 3.34 is there waiting. However, as pointed out on the Manjaro forum, this may help resolve the issue: https://bbs.archlinux.org/viewtopic.php?...8#p1883388
|
Question for GNOME3 users
