[Bug 999957] Re: Inconsistency detected by ld.so:
In X3:Reunion I get the game to work by deleting the following libraries from $X3/lib/lib1, so it takes the system provided ones libSDL-1.2.so.0 libgcc_s.so.1 libm.so.6 libogg.so.0 libopenal.so.1 libsndfile.so.1 libstdc++.so.6 libz.so.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/57 Title: Inconsistency detected by ld.so: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/57/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 295266] Re: KDE doesn't honor root certs chosen by ca-certificates
https://bugs.kde.org/show_bug.cgi?id=162485 ** Bug watch removed: KDE Bug Tracking System #162485 https://bugs.kde.org/show_bug.cgi?id=162485 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde4libs in Ubuntu. https://bugs.launchpad.net/bugs/295266 Title: KDE doesn't honor root certs chosen by ca-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/295266/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 295266] Re: KDE doesn't honor root certs chosen by ca-certificates
You ARE (one of the) maintainer(s), right? How are you tracking this issue now, if you don't know if it's in KDE's tracker? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/295266 Title: KDE doesn't honor root certs chosen by ca-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/295266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 295266] Re: KDE doesn't honor root certs chosen by ca-certificates
Is this bug then triaged into KDE's bug tracker? If you want to defer it to KDE upstream, please at least provide a link to the upstream bug # -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/295266 Title: KDE doesn't honor root certs chosen by ca-certificates To manage notifications about this bug go to: https://bugs.launchpad.net/kdelibs/+bug/295266/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49228] Re: kscreensaver-xsavers installed but screensavers from xscreensaver-gl missing
Also, these xscreensaver hacks are missing in kscreensaver-xsavers- extra: $ for i in * ; do [[ -f /usr/share/kde4/services/ScreenSavers/$i.desktop ]] || echo $i ; done companioncube hilbert ljlatest popsquares rubikblocks surfaces tronbit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/49228 Title: kscreensaver-xsavers installed but screensavers from xscreensaver-gl missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeartwork/+bug/49228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49228] Re: kscreensaver-xsavers installed but screensavers from xscreensaver-gl missing
still present in Precise -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdeartwork in Ubuntu. https://bugs.launchpad.net/bugs/49228 Title: kscreensaver-xsavers installed but screensavers from xscreensaver-gl missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeartwork/+bug/49228/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 948235] Re: Intel wireless still randomly drops connection
** Changed in: linux (Ubuntu Precise) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/948235 Title: Intel wireless still randomly drops connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/948235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 898370] Re: ubuntu hangs during upstart boot, ie no sysinit is executed
I hit a similar issue, although it isn't actually related to plymouth. In my case I had a few network devices marked as auto in /etc/network/interfaces, including one that wasn't always present. The ifup -a called in /etc/init/networking.conf waits a long time on these interfaces and eventually fails. But because a signal is not emitted before ifup ends, it triggers /etc/init/failsafe-boot.conf to wait until all network devices are up, which takes quite a while. I marked these devices 'allow-hotplug' and my boot is back to normal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/898370 Title: ubuntu hangs during upstart boot, ie no sysinit is executed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/898370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601536] Re: KDE 4.5 RC: Login Manager forgets user name
On a clean install of kubuntu 11.10 I have not seen this problem -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/601536 Title: KDE 4.5 RC: Login Manager forgets user name To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/601536/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 366967] Re: ifupdown-udev integration should be thought-out more thoroghly
I'm willing to do that. I have done the upstart specifics of resolvconf over at bug #448095, and have made some improvements to resolvconf itself that can be beneficial to debian as well (basically factoring out hardcoded paths in /etc/resolvconf/*.d scripts and delegating those to the /sbin/resolvconf script, as well as consolidating initialisation into /sbin/resolvconf). It's all there at bug #448095, and I;m willing to discuss those changes with you to see how we can make it more robust on both Ubuntu and Debian. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/366967 Title: ifupdown-udev integration should be thought-out more thoroghly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/366967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366967] Re: ifupdown-udev integration should be thought-out more thoroghly
upstart configuration is already done. Also packaging and patches are available See Bug #448095 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/366967 Title: ifupdown-udev integration should be thought-out more thoroghly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/366967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366967] Re: ifupdown-udev integration should be thought-out more thoroghly
You could also try the PPA mentioned in comment 39 (has lucid packages), then read comment 83. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/366967 Title: ifupdown-udev integration should be thought-out more thoroghly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/366967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366967] Re: ifupdown-udev integration should be thought-out more thoroghly
The workaround in dupe bug #448095 might still work.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/366967 Title: ifupdown-udev integration should be thought-out more thoroghly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/366967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 755658] Re: kded4 consumes 100% CPU
Same on i386 natty, booting from USB HDD, seen with both FOSS nvidia video driver and binary driver. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde4libs in Ubuntu. https://bugs.launchpad.net/bugs/755658 Title: kded4 consumes 100% CPU -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Jürgen, I installed your deb, but it fails to create the /var/run/resolvconf directory. Also the /etc/resolv.conf symlink still points to /etc/resolvconf/run/resolv.conf output of dpkg -i : Preparing to replace resolvconf 1.46ubuntu1 (using resolvconf_1.46ubuntu1ppa1_all.deb) ... Unpacking replacement resolvconf ... Setting up resolvconf (1.46ubuntu1ppa1) ... Installing new version of config file /etc/resolvconf/update.d/libc ... touch: cannot touch `/var/run/resolvconf/enable-updates': No such file or directory Processing triggers for man-db ... Processing triggers for ureadahead ... -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Ok my bad :) I never thought of the /etc/init.d initscripts as 'config' files (and I guess no package marks them as such) so I extended this assumption to the upstart scripts too.. Never really used the '-s' option, thanks for the tip. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
I'm talking about the actual package Anders. Apparently the package contents are incorrect at your [1] link. $ dpkg -l | grep resolvconf ii resolvconf 1.46ubuntu1 name server information handler $ apt-cache showpkg resolvconf Package: resolvconf Versions: 1.46ubuntu1 (/var/lib/apt/lists/nl.archive.ubuntu.com_ubuntu_dists_maverick_universe_binary-amd64_Packages) (/var/lib/dpkg/status) $ dpkg -L resolvconf | grep /etc/init/ /etc/init/resolvconf.conf -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
I'm talking about the actual package Anders. Apparently the package contents are incorrect at your [1] link. $ dpkg -l | grep resolvconf ii resolvconf 1.46ubuntu1 name server information handler $ apt-cache showpkg resolvconf Package: resolvconf Versions: 1.46ubuntu1 (/var/lib/apt/lists/nl.archive.ubuntu.com_ubuntu_dists_maverick_universe_binary-amd64_Packages) (/var/lib/dpkg/status) $ dpkg -L resolvconf | grep /etc/init/ /etc/init/resolvconf.conf -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Ehh? Changelog of resolvconf doesn't match reality? Or am I looking in the wrong spot? https://code.launchpad.net/~ubuntu- branches/ubuntu/maverick/resolvconf/maverick * Merge from debian unstable (LP: #605116), remaining changes: - bin/resolvconf: + fail with non-zero exit code when /etc/resolv.conf is not a symlink. - debian/postinst: + use default /var/run. + make sure all run files are sent to /var/run, not /lib/init/rw + update regex to check that /var/run is a tmpfs (LP: #386822) + fix typo in comments - debian/rules: + don't install the init script in runlevels 0 and 6. - debian/postrm: + remove /var/run/resolvconf, not /lib/init/rw/resolvconf + also purge /var/run/resolvconf/interface -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
I just upgraded one of my systems to Maverick, and the bug seems to be solved out-of-the-box there. However, it seems that they just dropped in the upstart script from this bug without much thinking, resulting in somewhat of a mutant resolvconf, because a) the upstart script assumes the modified /sbin/resolvconf from this bug, i.e. it gets called with -r -i --enable-updates --dsiable-updates options, but the provided /sbin/resolvconf is not aware of these options. b) there's a link to start resolvconf from /etc/rcS.d, while there's also an upstart script (?!). The fact that /etc/init.d/resolvconf is 'upstardized' probably prevents it from doing double initialisation, but the link from /etc/rcS.d is not necessary. Third, resolvconf's data has been moved again back to /etc/resolvconf/run, forcing the need for a writable rootfs. So, it works at boot, but there's no enabling/disabling updates (start/stop resolvconf service) and no initialisation of the volatile directory structure by /sbin/resolvconf itself. This directory structure is probably instead prepared during install by the packaging scripts. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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
Re: [Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
My apologies, I have to backtrack on my prev statement. I thought to have read that on LWN some time in the past, but I cannot find such statement anymore through google. Fact is, that Debian hasn't moved to upstart OR systemd (or initng for that matter) yet, even in unstable, and is using insserv (optional) to parallelize the boot sequence. They are still contemplating which direction to take. see http://wiki.debian.org/LSBInitScripts/DependencyBasedBoot and http://lists.debian.org/debian-devel-announce/2009/09/msg3.html and the most recent announcement http://lists.debian.org/debian-devel-announce/2010/05/msg9.html .. where upstart is described as 'the most promising candidate'. Again, sorry for the confusion :) On Monday 27 September 2010 11:52:48 you wrote: > Isn't Debian still planning on moving to upstart? If so that would be a > major vote of confidence and would guarantee upstart sticks around for a > while longer. > > systemd looks very neat. That both RedHat and OpenSUSE are moving to > adopt it is telling but I don't think it's very likely Ubuntu will give > up upstart any time soon. More likely we'll see some borrowing of code > and ideas. FWIW, SysVinit compatibility is the highest on my wishlist. > > OTOH, if Debian decide to move to systemd all bets are off. In that case > I hope Ubuntu does the right thing and chucks upstart out rather than > increase Ubuntu's divergence from the rest of the Linux world. > > -- > resolvconf starts after ifupdown, does not pick the dns-nameserver and > dns-search lines up from /etc/network/interfaces > https://bugs.launchpad.net/bugs/448095 > You received this bug notification because you are a direct subscriber > of the bug. > -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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
Re: [Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
On Wednesday 15 September 2010 19:27:47 Liraz wrote: > Many thanks to everyone who helped track down this regression, which > effected TurnKey Linux users of the new TurnKey Core Lucid-based beta as > well: > > https://bugs.launchpad.net/turnkeylinux/+bug/596560 > > IMHO, for desktop usage upstart has great potential. But for servers > it's a net loss. Booting a few seconds faster doesn't matter as much as > stability and simplicity. I just wish there was some way to save all of > this asynchronous cleverness for the desktop. In a few years once Ubuntu > and Debian transition fully to upstart we should be OK, but now it's > ugly out there. Hmm I'm starting to doubt that, since many distributions are moving to systemd, and none except Ubuntu (and derivatives) to upstart. This will likely mean that most upstream projects will not take upstart into consideration, so Ubuntu alone will have to maintain it. If this bug is any indication.. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Fabrice, can you at least add an explanation why you unassigned MOTU? Do you mean this bug will be a WONTFIX? -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
@Simon: Hopefully Debian will pickup the changes that cleanup the hardcoded paths, but as I found out they don't use upstart, so those parts will be useless to them. So we're stuck with MOTU :) If I find the time I'll take another look at the packaging scripts, so at least the symlink setup works more reliably.. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Why not just install Simon's package? -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Since I haven't been looking at this bug for a while, I'll just dump my ideas of what IMO should be done in the postinst (and maybe other) package scripts, before I forget them. There's a couple of situations that should be handled: a) installing resolvconf while being in a non-resolvconf state b) upgrading resolvconf that has it's data in another place than the new resolvconf expects it to be (NOTE: which isn't necessarily /lib/init/rw! It's actual location is defined in /etc/default/resolvconf) In situation A, the problem is that resolvconf doesn't have the information yet to populate resolv.conf, so it should not be activated until reboot, or at least until networking is restarted. It's of course possible to already set up the right /etc/resolv.conf symlink, but the active /etc/resolv.conf should be copied into resolvconf's symlink target file verbatim, and should not be re-generated by resolvconf (possibly by implicitly disabling updates). This is a problem that already exists with the 'official' resolvconf, so it's not a new problem. In situation B I think we should copy the 'interfaces' folder from the old location over to the new location, maybe in combination with some validity checks to see if the information there matches the active network interfaces. The place of the old location might be deduced from the /etc/resolv.conf symlink, and/or from the old default location under /var. Also maybe cleanup the files at the old location. If I missed any other situations that might give rise to problems, please add them to this bugreport! -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
I just upgraded to lucid and installed your PPA package. Of course I forgot to check the situation before installing your PPA package, but anyway, I ended up with a different /etc/resolv.conf link. A quick check reveals that the postinst script in the deb is (re)creating the link to /etc/resolvconf/run. In the top of postinst however it is said that /lib/init/rw is now used, but it seems the rest of the script doesn't agree. Also in postinst is some initialization of the resolvconf directories that should now be done by /sbin/resolvconf. Anyway, I restored the link and everything works as it should, thanks! -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Thanks Simon for packaging this for Lucid, much appreciated. My currently installed resolvconf package notes the following contacts as maintainers: Maintainer: Ubuntu MOTU Developers Original-Maintainer: resolvconf maintainers So... you could try sending a notification to the MOTU devs, but they should have been made aware through this launchpad system already. The whole MOTU thing looks like a catchall anyway, so I think resolvconf in Ubuntu is just a Debian copypaste job. They should rename to COTU (Copy Of The Upstream). I think you'll have more luck contacting the debian maintainer... -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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
Re: [Bug 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Yeah I'm actually stunned that such a design failure is not acted upon by Ubuntu. Guess they just capitalize on the work done by Debian, without having to do the hard work of actually maintaining a distribution. However this bug MUST sting on servers and 'old-school' people that use /etc/network/interfaces instead of NetworkManager, not to mention all the HOWTOs on the net that suggest solutions involving /etc/network/interfaces. Just apply the new versions of resolvconf files attached to the bug and your problems will be gone, at least until the upgrade to 10.04 :-/ I myself am moving to Debian ASAP grtz, Sander On Sunday 07 February 2010 10:25:55 you wrote: > Just to say I have this bug too. :( > > Symptom: > > After a reboot, /etc/resolv.conf contains only this: > > $ cat /etc/resolv.conf > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE > OVERWRITTEN nameserver 127.0.0.1 > nameserver 10.18.4.3 > nameserver 10.18.4.1 > > There is no search domain, yet I specified it in /etc/network/interfaces > as follows: > > dns-nameservers 10.18.4.3 10.18.4.1 > dns-search blah.co.uk fudd.co.uk > > > However, if I now issue the following command : > > $ sudo /etc/init.d/networking restart > > It fixes /etc/resolv.conf, as per this: > > $ cat /etc/resolv.conf > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE > OVERWRITTEN nameserver 127.0.0.1 > search blah.co.uk fudd.co.uk > nameserver 10.18.4.3 > nameserver 10.18.4.1 > > Can't wait till this is fixed. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 507405] Re: unplugging/removing network device fails
for keywords sake : solves hotplug of network device, be it usb, pcmcia, firewire etc -- unplugging/removing network device fails https://bugs.launchpad.net/bugs/507405 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 507405] [NEW] unplugging/removing network device fails
Public bug reported: Binary package hint: ifupdown There's a typo in the event name in /etc/init/network-interface.conf stop on net-device-removed INTERFACE=$INTERFACE should be stop on net-device-remove INTERFACE=$INTERFACE ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- unplugging/removing network device fails https://bugs.launchpad.net/bugs/507405 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 130437] Re: udev rule can fail to run ifdown, break reinserting device
hmm and now I cannot reproduce anymore :-Z must be lack of coffee.. ** Changed in: ifupdown (Ubuntu) Status: Confirmed => Fix Released -- udev rule can fail to run ifdown, break reinserting device https://bugs.launchpad.net/bugs/130437 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 130437] Re: udev rule can fail to run ifdown, break reinserting device
yeah I just found out Karmic has a typo in /etc/init/network- interface.conf stop on net-device-removed INTERFACE=$INTERFACE should be stop on net-device-remove INTERFACE=$INTERFACE Furthermore, the DRIVERS var is not filled when the device gets plugged (add action), resulting in an infinite amount of entries in /etc/udev/rules.d/70-persistent-net.rules (because the device doesn't match the dynamically generated rule there) ** Changed in: ifupdown (Ubuntu) Status: Fix Released => Confirmed -- udev rule can fail to run ifdown, break reinserting device https://bugs.launchpad.net/bugs/130437 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 130437] Re: udev rule can fail to run ifdown, break reinserting device
yeah I just found out Karmic has a typo in /etc/init/network- interface.conf stop on net-device-removed INTERFACE=$INTERFACE should be stop on net-device-remove INTERFACE=$INTERFACE Furthermore, the DRIVERS var is not filled when the device gets plugged (add action), resulting in an infinite amount of entries in /etc/udev/rules.d/70-persistent-net.rules (because the device doesn't match the dynamically generated rule there) -- udev rule can fail to run ifdown, break reinserting device https://bugs.launchpad.net/bugs/130437 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 130437] Re: udev rule can fail to run ifdown, break reinserting device
yeah I just found out Karmic has a typo in /etc/init/network- interface.conf stop on net-device-removed INTERFACE=$INTERFACE should be stop on net-device-remove INTERFACE=$INTERFACE Furthermore, the DRIVERS var is not filled when the device gets plugged (add action), resulting in an infinite amount of entries in /etc/udev/rules.d/70-persistent-net.rules (because the device doesn't match the dynamically generated rule there) -- udev rule can fail to run ifdown, break reinserting device https://bugs.launchpad.net/bugs/130437 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Yes I thought that too, Universe is not the place for resolvconf. But anyway, it seems no one from Ubuntu is interested in this bug? -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
** Changed in: resolvconf (Ubuntu) Assignee: (unassigned) => MOTU (motu) -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
ok, time for a full checklist :) - update /sbin/resolvconf from bug attachment - update /etc/resolvconf/update.d/libc from bug attachment - install /etc/init/resolvconf.conf from bug attachment - remove /etc/rcS.d/S07resolvconf - make sure /etc/resolv.conf symlinks to /lib/init/rw/resolvconf/resolv.conf vpn or tunnelling should work as good as before. Nothing has changed for 'late' connections. debugging is a bit hard, but you can see the non-zero exit code if you boot in rescue mode. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 340071] Re: /etc/rcS.d/S07resolvconf is too early
see also #448095 -- /etc/rcS.d/S07resolvconf is too early https://bugs.launchpad.net/bugs/340071 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Found one more tiny bug. fixed it and replaced /sbin/resolvconf attachment. ** Attachment added: "/sbin/resolvconf" http://launchpadlibrarian.net/37215643/resolvconf ** Attachment removed: "replacement for /sbin/resolvconf" http://launchpadlibrarian.net/37141756/sbin.resolvconf -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Did you redownload the /sbin/resolvconf replacement? Can you confirm there are no differences between your copy and the attachment? Because you report the same error the first /sbin/resolvconf replacement I posted had, and I cannot reproduce your current error with the current one. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
** Attachment removed: "replacement for /sbin/resolvconf" http://launchpadlibrarian.net/37130195/sbin.resolvconf ** Attachment removed: "resolvconf.conf" http://launchpadlibrarian.net/37105983/resolvconf.conf -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
You should use the /sbin/resolvconf from #17. I made a stupid mistake in the one I posted first. There's no need to create /lib/init/rw/resolvconf/interface by hand. It should be created at boot, or by calling /sbin/resolvconf -i as root. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
but still, this is probably not the bug you suffer from.. -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
resolvconf.conf should be saved in /etc/init -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
** Attachment added: "new replacement for /sbin/resolvconf" http://launchpadlibrarian.net/37141756/sbin.resolvconf -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
** Attachment added: "replacement for /etc/resolvconf/update.d/libc" http://launchpadlibrarian.net/37130232/etc.resolvconf.update.d.libc -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
** Attachment added: "replacement for /sbin/resolvconf" http://launchpadlibrarian.net/37130195/sbin.resolvconf -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Ok I made the upstart script 'restartable', and unified more hardcoded paths into /sbin/resolvconf - the initialisation of the rundir can now be forced with /sbin/resolvconf -i, and is automatically done by the upstart script when no valid structure is found - starting and stopping the service now sets the enabled/disabled state via /sbin/resolvconf. - triggering an update is now only done using /sbin/resolvconf -u - the rundir can now be queried using /sbin/resolvconf -r So basically this solves the bug, and also cleans up the scattered resolvconf initialisation There are probably other scripts in /etc/resolvconf/update.d that still need RW access to other parts of the filesystem, but these updates can be done later in the bootprocess, e.g. calling a resolvconf -u before bind is started, or after /var becomes writable or something similar. I so far only tested the lifecycle of the libc resolver. ** Attachment added: "resolvconf.conf" http://launchpadlibrarian.net/37130179/resolvconf.conf -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
q.dinar, probably not the same bug, since resolving works for you with ping and host -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Jürgen, you mean this should be the case in 9.10 or 10.04 ? -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Hmm yeah I wasn't really clear in my prev post. It definately obsoletes the old sysv init script, which should be removed. The initialisation part is the most essential and moved to the upstart script. The other actions on the init script are really nothing more than calling (or not) 'update' on resolvconf, but as you can see from /sbin/resolvconf and /etc/init.d/resolvconf there is duplicated code there (and should all be moved to /sbin/resolvconf). But you are right about the 'update -i', that should be added to the upstart script at initialisation. You are also right about the difference in the old init script about boot-time start and service-restart later. A restart on the old initscript merely calls update. But since I know hardly any upstart specifics I don't know how to define the difference between init() and start() precisely. The move to /lib/init/rw makes the difference less important though, since /lib/init/rw is clean after each boot, since it's not persistent. When using /etc/resolvconf/run you might encounter leftovers from previous boots, but with /lib/init/rw we could just create the resolvconf structure if it's not there yet, and have subsequent calls to stop/start/restart mimic the old initscript behaviour. I can make a more complete upstart script if anyone's interested? -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
oh and symlink your /etc/resolv.conf to /lib/init/rw/resolvconf/resolv.conf ! -- resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces https://bugs.launchpad.net/bugs/448095 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 448095] Re: resolvconf starts after ifupdown, does not pick the dns-nameserver and dns-search lines up from /etc/network/interfaces
Hi,
I made an upstart script, like Scott suggested, which initialises the
resolvconf directory structure. I have it start pre-udev, so it's sure
to fire before ifup. It replaces the sysv link in rcS.d, but I also made
some changes to resolvconf itself, basically I moved the resolvconf run
directory to /lib/init/rw/, to have the earliest available writable
filesystem from the start of the boot process.
Anyway, the upstart script is attached, and put the following lines in
/sbin/resolvconf
[ -e /etc/default/resolvconf ] && . /etc/default/resolvconf
RUN_DIR=${RESOLVCONF_RUNDIR:=/lib/init/rw/resolvconf}
(uncomment the old RUN_DIR line of course)
and in /etc/resolvconf/update.d/libc :
[ -e /etc/default/resolvconf ] && . /etc/default/resolvconf
DYNAMICRSLVCNFFILE="${RESOLVCONF_RUNDIR:=/lib/init/rw/resolvconf}/resolv.conf"
(again uncomment the old var)
** Attachment added: "resolvconf.conf"
http://launchpadlibrarian.net/37105983/resolvconf.conf
--
resolvconf starts after ifupdown, does not pick the dns-nameserver and
dns-search lines up from /etc/network/interfaces
https://bugs.launchpad.net/bugs/448095
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 414251] Re: Karmic: MD RAID doesn't work
I had the same problem when upgrading to karmic RC1 My setup : /dev/sd[ab]1 - software raid1 /boot /dev/sd[ab]5 - software raid1 LVM vg /dev/sd[ab]6 - software raid0 LVM vg root, swap, tmp are on the LVM volumes The initrd dropped me to a shell at boot. The cause seems to be dmraid (fakeraid), because when I removed it (using a livecd) and regenerated the initrd I could boot again. If dmraid is installed and present in the initrd there are only /dev/sd[ab] device nodes under /dev, no partition device nodes, so it seems dmraid (fakeraid) claims the disks before mdadm (softraid) can claim them. Possibly useful information: - I don't know if I had dmraid installed under Jaunty. Probably not. - I have an nvidia chipset, fakeraid disabled -- Karmic: MD RAID doesn't work https://bugs.launchpad.net/bugs/414251 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 286565] Re: error with gcc-4.3 compilation: "/usr/include/bits/fcntl2.h:51: error: call to '__open_missing_mode' declared with attribute error"
Hmm spoke too soon. I downgraded to 1ubuntu9 but the problem still occurs. Will try with even older versions, when I find the time. -- error with gcc-4.3 compilation: "/usr/include/bits/fcntl2.h:51: error: call to '__open_missing_mode' declared with attribute error" https://bugs.launchpad.net/bugs/286565 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 286565] Re: error with gcc-4.3 compilation: "/usr/include/bits/fcntl2.h:51: error: call to '__open_missing_mode' declared with attribute error"
Hi, I can confirm this with building gcc-native of OpenEmbedded. (Here openembedded builds a native crosscompiler using the system compiler, gcc 4.3.2-1ubuntu10 in this case) : /usr/include/bits/fcntl2.h:51: error: call to '__open_missing_mode' declared with attribute error: open with O_CREAT in second argument needs 3 arguments This problem appeared after upgrading to 1ubuntu10 version and did not occur with 1ubuntu9 ** Changed in: gcc-4.3 (Ubuntu) Status: New => Confirmed -- error with gcc-4.3 compilation: "/usr/include/bits/fcntl2.h:51: error: call to '__open_missing_mode' declared with attribute error" https://bugs.launchpad.net/bugs/286565 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 222504] [NEW] fusesmb missing from exclusions in /etc/updatedb.conf
Public bug reported: Binary package hint: mlocate PRUNEFS variable in /etc/updatedb.conf should include 'fusesmb' in order to avoid scanning the entire samba network ** Affects: mlocate (Ubuntu) Importance: Undecided Status: New -- fusesmb missing from exclusions in /etc/updatedb.conf https://bugs.launchpad.net/bugs/222504 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 219953] Re: twinkle crashes when dialling out
apparently this is caused by ALSA. I changed my 'asym' device definition in /etc/asound.conf and now it works. Somehow twinkle did not detect a sound device problem but crashed instead.. -- twinkle crashes when dialling out https://bugs.launchpad.net/bugs/219953 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 219953] Re: twinkle crashes when dialling out
additional info: twinkle crashes immediately when dialing an extension on an asterisk server and then pressing the dial button. When dialling a direct connection to another sip client, twinkle crashes when the other side picks up. -- twinkle crashes when dialling out https://bugs.launchpad.net/bugs/219953 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 219953] [NEW] twinkle crashes when dialling out
Public bug reported: Binary package hint: twinkle KCrash: Application 'twinkle' crashing... twinkle: userintf.cpp:2141: virtual void t_userintf::lock(): Assertion `!is_prohibited_thread()' failed. Unable to start Dr. Konqi This happens with twinkle 1.1-2build2_i386 under Hardy ** Affects: twinkle (Ubuntu) Importance: Undecided Status: New -- twinkle crashes when dialling out https://bugs.launchpad.net/bugs/219953 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 109211] Re: feisty doesn't work with external CD writers anymore
I can confirm that the workaround from Wenzhuo Zhang solves my problem with burning. However, the problem manifested itself in a different way. I have an internal PHILIPS DVD+/-RW SDVD8441 dvd writer device, and the chipset is ICH6 (also using (ata_)piix driver). Burning a CD does not immediately fail, but it usually fails after 100-200MB of data is written. I had no problems adding the old ATA drivers to the initial ramdisk, but people should check that grub (root=UUID=...) and /etc/fstab use UUIDs for identifying the filesystems, otherwise this operation could render the system unbootable. ** Changed in: linux-source-2.6.20 (Ubuntu) Status: New => Confirmed ** Tags added: cdrw piix -- feisty doesn't work with external CD writers anymore https://bugs.launchpad.net/bugs/109211 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
