[Bug 1891680] Re: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst
Is there an ETA when we can finally do-release-upgrade from 18.04 to 20.04? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891680 Title: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1891680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 582173] [NEW] texlive installation error on karmic-lucid upgrade
Public bug reported: Binary package hint: update-manager Got the following error message on upgrade in kubuntu: subprocess installed post-installation script returned error exit status 1 ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: tex texlive update -- texlive installation error on karmic-lucid upgrade https://bugs.launchpad.net/bugs/582173 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 242869] Re: dnsmasq's dhcp blocked to clients by firestarter
dnsmasq takes care of so many headaches for a small network, this problem was really killing me since firestarter is probably the best gui front-end to iptables I've found. But the above problem was plaguing me and the fix to user-pre above didn't seem to help. In case anyone does what I did, I want to post the solution. I cut and pated the above-line from my browser into the user-pre file and it didn't work. What I finally discovered after banging my head on this one for several days was that the --sport and --dport argument got converted to and en-dash or some such non-ascii character by the browser and were invalid. When you past the above, make sure to change them! I found this by running firestarter --start from the command line, which will echo all the iptables errors to the console. I found several other problems with my firestarter configuration this way as well. For example, I found that it was unable to resolve the hostnames I used in several rules, so they weren't getting into the firewall. I had to hard-code IP addresses instead. I hope this helps someone else. Regards, ded -- dnsmasq's dhcp blocked to clients by firestarter https://bugs.launchpad.net/bugs/242869 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 242869] Re: dnsmasq's dhcp blocked to clients by firestarter
dnsmasq takes care of so many headaches for a small network, this problem was really killing me since firestarter is probably the best gui front-end to iptables I've found. But the above problem was plaguing me and the fix to user-pre above didn't seem to help. In case anyone does what I did, I want to post the solution. I cut and pated the above-line from my browser into the user-pre file and it didn't work. What I finally discovered after banging my head on this one for several days was that the --sport and --dport argument got converted to and en-dash or some such non-ascii character by the browser and were invalid. When you past the above, make sure to change them! I found this by running firestarter --start from the command line, which will echo all the iptables errors to the console. I found several other problems with my firestarter configuration this way as well. For example, I found that it was unable to resolve the hostnames I used in several rules, so they weren't getting into the firewall. I had to hard-code IP addresses instead. I hope this helps someone else. Regards, ded -- dnsmasq's dhcp blocked to clients by firestarter https://bugs.launchpad.net/bugs/242869 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361689] Re: hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices
Patch also worked for me on AMD64. Thanks, Chris. -- hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices https://bugs.launchpad.net/bugs/361689 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361689] Re: hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices
All, Has everyone else been able to work around this issue, or is it just me? Since my jaunty update, I can't get mouse or keyboard with mdadm installed. I was hoping someone would tell me what to do about the libblkid1 dependency in Chris's hal update---at least on amd64---but no traffic here for several days. Chris, any help? Any one else? Does it work on an i386? Regards, -- hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices https://bugs.launchpad.net/bugs/361689 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361689] Re: hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices
Spoke too soon. After installing both Chris's fixed hal and the libblkid1 update above, my AMD64 system failed to boot, pausing about 1/5 of the way through. If I hit Alt-Ctl-Del, I could get the boot to resume but with my / mounted read-only. I suspect something is wrong with the libblkid1 that is causing the problem. Anyone else seeing this? -- hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices https://bugs.launchpad.net/bugs/361689 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361689] Re: hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices
Eric, thanks for confirming. Is your system AMD64 or i386? -- hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices https://bugs.launchpad.net/bugs/361689 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361689] Re: hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices
It's not something I would have thought of on my own, but it appears to be a dependency in the amd .deb hal package you posted above: r...@saturn:/home/ded/Downloads# dpkg -i hal_0.5.12+git20090512-0ubuntu2_amd64.deb (Reading database ... 94344 files and directories currently installed.) Preparing to replace hal 0.5.12~rc1+git20090403-0ubuntu1 (using hal_0.5.12+git20090512-0ubuntu2_amd64.deb) ... * Stopping Hardware abstraction layer hald [ OK ] Unpacking replacement hal ... dpkg: dependency problems prevent configuration of hal: hal depends on libblkid1 (= 2.15~rc2-1ubuntu1); however: Version of libblkid1 on system is 1.41.4-1ubuntu1. dpkg: error processing hal (--install): dependency problems - leaving unconfigured Processing triggers for man-db ... Errors were encountered while processing: hal Is karmic poison? Why the warning? Thanks. -- hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices https://bugs.launchpad.net/bugs/361689 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361689] Re: hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices
Chris et. al., OK, I get it now. karmic is the next release---my bad, just an end user here. Still, is there some repository that has version 2.15 of libblkid1 for jaunty? Would someone please post a link or the sources entry for such a repository? Looks like Chris's fix to hal needs it from somewhere at least on the 64-bit systems. Thanks. -- hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices https://bugs.launchpad.net/bugs/361689 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361689] Re: hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices
Same deal here, except that the fixed hal .deb depends on version 2.15 of libblkid1 which is not available, at least on amd64, in the repositories either. My system is now working (after some painful googling with links) after applying the following: http://launchpadlibrarian.net/26631965/libblkid1_2.15-1ubuntu2_amd64.deb Then applying Chris's patch from above. Gigthanks, Chris. And like everyone else, I think the raid-running world ought to be warned off of Jaunty until this is fixed in the distribution. Regards, ded -- hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling mdraid devices https://bugs.launchpad.net/bugs/361689 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 306401] Re: Brother MFC8840D errors on 1st print job
A me too on this bug. But it's been there at least since Hardy, probably before. Thanks for the report, David. -- Brother MFC8840D errors on 1st print job https://bugs.launchpad.net/bugs/306401 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
