Bug#948288: A workaround ...
... that circumvents both problems but does not solve them turns out to be disabling Wayland and sticking with Xorg by means of changing #WaylandEnable=false to WaylandEnable=false in /etc/gdm3/daemon.conf and rebooting. The original problems didn't go away, of course; the bugs still persist in whichever state they might be.
Bug#948288: bugs 948288 and 950504 are related but not the same
affects 948288 gdm3 affects 950504 gnome-shell -- In http://bugs.debian.org/948288 , we deal with a segfault of gnome-shell and Mesa issues using the default kernel command line without nomodeset. In http://bugs.debian.org/950504, we deal with the boot process getting stuck when nomodeset option in the kernel command line.
Bug#948288: gnome-shell reproducibly crashes on boot, and the boot process gets stuck
Dear Bernhard, As to what happens with nomodeset, I posted another bug report against gdm3: http://bugs.debian.org/950504. There, we probably won't have to deal with a gnome-shell segfault and Mesa issues that we have to deal with here. Best regards, Md Ayquassar
Bug#950504: gdm3 reproducibly gets stuck upon boot with nomodeset kernel setting: boot photos 1
Here are some initial boot photos.
Bug#948288: gnome-shell reproducibly crashes on boot, and the boot process gets stuck
I added nomodeset as described in https://askubuntu.com/a/38834 . Then, the boot process displayed some error concerning UMS and radeon early in the process, and the screen resolution is different. The boot process still gets stuck, and switching with Ctrl+Alt+F1 followed by Ctrl+Alt+F2 makes it continue, but the segfault message disappears from dmesg.
Bug#948288: gnome-shell reproducibly crashes on boot, and the boot process gets stuck
In the attachment you find /var/log/Xorg.0.log. It contains some error message. Concerning nomodeset: can I add it during boot process when the grub screen pops up? [37.930] X.Org X Server 1.20.4 X Protocol Version 11, Revision 0 [37.931] Build Operating System: Linux 4.9.0-8-amd64 i686 Debian [37.931] Current Operating System: Linux T42-LAPTOP 4.19.0-6-686 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) i686 [37.931] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-686 root=UUID=c2e7e76d-6ee0-4705-9f83-ed1310bcbced ro quiet [37.931] Build Date: 05 March 2019 08:11:12PM [37.931] xorg-server 2:1.20.4-1 (https://www.debian.org/support) [37.931] Current version of pixman: 0.36.0 [37.931] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [37.931] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [37.932] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 1 18:22:53 2020 [38.244] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [38.454] (==) No Layout section. Using the first Screen section. [38.454] (==) No screen section available. Using defaults. [38.454] (**) |-->Screen "Default Screen Section" (0) [38.454] (**) | |-->Monitor "" [38.484] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [38.485] (==) Automatically adding devices [38.485] (==) Automatically enabling devices [38.485] (==) Automatically adding GPU devices [38.485] (==) Max clients allowed: 256, resource mask: 0x1f [38.905] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [38.905] Entry deleted from font path. [39.435] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [39.435] (==) ModulePath set to "/usr/lib/xorg/modules" [39.435] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [39.435] (II) Loader magic: 0x70a740 [39.435] (II) Module ABI versions: [39.435] X.Org ANSI C Emulation: 0.4 [39.435] X.Org Video Driver: 24.0 [39.435] X.Org XInput driver : 24.1 [39.435] X.Org Server Extension : 10.0 [39.443] (++) using VT number 7 [39.443] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [39.444] (II) xfree86: Adding drm device (/dev/dri/card0) [39.461] (--) PCI:*(1@0:0:0) 1002:4c57:1014:0530 rev 0, Mem @ 0xe000/134217728, 0xc010/65536, I/O @ 0x3000/256, BIOS @ 0x/131072 [39.557] (II) LoadModule: "glx" [39.584] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [40.260] (II) Module glx: vendor="X.Org Foundation" [40.260] compiled for 1.20.4, module version = 1.0.0 [40.260] ABI class: X.Org Server Extension, version 10.0 [40.260] (II) Applying OutputClass "Radeon" to /dev/dri/card0 [40.260] loading driver: radeon [40.260] (==) Matched radeon as autoconfigured driver 0 [40.260] (==) Matched ati as autoconfigured driver 1 [40.260] (==) Matched modesetting as autoconfigured driver 2 [40.260] (==) Matched fbdev as autoconfigured driver 3 [40.260] (==) Matched vesa as autoconfigured driver 4 [40.260] (==) Assigned the driver to the xf86ConfigLayout [40.260] (II) LoadModule: "radeon" [40.329] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [40.575] (II) Module radeon: vendor="X.Org Foundation" [40.575] compiled for 1.20.4, module version = 19.0.1 [40.575] Module class: X.Org Video Driver [40.575] ABI class: X.Org Video Driver, version 24.0 [40.575] (II) LoadModule: "ati" [40.575] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [40.594] (II) Module ati: vendor="X.Org Foundation" [40.594] compiled for 1.20.4, module version = 19.0.1 [40.594] Module class: X.Org Video Driver [40.594] ABI class: X.Org Video Driver, version 24.0 [40.596] (II) LoadModule: "modesetting" [40.596] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [40.722] (II) Module modesetting: vendor="X.Org Foundation" [40.722] compiled for 1.20.4, module version = 1.20.4 [40.722] Module class: X.Org Video Driver [40.722] ABI class: X.Org Video Driver, version 24.0 [40.722] (II) LoadModule: "fbdev" [40.723] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [40.796] (II) Module fbdev: vendor="X.Org Foundation" [40.796] compiled for 1.20.0, module version = 0.5.0 [40.796] Module class: X.Org Video Driver [40.796]
Bug#948288: gnome-shell reproducibly crashes on boot, and the boot process gets stuck
First, thanks for a quick response. Second, is a reassignment to some Mesa package required? Third, is there anything else I can do as a user to help the developers to bugfix this? Bug at line 1017 is strange: if there is a NULL dereference there, there should also probably be one in line 1016 unless someone has a deterministic concurrent access to that data. Fourth, I apologize for long delays.I don’t always have the laptop at my direct disposal. 31.01.2020, 02:09, Bernhard Übelacker Hello Md Ayquassar, sorry, I did not recognize that you seem to have a usrmerge'd system. Then I get following backtraces from your core dump, with and without debug symbols. It looks like a function pointer gets called unconditionally, while containing NULL. Seems to be graphics driver related. Kind regards, Bernhard https://sources.debian.org/src/mesa/18.3.6-2/src/egl/drivers/dri2/egl_dri2.c/#L1017 (gdb) bt #0 0x in ?? () #1 0xaf7d2c74 in ?? () from /lib/i386-linux-gnu/libEGL_mesa.so.0 #2 0xaf7d755e in ?? () from /lib/i386-linux-gnu/libEGL_mesa.so.0 #3 0xade2d004 in ?? () from /usr/lib/i386-linux-gnu/dri/radeon_dri.so #4 0xade2d812 in ?? () from /usr/lib/i386-linux-gnu/dri/radeon_dri.so #5 0xade9232f in ?? () from /usr/lib/i386-linux-gnu/dri/radeon_dri.so #6 0xaf7d29ba in ?? () from /lib/i386-linux-gnu/libEGL_mesa.so.0 #7 0xaf7c061c in eglMakeCurrent () from /lib/i386-linux-gnu/libEGL_mesa.so.0 #8 0xb4cd8b58 in ?? () from /lib/i386-linux-gnu/libEGL.so.1 #9 0xb674a1bd in _cogl_winsys_egl_make_current () from /usr/lib/i386-linux-gnu/mutter/libmutter-cogl-3.so #10 0xb6d8f1f6 in ?? () from /lib/i386-linux-gnu/libmutter-3.so.0 #11 0xb6ceaca4 in meta_renderer_rebuild_views () from /lib/i386-linux-gnu/libmutter-3.so.0 #12 0xb6d920fa in meta_stage_native_rebuild_views () from /lib/i386-linux-gnu/libmutter-3.so.0 #13 0xb6d83ba7 in ?? () from /lib/i386-linux-gnu/libmutter-3.so.0 #14 0xb6ccf11a in ?? () from /lib/i386-linux-gnu/libmutter-3.so.0 #15 0xb6ccff40 in ?? () from /lib/i386-linux-gnu/libmutter-3.so.0 #16 0xb6d83f98 in ?? () from /lib/i386-linux-gnu/libmutter-3.so.0 #17 0xb6cd053a in meta_clutter_init () from /lib/i386-linux-gnu/libmutter-3.so.0 #18 0xb6d20323 in meta_init () from /lib/i386-linux-gnu/libmutter-3.so.0 #19 0x004ad53d in ?? () #20 0xb6aa2b41 in __libc_start_main (main=0x4ad430, argc=1, argv=0xbff2c2a4, init=0x4adfa0, fini=0x4ae000, rtld_fini=0xb7f97520 <_dl_fini>, stack_end=0xbff2c29c) at ../csu/libc-start.c:308 #21 0x004ad8d1 in ?? () (gdb) Core was generated by `/usr/bin/gnome-shell'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x in ?? () [Current thread is 1 (Thread 0xb1f2eb80 (LWP 899))] (gdb) set width 0 (gdb) set pagination off (gdb) bt #0 0x in ?? () #1 0xaf7d2c74 in dri2_egl_surface_alloc_local_buffer (dri2_surf=0x1b8e9f0, att=9, format=32) at ../src/egl/drivers/dri2/egl_dri2.c:1017 #2 0xaf7d755e in dri2_drm_get_buffers_with_format (driDrawable=0x1b73580, width=0x1b73598, height=0x1b7359c, attachments=0xbff2bb04, count=2, out_count=0xbff2baf8, loaderPrivate=0x1b8e9f0) at ../src/egl/drivers/dri2/platform_drm.c:344 #3 0xade2d004 in radeon_update_renderbuffers (context=0x19e7d60, drawable=0x1b73580, front_only=0 '\000') at ../src/mesa/drivers/dri/radeon/radeon_common_context.c:421 #4 0xade2d812 in radeonMakeCurrent (driContextPriv=0x19e7d60, driDrawPriv=0x1b73580, driReadPriv=0x1b73580) at ../src/mesa/drivers/dri/radeon/radeon_common_context.c:616 #5 0xade9232f in driBindContext (pcp=0x19e7d60, pdp=0x1b73580, prp=0x1b73580) at ../src/mesa/drivers/dri/common/dri_util.c:579 #6 0xaf7d29ba in dri2_make_current (drv=0x19e5120, disp=0x19e49c0, dsurf=0x1b8e9f0, rsurf=0x1b8e9f0, ctx=) at ../src/egl/drivers/dri2/egl_dri2.c:1516 #7 0xaf7c061c in eglMakeCurrent (dpy=0x19e49c0, draw=0x1b8e9f0, read=0x1b8e9f0, ctx=0x19fe5c0) at ../src/egl/main/eglapi.c:860 #8 0xb4cd8b58 in InternalMakeCurrentVendor (dpy=0x19e3dd0, draw=draw@entry=0x1b8e9f0, read=0x1b8e9f0, read@entry=0x19c3310, context=0x19fe5c0, apiState=0x19fe360, vendor=) at ../../../src/EGL/libegl.c:861 #9 0xb4cd9606 in eglMakeCurrent (dpy=, draw=, read=0x1b8e9f0, context=0x19fe5c0) at ../../../src/EGL/libegl.c:727 #10 0xb674a1bd in _cogl_winsys_egl_make_current (display=0x19ca4d8, draw=0x1b8e9f0, read=0x1b8e9f0, context=0x19fe5c0) at winsys/cogl-winsys-egl.c:300 #11 0xb6d8f1f6 in meta_renderer_native_create_view (renderer=0x19c8610, logical_monitor=0x19bbf20) at backends/native/meta-renderer-native.c:2949 #12 0xb6ceaca4 in meta_renderer_create_view (logical_monitor=, renderer=0x19c8610) at ./backends/meta-renderer.h:36 #13 meta_renderer_rebuild_views (renderer=0x19c8610) at backends/meta-renderer.c:73 #14 0xb6d920fa in meta_stage_native_rebuild_views (stage_native=0x19c2470) at backends/native/meta-stage-native.c:141 #15 0xb6d83ba7 in meta_backend_native_update_screen_size (backend=0x19a48b8, width=1024, heig
Bug#948288: gnome-shell reproducibly crashes on boot, and the boot process gets stuck
Dear Bernhard: In the attachment you find the output again and file generated, namely, /tmp/reportbug-gnome-shell-backup-20200130-3154-vovyhuqk. (I think the attachments might be easier to view due to line breaks at proper places.) Best regards, Md Ayquassar reportbug-gnome-shell-backup-20200130-3154-vovyhuqk Description: Binary data Warning: no reportbug configuration found. Proceeding in novice mode. Detected character set: UTF-8 Please change your locale if this is incorrect. Using 'guest ' as your from address. Getting status for gnome-shell... Will send report to Debian (per lsb_release). Maintainer for gnome-shell is 'Debian GNOME Maintainers '. Looking up dependencies of gnome-shell... Getting status for related package gnome-session... Looking up 'depends' of related package gnome-session... Looking up 'suggests' of related package gnome-session... Getting status for related package gnome-settings-daemon... Looking up 'depends' of related package gnome-settings-daemon... Looking up 'recommends' of related package gnome-settings-daemon... Getting status for related package libgjs0g... Looking up 'depends' of related package libgjs0g... Getting status for related package libmutter-3-0... Looking up 'depends' of related package libmutter-3-0... Looking up status of additional packages... Getting changed configuration files... Rewriting subject to 'gnome-shell: none' Saving a backup of the report at /tmp/reportbug-gnome-shell-backup-20200130-3154-vovyhuqk Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: guest To: Debian Bug Tracking System Subject: gnome-shell: none Package: gnome-shell Version: 3.30.2-11~deb10u1 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.19.0-6-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii evolution-data-server3.30.5-1 ii gir1.2-accountsservice-1.0 0.6.45-2 ii gir1.2-atspi-2.0 2.30.0-7 ii gir1.2-freedesktop 1.58.3-2 ii gir1.2-gcr-3 3.28.1-1 ii gir1.2-gdesktopenums-3.0 3.28.1-1 ii gir1.2-gdm-1.0 3.30.2-3 ii gir1.2-geoclue-2.0 2.5.2-1 ii gir1.2-glib-2.0 1.58.3-2 ii gir1.2-gnomebluetooth-1.03.28.2-4~deb10u1 ii gir1.2-gnomedesktop-3.0 3.30.2.1-2 ii gir1.2-gtk-3.0 3.24.5-1 ii gir1.2-gweather-3.0 3.28.2-2 ii gir1.2-ibus-1.0 1.5.19-4+deb10u1 ii gir1.2-mutter-3 3.30.2-9~deb10u1 ii gir1.2-nm-1.01.14.6-2+deb10u1 ii gir1.2-nma-1.0 1.8.20-1.1 ii gir1.2-pango-1.0 1.42.4-7~deb10u1 ii gir1.2-polkit-1.00.105-25 ii gir1.2-rsvg-2.0 2.44.10-2.1 ii gir1.2-soup-2.4 2.64.2-2 ii gir1.2-upowerglib-1.00.99.10-1 ii gjs 1.54.3-1 ii gnome-backgrounds3.30.0-1 ii gnome-settings-daemon3.30.2-3 ii gnome-shell-common 3.30.2-11~deb10u1 ii gsettings-desktop-schemas3.28.1-1 ii libatk-bridge2.0-0 2.30.0-5 ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo21.16.0-4 ii libcanberra-gtk3-0 0.30-7 ii libcanberra0 0.30-7 ii libcroco30.6.12-3 ii libecal-1.2-19 3.30.5-1 ii libedataserver-1.2-233.30.5-1 ii libgcr-base-3-1 3.28.1-1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libgirepository-1.0-11.58.3-2 ii
Bug#948288: gnome-shell reproducibly crashes on boot, and the boot process gets stuck
Below you find the output of guest@T42-LAPTOP:~$ reportbug --template gnome-shell 1>>/tmp/reportbug_output.log 2>&1 copied and pasted from the file repotbug_output.log: Warning: no reportbug configuration found. Proceeding in novice mode. Detected character set: UTF-8 Please change your locale if this is incorrect.Using 'guest ' as your from address. Getting status for gnome-shell... Will send report to Debian (per lsb_release). Maintainer for gnome-shell is 'Debian GNOME Maintainers '. Looking up dependencies of gnome-shell... Getting status for related package gnome-session... Looking up 'depends' of related package gnome-session... Looking up 'suggests' of related package gnome-session... Getting status for related package gnome-settings-daemon... Looking up 'depends' of related package gnome-settings-daemon... Looking up 'recommends' of related package gnome-settings-daemon... Getting status for related package libgjs0g... Looking up 'depends' of related package libgjs0g... Getting status for related package libmutter-3-0... Looking up 'depends' of related package libmutter-3-0... Looking up status of additional packages... Getting changed configuration files...Rewriting subject to 'gnome-shell: none' Saving a backup of the report at /tmp/reportbug-gnome-shell-backup-20200130-3154-vovyhuqk Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: guest To: Debian Bug Tracking System Subject: gnome-shell: nonePackage: gnome-shell Version: 3.30.2-11~deb10u1 Severity: wishlistDear Maintainer,*** Reporter, please consider answering these questions, where appropriate What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead?*** End of the template - remove these template lines *** -- System Information: Debian Release: 10.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: i386 (i686)Kernel: Linux 4.19.0-6-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system)Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii evolution-data-server 3.30.5-1 ii gir1.2-accountsservice-1.0 0.6.45-2 ii gir1.2-atspi-2.0 2.30.0-7 ii gir1.2-freedesktop 1.58.3-2 ii gir1.2-gcr-3 3.28.1-1 ii gir1.2-gdesktopenums-3.0 3.28.1-1 ii gir1.2-gdm-1.0 3.30.2-3 ii gir1.2-geoclue-2.0 2.5.2-1 ii gir1.2-glib-2.0 1.58.3-2 ii gir1.2-gnomebluetooth-1.0 3.28.2-4~deb10u1 ii gir1.2-gnomedesktop-3.0 3.30.2.1-2 ii gir1.2-gtk-3.0 3.24.5-1 ii gir1.2-gweather-3.0 3.28.2-2 ii gir1.2-ibus-1.0 1.5.19-4+deb10u1 ii gir1.2-mutter-3 3.30.2-9~deb10u1 ii gir1.2-nm-1.0 1.14.6-2+deb10u1 ii gir1.2-nma-1.0 1.8.20-1.1 ii gir1.2-pango-1.0 1.42.4-7~deb10u1 ii gir1.2-polkit-1.0 0.105-25 ii gir1.2-rsvg-2.0 2.44.10-2.1 ii gir1.2-soup-2.4 2.64.2-2 ii gir1.2-upowerglib-1.0 0.99.10-1 ii gjs 1.54.3-1 ii gnome-backgrounds 3.30.0-1 ii gnome-settings-daemon 3.30.2-3 ii gnome-shell-common 3.30.2-11~deb10u1 ii gsettings-desktop-schemas 3.28.1-1 ii libatk-bridge2.0-0 2.30.0-5 ii libatk1.0-0 2.30.0-2 ii libc6 2.28-10 ii libcairo2 1.16.0-4 ii libcanberra-gtk3-0 0.30-7 ii libcanberra0 0.30-7 ii libcroco3 0.6.12-3 ii libecal-1.2-19 3.30.5-1 ii libedataserver-1.2-23 3.30.5-1 ii libgcr-base-3-1 3.28.1-1 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libgirepository-1.0-1 1.58.3-2 ii libgjs0g 1.54.3-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libglib2.0-bin 2.58.3-2+deb10u2 ii libgstreamer1.0-0 1.14.4-1 ii libgtk-3-0 3.24.5-1 ii libical3 3.0.4-3 ii libjson-glib-1.0-0 1.4.4-2 ii libmutter-3-0 3.30.2-9~deb10u1 ii libnm0 1.14.6-2+deb10u1 ii libpango-1.0-0 1.42.4-7~deb10u1 ii libpangocairo-1.0-0 1.42.4-7~deb10u1 ii libpolkit-agent-1-0 0.105-25 ii libpolkit-gobject-1-0 0.105-25 ii libpulse-mainloop-glib0 12.2-4+deb10u1 ii libpulse0 12.2-4+deb10u1 ii libsecret-1-0 0.18.7-1 ii libstartup-notification0 0.12-6 ii libsystemd0 241-7~deb10u2 ii libx11-6 2:1.6.7-1 ii libxfixes3 1:5.0.3-1 ii mutter 3.30.2-9~deb10u1 ii python3 3.7.3-1Versions of packages gnome-shell recommends: ii bolt 0.7-2 ii chrome-gnome-shell 10.1-5 ii gdm3 3.30.2-3 ii gkbd-capplet 3.26.1-1 ii gnome-control-center 1:3.30.3-2~deb10u1 ii gnome-user-docs 3.30.2-1 ii iio-sensor-proxy 2.4-2 ii switcheroo-control 1.2-2 ii unzip 6.0-23+deb10u1Versions of packages gnome-shell suggests: pn gir1.2-telepathyglib-0.12 pn gir1.2-telepathylogger-0.2 Versions of packages gnome-session depends on: ii gnome-session-bin 3.30.1-2 ii gnome-session-common 3.30.1-2 ii gnome-settings-daemon 3.30.2-3Versions of packages gnome-session suggests: ii desktop-base 10.0.2 ii gnome-keyring 3.28.2-5Versions of packages gnome-settings-daemon depends on: ii gnome-settings-daemon-common 3.30.2-3 ii
Bug#948288: Acknowledgement (gnome-shell reproducibly crashes on boot, and the boot process gets stuck)
Below you find is the dmesg output. [ 0.00] Linux version 4.19.0-6-686 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) [ 0.00] Disabled fast string operations [ 0.00] x86/fpu: x87 FPU will use FXSAVE [ 0.00] BIOS-provided physical RAM map: [ 0.00] BIOS-e820: [mem 0x-0x0009efff] usable [ 0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved [ 0.00] BIOS-e820: [mem 0x000d2000-0x000d3fff] reserved [ 0.00] BIOS-e820: [mem 0x000dc000-0x000f] reserved [ 0.00] BIOS-e820: [mem 0x0010-0x7ff5] usable [ 0.00] BIOS-e820: [mem 0x7ff6-0x7ff76fff] ACPI data [ 0.00] BIOS-e820: [mem 0x7ff77000-0x7ff78fff] ACPI NVS [ 0.00] BIOS-e820: [mem 0x7ff8-0x7fff] reserved [ 0.00] BIOS-e820: [mem 0xff80-0x] reserved [ 0.00] Notice: NX (Execute Disable) protection missing in CPU! [ 0.00] SMBIOS 2.3 present. [ 0.00] DMI: IBM 2373ZJD/2373ZJD, BIOS 1RETDRWW (3.23 ) 06/18/2007 [ 0.00] tsc: Fast TSC calibration failed [ 0.00] e820: update [mem 0x-0x0fff] usable ==> reserved [ 0.00] e820: remove [mem 0x000a-0x000f] usable [ 0.00] last_pfn = 0x7ff60 max_arch_pfn = 0x10 [ 0.00] MTRR default type: uncachable [ 0.00] MTRR fixed ranges enabled: [ 0.00] 0-9 write-back [ 0.00] A-B uncachable [ 0.00] C-C write-protect [ 0.00] D-DBFFF uncachable [ 0.00] DC000-D write-back [ 0.00] E-F write-protect [ 0.00] MTRR variable ranges enabled: [ 0.00] 0 base 0 mask F8000 write-back [ 0.00] 1 base 07FF8 mask 8 uncachable [ 0.00] 2 disabled [ 0.00] 3 disabled [ 0.00] 4 disabled [ 0.00] 5 disabled [ 0.00] 6 disabled [ 0.00] 7 disabled [ 0.00] x86/PAT: PAT not supported by CPU. [ 0.00] x86/PAT: Configuration [0-7]: WB WT UC- UC WB WT UC- UC [ 0.00] initial memory mapped: [mem 0x-0x1fff] [ 0.00] BRK [0x1faf7000, 0x1faf7fff] PGTABLE [ 0.00] RAMDISK: [mem 0x32681000-0x35337fff] [ 0.00] ACPI: Early table checksum verification disabled [ 0.00] ACPI: RSDP 0x000F6D70 24 (v02 IBM ) [ 0.00] ACPI: XSDT 0x7FF6A672 4C (v01 IBM TP-1R 3230 LTP ) [ 0.00] ACPI: FACP 0x7FF6A700 F4 (v03 IBM TP-1R 3230 IBM 0001) [ 0.00] ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/32 (20180810/tbfadt-569) [ 0.00] ACPI BIOS Warning (bug): Optional FADT field Gpe1Block has valid Address but zero Length: 0x102C/0x0 (20180810/tbfadt-624) [ 0.00] ACPI: DSDT 0x7FF6A8E7 00C530 (v01 IBM TP-1R 3230 MSFT 010E) [ 0.00] ACPI: FACS 0x7FF78000 40 [ 0.00] ACPI: FACS 0x7FF78000 40 [ 0.00] ACPI: SSDT 0x7FF6A8B4 33 (v01 IBM TP-1R 3230 MSFT 010E) [ 0.00] ACPI: ECDT 0x7FF76E17 52 (v01 IBM TP-1R 3230 IBM 0001) [ 0.00] ACPI: TCPA 0x7FF76E69 32 (v01 IBM TP-1R 3230 PTL 0001) [ 0.00] ACPI: BOOT 0x7FF76FD8 28 (v01 IBM TP-1R 3230 LTP 0001) [ 0.00] 1171MB HIGHMEM available. [ 0.00] 875MB LOWMEM available. [ 0.00] mapped low ram: 0 - 36bfe000 [ 0.00] low ram: 0 - 36bfe000 [ 0.00] BRK [0x1faf8000, 0x1faf8fff] PGTABLE [ 0.00] Zone ranges: [ 0.00] DMA [mem 0x1000-0x00ff] [ 0.00] Normal [mem 0x0100-0x36bfdfff] [ 0.00] HighMem [mem 0x36bfe000-0x7ff5] [ 0.00] Movable zone start for each node [ 0.00] Early memory node ranges [ 0.00] node 0: [mem 0x1000-0x0009efff] [ 0.00] node 0: [mem 0x0010-0x7ff5] [ 0.00] Initmem setup node 0 [mem 0x1000-0x7ff5] [ 0.00] On node 0 totalpages: 524030 [ 0.00] DMA zone: 40 pages used for memmap [ 0.00] DMA zone: 0 pages reserved [ 0.00] DMA zone: 3998 pages, LIFO batch:0 [ 0.00] Normal zone: 2150 pages used for memmap [ 0.00] Normal zone: 220158 pages, LIFO batch:63 [ 0.00] HighMem zone: 299874 pages, LIFO batch:63 [ 0.00] Using APIC driver default [ 0.00] ACPI: PM-Timer IO Port: 0x1008 [ 0.00] Local APIC disabled by BIOS -- you can enable it with "lapic" [ 0.00] APIC: disable apic facility [ 0.00] APIC: switched to apic NOOP [ 0.00] smpboot: Allowing 1 CPUs, 0 hotplug CPUs [ 0.00] PM: Registered nosave memory: [mem 0x-0x0fff] [ 0.00] PM: Registered nosave memory: [mem 0x0009f000-0x0009] [ 0.00] PM: Registered nosave memory: [mem 0x000a-0x000d1fff] [ 0.00] PM: Registered nosave memory: [mem 0x000d2000-0x000d3fff] [ 0.00] PM: Registered nosave memory:
Bug#932375: Re: Bug#932375: How to make UXterm use reverse colors automatically?
Thank you! The new title describes the issue pretty well. As for me personally, I'm more interested in a slightly different question of how to have white-on-black uxterm by default. (Naturally, one could hack /usr/bin/uxterm, but this is likely to break on the next package update).
Bug#932375: How to make UXterm use reverse colors automatically?
reassign 932375 mutter severity 932375 wishlist thanks Reassign reason: as suggested by Sven, the issue is apparently more related to the window/display manager rather than to UXTerm itself, cf. http://gitlab.gnome.org/GNOME/mutter/issues/677
Bug#932375: Re: Bug#932375: UXTerm: reversion of colors won't work
Do you run xterm on a different machine than your desktop? It's all on one and the same laptop for one and the same user. > As for > the startup files, I am not aware of any user-level user ones beyond .xinitrc, > ~/.Xresources and ~/.config/autostart/*desktop, and all of them seem to be > ignored in Wayland (though, you may prove me wrong). The first two are definitely ignored, the third ought to work, I think. For me, it doesn't (see my message from Sat, 20 Jul 2019 17:36:27 +0300). However, I don't use Gnome and the only Wayland experience I ever had> was with Weston. I never used Weston. Right now: $ echo $GDMSESSION gnome There will be nobody who tracks the issue if it remains assigned to xterm, so that point is rather moot. You could file a wishlist bug for mutter instead and link to the Gnome gitlab issue I gave you. I won't be able to write a *good* bug report or a wishlist issue for mutter, since it's not a user-level application that I interact with directly: I know nothing about mutter. However, I may reassign the current bug report there. 20.07.2019, 19:32, Sven Joachim On 2019-07-20 19:56 +0300, Md Ayquassar wrote: > So, would > > $ cat .Xdefaults > UXTerm*reverseVideo: true > > and a reboot be sufficient? Without rebooting, there is no effect so > far. That's strange, it should take effect whenever you launch a new uxterm. Do you run xterm on a different machine than your desktop? > As for > the startup files, I am not aware of any user-level user ones beyond .xinitrc, > ~/.Xresources and ~/.config/autostart/*desktop, and all of them seem to be > ignored in Wayland (though, you may prove me wrong). The first two are definitely ignored, the third ought to work, I think. However, I don't use Gnome and the only Wayland experience I ever had was with Weston. > As for closing the bug report, I see your point. Of course, if you are a Debian > person, you have all the rights to maintain the bug database as Debian would like > it. However, as of now the issue seems to be a wish for a useful piece of > functionality to be restored after exchanging one piece of software with another > one. So, I'd be happy to see the report marked as "wishlist" rather than closed, > simply to keep track that the issue is ongoing. There will be nobody who tracks the issue if it remains assigned to xterm, so that point is rather moot. You could file a wishlist bug for mutter instead and link to the Gnome gitlab issue I gave you. BTW, instead of reverseVideo you may want to set the Foreground and Background resources. Cheers, Sven
Bug#932375: Re: Bug#932375: UXTerm: reversion of colors won't work
So, would $ cat .Xdefaults UXTerm*reverseVideo: true and a reboot be sufficient? Without rebooting, there is no effect so far. As for the startup files, I am not aware of any user-level user ones beyond .xinitrc, ~/.Xresources and ~/.config/autostart/*desktop, and all of them seem to be ignored in Wayland (though, you may prove me wrong). As for closing the bug report, I see your point. Of course, if you are a Debian person, you have all the rights to maintain the bug database as Debian would like it. However, as of now the issue seems to be a wish for a useful piece of functionality to be restored after exchanging one piece of software with another one. So, I'd be happy to see the report marked as "wishlist" rather than closed, simply to keep track that the issue is ongoing.
Bug#932375: UXTerm: reversion of colors won't work
Nnow with more newlines for proper html formatting: The following doesn't help either: $ cat .config/autostart/source_Xresources.desktop [Desktop Entry] Type=Application Exec=xrdb -merge ~/.Xresources Hidden=false X-GNOME-Autostart-enabled=true Name=Source Xresources Comment=Source local .Xresources $ cat ~/.Xresources UXTerm*reverseVideo: true $ No possibility to autostart local scripts any more?
Bug#932375: UXTerm: reversion of colors won't work
The following doesn't help either: $ cat .config/autostart/source_Xresources.desktop [Desktop Entry]Type=Application Exec=xrdb -merge ~/.Xresources Hidden=false X-GNOME-Autostart-enabled=true Name=Source Xresources Comment=Source local .Xresources $ cat ~/.Xresources UXTerm*reverseVideo: true $ No possibility to autostart local scripts any more?
Bug#932375: RE: RE: Re: Bug#932375: UXTerm: reversion of colors won't work
I know about the -rv option. It's one-off, i.e., you have to provide it again and again. As for .xinitrc, I thought that wayland doesn't source it on startup. > > Anyway, having said all that, what's the "official" way to have the uxterm > > default colors *automatically* white-on-black now? > > well... it's not a bug in xterm, > but rather a deficiency in packaging or configuration. The command-line option -rv is the easy way to turn on reverse-video: -rv This option indicates that reverse video should be simulated by swapping the foreground and background colors. The corresponding resource name is reverseVideo. and if I wanted to make my .xinitrc more portable, I'd use -fg and -bg
Bug#932375: RE: RE: Re: Bug#932375: UXTerm: reversion of colors won't work
Now properly formatted such that the html output is ok. $ echo $XDG_SESSION_TYPE wayland $ echo $DESKTOP_SESSION gnome $ cat /etc/X11/default-display-manager /usr/sbin/gdm3 After taking a look at the reason why they dropped support for loading .Xresources by default (cf. https://bugzilla.redhat.com/show_bug.cgi?id=1225384), I decided to test whether that old reason is still valid. It is not: $ cat ~/.Xresources UXTerm*reverseVideo: true $ time xrdb -merge ~/.Xresources real 0m0,018s user 0m0,012s sys 0m0,006s This time spent is clearly below what a human would need to type in "xrdb -merge ~/.Xresources" manually and way below what a human is able to perceive. But complaining on this regression might belong to a different bug, I guess. Anyway, having said all that, what's the "official" way to have the uxterm default colors *automatically* white-on-black now?
Bug#932375: RE: Re: Bug#932375: UXTerm: reversion of colors won't work
$ echo $XDG_SESSION_TYPE wayland$ echo $DESKTOP_SESSION gnome$ cat /etc/X11/default-display-manager /usr/sbin/gdm3 After taking a look at the reason why they dropped support for loading .Xresources by default (cf. https://bugzilla.redhat.com/show_bug.cgi?id=1225384), I decided to test whether that old reason is still valid. It is not: $ cat ~/.Xresources UXTerm*reverseVideo: true$ time xrdb -merge ~/.Xresourcesreal 0m0,018s user 0m0,012s sys 0m0,006s This time spent is clearly below what a human would need to type in "xrdb -merge ~/.Xresources" manually and way below what a human is able to perceive. But complaining on this regression might belong to a different bug, I guess. Anyway, having said all that, what's the "official" way to have the uxterm default colors *automatically* white-on-black now?
Bug#932375: Re: Bug#932375: UXTerm: reversion of colors won't work
Do you use Gnome with Wayland? I don't know; probably it's still xorg after upgrading from Debian stretch. I'll double-check and post here in short.
Bug#932375: UXTerm: reversion of colors won't work
Package: xterm Version: 344-1 By default, the color of a uxterm is black foreground and white background. However, I'd like to have it reverse: white text on black background. To this end, I put UXTerm*reverseVideo: true into my ~/.Xresources, run xrdb ~/.Xresources, and reboot. I observe no change: it's still black on white as before. However, there should be a change, and some folks do observe it on other systems: https://superuser.com/questions/1461093/how-to-make-uxterm-white-on-black?noredirect=1#comment2203810_1461093 Any help? I run an up-to-date buster with kernel 4.19.0-5-amd64.
Bug#915570: Thunderbird: Sent mail stays in the draft folder
Package: thunderbird Version: 1:60.3.0-1~deb9u1 For several (all?) IMAP e-mail accounts of mine in Thunderbird, whenever I write a long mail and send it, the autosaved copies in the "Drafts" folder won't disappear. However, the expected behavior is that after sending an e-mail, all draft copies of it should disappear automatically. (A copy does appear also in the "Sent" folder; there is no issue with that.)
Bug#915070: wodim ignores -dummy
Package: wodim Version: 9:1.1.11-3+b2 Severity: critical Starting with a blank 4.7 Gb DVD-R in the optical drive "HL-DT-ST DVD+-RW GS30N", my_file.iso containing a freshly downloaded copy of Windows 10 (US English, x64), and issuing $ sudo wodim -v driver=mmc_cd_dvd dev=/dev/sg1 -dummy -dao speed=1 fs=100m driveropts=noburnfree -data my_file.iso twice, I discovered that the first dry run succeeded, but the second did not. Upon ejecting the disc, I saw a differently colored ring on the disc. So, wodim didn't turn off the laser completely and thus made the disc unusable. So, we can no more test wodim's features without destroying discs. In practical terms, this makes wodim a harmful program. I suggest removing it from Debian completely.
Bug#903293: Re: Bug#903293: Please update elsarticle
Thank you, Norbert. Notice that this bugreport intentionally doesn't insist on a particular version to be included into Debian, leavong the choice to you: - 2.0 (from http://support.river-valley.com/wiki/index.php?title=Elsarticle.cls) is mildly buggy (as usual) and very stable. I did try it out. - 3.0 (from CTAN), which I never tried out.
Bug#903293: Please update elsarticle
Package: texlive-publishers Version: 2016.20170123-5 Severity: wishlist Please update elsarticle to a newer version. The elsarticle version shipped with Debian stable (and, to the best of my knowledge, 2018.20180505-1 from Debian testing), is 1.2.0 from 2009. In the meantime, I saw version 2.0 from 2012, still available from rivervalley. The current version is 3.0 from 2018 and is available from CTAN; moreover, elsevier links to it. This update not urgent, but is clearly necessary. Thanks in advance.
Bug#509574: stable-proposed-updates erwartet, aber stretch-proposed-updates bekommen
severity 509574 normalthanks Similar problem for me here: the lines deb http://httpredir.debian.org/debian stable-proposed-updates main non-free contrib deb-src http://httpredir.debian.org/debian stable-proposed-updates main non-free contrib in /etc/apt/sources.list lead to W: Konflikt bei Distribution: http://cdn-fastly.deb.debian.org/debian stable-proposed-updates InRelease (stable-proposed-updates erwartet, aber stretch-proposed-updates bekommen) upon running "aptitude update". In different disguises, this problem exists for years.
