Bug#934445: engrampa: random crashes with core dump
Package: engrampa Version: 1.22.1-1 Severity: important Dear Maintainer, I am experiencing some crashes with core dump regarding engrampa for sometime. $ coredumpctl info 3847 PID: 3847 (engrampa) UID: 1000 (adam) GID: 1000 (adam) Signal: 11 (SEGV) Timestamp: Sat 2019-08-10 23:16:00 CST (10h ago) Command Line: engrampa /home/adam/Downloads/pkg/fzbwksjt_downcc.com.zip Executable: /usr/bin/engrampa Control Group: /user.slice/user-1000.slice/session-2.scope Unit: session-2.scope Slice: user-1000.slice Session: 2 Owner UID: 1000 (adam) Boot ID: fe9a729066a445b8a9b18c1d08fc80f6 Machine ID: 647a0bfe1e794d9db74e8b9202aab665 Hostname: MyDebian Storage: /var/lib/systemd/coredump/core.engrampa.1000.fe9a729066a445b8a9b18c1d08fc80f6.3847.156545016000.lz4 Message: Process 3847 (engrampa) of user 1000 dumped core. Stack trace of thread 3847: #0 0x7f4638d2e300 gdk_window_is_destroyed (libgdk-3.so.0) #1 0x7f463901d930 gtk_get_event_widget (libgtk-3.so.0) #2 0x7f463915b0ac n/a (libgtk-3.so.0) #3 0x7f463901c116 n/a (libgtk-3.so.0) #4 0x55fd7cbf49eb n/a (engrampa) #5 0x7f46391af55b n/a (libgtk-3.so.0) #6 0x7f46388d0e8d g_closure_invoke (libgobject-2.0.so.0) #7 0x7f46388e4555 n/a (libgobject-2.0.so.0) #8 0x7f46388ecb9b g_signal_emit_valist (libgobject-2.0.so.0) #9 0x7f46388edb6f g_signal_emit (libgobject-2.0.so.0) #10 0x7f463915b144 n/a (libgtk-3.so.0) #11 0x7f463901c116 n/a (libgtk-3.so.0) #12 0x7f463901e23b gtk_main_do_event (libgtk-3.so.0) #13 0x7f4638d1d645 n/a (libgdk-3.so.0) #14 0x7f4638d4f6d2 n/a (libgdk-3.so.0) #15 0x7f46387e89ee g_main_context_dispatch (libglib-2.0.so.0) #16 0x7f46387e8c88 n/a (libglib-2.0.so.0) #17 0x7f46387e8d1c g_main_context_iteration (libglib-2.0.so.0) #18 0x7f46389eca0d g_application_run (libgio-2.0.so.0) #19 0x55fd7cbe93ae n/a (engrampa) #20 0x7f463843109b __libc_start_main (libc.so.6) #21 0x55fd7cbe943a n/a (engrampa) Stack trace of thread 3849: #0 0x7f46384fb819 __GI___poll (libc.so.6) #1 0x7f46387e8bf6 n/a (libglib-2.0.so.0) #2 0x7f46387e8d1c g_main_context_iteration (libglib-2.0.so.0) #3 0x7f46387e8d61 n/a (libglib-2.0.so.0) #4 0x7f463881189d n/a (libglib-2.0.so.0) #5 0x7f46385d5fa3 start_thread (libpthread.so.0) #6 0x7f46385064cf __clone (libc.so.6) Stack trace of thread 3852: #0 0x7f4638500f59 syscall (libc.so.6) #1 0x7f4638833a7f g_cond_wait_until (libglib-2.0.so.0) #2 0x7f46387ba0c1 n/a (libglib-2.0.so.0) #3 0x7f46387ba681 g_async_queue_timeout_pop (libglib-2.0.so.0) #4 0x7f4638812301 n/a (libglib-2.0.so.0) #5 0x7f463881189d n/a (libglib-2.0.so.0) #6 0x7f46385d5fa3 start_thread (libpthread.so.0) #7 0x7f46385064cf __clone (libc.so.6) Stack trace of thread 3850: #0 0x7f46384fb819 __GI___poll (libc.so.6) #1 0x7f46387e8bf6 n/a (libglib-2.0.so.0) #2 0x7f46387e8f82 g_main_loop_run (libglib-2.0.so.0) #3 0x7f4638a26e46 n/a (libgio-2.0.so.0) #4 0x7f463881189d n/a (libglib-2.0.so.0) #5 0x7f46385d5fa3 start_thread (libpthread.so.0) #6 0x7f46385064cf __clone (libc.so.6) Stack trace of thread 3851: #0 0x7f46384fb819 __GI___poll (libc.so.6) #1 0x7f46387e8bf6 n/a (libglib-2.0.so.0) #2 0x7f46387e8d1c g_main_context_iteration (libglib-2.0.so.0) #3 0x7f4634c48ffd n/a (libdconfsettings.so) #4 0x7f463881189d n/a (libglib-2.0.so.0) #5 0x7f46385d5fa3 start_thread (libpthread.so.0) #6 0x7f46385064cf __clone (libc.so.6) I installed libgtk-3-0-dbgsym dconf-gsettings-backend-dbgsym libglib2.0-0-dbgsym libc6-dbg engrampa-dbgsym and did a backtrace: $ gdb -q /usr/bin/engrampa --core /tmp/core.engrampa Reading symbols from /usr/bin/engrampa... Reading symbols from /usr/lib/debug/.build- id/47/9c8f5a98914960e3c5d1d20c3d32e05575dd7e.debug... [New LWP 3847] [New LWP 3849] [New LWP 3852] [New LWP 3850] [New LWP 3851] [Thread debugging using libthread_db enabled] Using
Bug#934105: xfdesktop4: xfdesktop crashes and coredump when upgrading
Package: xfdesktop4 Version: 4.12.4-2 Severity: important Dear Maintainer, * What led up to the situation? It's been some time that I experienced coredumps of xfdesktop and xfce4-panel when upgrading. * What exactly did you do (or not do) that was effective (or ineffective)? Using sid, I usually run apt update and upgrade daily to keep system up-to- date. But I've noticed that when upgrading is running, seems like usually when post-install phases, desktop wallpaper and xfce4-panel flash and disappear and then appear again. I first thought they were restarting due to some upgrade packages related to them. But later I found they were indeed xfdesktop and xfce4-panel crashes and I saw coredump files saved, weird thing is that this happens even when the packages upgrading are not related to the desktop itself. For example, today I only got google-chrome-stable updated and both xfdesktop and xfce4-panel crashed and coredumped. Below is what I got from journalctl -xe when xfdesktop crashed during google- chrome-stable upgrade. Aug 07 09:53:11 MyDebian systemd-coredump[5406]: Process 5159 (xfdesktop) of user 1000 dumped core. Stack trace of thread 5159: #0 0x7fc31ce4975a g_slice_alloc (libglib-2.0.so.0) #1 0x7fc31ce27316 g_list_prepend (libglib-2.0.so.0) #2 0x7fc31daf4b87 n/a (libwnck-1.so.22) #3 0x7fc31daf5b44 n/a (libwnck-1.so.22) #4 0x7fc31ce2b898 g_main_context_dispatch (libglib-2.0.so.0) #5 0x7fc31ce2bc88 n/a (libglib-2.0.so.0) #6 0x7fc31ce2bf82 g_main_loop_run (libglib-2.0.so.0) #7 0x7fc31d75d8e7 gtk_main (libgtk-x11-2.0.so.0) #8 0x55a665e6fc6c n/a (xfdesktop) #9 0x55a665e700a6 n/a (xfdesktop) #10 0x7fc31ce28263 n/a (libglib-2.0.so.0) #11 0x7fc31ce28c9e n/a (libglib-2.0.so.0) #12 0x7fc31ce2b928 g_main_context_dispatch (libglib-2.0.so.0) #13 0x7fc31ce2bc88 n/a (libglib-2.0.so.0) #14 0x7fc31ce2bd1c g_main_context_iteration (libglib-2.0.so.0) #15 0x7fc31d0aca0d g_application_run (libgio-2.0.so.0) #16 0x55a665e64fad main (xfdesktop) #17 0x7fc31cc1f09b __libc_start_main (libc.so.6) #18 0x55a665e64fea _start (xfdesktop) Stack trace of thread 5162: #0 0x7fc31cce9819 __poll (libc.so.6) #1 0x7fc31ce2bbf6 n/a (libglib-2.0.so.0) #2 0x7fc31ce2bd1c g_main_context_iteration (libglib-2.0.so.0) #3 0x7fc31ce2bd61 n/a (libglib-2.0.so.0) #4 0x7fc31ce5489d n/a (libglib-2.0.so.0) #5 0x7fc31cdc3fa3 start_thread (libpthread.so.0) #6 0x7fc31ccf44cf __clone (libc.so.6) Stack trace of thread 5163: #0 0x7fc31cce9819 __poll (libc.so.6) #1 0x7fc31ce2bbf6 n/a (libglib-2.0.so.0) #2 0x7fc31ce2bf82 g_main_loop_run (libglib-2.0.so.0) #3 0x7fc31d0e6e46 n/a (libgio-2.0.so.0) #4 0x7fc31ce5489d n/a (libglib-2.0.so.0) #5 0x7fc31cdc3fa3 start_thread (libpthread.so.0) #6 0x7fc31ccf44cf __clone (libc.so.6) -- Subject: Process 5159 (xfdesktop) dumped core -- Defined-By: systemd -- Support: https://www.debian.org/support -- Documentation: man:core(5) -- -- Process 5159 (xfdesktop) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. Aug 07 09:53:11 MyDebian
Bug#926328: network-manager-gnome: nm-applet crashes with a coredump when try to create a new WiFi network
Package: network-manager-gnome Version: 1.8.20-1 Severity: normal Dear Maintainer, I am experiencing a crash every time I try to create a hot-spot WiFi using nm- applet menu. The steps were: 1. Click nm-applet(I am using Xfce4 and xfce-panel, BTW), in the drop down menu, click Creat New WiFi Network... 2. In the pop up window, fill in Network Name and Key. 3. In the WiFi security drop down menu, select None or WEP 128bit Passphrase or WEP 40/128, doesn't matter, the result will be the same (a crash). 4. Click Create. And nm-applet will disappear from the panel Notification Area. In journalctl you'll see: https://cfp.vim-cn.com/cbfwN And there will be a new coredump in coredumpctl list like: Wed 2019-04-03 23:06:44 CST 19318 1000 1000 6 present /usr/bin/nm- applet coredumpctl info shows this: https://cfp.vim-cn.com/cbfwP -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=zh_CN.utf8, LC_CTYPE=zh_CN.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=zh_CN.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages network-manager-gnome depends on: ii dbus-user-session [default-dbus-session-bus] 1.12.12-1 ii dbus-x11 [dbus-session-bus] 1.12.12-1 ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii libatk1.0-0 2.30.0-2 ii libayatana-appindicator3-10.5.3-4 ii libc6 2.28-8 ii libcairo2 1.16.0-4 ii libgdk-pixbuf2.0-02.38.1+dfsg-1 ii libglib2.0-0 2.58.3-1 ii libgtk-3-03.24.5-1 ii libjansson4 2.12-1 ii libmm-glib0 1.10.0-1 ii libnm01.14.6-2 ii libnma0 1.8.20-1 ii libnotify40.7.7-4 ii libpango-1.0-01.42.4-6 ii libpangocairo-1.0-0 1.42.4-6 ii libsecret-1-0 0.18.7-1 ii libselinux1 2.8-1+b1 ii network-manager 1.14.6-2 ii policykit-1-gnome [polkit-1-auth-agent] 0.105-7 Versions of packages network-manager-gnome recommends: ii gnome-keyring3.28.2-5 ii iso-codes4.2-1 ii mobile-broadband-provider-info 20170903-1 ii notification-daemon 3.20.0-4 ii xfce4-notifyd [notification-daemon] 0.4.3-1 Versions of packages network-manager-gnome suggests: pn network-manager-openconnect-gnome pn network-manager-openvpn-gnome pn network-manager-pptp-gnome pn network-manager-vpnc-gnome -- no debconf information
Bug#906745: libreoffice-calc: LibreOffice-Calc takes all available memory and freezes system when open a file
Package: libreoffice-calc Version: 1:6.1.0-1 Severity: important Dear Maintainer, LibreOffice-Calc just became extremely unstable lately. When I opened a regular csv file with about 200~300 rows x 5~10 columns, the dialogue popped out to let me choose the proper separator, which in my case was comma. Right after I clicked OK to open the file, LibreOffice-Calc took all available memory and soon froze the whole system. The whole process happened really fast, typically in less than 10 sec I think. When desktop was forzen, keyboard and touchpad failed to work anymore or worked with a really long lag(more than 20 sec maybe). Ctrl + Alt + F2 to switch to tty would hang on a black screen and tty login prompt never showed up. Only thing I could do was to long press power button to restart, or SysRq method worked last time I tried. Things I've tried: - Open a different file. I have several csv files with comma as separator and all about 200～300 rows x 5~10 columns. Files cotents are similar and definitely normal. - Open files by just double clicking the file, or open LibreOffice -> LibreOffice Calc -> open file, or open LbreOffice Calc -> open file. - sudo apt purge --autoremove libreoffice, then find ~ -iname "*libreoffice*" and remove all file, then remove ~/.config/libreoffice or any possible in ~ that could be related to LibreOffice. Then sudo apt install libreoffice again to get a fresh start. And I didn't change any options away from from default values. But all these tests were in vain. LibreOffice Calc just forze my desktop again an hour ago. I've also noticed that the freeze does not happen every time I use it, even if it's the same files I am opening. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libreoffice-calc depends on: ii coinor-libcbc3 2.9.9+repack1-1 ii coinor-libcoinmp1v51.8.3-2 ii coinor-libcoinutils3v5 2.10.14+repack1-1 ii libatlas3-base [liblapack.so.3]3.10.3-7+b1 ii libblas3 [libblas.so.3]3.8.0-1+b1 ii libboost-filesystem1.62.0 1.62.0+dfsg-8 ii libboost-iostreams1.62.0 1.62.0+dfsg-8 ii libbz2-1.0 1.0.6-9 ii libc6 2.27-5 ii libetonyek-0.1-1 0.1.8-1 ii libgcc11:8.2.0-4 ii libicu60 60.2-6 ii liblapack3 [liblapack.so.3]3.8.0-1+b1 ii liblcms2-2 2.9-2 ii libmwaw-0.3-3 0.3.14-1 ii libodfgen-0.1-10.1.7-1 ii libopenblas-base [liblapack.so.3] 0.3.2+ds-1.1~1patchTLS ii liborcus-0.13-00.13.4-6 ii libreoffice-base-core 1:6.1.0-1 ii libreoffice-core 1:6.1.0-1 pn librevenge-0.0-0 ii libstaroffice-0.0-00.0.6-1 ii libstdc++6 8.2.0-4 ii libwps-0.4-4 0.4.10-1 ii libxml22.9.4+dfsg1-7+b1 ii lp-solve 5.5.0.15-4+b1 ii uno-libs3 6.1.0-1 ii ure6.1.0-1 ii zlib1g 1:1.2.11.dfsg-1 libreoffice-calc recommends no packages. Versions of packages libreoffice-calc suggests: pn ocl-icd-libopencl1 Versions of packages libreoffice-core depends on: ii fontconfig2.13.0-5 ii fonts-opensymbol 2:102.10+LibO6.1.0-1 ii libboost-date-time1.62.0 1.62.0+dfsg-8 ii libboost-locale1.62.0 1.62.0+dfsg-8 ii libc6 2.27-5 ii libcairo2 1.15.10-3 ii libclucene-contribs1v52.3.3.4+dfsg-1 ii libclucene-core1v52.3.3.4+dfsg-1 ii libcmis-0.5-5v5 0.5.1+git20160603-3+b1 ii libcups2 2.2.8-5 ii libcurl3-gnutls 7.61.0-1 ii libdbus-1-3 1.12.10-1 ii libdbus-glib-1-2 0.110-3 ii libdconf1 0.28.0-2 ii libeot0 0.01-5 ii libepoxy0 1.4.3-1 ii libexpat1 2.2.6-1 ii libexttextcat-2.0-0 3.4.5-1 ii libfontconfig12.13.0-5 ii libfreetype6 2.8.1-2 ii libgcc1 1:8.2.0-4 ii libglib2.0-0 2.56.1-2 ii libgpgmepp6 1.11.1-1 ii libgraphite2-31.3.11-2 ii libharfbuzz-icu0 1.8.8-2 ii libharfbuzz0b 1.8.8-2 ii libhunspell-1.6-0 1.6.2-1+b1 pn libhyphen0 ii libice6 2:1.0.9-2 ii libicu60
Bug#904544: gimp failed to launch from menu entry or terminal command
Package: gimp Version: 2.10.2-1 Severity: important Dear Maintainer, I don't know how long it has been like this, maybe a monthor so. GIMP just won't launch for me. When I click GIMP launcher from menu entry, nothing happens. When I type gimp in a terminal, the cmd just hangs there and nothing happens, there isn't anything echoing back even when I use --verbose option. When I Ctrl-C to stop it, I get something like: 11669 segmentation fault (core dumped) gimp Here is the output of coredumpctl info -1 after the segment fault: https://cfp.vim-cn.com/cbfkp *** 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: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gimp depends on: ii gimp-data2.10.2-1 ii libaa1 1.4p5-44+b2 ii libbabl-0.1-01:0.1.54-dmo1 ii libbz2-1.0 1.0.6-8.1 ii libc62.27-5 ii libcairo21.15.10-3 ii libfontconfig1 2.13.0-5 ii libfreetype6 2.8.1-2 ii libgcc1 1:8.1.0-12 ii libgdk-pixbuf2.0-0 2.36.11-2 ii libgegl-0.4-01:0.4.6-dmo1 ii libgexiv2-2 0.10.8-1 ii libgimp2.0 2.10.2-1 ii libglib2.0-0 2.56.1-2 ii libgs9 9.22~dfsg-2.1 ii libgtk2.0-0 2.24.32-2 ii libgudev-1.0-0 232-2 ii libharfbuzz0b1.8.4-1 ii libheif1 1.3.2-1 ii libilmbase23 2.2.1-2 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-2 ii liblzma5 5.2.2-1.3 pn libmng1 ii libmypaint-1.3-0 1:1.3.0-dmo6 ii libopenexr23 2.2.1-4 ii libopenjp2-7 2.3.0-1 ii libpango-1.0-0 1.42.1-2 ii libpangocairo-1.0-0 1.42.1-2 ii libpangoft2-1.0-01.42.1-2 ii libpng16-16 1.6.34-2 ii libpoppler-glib8 0.63.0-2 ii librsvg2-2 2.40.20-2 ii libstdc++6 8.1.0-12 ii libtiff5 4.0.9-6 ii libwebp6 0.6.1-2 ii libwebpdemux20.6.1-2 ii libwebpmux3 0.6.1-2 ii libwmf0.2-7 0.2.8.4-12 ii libx11-6 2:1.6.5-1 ii libxcursor1 1:1.1.15-1 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxmu6 2:1.1.2-2 ii libxpm4 1:3.5.12-1 ii xdg-utils1.1.3-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages gimp recommends: ii ghostscript 9.22~dfsg-2.1 Versions of packages gimp suggests: pn gimp-data-extras pn gimp-help-en | gimp-help pn gimp-python ii gvfs-backends 1.36.1-1+b1 ii libasound21.1.6-1 -- no debconf information
Bug#901806: gvfs: error message and timeout popup after remove USB flash drive
Package: gvfs Version: 1.36.1-1+b1 Severity: important Dear Maintainer, Every time I try to remove a USB flash drive from Thunar by right clicking and select 'Eject' I get a notification saying that data is writing and wait. Minutes after that a popup window appears saying timeout. I tried 'journalctl -e' and I'll see this: Jun 18 22:44:43 MyDebian upowerd[1426]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 Jun 18 22:44:43 MyDebian udisksd[653]: Powered off /dev/sdc - successfully wrote to sysfs path /sys/devices/pci:00/:00:14.0/usb2/2-2/remove Jun 18 22:44:43 MyDebian gvfs-udisks2-vo[1450]: gvfs_udisks2_drive_stop_finish: assertion 'g_async_result_is_tagged (result, gvfs_udisks2_drive_stop)' failed Jun 18 22:44:43 MyDebian gvfs-udisks2-vo[1450]: g_dbus_method_invocation_return_gerror: assertion 'error != NULL' failed Jun 18 22:44:43 MyDebian gvfs-udisks2-vo[1450]: g_error_free: assertion 'error != NULL' failed Jun 18 22:44:43 MyDebian upowerd[1426]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb2/2-2 Jun 18 22:44:43 MyDebian kernel: usb 2-2: USB disconnect, device number 2 I found the same bug report here: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1762595 and the fix here:https://gitlab.gnome.org/GNOME/gvfs/commit/38831e4e. But I checked the source code:https://salsa.debian.org/gnome-team/gvfs/blob/debian/master/monitor/udisks2/gvfsudisks2mount.c and seemingly the fix has not been introduced. -- System Information: Debian Release: buster/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gvfs depends on: ii gvfs-common 1.36.1-1 ii gvfs-daemons 1.36.1-1+b1 ii gvfs-libs 1.36.1-1+b1 ii libc6 2.27-3 ii libglib2.0-0 2.56.1-2 gvfs recommends no packages. Versions of packages gvfs suggests: ii gvfs-backends 1.36.1-1+b1 -- no debconf information
