GNOME Bugzilla – Bug 328862
Evolution crashes when I try to print
Last modified: 2013-09-13 00:57:57 UTC
Steps to reproduce: 1. Set gtk key bindings preferences to Emacs in gconf-editor. 2. Start composing a message in Evolution. 3. Type <ctrl-P>, which should go to the previous line. Instead, the app crashes. Stack trace: Other information: I'm running evo evolution-2.5.4-2 on fc5t2.
Here's the backtrace from bug-buddy. Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208531280 (LWP 9006)] [New Thread -1364403296 (LWP 9108)] [New Thread -1353913440 (LWP 9107)] [New Thread -1326449760 (LWP 9016)] [New Thread -1278055520 (LWP 9015)] [New Thread -1314505824 (LWP 9013)] [New Thread -1267565664 (LWP 9011)] [New Thread -1257067616 (LWP 9010)] [New Thread -1246184544 (LWP 9009)] [New Thread -1235694688 (LWP 9008)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0x009e5402 in __kernel_vsyscall ()
+ Trace 65668
Thread 1 (Thread -1208531280 (LWP 9006))
By the way, this is absolutely 100% reproducible for me with just the instructions above.
I just tried with default keybindings instead of Emacs, and evo still crashes when I type ctrl-P. So this has nothing to do with the keybindings in force, and appears to be an issue when trying to bring up the Print dialog. Yep, I just tried the File->Print menu item, and it crashes evo too, and in fact trying to print from *anywhere* makes it go kaboom.
By the way, the implication here is that Emacs keybindings are broken in Gnome 2.13. ctrl-P should go to the previous line, not bring up a print dialog. Should I file a separate bug against that, and if so, against which component?
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Same stacktrace down to frame 14 as bug 326572, both related to CUPS and dbus. Looks like a duplicate. Marking as such. *** This bug has been marked as a duplicate of 326572 ***
Confirmed dupe by comment #3. :) Bryan: Yes, the accelerator clash when using emacs keybindings would be a different bug. Feel free to file one especially for this. Although I believe it already is filed. Need to search...
*** Bug 328868 has been marked as a duplicate of this bug. ***
Bryan: Found the keybindings issue. See bug 203420 comment 9.
Thanks!