[Bug 943886] [NEW] package postgresql-8.4 8.4.11-0ubuntu0.10.04 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1
Public bug reported: failed to upgrade due to error 1 ProblemType: Package DistroRelease: Ubuntu 10.04 Package: postgresql-8.4 8.4.11-0ubuntu0.10.04 ProcVersionSignature: Ubuntu 2.6.32-39.86-generic 2.6.32.56+drm33.22 Uname: Linux 2.6.32-39-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu Mar 1 10:58:24 2012 ErrorMessage: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) SourcePackage: postgresql-8.4 Title: package postgresql-8.4 8.4.11-0ubuntu0.10.04 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 ** Affects: postgresql-8.4 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/943886 Title: package postgresql-8.4 8.4.11-0ubuntu0.10.04 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/943886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 943886] Re: package postgresql-8.4 8.4.11-0ubuntu0.10.04 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/943886 Title: package postgresql-8.4 8.4.11-0ubuntu0.10.04 failed to install/upgrade: il sottoprocesso vecchio script di post-installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/943886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728593] [NEW] package dahdi-dkms 1:2.2.1 dfsg-1ubuntu2 failed to install/upgrade: dahdi kernel module failed to build.
Public bug reported: Binary package hint: dahdi-linux After restart, my launchpad is all messed up with missing icons e blank spaces. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: dahdi-dkms 1:2.2.1+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-29.58-generic 2.6.32.28+drm33.13 Uname: Linux 2.6.32-29-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Thu Mar 3 18:46:28 2011 ErrorMessage: dahdi kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) PackageArchitecture: all PackageVersion: 1:2.2.1+dfsg-1ubuntu2 SourcePackage: dahdi-linux Title: package dahdi-dkms 1:2.2.1+dfsg-1ubuntu2 failed to install/upgrade: dahdi kernel module failed to build ** Affects: dahdi-linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728593 Title: package dahdi-dkms 1:2.2.1 dfsg-1ubuntu2 failed to install/upgrade: dahdi kernel module failed to build. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 728593] Re: package dahdi-dkms 1:2.2.1 dfsg-1ubuntu2 failed to install/upgrade: dahdi kernel module failed to build.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/728593 Title: package dahdi-dkms 1:2.2.1 dfsg-1ubuntu2 failed to install/upgrade: dahdi kernel module failed to build. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 620313] Re: [hamster plugin] not start tracking tasks
rbertran's patch worked for me. Thanks :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/620313 Title: [hamster plugin] not start tracking tasks -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665217] [NEW] can't close java windows on chat
Public bug reported: Binary package hint: firefox once i've opened a java chat, i can't close the windows i want to. It seems the red X button doesn't work at all and the windos stay opened all the time, untill i close the program firefox one and for all. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.11+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Oct 22 19:02:32 2010 FirefoxPackages: firefox 3.6.11+build3+nobinonly-0ubuntu0.10.10.1 firefox-gnome-support 3.6.11+build3+nobinonly-0ubuntu0.10.10.1 firefox-branding 3.6.11+build3+nobinonly-0ubuntu0.10.10.1 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) ProcEnviron: LANG=it_IT.utf8 SHELL=/bin/bash SourcePackage: firefox ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- can't close java windows on chat https://bugs.launchpad.net/bugs/665217 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 665217] Re: can't close java windows on chat
-- can't close java windows on chat https://bugs.launchpad.net/bugs/665217 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 660899] [NEW] package cacti (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Public bug reported: Binary package hint: cacti i don't know ProblemType: Package Architecture: i386 Date: Thu Oct 14 10:26:17 2010 DistroRelease: Ubuntu 9.10 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 Package: cacti (not installed) ProcVersionSignature: Ubuntu 2.6.31-22.65-generic SourcePackage: cacti Title: package cacti (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Uname: Linux 2.6.31-22-generic i686 ** Affects: cacti (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- package cacti (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 https://bugs.launchpad.net/bugs/660899 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 660899] Re: package cacti (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
-- package cacti (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 https://bugs.launchpad.net/bugs/660899 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 600724] Re: brightness control did not work after latest kernel update
** Also affects: ubuntu Importance: Undecided Status: New ** Changed in: ubuntu Status: New = Invalid -- brightness control did not work after latest kernel update https://bugs.launchpad.net/bugs/600724 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 535424] Re: No stable wireless connections
I have the same first problem related here above! $ lspci | grep Wireless 03:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless Network Adapter (rev 01) $ uname -r 2.6.32-22-generic I have an Acer 5570Z-2607 Ubuntu 10.04 32bits It have started since I've installed Ubuntu version 9.04. At 8ths and 7ths it didn't happen. Thanks! -- No stable wireless connections https://bugs.launchpad.net/bugs/535424 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 407428] Re: worker signal mask inherited by children
Seems like this bug is also happening in 9.04 Jaunty Jackalope since udev is in 141 and my system gets clogged by f**king sshd process with nothing connected to them. -- worker signal mask inherited by children https://bugs.launchpad.net/bugs/407428 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 50430] Re: NIS has problems starting before the network comes up
Johan, unless you use NIS on an laptop I recommend to deinstall network-manager and use the old style /etc/interfaces configuration. At least this works for me. Don't have the respective machine at hand right now, so I'm not 100% sure if it is karmic already but I positively think so. g., fil - Johan Walles johan.wal...@gmail.com schrieb: Has anybody managed to work around this on Karmic? I just upgraded to Karmic, and my previous workaround is no good any more, and I now have to (re)start NIS manually at each boot :-(. Also, the top of the bug page says This bug affects you and one other person. Considering the amount of people subscribed to this that doesn't sound reasonable, please mark the top of the bug page if you're affected! -- NIS has problems starting before the network comes up https://bugs.launchpad.net/bugs/50430 You received this bug notification because you are a direct subscriber of the bug. Status in “autofs” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: New Status in “nis” package in Ubuntu: Confirmed Bug description: Binary package hint: nis in /etc/rcX.d there are the symlinks, but I can not log in with a nis User. If I manually start /etc/init.d/nis from console with a local Account, after that I can log in with an NIS-account on Console and GDM. This Bug appears after Update to Kernel -25. May be NIS starts to early, before the Network is running. To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/50430/+subscribe -- NIS has problems starting before the network comes up https://bugs.launchpad.net/bugs/50430 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs 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
Re: [Bug 50430] Re: NIS has problems starting before the network comes up
Johan, unless you use NIS on an laptop I recommend to deinstall network-manager and use the old style /etc/interfaces configuration. At least this works for me. Don't have the respective machine at hand right now, so I'm not 100% sure if it is karmic already but I positively think so. g., fil - Johan Walles johan.wal...@gmail.com schrieb: Has anybody managed to work around this on Karmic? I just upgraded to Karmic, and my previous workaround is no good any more, and I now have to (re)start NIS manually at each boot :-(. Also, the top of the bug page says This bug affects you and one other person. Considering the amount of people subscribed to this that doesn't sound reasonable, please mark the top of the bug page if you're affected! -- NIS has problems starting before the network comes up https://bugs.launchpad.net/bugs/50430 You received this bug notification because you are a direct subscriber of the bug. Status in “autofs” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: New Status in “nis” package in Ubuntu: Confirmed Bug description: Binary package hint: nis in /etc/rcX.d there are the symlinks, but I can not log in with a nis User. If I manually start /etc/init.d/nis from console with a local Account, after that I can log in with an NIS-account on Console and GDM. This Bug appears after Update to Kernel -25. May be NIS starts to early, before the Network is running. To unsubscribe from this bug, go to: https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/50430/+subscribe -- NIS has problems starting before the network comes up https://bugs.launchpad.net/bugs/50430 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 213574] Re: Autofs fails to start with maps from NIS
*** This bug is a duplicate of bug 50430 *** https://bugs.launchpad.net/bugs/50430 I assume there's a conceptual bug, not to fix in any single package: NetworkManager is basically incompatible with sysV init. This also applies to sysV powered by upstart. Unless a consistent event-driven model is in place NetworkManager may be fine for the occasional network- hopping Laptop but stays bogus on any centrally-managed corporate network. Just don't use it there yet. For the time being dependencies should be fixed: Install nis or kin - purge nwm. Even then: The idea behind nwm is to flexibly handle failures or delay of non-essential services. There's no flexibility in handling missing user-maps or other name-service. On my OSX Desktop I regularly get a login prompt refusing my nis credentials since booting the shell overtook setting up the network. Three failures gave me some early coffe and newspaper befor I realized the cause. The only sensible way here would be to tell the user what we're waiting for. Another package to be hacked. For the new era to dawn we have to look into service dependencies from a higher level. Guess here's the limitation of a per-package bug-tracking approach. And I'd agree to favour wrapping over fixing. Shouldn't be autofs's burden what new concepts nwm or upstart make up. g., fil - Paul Smith psm...@gnu.org schrieb: *** This bug is a duplicate of bug 50430 *** https://bugs.launchpad.net/bugs/50430 On Tue, 2009-10-13 at 18:16 +, Chuck Short wrote: *** This bug is a duplicate of bug 50430 *** https://bugs.launchpad.net/bugs/50430 ** This bug has been marked a duplicate of bug 50430 NIS has problems starting before the network comes up Why has this bug been marked as a duplicate of 50430? 50430 talks about NIS (ypbind) not working properly on NetworkManager enabled systems. That should be fixed for a few releases now, and indeed I haven't seen it on my systems in a while. My suspicion is that the people who are still having trouble are really having problems with NetworkManager not detecting/reporting the network status of their systems properly (saying the network is up when it isn't or vice versa). This bug (213574) is about autofs not working properly on NetworkManager enabled systems. That is basically the same problem, but a completely different package (in fact that's my major complaint about NetworkManager: adding it to your system requires that you go around and hack on each network-aware service on your system, one at a time, to make them compatible with NetworkManager). I've not upgraded to Karmic but I've seen absolutely nothing that leads me to believe anyone has made any effort to enhance autofs, either the daemon itself (a la ypbind) or even just the init scripts, to be NM-aware. Until that happens this bug will not be fixed. What has to happen on a very abstract level is that you can't start autofs until all the services that it utilizes (based on /etc/nsswitch.conf for example) are running, if they are supposed to be started. It's hard because on many systems, /etc/nsswitch.conf lists nis or nisplus as a source for automount, and yet these services are not enabled. On other systems, automount data is taken from LDAP. Other places it comes from flat files. Etc. And remember, by running I don't just mean that the init script has completed. In the brave new world of NetworkManager, having the init script complete does NOT mean that the service is available. It just means that it may _become_ available, sometime later. autofs has to wait until these services are actually active, before it can start. In the old days, with a simple serialized boot process implying that once an init script was complete that service was available, this was simple. Now it's become very tricky indeed. -- Autofs fails to start with maps from NIS https://bugs.launchpad.net/bugs/213574 You received this bug notification because you are a direct subscriber of the bug (via bug 50430). Status in “autofs” package in Ubuntu: New Bug description: Binary package hint: autofs On Ubuntu Hardy with NetworkManager enabled, autofs doesn't work if your maps are distributed by NIS (which is extremely common in corporate environments). In Hardy, NIS is configured to wait for NetworkManager to bring up the interface; it listens on dbus for the network start event and only then will it bind to the NIS server. This is good, I guess, since otherwise NIS can't bind. However, it means that after S18nis starts, unlike a typical system, on Ubuntu NIS is not bound to a server yet. That means when we get to S19autofs and it tries to run ypcat etc. to grab the auto.master and other maps, nothing is printed. That means autofs doesn't come up properly and we have to restart it by hand after the system has successfully booted. I HATE the idea of forcing autofs to start
[Bug 50430] Re: [Bug 213574] Re: Autofs fails to start with maps from NIS
I assume there's a conceptual bug, not to fix in any single package: NetworkManager is basically incompatible with sysV init. This also applies to sysV powered by upstart. Unless a consistent event-driven model is in place NetworkManager may be fine for the occasional network- hopping Laptop but stays bogus on any centrally-managed corporate network. Just don't use it there yet. For the time being dependencies should be fixed: Install nis or kin - purge nwm. Even then: The idea behind nwm is to flexibly handle failures or delay of non-essential services. There's no flexibility in handling missing user-maps or other name-service. On my OSX Desktop I regularly get a login prompt refusing my nis credentials since booting the shell overtook setting up the network. Three failures gave me some early coffe and newspaper befor I realized the cause. The only sensible way here would be to tell the user what we're waiting for. Another package to be hacked. For the new era to dawn we have to look into service dependencies from a higher level. Guess here's the limitation of a per-package bug-tracking approach. And I'd agree to favour wrapping over fixing. Shouldn't be autofs's burden what new concepts nwm or upstart make up. g., fil - Paul Smith psm...@gnu.org schrieb: *** This bug is a duplicate of bug 50430 *** https://bugs.launchpad.net/bugs/50430 On Tue, 2009-10-13 at 18:16 +, Chuck Short wrote: *** This bug is a duplicate of bug 50430 *** https://bugs.launchpad.net/bugs/50430 ** This bug has been marked a duplicate of bug 50430 NIS has problems starting before the network comes up Why has this bug been marked as a duplicate of 50430? 50430 talks about NIS (ypbind) not working properly on NetworkManager enabled systems. That should be fixed for a few releases now, and indeed I haven't seen it on my systems in a while. My suspicion is that the people who are still having trouble are really having problems with NetworkManager not detecting/reporting the network status of their systems properly (saying the network is up when it isn't or vice versa). This bug (213574) is about autofs not working properly on NetworkManager enabled systems. That is basically the same problem, but a completely different package (in fact that's my major complaint about NetworkManager: adding it to your system requires that you go around and hack on each network-aware service on your system, one at a time, to make them compatible with NetworkManager). I've not upgraded to Karmic but I've seen absolutely nothing that leads me to believe anyone has made any effort to enhance autofs, either the daemon itself (a la ypbind) or even just the init scripts, to be NM-aware. Until that happens this bug will not be fixed. What has to happen on a very abstract level is that you can't start autofs until all the services that it utilizes (based on /etc/nsswitch.conf for example) are running, if they are supposed to be started. It's hard because on many systems, /etc/nsswitch.conf lists nis or nisplus as a source for automount, and yet these services are not enabled. On other systems, automount data is taken from LDAP. Other places it comes from flat files. Etc. And remember, by running I don't just mean that the init script has completed. In the brave new world of NetworkManager, having the init script complete does NOT mean that the service is available. It just means that it may _become_ available, sometime later. autofs has to wait until these services are actually active, before it can start. In the old days, with a simple serialized boot process implying that once an init script was complete that service was available, this was simple. Now it's become very tricky indeed. -- Autofs fails to start with maps from NIS https://bugs.launchpad.net/bugs/213574 You received this bug notification because you are a direct subscriber of the bug (via bug 50430). Status in “autofs” package in Ubuntu: New Bug description: Binary package hint: autofs On Ubuntu Hardy with NetworkManager enabled, autofs doesn't work if your maps are distributed by NIS (which is extremely common in corporate environments). In Hardy, NIS is configured to wait for NetworkManager to bring up the interface; it listens on dbus for the network start event and only then will it bind to the NIS server. This is good, I guess, since otherwise NIS can't bind. However, it means that after S18nis starts, unlike a typical system, on Ubuntu NIS is not bound to a server yet. That means when we get to S19autofs and it tries to run ypcat etc. to grab the auto.master and other maps, nothing is printed. That means autofs doesn't come up properly and we have to restart it by hand after the system has successfully booted. I HATE the idea of forcing autofs to start listening on dbus, like someone hacked ypbind to do; it just seems really wrong to have
[Bug 50430] Re: NIS has problems starting before the network comes up
Same old problem on a fresh 9.04. It boils down to: ypbind is tried at S18nis, NetworkManager starts a lot later at S28NetworkManager. IP connectivity often isn't up after S99, at least if using DHCP. The problem disappears after configuring the old way via /etc/network/interfaces , thereby shortcutting NetworkManager. Looks like NM introduced having network only a lot later in the startup process; Should affect other network-dependent services similiarly. ypbind's NM integration does not help at all as long NM isn't yet running while it is started (see ypbind manpage). i.e. -no-dbus does not make any difference here... Fix it by having ypbind started after NM without -no-dbus, or via /etc/network/if-up.d/ to ensure we already have net. In case of NIS passwd this creates the possibility of having a temporarily unfunctional login prompt shown, so some user feedback about network connectivity should be introduced there. The startup sequence currently delivered with nis is generally incompatible with Ubuntu Desktop's reliance on NetworkManager for bringing up IP connectivity. One of three things needs to happen: * rework nis startup sequence + handle possible login deferral, or * return to using /etc/network/interfaces at least for some primary interface, or * move nis from main and regard it unsupported g., Filip Moritz -- NIS has problems starting before the network comes up https://bugs.launchpad.net/bugs/50430 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 50430] Re: NIS has problems starting before the network comes up
** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- NIS has problems starting before the network comes up https://bugs.launchpad.net/bugs/50430 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 174162] Re: cannot bind to YP server under AMD64
*** This bug is a duplicate of bug 152794 *** https://bugs.launchpad.net/bugs/152794 #152794 itself is duplicate of #50430. This one blocks setting it so. Here should point straight to #50430 but it seems like I can't change that. -- cannot bind to YP server under AMD64 https://bugs.launchpad.net/bugs/174162 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 152794] Re: nis daemon fails to attach to domain the first time it is run in Gutsy
this seems a duplicate of #50430. shortcutting NM by configuring your interface the old style in /etc/network/interfaces should solve your problems for the time being. -- nis daemon fails to attach to domain the first time it is run in Gutsy https://bugs.launchpad.net/bugs/152794 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 354588] Re: NIS fails to bind to YP server during boot
*** This bug is a duplicate of bug 50430 *** https://bugs.launchpad.net/bugs/50430 ** This bug has been marked a duplicate of bug 50430 NIS has problems starting before the network comes up -- NIS fails to bind to YP server during boot https://bugs.launchpad.net/bugs/354588 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 50430] Re: NIS has problems starting before the network comes up
** Also affects: autofs (Ubuntu) Importance: Undecided Status: New -- NIS has problems starting before the network comes up https://bugs.launchpad.net/bugs/50430 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 50430] Re: NIS has problems starting before the network comes up
or, solution #4 * add some package legacy-network or the like, that re-introduces /etc/network/interfaces config. Let nis, autofs and the like depend on this one. Traditional unix concepts require having network up early. Don't twist them all, instead satisfy their need. -- NIS has problems starting before the network comes up https://bugs.launchpad.net/bugs/50430 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 182063] Re: Periodic hangs/high cpu usage
I'm unable to reproduce this with 2.6.27-2. Definitely still happens with 2.6.26-*. -- Periodic hangs/high cpu usage https://bugs.launchpad.net/bugs/182063 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 200210] Re: no sound after suspend with snd_hda_intel since 2.6.24-7's alsa-update to 1.0.16
Also affects Samsung R20, another ALC262 chip. model=hippo fixes it here. -- no sound after suspend with snd_hda_intel since 2.6.24-7's alsa-update to 1.0.16 https://bugs.launchpad.net/bugs/200210 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 211427] Re: no sound after suspend/hibernate
*** This bug is a duplicate of bug 200210 *** https://bugs.launchpad.net/bugs/200210 ** This bug has been marked a duplicate of bug 200210 no sound after suspend with snd_hda_intel since 2.6.24-7's alsa-update to 1.0.16 -- no sound after suspend/hibernate https://bugs.launchpad.net/bugs/211427 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 211427] Re: no sound after suspend/hibernate
Confirmed here on the same hardware. Removing and reloading the snd-hda- intel module after resuming from hibernate fixes the issue. This problem is not present when using gutsy kernel, it is a regression since 2.6.22. -- no sound after suspend/hibernate https://bugs.launchpad.net/bugs/211427 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 182063] Re: Periodic hangs/high cpu usage
No change for me in 2.6.24-12 or -13. This also happens on a clean boot, not just after suspend/hibernate. Regarding the other bug, I have never had a boot hang on this machine with a 2.6.24 kernel. The problem only appears after X has started. But this is HPET related. Booting with hpet=disable works fine. -- Periodic hangs/high cpu usage https://bugs.launchpad.net/bugs/182063 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 152772] Re: Random system freeze if multicore processing is enabled on Samsung R20 with Intel Core Duo T2350
*** This bug is a duplicate of bug 182063 *** https://bugs.launchpad.net/bugs/182063 I don't think this is a duplicate of https://bugs.launchpad.net/bugs/182063, because I don't see any of the symptoms described here. Thomas: could you see if booting the gutsy kernel with hpet=disable has any effect? -- Random system freeze if multicore processing is enabled on Samsung R20 with Intel Core Duo T2350 https://bugs.launchpad.net/bugs/152772 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 160260] Re: flac folder missing when browsing audiocd
Same problem here. The flac tab is also missing from the AudioCD settings in kcontrol. Opening that section (kcmshell audiocd) gives the following error: kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/kde3/libaudiocd_encoder_flac.so: undefined symbol: create_audiocd_encoders So it looks like this is a kde bug rather than a problem with flac. -- flac folder missing when browsing audiocd https://bugs.launchpad.net/bugs/160260 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdemultimedia in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 182063] Re: Periodic hangs/high cpu usage
** Attachment added: dmesg.log http://launchpadlibrarian.net/11285713/dmesg.log -- Periodic hangs/high cpu usage https://bugs.launchpad.net/bugs/182063 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 182063] Re: Periodic hangs/high cpu usage
** Attachment added: lspci-vvnn.log http://launchpadlibrarian.net/11285708/lspci-vvnn.log -- Periodic hangs/high cpu usage https://bugs.launchpad.net/bugs/182063 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 182063] Re: Periodic hangs/high cpu usage
** Attachment added: version.log http://launchpadlibrarian.net/11285707/version.log -- Periodic hangs/high cpu usage https://bugs.launchpad.net/bugs/182063 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 182063] Re: Periodic hangs/high cpu usage
** Attachment added: uname-a.log http://launchpadlibrarian.net/11285705/uname-a.log -- Periodic hangs/high cpu usage https://bugs.launchpad.net/bugs/182063 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 182063] Periodic hangs/high cpu usage
Public bug reported: My computer goes into a soft hang every few seconds. A key press or mouse movement wakes the system up but causes high cpu load 50%. No errors are displayed in dmesg or other logs. The last kernel which worked well for me was feisty 2.6.20-16. This seems to be due to cpu frequency scaling in newer kernels. With the latest hardy kernel, the system is able to boot completely. The problem still occurs in X and during shutdown. Booting with nohz=off seems to stop the problem from occurring. With gutsy kernels, the system hangs multiple times during boot or shutdown requiring a key press to continue. Hardware: Samsung R20 laptop, Core Duo T2250 1.73GHz, 768MB, Ati X1250 IGP This problem has been reported in the forums before but I didn't find any bug report, e.g. http://ubuntuforums.org/showthread.php?t=647386highlight=r20 http://ubuntuforums.org/showthread.php?t=586797highlight=r20 http://ubuntuforums.org/showthread.php?t=522083highlight=r20 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Periodic hangs/high cpu usage https://bugs.launchpad.net/bugs/182063 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 103061] When i was changing the icons theme the desktop system crashed
Public bug reported: Binary package hint: thunar I only was changing the icon theme but when i select some most beauty the system desktop crash. ** Affects: thunar (Ubuntu) Importance: Undecided Status: Unconfirmed -- When i was changing the icons theme the desktop system crashed https://bugs.launchpad.net/bugs/103061 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 103061] Re: When i was changing the icons theme the desktop system crashed
** Attachment added: _usr_lib_thunar_xfce4_panel-plugins_thunar-tpa.1001.crash http://librarian.launchpad.net/7146754/_usr_lib_thunar_xfce4_panel-plugins_thunar-tpa.1001.crash -- When i was changing the icons theme the desktop system crashed https://bugs.launchpad.net/bugs/103061 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
