dead shortcuts i.e. Alt+F1; gconf-editor crashed with SIGSEGV in gconf_value_copy()

Bug #952224 reported by Michael Zywek
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gconf-editor (Ubuntu)

Bug Description

 lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
apt-cache policy gconf-editor
  Installiert: 3.0.1-1ubuntu1
  Kandidat: 3.0.1-1ubuntu1
 *** 3.0.1-1ubuntu1 0
        500 precise/universe i386 Packages
        100 /var/lib/dpkg/status

The crash of gconf-editor was the result of looking for the reason, why my windows do not react on commands like Alt+F10, Alt+F8, Alt+F7, Alt+F4 Alt+Tab and so on. Clicking through thousands of possibilities gconf-editor suddenly crashed. I cannot reproduce the failure. I think this is not important.

Important is the system noreaction to basical shortcuts, only theSuper/Mode4/Windows-Key gives a result with the dash. Even Alt+F1 or Alt+F2 are dead.

If my crash-report is not correctly on this place, I ask you kindly to send it to that part of ubuntu, who has to be busy with these problem of Alt+F1 and so on.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gconf-editor 3.0.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Sun Mar 11 13:42:41 2012
ExecutablePath: /usr/bin/gconf-editor
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111130.1)
ProcCmdline: gconf-editor
 Segfault happened at: 0xb774ca76 <gconf_value_copy+38>: mov (%edi),%eax
 PC (0xb774ca76) ok
 source "(%edi)" (0x00000033) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gconf-editor
 gconf_value_copy () from /usr/lib/i386-linux-gnu/
 ?? () from /usr/lib/i386-linux-gnu/
 g_boxed_copy () from /usr/lib/i386-linux-gnu/
 g_value_set_boxed () from /usr/lib/i386-linux-gnu/
 gtk_tree_model_get_value () from /usr/lib/i386-linux-gnu/
Title: gconf-editor crashed with SIGSEGV in gconf_value_copy()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Michael Zywek (mzpc) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

 gconf_value_copy (src=0x33) at gconf-value.c:734
 _g_type_boxed_copy (type=142241704, value=0x33) at /build/buildd/glib2.0-2.31.20/./gobject/gtype.c:4239
 g_boxed_copy (boxed_type=142241704, src_boxed=0x33) at /build/buildd/glib2.0-2.31.20/./gobject/gboxed.c:337
 value_set_boxed_internal (need_free=1, need_copy=1, boxed=0x33, value=0xbfa0fb64) at /build/buildd/glib2.0-2.31.20/./gobject/gboxed.c:464
 g_value_set_boxed (value=0xbfa0fb64, boxed=0x33) at /build/buildd/glib2.0-2.31.20/./gobject/gboxed.c:481

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gconf-editor (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gconf-editor (Ubuntu):
status: New → Confirmed
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.