GNOME Bugzilla – Bug 485894
crash in Deskbar: I have no idea what I wa...
Last modified: 2007-10-12 10:27:20 UTC
What were you doing when the application crashed? I have no idea what I was doing, because I've seen this bug reporting tool, when I came back to the computer Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.20.0 2007-09-17 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-14-generic #1 SMP Wed Oct 10 06:00:47 GMT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Human Icon Theme: Human Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0 CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 ----------- .xsession-errors (93 sec old) --------------------- wodim stdout: Lout start: 867 MB (85:57/59) = 386684 sectors wodim stdout: Current Secsize: 2048 wodim stdout: ATIP info from disk: wodim stdout: Indicated writing power: 5 wodim stdout: Is not unrestricted wodim stdout: Is not erasable wodim stdout: ATIP start of lead in: -11933 (97:22/67) wodim stdout: ATIP start of lead out: 359849 (79:59/74) wodim stdout: Disk type: Short strategy type (Phthalocyanine or similar) wodim stdout: Manuf. index: 43 wodim stdout: Manufacturer: Acer Media Technology, Inc. wodim stdout: Blocks total: 359849 Blocks current: 359849 Blocks remaining: -26835 process stdout: HUP process stderr: HUP Error: [10/11/2007 5:14:10 PM] (Error writing disc) - The files selected did not fit on the CD. -------------------------------------------------- Traceback (most recent call last):
+ Trace 169632
run_old(*args, **kwargs)
self.__target(*self.__args, **self.__kwargs)
function(*args, **kwargs)
'results': 15}), proxies=get_proxy())
return opener.open(url)
return getattr(self, name)(url)
h.endheaders()
self._send_output()
self.send(msg)
self.connect()
raise socket.error, msg
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 482379 ***