unity-settings-daemon crashed with signal 5 in _XReply()

Bug #1306436 reported by zhifeng hu
118
This bug affects 18 people
Affects Status Importance Assigned to Milestone
unity-settings-daemon (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

it crashed itself

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity-settings-daemon 14.04.0+14.04.20140407-0ubuntu1
Uname: Linux 3.14.0-031400-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr 11 15:58:55 2014
ExecutablePath: /usr/lib/unity-settings-daemon/unity-settings-daemon
InstallationDate: Installed on 2014-04-01 (10 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140328)
ProcCmdline: /usr/lib/unity-settings-daemon/unity-settings-daemon
Signal: 5
SourcePackage: unity-settings-daemon
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/unity-settings-daemon-1.0/libclipboard.so
Title: unity-settings-daemon crashed with signal 5 in _XReply()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
zhifeng hu (zhifeng) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XSync (dpy=0x11c65e0, discard=discard@entry=0) at ../../src/Sync.c:44
 send_selection_notify (manager=manager@entry=0x12a8230, success=<optimized out>) at gsd-clipboard-manager.c:153
 clipboard_manager_process_event (xev=0x7fff1d0b0c00, manager=<optimized out>) at gsd-clipboard-manager.c:786
 clipboard_manager_event_filter (xevent=0x7fff1d0b0c00, event=<optimized out>, manager=0x12a8230) at gsd-clipboard-manager.c:824
 gdk_event_apply_filters (xevent=xevent@entry=0x7fff1d0b0c00, event=event@entry=0x1543150, window=window@entry=0x11dc3b0) at /build/buildd/gtk+3.0-3.10.8/./gdk/x11/gdkeventsource.c:81

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in unity-settings-daemon (Ubuntu):
status: New → Confirmed
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

I have been direct here after Bug #1493107 was marked of a duplicate of this one. I can see the stacktrace bits do look similar in places. Something about the clipboard being present in both. I do not think I had just performed a copy or paste when I hit this issue but it would be very likely that I had something in a buffer.

Are there any steps I should take to aid diagnostics, should this bug reproduce on my system?

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

It seems that I hit this again today while also seeing Bug #1493103, Bug #1493852 and Bug #1022993.

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Seen again today it seems.

Revision history for this message
Bård Lind (bard-lind) wrote :

This bug keeps comming almost every time I connect an external screen.

tags: added: wily
tags: added: xenial
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Occurred again today.

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

I am doing OK at being taken to this page every few months.

Revision history for this message
Mateusz Bysiek (mbdev) wrote :

Been happening randomly to me for years. It happens rarely, and when it happens it usually does after the system is on for at least a week. Interestingly several other processes crash at the same time. And even the theme "crashes" from Radiance into default Ambiance... Things go back to normal after restart.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.