Your message dated Thu, 5 Sep 2024 20:35:01 -0400
with message-id
<CAD+GYvyYLhPp4bLcYZOq6WG61ubS=ra6okz8i7gyhbhn4of...@mail.gmail.com>
and subject line Re: gnome-shell is trapped with invalid opcode when working
with gdm3.
has caused the Debian Bug report #790862,
regarding gnome-shell is trapped with invalid opcode when working with gdm3.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
790862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell
Version: 3.16.2-4
Severity: normal
Dear Maintainer,
When I log in this machine (with Intel(R) Celeron(R) CPU U3400 @
1.07GHz) after booting, the normal screen of gnome-shell DE appears, but the
whole screen turns black. If I press a key, the lockdown screen appears. When I
try to type the password, it enters an endless loop as if the unlock button
were
clicked repeatedly, as the screen starts blinking, and any input to the
password
textbox disappears, except that a notice like "authentication failed(In
Chinese)" is shown. With the help of my friend, I tried to login from text ttys
(1~6), and restart gdm3. But the gnome-shell crashes, with the following lines
in the syslog:
>Jul 2 19:29:49 toshiba-chenlin kernel: [ 115.119886] traps: gnome-
shell[3129] trap invalid opcode ip:7f729104a639 sp:7ffc81171df8 error:0
>Jul 2 19:29:51 toshiba-chenlin dbus[1950]: [system] Activating service
name='org.freedesktop.GeoClue2' (using servicehelper)
>Jul 2 19:29:51 toshiba-chenlin dbus[1950]: [system] Successfully activated
service 'org.freedesktop.GeoClue2'
>Jul 2 19:29:51 toshiba-chenlin kernel: [ 117.825838] traps: gnome-
shell[3218] trap invalid opcode ip:7f857808d639 sp:7ffef6ea8d78 error:0
>Jul 2 19:29:51 toshiba-chenlin gnome-session[3064]: WARNING: App 'gnome-
shell.desktop' respawning too quickly
And it seems the above "black screen" phenomenon is also caused by the crash of
gnome shell.
Now I have to switch to an lxde env I installed earlier for work.
This bug nevers appears on any other machines I know, running debian testing
and full gnome DE.
My friend tried to get cores from any possible crashed program, but could not
find any way. If you have and idea about how to get cores for gdm3,please let
me know, so I can gather more info for the bug.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (900, 'testing'), (500, 'testing-proposed-updates'), (500,
'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages gnome-shell depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2
ii evolution-data-server 3.16.3-1+b1
ii gir1.2-accountsservice-1.0 0.6.40-2
ii gir1.2-atspi-2.0 2.16.0-1
ii gir1.2-caribou-1.0 0.4.18.1-1
ii gir1.2-clutter-1.0 1.22.2-3
ii gir1.2-freedesktop 1.44.0-1+b1
ii gir1.2-gcr-3 3.16.0-1
ii gir1.2-gdesktopenums-3.0 3.16.1-1
ii gir1.2-gdm3 3.14.1-8
ii gir1.2-gkbd-3.0 3.6.0-1
ii gir1.2-glib-2.0 1.44.0-1+b1
ii gir1.2-gnomebluetooth-1.0 3.16.1-1
ii gir1.2-gnomedesktop-3.0 3.16.2-2
ii gir1.2-gtk-3.0 3.16.4-2
ii gir1.2-gweather-3.0 3.16.1-1
ii gir1.2-ibus-1.0 1.5.10-1
ii gir1.2-mutter-3.0 3.16.2-2
ii gir1.2-networkmanager-1.0 1.0.2-2
ii gir1.2-nmgtk-1.0 1.0.2-1
ii gir1.2-pango-1.0 1.36.8-3
ii gir1.2-polkit-1.0 0.105-8
ii gir1.2-soup-2.4 2.50.0-2
ii gir1.2-telepathyglib-0.12 0.24.1-1
ii gir1.2-telepathylogger-0.2 0.8.1-1
ii gir1.2-upowerglib-1.0 0.99.3-1+b1
ii gjs 1.43.3-2
ii gnome-backgrounds 3.16.0-1
ii gnome-icon-theme-symbolic 3.12.0-1
ii gnome-settings-daemon 3.16.2-3
ii gnome-shell-common 3.16.2-4
ii gnome-themes-standard 3.16.2-2
ii gsettings-desktop-schemas 3.16.1-1
ii libatk-bridge2.0-0 2.16.0-1
ii libatk1.0-0 2.16.0-2
ii libc6 2.19-18
ii libcairo2 1.14.2-2
ii libcanberra-gtk3-0 0.30-2.1
ii libcanberra0 0.30-2.1
ii libclutter-1.0-0 1.22.2-3
ii libcogl-pango20 1.20.0-2
ii libcogl20 1.20.0-2
ii libcroco3 0.6.8-3+b1
ii libdbus-glib-1-2 0.102-1
ii libecal-1.2-18 3.16.3-1+b1
ii libedataserver-1.2-20 3.16.3-1+b1
ii libgcr-base-3-1 3.16.0-1
ii libgdk-pixbuf2.0-0 2.31.4-2
ii libgirepository-1.0-1 1.44.0-1+b1
ii libgjs0e [libgjs0-libmozjs-24-0] 1.43.3-2
ii libglib2.0-0 2.44.1-1.1
ii libgstreamer1.0-0 1.4.5-2
ii libgtk-3-0 3.16.4-2
ii libical1a 1.0-1.3
ii libjson-glib-1.0-0 1.0.4-1
ii libmozjs-24-0 24.2.0-3
ii libmutter0f 3.16.2-2
ii libnm-glib4 1.0.2-2
ii libnm-util2 1.0.2-2
ii libpango-1.0-0 1.36.8-3
ii libpangocairo-1.0-0 1.36.8-3
ii libpolkit-agent-1-0 0.105-8
ii libpolkit-gobject-1-0 0.105-8
ii libpulse-mainloop-glib0 6.0-2
ii libpulse0 6.0-2
ii libsecret-1-0 0.18.2-1
ii libstartup-notification0 0.12-4
ii libsystemd0 220-7
ii libtelepathy-glib0 0.24.1-1
ii libx11-6 2:1.6.3-1
ii libxfixes3 1:5.0.1-2+b2
ii mutter 3.16.2-2
ii python3 3.4.2-2
ii telepathy-mission-control-5 1:5.16.3-1
Versions of packages gnome-shell recommends:
ii gdm3 3.14.1-8
ii gkbd-capplet 3.6.0-1
ii gnome-contacts 3.16.2-1
ii gnome-control-center 1:3.16.2-2+b1
ii gnome-user-guide 3.16.1-1
ii unzip 6.0-17
gnome-shell suggests no packages.
--- End Message ---
--- Begin Message ---
There have been many changes to Debian and GNOME Shell since this bug
was originally reported. If you are still experiencing this issue with
Debian 12, please report a new bug.
Thank you,
Jeremy Bícha
--- End Message ---
