Your message dated Sat, 22 Nov 2025 16:43:23 -0500 with message-id <caaajcmydjeek6fftrto8wfxno9rjxvpq4-h7x1cm7t6nlks...@mail.gmail.com> and subject line closing old gnome-shell bugs has caused the Debian Bug report #815015, regarding gnome-shell crashes after moving 2048-qt to other screen 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 [email protected] immediately.) -- 815015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815015 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gnome-shell Version: 3.18.1-1 Severity: normal Dear Maintainer, I am using gnome-shell with two screen configuration. So I installed 2048-qt, run it and wanted to move this window to my second screen. After that all gui froze for a couple of seconds and 2048-qt came to first screen. When I repeated this steps, I got "Oh no, something gone wrong!" screen and logout. Here is a "coredumpctl dump" of gnome-shell process: ecko@megapeka:~$ coredumpctl dump 14706 PID: 14706 (gnome-shell) UID: 1000 (ecko) GID: 1000 (ecko) Signal: 5 (TRAP) Timestamp: Ср 2016-02-17 22:06:30 MSK (1min 50s ago) Command Line: /usr/bin/gnome-shell Executable: /usr/bin/gnome-shell Control Group: /user.slice/user-1000.slice/session-19.scope Unit: session-19.scope Slice: user-1000.slice Session: 19 Owner UID: 1000 (ecko) Boot ID: ee9b2006e4574c448aa599a4801ddee0 Machine ID: 50332dd2fce9449cb1add1571d159a99 Hostname: megapeka Coredump: /var/lib/systemd/coredump/core.gnome- shell.1000.ee9b2006e4574c448aa599a4801ddee0.14706.1455735990000000.xz Message: Process 14706 (gnome-shell) of user 1000 dumped core. Stack trace of thread 14706: #0 0x00007fc2c004287b g_logv (libglib-2.0.so.0) #1 0x00007fc2c00429ef g_log (libglib-2.0.so.0) #2 0x00007fc2bccd2108 n/a (libgdk-3.so.0) #3 0x00007fc2bccdd349 n/a (libgdk-3.so.0) #4 0x00007fc2bcf9246d _XError (libX11.so.6) #5 0x00007fc2bcf8f3a7 n/a (libX11.so.6) #6 0x00007fc2bcf8f465 n/a (libX11.so.6) #7 0x00007fc2bcf90420 _XReply (libX11.so.6) #8 0x00007fc2bcf8bcad XSync (libX11.so.6) #9 0x00007fc2c1a1a0df meta_prop_get_values (libmutter.so.0) #10 0x00007fc2c1a133ae meta_window_reload_property_from_xwindow (libmutter.so.0) #11 0x00007fc2c1a1790a process_property_notify (libmutter.so.0) #12 0x00007fc2c1a0d14b handle_other_xevent (libmutter.so.0) #13 0x00007fc2c1a0d79b meta_display_handle_xevent (libmutter.so.0) #14 0x00007fc2bccd7cb1 n/a (libgdk-3.so.0) #15 0x00007fc2bccd828f n/a (libgdk-3.so.0) #16 0x00007fc2bccaa2a9 gdk_display_get_event (libgdk-3.so.0) #17 0x00007fc2bccd7d32 n/a (libgdk-3.so.0) #18 0x00007fc2c003bfd7 g_main_context_dispatch (libglib-2.0.so.0) #19 0x00007fc2c003c230 n/a (libglib-2.0.so.0) #20 0x00007fc2c003c552 g_main_loop_run (libglib-2.0.so.0) #21 0x00007fc2c19eeafc meta_run (libmutter.so.0) #22 0x00000000004021a7 main (gnome-shell) #23 0x00007fc2bfa51870 __libc_start_main (libc.so.6) #24 0x00000000004022d4 _start (gnome-shell) Stack trace of thread 14719: #0 0x00007fc2bfb10b6d poll (libc.so.6) #1 0x00007fc2c003c1cc n/a (libglib-2.0.so.0) #2 0x00007fc2c003c552 g_main_loop_run (libglib-2.0.so.0) #3 0x00007fc2c0841396 n/a (libgio-2.0.so.0) #4 0x00007fc2c00629c5 n/a (libglib-2.0.so.0) #5 0x00007fc2bfddc284 start_thread (libpthread.so.0) #6 0x00007fc2bfb19a4d __clone (libc.so.6) Stack trace of thread 14712: #0 0x00007fc2bfb10b6d poll (libc.so.6) #1 0x00007fc2c003c1cc n/a (libglib-2.0.so.0) #2 0x00007fc2c003c2dc g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fc2c003c319 n/a (libglib-2.0.so.0) #4 0x00007fc2c00629c5 n/a (libglib-2.0.so.0) #5 0x00007fc2bfddc284 start_thread (libpthread.so.0) #6 0x00007fc2bfb19a4d __clone (libc.so.6) Stack trace of thread 14723: #0 0x00007fc2bfb10b6d poll (libc.so.6) #1 0x00007fc2bbeb5831 n/a (libpulse.so.0) #2 0x00007fc2bbea6e51 pa_mainloop_poll (libpulse.so.0) #3 0x00007fc2bbea74ee pa_mainloop_iterate (libpulse.so.0) #4 0x00007fc2bbea75a0 pa_mainloop_run (libpulse.so.0) #5 0x00007fc2bbeb57c6 n/a (libpulse.so.0) #6 0x00007fc2b20cc038 n/a (libpulsecommon-7.1.so) #7 0x00007fc2bfddc284 start_thread (libpthread.so.0) #8 0x00007fc2bfb19a4d __clone (libc.so.6) Stack trace of thread 14724: #0 0x00007fc2bfde18cf pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007fc2b1641d10 PR_WaitCondVar (libnspr4.so) #2 0x00007fc2bb899f0e n/a (libmozjs-24.so.0) #3 0x00007fc2b1647678 n/a (libnspr4.so) #4 0x00007fc2bfddc284 start_thread (libpthread.so.0) #5 0x00007fc2bfb19a4d __clone (libc.so.6) Stack trace of thread 14725: #0 0x00007fc2bfde18cf pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007fc2b1641d10 PR_WaitCondVar (libnspr4.so) #2 0x00007fc2bb9115ce n/a (libmozjs-24.so.0) #3 0x00007fc2b1647678 n/a (libnspr4.so) #4 0x00007fc2bfddc284 start_thread (libpthread.so.0) #5 0x00007fc2bfb19a4d __clone (libc.so.6) Stack trace of thread 17392: #0 0x00007fc2bfb15759 syscall (libc.so.6) #1 0x00007fc2c0080b1a g_cond_wait_until (libglib-2.0.so.0) #2 0x00007fc2c0010a19 n/a (libglib-2.0.so.0) #3 0x00007fc2c001103b g_async_queue_timeout_pop (libglib-2.0.so.0) #4 0x00007fc2c006341a n/a (libglib-2.0.so.0) #5 0x00007fc2c00629c5 n/a (libglib-2.0.so.0) #6 0x00007fc2bfddc284 start_thread (libpthread.so.0) #7 0x00007fc2bfb19a4d __clone (libc.so.6) Stack trace of thread 14721: #0 0x00007fc2bfb10b6d poll (libc.so.6) #1 0x00007fc2c003c1cc n/a (libglib-2.0.so.0) #2 0x00007fc2c003c2dc g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fc2a84d028d n/a (libdconfsettings.so) #4 0x00007fc2c00629c5 n/a (libglib-2.0.so.0) #5 0x00007fc2bfddc284 start_thread (libpthread.so.0) #6 0x00007fc2bfb19a4d __clone (libc.so.6) Refusing to dump core to tty. *** 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: stretch/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnome-shell depends on: ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2 ii evolution-data-server 3.18.3-1 ii gir1.2-accountsservice-1.0 0.6.40-3 ii gir1.2-atspi-2.0 2.18.3-4 ii gir1.2-caribou-1.0 0.4.19-1 ii gir1.2-clutter-1.0 1.24.2-1 ii gir1.2-freedesktop 1.46.0-3 ii gir1.2-gcr-3 3.18.0-1 ii gir1.2-gdesktopenums-3.0 3.18.1-1 ii gir1.2-gdm3 3.18.0-2 ii gir1.2-gkbd-3.0 3.6.0-1 ii gir1.2-glib-2.0 1.46.0-3 ii gir1.2-gnomebluetooth-1.0 3.18.2-1 ii gir1.2-gnomedesktop-3.0 3.18.2-1 ii gir1.2-gtk-3.0 3.18.7-1 ii gir1.2-gweather-3.0 3.18.1-1 ii gir1.2-ibus-1.0 1.5.11-1 ii gir1.2-mutter-3.0 3.18.2-1 ii gir1.2-networkmanager-1.0 1.1.90-6 ii gir1.2-nmgtk-1.0 1.1.90-3 ii gir1.2-pango-1.0 1.38.1-1 ii gir1.2-polkit-1.0 0.105-14.1 ii gir1.2-soup-2.4 2.52.2-1 ii gir1.2-telepathyglib-0.12 0.24.1-1.1 ii gir1.2-telepathylogger-0.2 0.8.2-1 ii gir1.2-upowerglib-1.0 0.99.3-1+b3 ii gjs 1.43.3-2 ii gnome-backgrounds 3.18.0-1 ii gnome-icon-theme-symbolic 3.12.0-1 ii gnome-settings-daemon 3.18.2-1 ii gnome-shell-common 3.18.1-1 ii gsettings-desktop-schemas 3.18.1-1 ii libatk-bridge2.0-0 2.18.1-1 ii libatk1.0-0 2.18.0-1 ii libc6 2.21-8 ii libcairo2 1.14.6-1 ii libcanberra-gtk3-0 0.30-2.1 ii libcanberra0 0.30-2.1 ii libclutter-1.0-0 1.24.2-1 ii libcogl-pango20 1.22.0-2 ii libcogl20 1.22.0-2 ii libcroco3 0.6.11-1 ii libdbus-glib-1-2 0.106-1 ii libecal-1.2-19 3.18.3-1 ii libedataserver-1.2-21 3.18.3-1 ii libgcr-base-3-1 3.18.0-1 ii libgdk-pixbuf2.0-0 2.32.3-1.2 ii libgirepository-1.0-1 1.46.0-3 ii libgjs0e [libgjs0-libmozjs-24-0] 1.43.3-2 ii libglib2.0-0 2.46.2-3 ii libgstreamer1.0-0 1.6.3-1 ii libgtk-3-0 3.18.7-1 ii libical1a 1.0.1-0.1 ii libjson-glib-1.0-0 1.0.4-2 ii libmozjs-24-0 24.2.0-3 ii libmutter0g 3.18.2-1 ii libnm-glib4 1.1.90-6 ii libnm-util2 1.1.90-6 ii libpango-1.0-0 1.38.1-1 ii libpangocairo-1.0-0 1.38.1-1 ii libpolkit-agent-1-0 0.105-14.1 ii libpolkit-gobject-1-0 0.105-14.1 ii libpulse-mainloop-glib0 7.1-2 ii libpulse0 7.1-2 ii libsecret-1-0 0.18.3-1 ii libstartup-notification0 0.12-4 ii libsystemd0 228-6 ii libtelepathy-glib0 0.24.1-1.1 ii libx11-6 2:1.6.3-1 ii libxfixes3 1:5.0.1-2+b2 ii mutter 3.18.2-1 ii python3 3.5.1-1 ii telepathy-mission-control-5 1:5.16.3-2 Versions of packages gnome-shell recommends: ii gdm3 3.18.0-2 ii gkbd-capplet 3.6.0-1 ii gnome-contacts 3.18.1-1 ii gnome-control-center 1:3.18.2-1 ii gnome-themes-standard-data 3.18.0-2 ii gnome-user-guide 3.18.1-1 ii iio-sensor-proxy 1.1-1 ii unzip 6.0-20 gnome-shell suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---There have been many changes to Debian since this bug was originally reported. If you are still experiencing this issue with Debian 13 (or with Debian 12 or Testing or Unstable), please report a new bug. Thank you, Jeremy Bích
--- End Message ---
