Bug 343557 - Removing image from Password and User settings crashes systems settings
Summary: Removing image from Password and User settings crashes systems settings
Status: RESOLVED INTENTIONAL
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_useraccount (show other bugs)
Version: 5.2.0
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
: 340812 346417 347515 348307 348432 348641 348803 349372 349761 352141 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-01-30 07:38 UTC by Sudhir Khanger
Modified: 2015-09-26 13:29 UTC (History)
11 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sudhir Khanger 2015-01-30 07:38:14 UTC
Application: systemsettings5 (5.2.0)

Qt Version: 5.4.0
Operating System: Linux 3.18.3-201.fc21.x86_64 x86_64
Distribution: "Fedora release 21 (Twenty One)"

-- Information about the crash:
- What I was doing when the application crashed:
1. No images are provided to be choosen as face in Personalization>Account Details>Password and User Accounts>Change your face.
2. The crash is caused if you remove the pre-existing ~/.face.icon and hit apply. Although when I look into my home folder the image is not there anymore.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f24edbb1880 (LWP 25103))]

Thread 2 (Thread 0x7f24d5f6e700 (LWP 25104)):
#0  0x00007f24e8e191fd in poll () at /lib64/libc.so.6
#1  0x00007f24e814f182 in _xcb_conn_wait () at /lib64/libxcb.so.1
#2  0x00007f24e8150cff in xcb_wait_for_event () at /lib64/libxcb.so.1
#3  0x00007f24d875f959 in QXcbEventReader::run() () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#4  0x00007f24e99b24ce in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5
#5  0x00007f24e715752a in start_thread () at /lib64/libpthread.so.0
#6  0x00007f24e8e2479d in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f24edbb1880 (LWP 25103)):
[KCrash Handler]
#5  0x00007f24e9babb9d in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () at /lib64/libQt5Core.so.5
#6  0x00007f24eb4e9efa in KDialogJobUiDelegate::Private::next() () at /lib64/libKF5JobWidgets.so.5
#7  0x00007f24e9bcdc2a in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5
#8  0x00007f24eaa00d3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#9  0x00007f24eaa06330 in QApplication::notify(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5
#10 0x00007f24e9b9d4ab in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /lib64/libQt5Core.so.5
#11 0x00007f24e9b9f4eb in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5
#12 0x00007f24e9bf4333 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5
#13 0x00007f24e639daeb in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#14 0x00007f24e639de88 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#15 0x00007f24e639df3c in g_main_context_iteration () at /lib64/libglib-2.0.so.0
#16 0x00007f24e9bf4727 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#17 0x00007f24e9b9ad42 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /lib64/libQt5Core.so.5
#18 0x00007f24e9ba27ec in QCoreApplication::exec() () at /lib64/libQt5Core.so.5
#19 0x000000000040e2fc in main ()

Reported using DrKonqi
Comment 1 Alexander Nestorov 2015-02-08 23:04:21 UTC
*** Bug 340812 has been marked as a duplicate of this bug. ***
Comment 2 Christoph Feck 2015-05-31 14:17:32 UTC
*** Bug 346417 has been marked as a duplicate of this bug. ***
Comment 3 Christoph Feck 2015-05-31 14:17:52 UTC
*** Bug 347515 has been marked as a duplicate of this bug. ***
Comment 4 Christoph Feck 2015-05-31 14:18:07 UTC
*** Bug 348307 has been marked as a duplicate of this bug. ***
Comment 5 Christoph Feck 2015-05-31 14:18:30 UTC
*** Bug 348432 has been marked as a duplicate of this bug. ***
Comment 6 Christoph Feck 2015-06-07 10:17:54 UTC
*** Bug 348641 has been marked as a duplicate of this bug. ***
Comment 7 Christoph Feck 2015-06-07 10:18:19 UTC
*** Bug 348803 has been marked as a duplicate of this bug. ***
Comment 8 Christoph Feck 2015-06-23 23:08:35 UTC
*** Bug 349372 has been marked as a duplicate of this bug. ***
Comment 9 Christoph Feck 2015-07-10 14:45:28 UTC
*** Bug 349761 has been marked as a duplicate of this bug. ***
Comment 10 Christoph Feck 2015-09-03 09:27:00 UTC
*** Bug 352141 has been marked as a duplicate of this bug. ***
Comment 11 Albert Astals Cid 2015-09-26 13:29:38 UTC
Starting with Plasma 5.4 kcm_useraccount has been deprecated in favor of user-manager (you can run with kcmshell5 user_manager).

This means that unfortunately we did not get to fix your bug, sorry about that.

We encourage you to try user-manager and report any bug or improvement you may find.

Sorry again for not fixing your bug and thanks for caring about KDE :)