Your message dated Fri, 15 Jun 2018 12:20:59 +0200 with message-id <CA+6XHwTZ0Fokw_ZY+QcHdQfk8j9w1dE-Nyvhm=LYn+ibXG=5...@mail.gmail.com> and subject line has caused the Debian Bug report #765283, regarding gparted crashing during scan 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.) -- 765283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765283 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: gparted Version: 0.19.0-1+b1 Severity: important Dear Maintainer, * What led up to the situation? Opening gparted * What exactly did you do (or not do) that was effective (or ineffective)? I open gparted with a meny enrty in fluxbox, or with Alt-F2 -> su-to-root -X -c gparted or in konsole "gksu gparted" * What was the outcome of this action? The little window where you enter the root p/w closes but it seems it reapears for a fraction of a second. Then gparted window opens, it scans the devoces for partitions and crashes sonner or later. Output in konsole: ****************************************************************** $ gksu gparted glibtop: Non-standard uts for running kernel: release 3.17-0.towo-siduction-686=3.17.0 gives version code 200960 Failed to get D-Bus connection: Unbekannter Fehler -1 Too few arguments. ====================== libparted : 3.2 ====================== Segmentation fault Too few arguments. ******************************************************************* dmesg: 963.284084] gpartedbin[8834]: segfault at 0 ip (null) sp b4edaeb0 error 4 in gpartedbin[8048000+116000] Now, the thing is, sometimes it *is* working, 3,4,5 times in a row, but then you can try 10, 20 times but gparted wouldn't survive scanning. I have this instability *with this installtion* for a long time. It began with gparted not starting at the first attempt, it always needed a second one. I really liked to help with testing 'cause I think it must be some subtle detail which causes this bug. Thanks. Michael -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.17-0.towo-siduction-686 (SMP w/1 CPU core; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gparted depends on: ii libatkmm-1.6-1 2.22.7-2.1 ii libc6 2.19-11 ii libgcc1 1:4.9.1-16 ii libglib2.0-0 2.42.0-2 ii libglibmm-2.4-1c2a 2.42.0-1 ii libgtk2.0-0 2.24.25-1 ii libgtkmm-2.4-1c2a 1:2.24.4-1.1 ii libpangomm-1.4-1 2.34.0-1.1 ii libparted-fs-resize0 3.2-6 ii libparted2 3.2-6 ii libsigc++-2.0-0c2a 2.4.0-1 ii libstdc++6 4.9.1-16 ii libuuid1 2.25.1-4 gparted recommends no packages. Versions of packages gparted suggests: ii dmraid 1.0.0.rc16-5 ii dmsetup 2:1.02.90-2 ii dosfstools 3.0.26-4 ii gpart 0.1h-11+b1 ii jfsutils 1.1.15-2.1 ii kpartx 0.5.0-5 ii mtools 4.0.18-2 ii ntfs-3g 1:2014.2.15AR.1-5 ii reiser4progs 1.0.9-2 ii reiserfsprogs 1:3.6.24-1 ii xfsprogs 3.2.1 ii yelp 3.14.0-1 -- no debconf information
--- End Message ---
--- Begin Message ---Version: 2.44.0-1 Fixed since glibmm 2.43.90. Stretch provides glibmm 2.50.0. 2.43.90 (unstable): Glib: * Error::register_init(): Call Glib::wrap_register_init(). (Kjell Ahlstedt) Bug #743466 (Mike Fleetwood).
--- End Message ---
