[Bug 99955] System instability while printing.
Public bug reported: I cannot provide a stack trace, etc, for this bug, as I am not sure what actually crashed, if anything did. I suspect it may be related to four other bugs I just posted, if for no other reason than similar behavior was reported in the description of a similar bug, but I am uncertain of this. Essentially, while attempting to print four images from GQView (I think it was, might have been gThumb), my system became substantially non- responsive, my swap space usage rose to 50% (I can't even recall ever hitting the swap before, I have a gig of RAM, and all I was doing was printing four images). The printer itself didn't even respond. The machine remained in that state for approximately thirty seconds, then the printer started, and things more or less settled down - although my swap usage remained at about %25 percent. I don't know if this is actually a bug or just an inefficient printing system, and I know that I haven't provided enough information by any means. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- System instability while printing. https://launchpad.net/bugs/99955 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99949] Re: [apport] udevd crashed with SIGSEGV in _fini()
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/7101343/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7101344/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7101345/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7101346/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/7101347/Registers.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/7101348/ThreadStacktrace.txt -- [apport] udevd crashed with SIGSEGV in _fini() https://launchpad.net/bugs/99949 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99951] Re: [apport] events crashed with SIGSEGV in exit()
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/7101360/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7101361/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7101362/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7101363/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/7101364/Registers.txt ** Attachment added: "Stacktrace.txt" http://librarian.launchpad.net/7101365/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/7101366/ThreadStacktrace.txt -- [apport] events crashed with SIGSEGV in exit() https://launchpad.net/bugs/99951 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99951] [apport] events crashed with SIGSEGV in exit()
Public bug reported: Binary package hint: acpid There's not really much to say; I was not aware of the reported crash when it happened (in point of fact, I have no idea when the crash did happen). All I know is, by the time I got into Gnome, I had four crash reports waiting, and I have no idea where they came from. I realize that this isn't much use, but I hope that it's at least a little better than nothing. I'm going to copy-paste this description to the other three bugs, since it's equally true for them. ProblemType: Crash Architecture: amd64 Date: Wed Mar 28 01:08:47 2007 Disassembly: 0x0: DistroRelease: Ubuntu 7.04 ExecutablePath: /etc/acpi/events InterpreterPath: /usr/sbin/acpid Package: acpid 1.0.4-5ubuntu6 PackageArchitecture: amd64 ProcCmdline: /usr/sbin/acpid -c /etc/acpi/events -s /var/run/acpid.socket ProcCwd: / ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin Signal: 11 SourcePackage: acpid StacktraceTop: ?? () ?? () from /lib64/ld-linux-x86-64.so.2 exit () from /lib/libc.so.6 ?? () Uname: Linux the-nemisis 2.6.20-13-generic #2 SMP Sat Mar 24 23:12:02 UTC 2007 x86_64 GNU/Linux UserGroups: ** Affects: acpid (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] events crashed with SIGSEGV in exit() https://launchpad.net/bugs/99951 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99949] [apport] udevd crashed with SIGSEGV in _fini()
Public bug reported: Binary package hint: udev There's not really much to say; I was not aware of the reported crash when it happened (in point of fact, I have no idea when the crash did happen). All I know is, by the time I got into Gnome, I had four crash reports waiting, and I have no idea where they came from. I realize that this isn't much use, but I hope that it's at least a little better than nothing. I'm going to copy-paste this description to the other three bugs, since it's equally true for them. ProblemType: Crash Architecture: amd64 Date: Wed Mar 28 01:08:17 2007 Disassembly: 0x0: DistroRelease: Ubuntu 7.04 ExecutablePath: /sbin/udevd Package: udev 103-0ubuntu14 PackageArchitecture: amd64 ProcCmdline: /sbin/udevd --daemon ProcCwd: / ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin Signal: 11 SourcePackage: udev Stacktrace: #0 0x in ?? () #1 0x2af61fccfd73 in ?? () from /lib/libselinux.so.1 #2 0x7fff8afe70d0 in ?? () #3 0x2af61fcdb601 in _fini () from /lib/libselinux.so.1 #4 0x in ?? () StacktraceTop: ?? () ?? () from /lib/libselinux.so.1 ?? () _fini () from /lib/libselinux.so.1 ?? () Uname: Linux the-nemisis 2.6.20-13-generic #2 SMP Sat Mar 24 23:12:02 UTC 2007 x86_64 GNU/Linux UserGroups: ** Affects: udev (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] udevd crashed with SIGSEGV in _fini() https://launchpad.net/bugs/99949 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99950] [apport] syslogd crashed with SIGSEGV in exit()
Public bug reported: Binary package hint: sysklogd There's not really much to say; I was not aware of the reported crash when it happened (in point of fact, I have no idea when the crash did happen). All I know is, by the time I got into Gnome, I had four crash reports waiting, and I have no idea where they came from. I realize that this isn't much use, but I hope that it's at least a little better than nothing. I'm going to copy-paste this description to the other three bugs, since it's equally true for them. ProblemType: Crash Architecture: amd64 Date: Wed Mar 28 01:08:46 2007 Disassembly: 0x0: DistroRelease: Ubuntu 7.04 ExecutablePath: /sbin/syslogd Package: sysklogd 1.4.1-20ubuntu4 PackageArchitecture: amd64 ProcCmdline: /sbin/syslogd ProcCwd: / ProcEnviron: PATH=/bin:/usr/bin:/sbin:/usr/sbin Signal: 11 SourcePackage: sysklogd StacktraceTop: ?? () ?? () from /lib64/ld-linux-x86-64.so.2 exit () from /lib/libc.so.6 ?? () Uname: Linux the-nemisis 2.6.20-13-generic #2 SMP Sat Mar 24 23:12:02 UTC 2007 x86_64 GNU/Linux UserGroups: ** Affects: sysklogd (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] syslogd crashed with SIGSEGV in exit() https://launchpad.net/bugs/99950 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99952] [apport] system-tools-backends crashed with SIGSEGV in exit()
Public bug reported: Binary package hint: system-tools-backends There's not really much to say; I was not aware of the reported crash when it happened (in point of fact, I have no idea when the crash did happen). All I know is, by the time I got into Gnome, I had four crash reports waiting, and I have no idea where they came from. I realize that this isn't much use, but I hope that it's at least a little better than nothing. I'm going to copy-paste this description to the other three bugs, since it's equally true for them. ProblemType: Crash Architecture: amd64 Date: Wed Mar 28 01:08:47 2007 Disassembly: 0x2b869b99b047: DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/system-tools-backends Package: system-tools-backends 2.2.0-0ubuntu1 PackageArchitecture: amd64 ProcCmdline: /usr/bin/system-tools-backends ProcCwd: / ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin Signal: 11 SourcePackage: system-tools-backends StacktraceTop: ?? () ?? () from /lib64/ld-linux-x86-64.so.2 exit () from /lib/libc.so.6 ?? () Uname: Linux the-nemisis 2.6.20-13-generic #2 SMP Sat Mar 24 23:12:02 UTC 2007 x86_64 GNU/Linux UserGroups: ** Affects: system-tools-backends (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] system-tools-backends crashed with SIGSEGV in exit() https://launchpad.net/bugs/99952 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99950] Re: [apport] syslogd crashed with SIGSEGV in exit()
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/7101349/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7101350/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7101351/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7101352/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/7101353/Registers.txt ** Attachment added: "Stacktrace.txt" http://librarian.launchpad.net/7101354/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/7101355/ThreadStacktrace.txt -- [apport] syslogd crashed with SIGSEGV in exit() https://launchpad.net/bugs/99950 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99952] Re: [apport] system-tools-backends crashed with SIGSEGV in exit()
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/7101367/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/7101368/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/7101369/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/7101370/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/7101371/Registers.txt ** Attachment added: "Stacktrace.txt" http://librarian.launchpad.net/7101372/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/7101373/ThreadStacktrace.txt -- [apport] system-tools-backends crashed with SIGSEGV in exit() https://launchpad.net/bugs/99952 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90921] Re: [apport] IndexHelper.exe crashed with SIGSEGV
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/6720892/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/6720893/Dependencies.txt ** Attachment added: "Disassembly.txt" http://librarian.launchpad.net/6720894/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/6720895/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/6720896/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/6720897/Registers.txt ** Attachment added: "Stacktrace.txt" http://librarian.launchpad.net/6720898/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/6720899/ThreadStacktrace.txt -- [apport] IndexHelper.exe crashed with SIGSEGV https://launchpad.net/bugs/90921 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90921] [apport] IndexHelper.exe crashed with SIGSEGV
Public bug reported: Binary package hint: beagle Mono's been crashing on start-up pretty much since I moved to the 7.04 beta. It happens as I'm logging into Gnome, before I've done anything. Other mono apps, like banshee or fspot, seem to work fine (well, maybe I should say "normally," since they can be a bit fuzzy at times of their own accord). I have not tried re-launching beagle to see if the problem recurs, mainly because I normally have no use for beagle anyway, and don't particularly miss it. I realize that this bug report is redundant to several others, and that the information that the li'l bug-reporting utility attaches isn't particularly useful for mono apps; if desired, I'll try to get the beagle/mono specific information and attach it later. ProblemType: Crash Architecture: amd64 Date: Fri Mar 9 01:39:04 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/lib/beagle/IndexHelper.exe InterpreterPath: /usr/bin/mono Package: beagle 0.2.16-0ubuntu4 PackageArchitecture: amd64 ProcCmdline: beagled-helper /usr/lib/beagle/IndexHelper.exe ProcCwd: /home/howe ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 LANGUAGE=en Signal: 11 SourcePackage: beagle StacktraceTop: ?? () ?? () ?? () ?? () ?? () Uname: Linux the-nemisis 2.6.20-9-generic #2 SMP Sun Feb 25 22:59:06 UTC 2007 x86_64 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video ** Affects: beagle (Ubuntu) Importance: Undecided Status: Unconfirmed -- [apport] IndexHelper.exe crashed with SIGSEGV https://launchpad.net/bugs/90921 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79484] syslog
syslog attached ** Attachment added: "/var/log/syslog" http://librarian.launchpad.net/5765031/syslog -- The Installer Crashed https://launchpad.net/bugs/79484 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79484] The Installer Crashed
Public bug reported:
Binary package hint: ubiquity
When first going into screen 7 ("How do you want to configure your disk
space?"), the installer announces that it's attempting to launch a
partitioning program, hangs for a few seconds, then crashes. If it
helps, I'm trying to install xubuntu Herd 2 onto a dual-booting machine,
that already has xubuntu 6.10 on it, with /home/ on a reiser partition
and everything else (i.e. /) on an XFS partition (I'd lilke to keep
/home and re-format and install into the XFS partition where / currently
lives).
Here's the trackback:
Traceback (most recent call last):
File "/usr/lib/ubiquity/bin/ubiquity", line 185, in ?
main()
File "/usr/lib/ubiquity/bin/ubiquity", line 180, in main
install(args[0])
File "/usr/lib/ubiquity/bin/ubiquity", line 56, in install
ret = wizard.run()
File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 310, in run
self.process_step()
File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 867, in process_step
self.process_autopartitioning()
File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 922, in
process_autopartitioning
choice = self.get_autopartition_choice()[0]
File "/usr/lib/ubiquity/ubiquity/frontend/gtkui.py", line 1620, in
get_autopartition_choice
raise AssertionError, "no active autopartitioning choice"
AssertionError: no active autopartitioning choice
I notice in the above the mentioning of autopartitioning; it may be
pertinent to note that at no point does it ask me if I want to
autopartition, or set my partitions up manually, or any of the other
usual choices: it just launches right into the partitioning tool.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
The Installer Crashed
https://launchpad.net/bugs/79484
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
