[apport] gedit crashed with SIGSEGV in gpa_node_set_path_value()

Bug #85393 reported by Loic
58
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit
Expired
Critical
gedit (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gedit

Just made a "print preview", then I changed the font size, then I tried to close the "preview", to make another preview... It crashes when I tried to close the "preview".

ProblemType: Crash
Date: Thu Feb 15 09:57:36 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gedit
Package: gedit 2.17.5-0ubuntu1
ProcCmdline: gedit file:///home/lolichon/Desktop/logger.sdl.diff
ProcCwd: /home/lolichon
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/tcsh
Signal: 11
SourcePackage: gedit
StacktraceTop:
 gpa_node_set_path_value ()
 gnome_print_config_set_int ()
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Uname: Linux lolichon-laptop 2.6.20-8-generic #2 SMP Tue Feb 13 01:14:41 UTC 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
Loic (loic-sf) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. The backtrace matches http://bugzilla.gnome.org/show_bug.cgi?id=405900 upstream, I've added a comment pointing that launchpad bug

Changed in gedit:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Andrew Mitchell (ajmitch) wrote :

Run through apport-retrace

Changed in gedit:
status: Unknown → Unconfirmed
Revision history for this message
Sebastian Urban (surban) wrote :

Opened the print dialog, added a printer, clicked on preview, closed the previewed, opened the print dialog again, then it crashed.

Revision history for this message
ricardisimo (ricardisimo) wrote :

Same crash here. I'll send the bug report if apport hasn't already. Just let me know... otherwise I'll save you the bandwidth/disk space.

Revision history for this message
Sebastien Bacher (seb128) wrote :

There is already a detailled crash file, no need of a new one

Changed in gedit:
status: New → Confirmed
Changed in gedit:
status: Confirmed → Triaged
Changed in gedit:
status: Confirmed → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Can you still reproduce the crash with gedit 2.20.X ?

Revision history for this message
FS (jg1816) wrote : RE: [Bug 85393] Re: [apport] gedit crashed with SIGSEGV in gpa_node_set_path_value()

No
> From: <email address hidden>> To: <email address hidden>> Date: Tue, 8 Jan 2008 14:18:50 +0000> Subject: [Bug 85393] Re: [apport] gedit crashed with SIGSEGV in gpa_node_set_path_value()> > Can you still reproduce the crash with gedit 2.20.X ?> > -- > [apport] gedit crashed with SIGSEGV in gpa_node_set_path_value()> https://bugs.launchpad.net/bugs/85393> You received this bug notification because you are a direct subscriber> of the bug.
_________________________________________________________________
Use fowl language with Chicktionary. Click here to start playing!
http://puzzles.sympatico.msn.ca/chicktionary/index.html?icid=htmlsig

Revision history for this message
Alex Mayorga (alex-mayorga) wrote :

I've seen this crash today on Hardy (gedit 2.20.4). Attached the .crash that ocurred while trying to see the print preview.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Alex, can you use apport to send that report? Just go to /var/crash/ and double click on the .crash file, apport will send it to launchpad and it can generate an automatic backtrace with it, thanks.

Changed in gedit:
status: Incomplete → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug was due to the libgnomeprint code which has been replaced by gtkprint in hardy, closing the bug as deprecated

Changed in gedit:
status: Triaged → Invalid
Changed in gedit:
importance: Unknown → Critical
status: Invalid → Expired
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.