Application: partitionmanager (3.0.1) Qt Version: 5.7.1 Frameworks Version: 5.36.0 Operating System: Linux 4.12.5-300.fc26.x86_64 x86_64 Distribution: "Fedora release 26 (Twenty Six)" -- Information about the crash: - What I was doing when the application crashed: Entering user password and root password in the next window - Unusual behavior I noticed: crashed and I don't have usage rights as the system admin The crash can be reproduced every time. -- Backtrace: Application: KDE-Partitionsverwaltung (partitionmanager), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3781d52940 (LWP 30126))] Thread 6 (Thread 0x7f37339a0700 (LWP 32253)): [KCrash Handler] #6 0x00007f3781851fd3 in FS::lvm2_pv::getPVs(QList<Device*> const&) () from /lib64/libkpmcore.so.4 #7 0x00007f3781870937 in DeviceScanner::scan() () from /lib64/libkpmcore.so.4 #8 0x00007f377de07c9e in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x00007f377ac5236d in start_thread () from /lib64/libpthread.so.0 #10 0x00007f377d1efb8f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f375113d700 (LWP 32117)): #0 0x00007f377ac5881b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f3755a20ccb in thread_function () from /usr/lib64/dri/swrast_dri.so #2 0x00007f3755a20b47 in impl_thrd_routine () from /usr/lib64/dri/swrast_dri.so #3 0x00007f377ac5236d in start_thread () from /lib64/libpthread.so.0 #4 0x00007f377d1efb8f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f375193e700 (LWP 32116)): #0 0x00007f377ac5881b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f3755a20ccb in thread_function () from /usr/lib64/dri/swrast_dri.so #2 0x00007f3755a20b47 in impl_thrd_routine () from /usr/lib64/dri/swrast_dri.so #3 0x00007f377ac5236d in start_thread () from /lib64/libpthread.so.0 #4 0x00007f377d1efb8f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f375fe81700 (LWP 30136)): #0 0x00007f3776c184c4 in g_mutex_unlock () from /lib64/libglib-2.0.so.0 #1 0x00007f3776bd2467 in g_main_context_acquire () from /lib64/libglib-2.0.so.0 #2 0x00007f3776bd3425 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x00007f3776bd367c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x00007f377dffae6b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #5 0x00007f377dfab60a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #6 0x00007f377de0399a in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x00007f377ed0da39 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #8 0x00007f377de07c9e in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x00007f377ac5236d in start_thread () from /lib64/libpthread.so.0 #10 0x00007f377d1efb8f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f3768da8700 (LWP 30131)): #0 0x00007f377d1e3a9d in poll () from /lib64/libc.so.6 #1 0x00007f37762c9c97 in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x00007f37762cba8a in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x00007f376d00aba9 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x00007f377de07c9e in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x00007f377ac5236d in start_thread () from /lib64/libpthread.so.0 #6 0x00007f377d1efb8f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f3781d52940 (LWP 30126)): #0 0x00007f377d1df19d in read () from /lib64/libc.so.6 #1 0x00007f3776c17170 in g_wakeup_acknowledge () from /lib64/libglib-2.0.so.0 #2 0x00007f3776bd3078 in g_main_context_check () from /lib64/libglib-2.0.so.0 #3 0x00007f3776bd3510 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #4 0x00007f3776bd367c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x00007f377dffae4f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #6 0x00007f377dfab60a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5 #7 0x00007f377dfb327c in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #8 0x0000001778791478 in main () Possible duplicates by query: bug 380423, bug 376895. Reported using DrKonqi
I'm confused bit "Entering user password and root password in the next window". Did you really have to enter password twice? I suspect that for some reason in your case KDE Partition Manager failed to get root privileges. Can you try to explain a bit more exactly what were you doing. I might try to download fedora live in the meantime. This backtrace looks like the one from unprivileged program that is trying to access lvm devices. There was a fix for this crash in kpmcore 3.1.0 but in any case unprivileged KDE Partition Manager would be useless.
Created attachment 107333 [details] attachment-27926-0.html Thanks for this awesome support for free, I never thought of getting an reply. Yes the application asked twice my password. I now ended up installing Fedora completly new, with even stronger and longer Passwords and encrypted my installation and I forced IPV6 for my connection and enableing FIPS in Firefox. I also notice an overall speed increase now. I hope my Report helps anyways somehow. On 17 Aug 2017 17:05, "Andrius Štikonas" <bugzilla_noreply@kde.org> wrote: https://bugs.kde.org/show_bug.cgi?id=383636 --- Comment #1 from Andrius Štikonas <andrius@stikonas.eu> --- I'm confused bit "Entering user password and root password in the next window". Did you really have to enter password twice? I suspect that for some reason in your case KDE Partition Manager failed to get root privileges. Can you try to explain a bit more exactly what were you doing. I might try to download fedora live in the meantime. This backtrace looks like the one from unprivileged program that is trying to access lvm devices. There was a fix for this crash in kpmcore 3.1.0 but in any case unprivileged KDE Partition Manager would be useless. -- You are receiving this mail because: You reported the bug.
Hmm, after some brief testing on fedora live cd, I can't reproduce it. Maybe I'll might try to actually install fedora at some point in virtual machine but I doubt that I'll be able to reproduce the crash... Any chance you can try to see if KDE Partition Manager from rawhide works? Since there were some fixes. (In reply to Johann Kribus from comment #2) > Created attachment 107333 [details] > attachment-27926-0.html > > Thanks for this awesome support for free, I never thought of getting an > reply. > > Yes the application asked twice my password. I now ended up installing > Fedora completly new, with even stronger and longer Passwords and encrypted > my installation and I forced IPV6 for my connection and enableing FIPS in > Firefox. I also notice an overall speed increase now. I hope my Report > helps anyways somehow. > > On 17 Aug 2017 17:05, "Andrius Štikonas" <bugzilla_noreply@kde.org> wrote: > > https://bugs.kde.org/show_bug.cgi?id=383636 > > --- Comment #1 from Andrius Štikonas <andrius@stikonas.eu> --- > I'm confused bit > > "Entering user password and root password in the next window". Did you > really > have to enter password twice? > > I suspect that for some reason in your case KDE Partition Manager failed to > get > root privileges. Can you try to explain a bit more exactly what were you > doing. > I might try to download fedora live in the meantime. > > This backtrace looks like the one from unprivileged program that is trying > to > access lvm devices. There was a fix for this crash in kpmcore 3.1.0 but in > any > case unprivileged KDE Partition Manager would be useless. > > -- > You are receiving this mail because: > You reported the bug.
Created attachment 107336 [details] attachment-28912-0.html Works perfectly fine now, even formatting the HFS+ USB Stick in NTFS. I report everything if something happens like this again. Thanks. On 17 Aug 2017 7:26 PM, "Andrius Štikonas" <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=383636 > > --- Comment #3 from Andrius Štikonas <andrius@stikonas.eu> --- > Hmm, after some brief testing on fedora live cd, I can't reproduce it. > > Maybe I'll might try to actually install fedora at some point in virtual > machine but I doubt that I'll be able to reproduce the crash... > > Any chance you can try to see if KDE Partition Manager from rawhide works? > Since there were some fixes. > > (In reply to Johann Kribus from comment #2) > > Created attachment 107333 [details] > > attachment-27926-0.html > > > > Thanks for this awesome support for free, I never thought of getting an > > reply. > > > > Yes the application asked twice my password. I now ended up installing > > Fedora completly new, with even stronger and longer Passwords and > encrypted > > my installation and I forced IPV6 for my connection and enableing FIPS in > > Firefox. I also notice an overall speed increase now. I hope my Report > > helps anyways somehow. > > > > On 17 Aug 2017 17:05, "Andrius Štikonas" <bugzilla_noreply@kde.org> > wrote: > > > > https://bugs.kde.org/show_bug.cgi?id=383636 > > > > --- Comment #1 from Andrius Štikonas <andrius@stikonas.eu> --- > > I'm confused bit > > > > "Entering user password and root password in the next window". Did you > > really > > have to enter password twice? > > > > I suspect that for some reason in your case KDE Partition Manager failed > to > > get > > root privileges. Can you try to explain a bit more exactly what were you > > doing. > > I might try to download fedora live in the meantime. > > > > This backtrace looks like the one from unprivileged program that is > trying > > to > > access lvm devices. There was a fix for this crash in kpmcore 3.1.0 but > in > > any > > case unprivileged KDE Partition Manager would be useless. > > > > -- > > You are receiving this mail because: > > You reported the bug. > > -- > You are receiving this mail because: > You reported the bug.
Ok. I'll close it for now. If you encounter it again, please report a new bug.