Bug 352141 - Removal of user photo in system settings causes crash.
Summary: Removal of user photo in system settings causes crash.
Status: RESOLVED DUPLICATE of bug 343557
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-09-02 04:48 UTC by Tyler
Modified: 2015-09-03 09:27 UTC (History)
0 users

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 Tyler 2015-09-02 04:48:51 UTC
Application: systemsettings5 (5.2.2)

Qt Version: 5.4.1
Operating System: Linux 3.19.0-26-generic x86_64
Distribution: Ubuntu 15.04

-- Information about the crash:
- What I was doing when the application crashed:  I opened Account Details, clicked on the user photo and clicked Remove Image and OK.  When I click Apply in the main window it crashes with the error: "Could not delete file /home/myUser/.face.icon.".  It is fully repeatable.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff7c7cbe780 (LWP 5674))]

Thread 2 (Thread 0x7ff7b83d7700 (LWP 5675)):
#0  0x00007ff7c43d38dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007ff7c26c9b72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007ff7c26cb64f in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007ff7bb1b3099 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#4  0x00007ff7c4a5bb0e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007ff7c15c76aa in start_thread (arg=0x7ff7b83d7700) at pthread_create.c:333
#6  0x00007ff7c43deeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7ff7c7cbe780 (LWP 5674)):
[KCrash Handler]
#6  0x0000000000000000 in ?? ()
#7  0x00007ff7c4ca845f in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007ff7bf23655c in KDialogJobUiDelegate::Private::next() () from /usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5
#9  0x00007ff7c4ccb73a in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007ff7c5a93b2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#11 0x00007ff7c5a99000 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007ff7c4c99c2b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007ff7c4c9bc9b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007ff7c4cf2843 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007ff7c10a1c3d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#16 0x00007ff7c10a1f20 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#17 0x00007ff7c10a1fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007ff7c4cf2c57 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007ff7c4c973e2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#20 0x00007ff7c4c9f02c in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x000000000040eebc in main ()

Reported using DrKonqi
Comment 1 Christoph Feck 2015-09-03 09:27:00 UTC

*** This bug has been marked as a duplicate of bug 343557 ***