[Bug 94941] Re: [apport] frontend crashed with SIGSEGV in xcall_QGroupBox()
I can't reproduce it as I don't think it would be possible to gobble the exact same configuration together as I had when this happened. So I won't be able to provide any more informatione, especially no stack trace. As I seem to be the only one with this problem, I thinks it is safe to close this bug. Thx. -- [apport] frontend crashed with SIGSEGV in xcall_QGroupBox() https://bugs.launchpad.net/bugs/94941 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94941] Re: [apport] frontend crashed with SIGSEGV in xcall_QGroupBox()
** Attachment added: "CoreDump.gz" http://librarian.launchpad.net/6900191/CoreDump.gz ** Attachment added: "Dependencies.txt" http://librarian.launchpad.net/6900192/Dependencies.txt ** Attachment added: "ProcMaps.txt" http://librarian.launchpad.net/6900193/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://librarian.launchpad.net/6900194/ProcStatus.txt ** Attachment added: "Registers.txt" http://librarian.launchpad.net/6900195/Registers.txt ** Attachment added: "Stacktrace.txt" http://librarian.launchpad.net/6900196/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://librarian.launchpad.net/6900197/ThreadStacktrace.txt -- [apport] frontend crashed with SIGSEGV in xcall_QGroupBox() https://launchpad.net/bugs/94941 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94941] [apport] frontend crashed with SIGSEGV in xcall_QGroupBox()
Public bug reported: suddenly, while having adept updating in the background and using akregator, I was asked to enter my root password (kdesu) and then network manager crashed, my (dhcp assigned) ip adress vanished and the network connection went down. After /etc/init.d/networking restart eversahting worked fine again ProblemType: Crash Architecture: i386 Date: Fri Mar 23 00:09:22 2007 Disassembly: 0x22: DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/share/debconf/frontend InterpreterPath: /usr/bin/perl Package: debconf 1.5.11ubuntu1 PackageArchitecture: all ProcCmdline: /usr/bin/perl -w /usr/share/debconf/frontend /var/lib/dpkg/tmp.ci/preinst upgrade 1:7.2-0ubuntu1 ProcCwd: / ProcEnviron: PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: debconf StacktraceTop: ?? () xcall_QGroupBox () from /usr/lib/libsmokeqt.so.1 ?? () from /usr/lib/perl5/auto/Qt/Qt.so ?? () ?? () Uname: Linux SIDIOUS 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux UserGroups: ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- [apport] frontend crashed with SIGSEGV in xcall_QGroupBox() https://launchpad.net/bugs/94941 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899481] Re: installer crashes; bug report cannot be sent
Just to clarify: I wasn't trying to put Ubuntu on a separate partition or to install it alongside Windows. I only used Windows because I couldn't find another way to create an install USB key for Ubuntu. Unetbootin is not available for PowerPC machines, even running Linux, and I was trying to install onto a new intel machine which therefore didn't have an existing working OS to use Unetbootin in. I therefore used Unetbootin on a machine running XP in my workplace. I'm no longer trying to install Ubuntu at all on anything. I've tried installing Ubuntu on a total of 3 machines to date and not one has been a success. (One install failure described here; one never actually launched the installer; one did install but was unbearable to use with crippled graphics.) I'm currently running Arch, Debian testing and Debian stable on these machines and they all work fine. I was not therefore seeking support. I was just reporting a possible bug. If you think it was just a corrupt download, fine. End of story. Case closed. :) I still think posting checksums on the installation page would be a good idea. This is something I will always check if I can find them. Similarly signatures. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/899481 Title: installer crashes; bug report cannot be sent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/899481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883585] Re: Kubuntu 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status
Is this connected to bug # 647137 for Debian? I filed that and the report is at http://lists.alioth.debian.org/pipermail/pkg-cups- devel/2011-October/009738.html">http://lists.alioth.debian.org/pipermail /pkg-cups-devel/2011-October/009738.html. That also concerns failures after updating cups and affects the use of multiple printers using multiple ways of connecting, multiple drivers and multiple protocols. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883585 Title: Kubuntu 11.10 -- Network/Local Printers found but cannot print - Unable to get printer status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/883585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899481] Re: installer crashes; bug report cannot be sent
Thanks for getting back to me. I would be happy to do this if it might help. I am not sure how the instructions apply to my case, though. I created the USB key with unetbootin. Do you know where it would have stored the downloaded image on a Windows XP machine? Assuming you can tell me that, can I safely copy the file elsewhere to check the sum rather than trying to do it in Windows or would I need to do it in place for any reason? Please note that I will probably need quite detailed instructions to locate the file in Windows. Provided I can then copy it elsewhere to check, it is no problem. I just know absolutely nothing about how Windows works or where it might have put things. [The only reason I used Windows was because I couldn't find another way to create a live USB key for Ubuntu.] Please also note that I currently have no intention of running the installer on the same machine again as it would re-erase the EFI partition. Also, if there as insufficient room on the Windows box for the downloaded image, I may have stored it on a second USB key. In that case, I no longer have the image which might have been corrupt. I would also point out that if the download page had given any kind of pointer to the existence of checksums, I would have used these in the first place. I explicitly looked for these and could not find anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/899481 Title: installer crashes; bug report cannot be sent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/899481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899481] [NEW] installer crashes; bug report cannot be sent
Public bug reported: 3 related issues (unrelated issue: why is it so hard to file a bug report? I keep getting documentation telling me it might be a support question!) - Live USB key only works once without manual edit; works multiple times after manual edit - installer run from Live USB key crashes (content of report suggest failure to grep required seed file during copying) - form to submit bug report can be filled out but not sent (clicking on submit button repeatedly has no effect) (also form asks for 2 attachments but allows only 1) Ubuntu 11.10 for amd64 (x86_64) Key created using unetbootin (auto download of iso rather than feeding iso) on Windows XP - current version of unetbootin unless updated in past week; no space set aside for preservation of files across boots Ubuntu can be launched from key once live. After that it is necessary to recreate the key or to edit two config files manually. I did the former once and then the latter. I do not have routine access to a machine capable of running unetbootin except the one I'm trying to put an OS on which doesn't currently have a working OS. Machine is booting UEFI. Ask installer to use pre-created partitions without reformatting. (vfat for EFI system partition just over 200MB is partition 1, no partition 2, partition 4 is about 9G for swap, partition 7, 8, 9, 10 for /usr/local, /, /var, /home respectively. Other partitions not to be used by installer. 7, 8 are about 20G. 9 is about 15G. 10 is probably about 150G or so. Disk is 320G total formatted GPT in gdisk. Choose location: OK. Copying files... Crash. I didn't take too much notice of the bug report content as it was hard to read it as it was and I figured it would be posted online and easy to look at later. But it failed to grep a seed file it needed. Agree to submit bug report. Spend considerable time writing one. Browse to upload syslog. Notice it wants partman but that it is not possible to attach second file. Check report. Hit submit. Hit submit. Etc. Finally give up. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/899481 Title: installer crashes; bug report cannot be sent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/899481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 899481] Re: installer crashes; bug report cannot be sent
Correction: partitioning was done in gnu parted. EFI partition was created in gdisk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/899481 Title: installer crashes; bug report cannot be sent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/899481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 811485] Re: EFI SYSTEM PARTITION should be atleast 100 MiB size and formatted as FAT32, not FAT16
I'm far from confident about this but running Ubuntu's installer on my machine finally allowed me to boot from a GPT partitioned disk. Not immediately because the installer crashed and although it wiped my EFI system partition, it didn't get around to putting anything else in it afterwards. And even when I copied my backup back, the UUIDs didn't match thus causing trouble for my intact install of linux. But at least I could get to a grub prompt after copying my backed up ESP back. That was a huge improvement. And after fixing the UUID, I have a working installation of linux. (Not of Ubuntu, obviously.) As far as I can tell, the only thing Ubuntu's installer did which I didn't do was to use fat16 rather than fat32 to format the partition. I am almost certain that my machine would have remained unbootable if it had used fat32. I found a reference in bug #769669 to a minimum size for the fat32 partition of 256M. That might explain why my machine was not booting. My EFI partition is only 202M. But if that is why, the installer should also insist on a partition which meets that requirement if it switches to fat32 for the EFI partition. My machine has Phoenix SecureCore Tiano firmware. Version 1.14. Reference: https://bbs.archlinux.org/viewtopic.php?pid=1024473#p1024473 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/811485 Title: EFI SYSTEM PARTITION should be atleast 100 MiB size and formatted as FAT32, not FAT16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-efi/+bug/811485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
