GNOME Bugzilla – Bug 350122
Critical warning in gnome_paper_selector_load_paper_size
Last modified: 2009-11-27 05:16:34 UTC
What were you doing when the application crashed? I clicked on the File -> Print... menu item for the second time since the application was opened. After force quitting the application, I am no longer able to restart it from the terminal. Strace'ing the application gives the following at the end of the strace output: stat64("/tmp/gedit.testuser.1603981544", {st_mode=S_IFSOCK|0755, st_size=0, ...}) = 0 geteuid32() = 1001 close(14) = 0 stat64("/tmp/gedit.testuser.1603981544", {st_mode=S_IFSOCK|0755, st_size=0, ...}) = 0 socket(PF_FILE, SOCK_STREAM, 0) = 14 connect(14, {sa_family=AF_FILE, path="/tmp/gedit.testuser.1603981544"}, 110) = 0 fstat64(14, {st_mode=S_IFSOCK|0777, st_size=0, ...}) = 0 fcntl64(14, F_GETFL) = 0x2 (flags O_RDWR) write(3, "\22\0\20\0\1\0 \1\37\1\0\0\37\0\0\0\10\0\5\0%\0\0\0001"..., 92) = 92 read(3, "\34\225S\0\1\0 \1\37\1\0\0Lw\322\341\0v\322\3418g\35\10"..., 32) = 32 read(3, "\1\316T\0\0\0\0\0!\1\0\0\0\0\0\0\0\0\0\0\34\0\0\0\34\0"..., 32) = 32 write(3, "\24\0\6\0\31\1\0\0!\1\0\0\6\0\0\0\0\0\0\0\377\377\377\177"..., 24) = 24 read(3, "\1 U\0\1\0\0\0\6\0\0\0\0\0\0\0\1\0\0\0\30\0\0\0\30\0\0"..., 32) = 32 read(3, "\0\0\0\0", 4) = 4 write(14, "0\t:1.0\t0\t0\n", 11) = 11 close(14) = 0 close(14) = -1 EBADF (Bad file descriptor) writev(13, [{"GIOP\1\2\1\5\0\0\0\0", 12}], 1) = 12 close(13) = 0 writev(11, [{"GIOP\1\2\1\5\0\0\0\0", 12}], 1) = 12 close(11) = 0 close(9) = 0 close(8) = 0 unlink("/tmp/orbit-testuser/linc-17b7-0-9fe3cc1e141f") = 0 close(12) = 0 exit_group(0) = ? testuser@home:~$ This is the exact behavior I have seen with another application that crashed (totem). Please see bug 350118 Distribution: Ubuntu 6.06 (dapper) Gnome Release: 2.15.90 2006-08-05 (JHBuild) BugBuddy Version: 2.15.91 Memory status: size: 51744768 vsize: 0 resident: 51744768 share: 0 rss: 20398080 rss_rlim: 0 CPU usage: start_time: 1154839808 rtime: 0 utime: 178 stime: 0 cutime:164 cstime: 0 timeout: 14 it_real_value: 0 frequency: 0 Backtrace was generated from '/opt/gnome2/bin/gedit' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1229670720 (LWP 6051)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 70014
I was able to run gedit again by deleting the tmp file in /tmp/gedit.testuser.1603981544 File -> Print error is reproducible by doing the following. Open Gedit click File -> Print... click cancel click File -> Print... This is the output to the terminal: testuser@home:~$ gedit & [2] 6094 testuser@home:~$ ** (gedit:6087): WARNING **: could not set the value of Settings.Document.Filter, node not found libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed aborting... ** (bug-buddy:6098): WARNING **: Couldn't load icon for Bonobo Component Browser ** (bug-buddy:6098): WARNING **: Couldn't load icon for Open Folder glibtop: This machine has 1 CPUs, 1 are being monitored. Error while running hook_stop: Invalid type combination in ordering comparison.
Does it still happen with latest 2.15 ? I can't reproduce it.
I cannot reproduce it on both CVS HEAD and 2.14. The fact gedit did not start after the crash seems due to a staled bacon connection and it is not related to the crash. The crash is due to a CRITICAL warning by libgnomeprintui. Moving to gnome-print.
Still here with 2.17.x: Distribution: Fedora Core release 6 (Rawhide) Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc) BugBuddy Version: 2.17.2 System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:45:28 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 78274560 vsize: 0 resident: 78274560 share: 0 rss: 18337792 rss_rlim: 0 CPU usage: start_time: 1166013361 rtime: 0 utime: 119 stime: 0 cutime:105 cstime: 0 timeout: 14 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gedit' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1208522528 (LWP 876)] 0x00c90402 in __kernel_vsyscall ()
+ Trace 93812
Is this still an issue in GNOME 2.24/2.26? Note that gnome-print has been deprecated and superseded by GTK+ printing functionality since GNOME 2.16. This means that gnome-print is NOT actively maintained anymore. If your reported issue is still valid for GTK+ printing, please feel free to file a bug report against gtk+/printing. If it is OBSOLETE, feel free to close this report.
Closing this bug report as no further information has been provided. Please feel free to reopen the bug if the problem still occurs with a newer version of GNOME 2.28.1 or later, thanks.