gedit crashed with SIGSEGV

Bug #191171 reported by RedHeron
8
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

additionally, the keyboard driver does not respond to control key functions such as shift.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Feb 11 22:01:56 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gedit
NonfreeKernelModules: vmnet vmblock vmmon nvidia
Package: gedit 2.21.1-0ubuntu2
PackageArchitecture: amd64
ProcCmdline: gedit
ProcCwd: /home/redheron
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gedit
Stacktrace:
 #0 0x00007fbb9478d674 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
 #1 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 9330):
 #0 0x00007fbb9478d674 in ?? () from /usr/lib/libgdk-x11-2.0.so.0
 #1 0x0000000000000000 in ?? ()
Title: gedit crashed with SIGSEGV
Uname: Linux rherp-devel 2.6.24-7-generic #1 SMP Thu Feb 7 00:56:31 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video

Revision history for this message
RedHeron (ray-jenson) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_gdk_keymap_key_is_modifier (keymap=<value optimized out>, keycode=37)
?? ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gedit:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in gedit:
status: Incomplete → Invalid
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.