GNOME Bugzilla – Bug 426337
crash in Gimmie: apt-upgrade
Last modified: 2007-04-04 22:37:00 UTC
What were you doing when the application crashed? apt-upgrade Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.0 2007-03-13 (Ubuntu) BugBuddy Version: 2.18.0 System: Linux 2.6.20-13-lowlatency #2 SMP PREEMPT Sun Mar 25 00:23:53 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Mist Icon Theme: Mist 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 --------------------- ** (gnome-cups-icon:7504): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:7504): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:7504): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:7504): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:7504): WARNING **: IPP request failed with status 1280 ** Message: Failed to close thumbnail pixbuf loader for /home/aguai/Desktop/1.jpg: 分析 JPEG 圖片檔時發生錯誤 (Application transferred too few scanlines) ** Message: Failed to close thumbnail pixbuf loader for /home/aguai/Desktop/1.jpg: 分析 JPEG 圖片檔時發生錯誤 (Application transferred too few scanlines) ** Message: Failed to close thumbnail pixbuf loader for /home/aguai/Desktop/1.jpg: 分析 JPEG 圖片檔時發生錯誤 (Application transferred too few scanlines) /usr/bin/diff: /etc/udev/rules.d/25-dmsetup.rules: 沒有此一檔案或目錄 ** Message: Failed to close thumbnail pixbuf loader for /home/aguai/Desktop/1.jpg: 分析 JPEG 圖片檔時發生錯誤 (Application transferred too few scanlines) -------------------------------------------------- Traceback (most recent call last):
+ Trace 125020
acct_doc = parse(self.accounts_path)
from xml.dom import expatbuilder
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 417988 ***