Bug 307853 - Partition manager- partition fix crash
Summary: Partition manager- partition fix crash
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-10-04 16:32 UTC by Remco
Modified: 2018-10-27 03:40 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (2.12 KB, text/plain)
2013-01-26 02:32 UTC, Darkmoon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Remco 2012-10-04 16:32:04 UTC
Application: kcmshell4 ()
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-30-generic-pae i686
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:

I couldn't access a 690 GB partition, so i tried to repair it with the partition fix button in Partition Manager.

-- Backtrace:
Application: KDE Control Module (kcmshell4), signal: Aborted
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb55dd980 (LWP 2501))]

Thread 2 (Thread 0xb182fb40 (LWP 2609)):
#0  0xb58e6108 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb58e6408 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb58a709b in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb58a7201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb6c368e7 in QEventDispatcherGlib::processEvents (this=0xb0f00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0xb6c0250d in QEventLoop::processEvents (this=0xb182f240, flags=...) at kernel/qeventloop.cpp:149
#6  0xb6c027a9 in QEventLoop::exec (this=0xb182f240, flags=...) at kernel/qeventloop.cpp:204
#7  0xb6aeb94c in QThread::exec (this=0x8721ea8) at thread/qthread.cpp:501
#8  0xb6bdfb5d in QInotifyFileSystemWatcherEngine::run (this=0x8721ea8) at io/qfilesystemwatcher_inotify.cpp:248
#9  0xb6aeede0 in QThreadPrivate::start (arg=0x8721ea8) at thread/qthread_unix.cpp:298
#10 0xb59bcd4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#11 0xb761face in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb55dd980 (LWP 2501)):
[KCrash Handler]
#7  0xb76fd424 in __kernel_vsyscall ()
#8  0xb75631ef in raise () from /lib/i386-linux-gnu/libc.so.6
#9  0xb7566835 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0xb5f7b13d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0xb5f78ed3 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0xb5f78f0f in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0xb5f790b4 in __cxa_rethrow () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#14 0xb6c02a55 in QEventLoop::exec (this=0xbfe2bff0, flags=...) at kernel/qeventloop.cpp:218
#15 0xb66400d9 in QDialog::exec (this=0x86042d0) at dialogs/qdialog.cpp:554
#16 0xb76f6b39 in kdemain (_argc=2, _argv=0xbfe2c324) at ../../kcmshell/main.cpp:292
#17 0x0804850b in main (argc=2, argv=0xbfe2c324) at kcmshell4_dummy.cpp:3

Possible duplicates by query: bug 307538, bug 307377, bug 307196, bug 307142, bug 306873.

Reported using DrKonqi
Comment 1 Christoph Feck 2012-10-04 17:12:42 UTC
Could you try again running from Konsole, and add the debug output you get?
Comment 2 Jekyll Wu 2012-10-06 11:55:41 UTC
Wait for information requested in comment #1. 

In short, you should type and run "sysemsettings" in konsole, then repeat the action in the report.
Comment 3 Darkmoon 2013-01-26 02:32:06 UTC
Created attachment 76728 [details]
New crash information added by DrKonqi

kcmshell4 () on KDE Platform 4.9.4 using Qt 4.8.3

- What I was doing when the application crashed:
Using Web Accounts KDE Control Module and entered a new Google Account using the Select a supported Web Account button Entered my user name and passwork and hit ok

-- Backtrace (Reduced):
#14 0xb6c837e7 in QEventLoop::exec (this=0xbfc374e8, flags=...) at kernel/qeventloop.cpp:218
#15 0xb66b2d2d in QDialog::exec (this=0x97dbe20) at dialogs/qdialog.cpp:554
#16 0xb776cb2d in kdemain (_argc=2, _argv=0xbfc376f4) at ../../kcmshell/main.cpp:292
#17 0x0804855b in main (argc=2, argv=0xbfc376f4) at kcmshell4_dummy.cpp:3
Comment 4 Andrew Crouthamel 2018-09-24 01:59:06 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 03:40:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!