[wacom]: gnome-settings-daemon crashed with SIGABRT in g_assertion_message()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gnome-settings-daemon (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
After connect wacom bamboo touch and pen.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-settings-
ProcVersionSign
Uname: Linux 3.2.0-21-generic x86_64
ApportVersion: 2.0-0ubuntu2
Architecture: amd64
Date: Sat Mar 31 10:48:30 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120117)
ProcCmdline: /usr/lib/
Signal: 6
SourcePackage: gnome-settings-
Title: [gsdwacom]: gnome-settings-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo
| Michał Kastelik (x-ubuntuman) wrote | #1 |
| Apport retracing service (apport) wrote Possible regression detected | #2 |
| tags: | added: regression-retracer |
| Apport retracing service (apport) wrote Stacktrace.txt | #4 |
| Apport retracing service (apport) wrote StacktraceTop.txt | #5 |
| Apport retracing service (apport) wrote ThreadStacktrace.txt | #6 |
| Changed in gnome-settings-daemon (Ubuntu): | |
| importance: | Undecided → Medium |
| summary: |
- [gsdwacom]: gnome-settings-daemon crashed with SIGABRT in raise() + [gsdwacom]: gnome-settings-daemon crashed with SIGABRT in + g_assertion_message() |
| tags: | removed: need-amd64-retrace |
| Launchpad Janitor (janitor) wrote Re: [gsdwacom]: gnome-settings-daemon crashed with SIGABRT in g_assertion_message() | #7 |
| Changed in gnome-settings-daemon (Ubuntu): | |
| status: | New → Confirmed |
| visibility: | private → public |
| summary: |
- [gsdwacom]: gnome-settings-daemon crashed with SIGABRT in + [wacom]: gnome-settings-daemon crashed with SIGABRT in g_assertion_message() |
This crash has the same stack trace characteristics as bug #934445. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.