Ubuntu
gedit package

gedit crashes when GNOME is logging out

Bug #33087 reported by Sitsofe Wheeler
12
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Normally, if you have an unsaved document in gedit and you attempt to log out, gedit will halt the log out process and present a dialog asking do you want to save and logout, don't save and logout or cancel the logout. When a restart is initiated using the purple arrows in the notification area gedit does not pop this dialog box up and instead crashes.

Steps to reproduce:
1. Start gedit .
2. Type 'a' so the document becomes new and unsaved.
3. Run /usr/bin/update-manager as root.
4. Ensure that an update that will suggest a restart (e.g. a kernel update) is selected and click Install Updates.
5. After the updates are installed an icon containing purple arrows will appear in the notification tray. Click on it.
6. In the Restart Required dialog choose the "Restart Now" button.

Expected results:
gedit to pop up a dialog saying: 'Save the changes to document "Unsaved Document 1" before closing?' with the options of "Logout without saving", "Cancel Logout" and "Save" or for gedit to save recovery files so that the work can be resumed when the system is restarted.

Actual results:
gedit briefly pops up a GNOME crash dialog before that closes by itself and the GNOME logs out and the computer restarts.

Revision history for this message
Phil Bull (philbull) wrote :

Thanks for the report.

It might be tricky to get a backtrace for this one. Could you run gedit in a terminal with the following command and reproduce the crash, please?

gedit > ~/gedit_output.txt

If gedit produces any output relating to the crash, hopefully it should be captured in 'gedit_output.txt' in your home directory. If it is, please attach the file.

What version of the gedit package do you have installed?

Thanks

Changed in gedit:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

I can't actually do much more testing unless you can give me a way to trigger the restart icon in the notification bar that doesn't involve real package upgrades. I've tried downgrading/upgrading various packages and it doesn't turn up so I need some other way (ideally by editing some file) in order to test this.

However this bug has two parts. There are times a crash doesn't happen but gedit still quits without putting up a warning dialog (only when a restart is forced from the notification bar). For this part I won't be able to give you backtrace.

I honestly can't remember what gedit I had at the time of filing although I'm fairly sure I've seen it with the gedit I have at the moment (2.13.93-0ubuntu1 ).

Changed in gedit:
status: Needs Info → Unconfirmed
Revision history for this message
Phil Bull (philbull) wrote :

There was an update today which required a restart, so I tried to reproduce the bug. I can confirm the issue, but gedit didn't crash so I didn't get any useful debugging output. It may be that the restart notification reboots the system using a different mechanism to the normal System | Logout method.

I'll keep trying to get some useful debugging info. No-one on IRC seemed to have any ideas on how to get the restart notification to appear on demand to test this.

Thanks

Changed in gedit:
status: Unconfirmed → Confirmed
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

"No-one on IRC seemed to have any ideas on how to get the restart notification to appear on demand to test this."

Dang. Thanks for trying.

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

just run" sudo /usr/share/update-notifier/notify-reboot-required" for that

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Ok first up this can be triggered simply by logging out when there are a few other apps about in addition to gedit.

I rigged gdb to follow gedit from a virtual terminal so I can add a backtrace. Strangely the problem seems python related.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote : gdb backtrace of gedit crash when GNOME is logging out

gdb backtrace of gedit crash when GNOME is logging out

Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for the backtrace - can you try again with libglib2.0-0-dbg and python2.4-dbg installed?

Changed in gedit:
status: Confirmed → Needs Info
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote : gdb backtrace of gedit crash when GNOME is logging out with symbols

gdb backtrace of gedit crash when GNOME is logging out with symbols

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Steps to reproduce:
1. Put
ulimit -c unlimited
export GNOME_DISABLE_CRASH_DIALOG=1
into your .gnomerc file.
2. Log into GNOME so .gnomerc is used.
3. Start gedit .
4. Click the log out button at the top left and select Log Out.

Expected results:
No core dump.

Actual results:
Core dump.

Additional information:
I believe if you have an otherwise clean profile disabling syntax highlighting will resolve the problem.

Changed in gedit:
status: Needs Info → Confirmed
Revision history for this message
Daniel Holbach (dholbach) wrote :

Is this still a problem in Edgy?

Changed in gedit:
status: Confirmed → Needs Info
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

I'm not in a position to test that right now. When edgy is in beta (in September) I'll do an install then. If you can ping me at that point it would be most helpful...

Revision history for this message
Daniel Holbach (dholbach) wrote :

Ping :-)

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Thanks for the ping.

I can't reproduce this in edgy (up to date as of 30 September 2006). Resolve fixed?

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

Marking as fixed for now. Feel free to reopen if you get the issue again

Changed in gedit:
status: Needs Info → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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