[Bug 896575] Re: ASUS M5A88-V EVO Ethernet instability
For what it's worth, the only thing that ended up helping in my case was to power off the machine, unplug it for 5 minutes (yes, unplug it, simply powering off didn't help), and then turn it back on. That process reset the network card and it came back up fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/896575 Title: ASUS M5A88-V EVO Ethernet instability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/896575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
Unfortunately I lost access to the box I had been using for testing and I haven't been able to bring up a similar box to run the test on. To make matters worse, I've now left the job that this was all for :( I had really hoped to test this before my last day but the stars never quite aligned. I tried creating a VM for testing but it couldn't talk to our NIS domain, so that didn't pan out. I requested a new machine to replace the one that died but it didn't show up before I left. Not sure how to proceed on this. I can see if someone there could test it for me but I don't have high hopes. If anyone else can verify the fix, that would be great! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- 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 569757] Re: NIS upstart dependency broken for lucid
Unfortunately I lost access to the box I had been using for testing and I haven't been able to bring up a similar box to run the test on. To make matters worse, I've now left the job that this was all for :( I had really hoped to test this before my last day but the stars never quite aligned. I tried creating a VM for testing but it couldn't talk to our NIS domain, so that didn't pan out. I requested a new machine to replace the one that died but it didn't show up before I left. Not sure how to proceed on this. I can see if someone there could test it for me but I don't have high hopes. If anyone else can verify the fix, that would be great! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845577] Re: mii-tool reporting incorrect duplex mode
Just a stab in the dark here, but could this be as simple as the fact that 1000baseT-HD is listed before 1000baseT-FD in the capabilities? I noticed the FD comes before HD for 100 and 10. eth0: negotiated 1000baseT-HD flow-control, link ok product info: vendor 00:07:32, model 17 rev 2 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control link partner: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845577 Title: mii-tool reporting incorrect duplex mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/845577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845577] Re: mii-tool reporting incorrect duplex mode
Oh, and ethtool output for what it's worth: Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x0033 (51) Link detected: yes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845577 Title: mii-tool reporting incorrect duplex mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/845577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 896575] Re: ASUS M5A88-V EVO Ethernet instability
I'm having this issue on Precise (after upgrading from Lucid, which also used the 8169 driver but had no issues). Currently my network card is stuck at 10baseT which is slower than my internet connection :) mii-tool output: eth0: negotiated 10baseT-FD flow-control, link ok product info: vendor 00:07:32, model 17 rev 2 basic mode: autonegotiation enabled basic status: autonegotiation complete, link ok capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD advertising: 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control link partner: 1000baseT-HD 1000baseT-FD 10baseT-FD 10baseT-HD flow-control ethtool output: Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Speed: 10Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x0033 (51) drv probe ifdown ifup Link detected: yes lshw output: lshw -class network *-network description: Ethernet interface product: RTL8111/8168B PCI Express Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: eth0 version: 03 serial: 6c:f0:49:e2:22:bf size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl_nic/rtl8168d-2.fw ip=10.27.27.35 latency=0 link=yes multicast=yes port=MII speed=10Mbit/s resources: irq:49 ioport:ce00(size=256) memory:fd9ff000-fd9f memory:fd9f8000-fd9fbfff memory:fd90-fd91 Happy to post anything else that might help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/896575 Title: ASUS M5A88-V EVO Ethernet instability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/896575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990892] [NEW] package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Attempted to install slapd for the first time, but on a machine recently upgraded from 10.04. I had already installed autofs-ldap before attempting to install slapd. This is my first experiment with LDAP so that's about all I know. Setting up slapd (2.4.28-1.1ubuntu4) ... Creating new user openldap... done. Creating initial configuration... Loading the initial configuration from the ldif file () failed with the following error while running slapadd: 4f9cbb70 str2entry: invalid value for attributeType olcSuffix #0 (syntax 1.3.6.1.4.1.1466.115.121.1.12) slapadd: could not parse entry (line=1051) dpkg: error processing slapd (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin ... ldconfig deferred processing now taking place Errors were encountered while processing: slapd E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 12.04 Package: slapd 2.4.28-1.1ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 AptOrdering: libodbc1: Install slapd: Install libodbc1: Configure slapd: Configure Architecture: amd64 Date: Sat Apr 28 23:54:24 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) SourcePackage: openldap Title: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-04-28 (0 days ago) ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/990892 Title: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/990892/+subscriptions -- 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 990892] Re: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/990892 Title: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/990892/+subscriptions -- 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 984276] Re: installing casper on a non live system causes update-initramfs to fail
Casper was installed on my system by remastersys, which I used to create a backup before upgrading. Nice synergy :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984276 Title: installing casper on a non live system causes update-initramfs to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/984276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990892] [NEW] package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Attempted to install slapd for the first time, but on a machine recently upgraded from 10.04. I had already installed autofs-ldap before attempting to install slapd. This is my first experiment with LDAP so that's about all I know. Setting up slapd (2.4.28-1.1ubuntu4) ... Creating new user openldap... done. Creating initial configuration... Loading the initial configuration from the ldif file () failed with the following error while running slapadd: 4f9cbb70 str2entry: invalid value for attributeType olcSuffix #0 (syntax 1.3.6.1.4.1.1466.115.121.1.12) slapadd: could not parse entry (line=1051) dpkg: error processing slapd (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin ... ldconfig deferred processing now taking place Errors were encountered while processing: slapd E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 12.04 Package: slapd 2.4.28-1.1ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 AptOrdering: libodbc1: Install slapd: Install libodbc1: Configure slapd: Configure Architecture: amd64 Date: Sat Apr 28 23:54:24 2012 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) SourcePackage: openldap Title: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-04-28 (0 days ago) ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990892 Title: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/990892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 990892] Re: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/990892 Title: package slapd 2.4.28-1.1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/990892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
The host I had been testing on has died a horrible death. I'm trying to find a new place to test this. On the bright side, the new host won't have ever had the old -proposed package to interfere with the upgrade, so if that was my problem, it should just work. Fingers crossed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- 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 569757] Re: NIS upstart dependency broken for lucid
The host I had been testing on has died a horrible death. I'm trying to find a new place to test this. On the bright side, the new host won't have ever had the old -proposed package to interfere with the upgrade, so if that was my problem, it should just work. Fingers crossed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
I'm having numerous problems installing the -proposed package on Lucid. Sometimes the upgrade succeeds, sometimes it fails. I haven't been able to figure out why yet (I think I'm starting from the same state each time, but maybe there's a file somewhere I'm not considering). If the package upgrade WORKS: 1) I get the following output: Preparing to replace nis 3.17-31 (using .../nis_3.17-31ubuntu0.10.04.3_i386.deb) ... * Stopping NIS services [ OK ] * Stopping NIS services [ OK ] Removing any system startup links for /etc/init.d/nis ... /etc/rc1.d/K18nis /etc/rc2.d/S18nis /etc/rc3.d/S18nis /etc/rc4.d/S18nis /etc/rc5.d/S18nis Unpacking replacement nis ... Processing triggers for ureadahead ... Processing triggers for man-db ... Setting up nis (3.17-31ubuntu0.10.04.3) ... ypbind start/running, process 18583 ypserv stop/pre-start, process 18612 2) There are several upstart jobs installed in /etc/init: start-ypbind.conf, yppasswd.conf, ypserv.conf, ypxferd.conf 3) Reverting the package to the older version leaves behind the /etc/init/*yp*.conf scripts behind If the package upgrade FAILS: 1) I get the following output: Preparing to replace nis 3.17-31 (using .../nis_3.17-31ubuntu0.10.04.3_i386.deb) ... * Stopping NIS services [ OK ] * Stopping NIS services [ OK ] Removing any system startup links for /etc/init.d/nis ... /etc/rc1.d/K18nis /etc/rc2.d/S18nis /etc/rc3.d/S18nis /etc/rc4.d/S18nis /etc/rc5.d/S18nis Unpacking replacement nis ... Processing triggers for ureadahead ... Processing triggers for man-db ... Setting up nis (3.17-31ubuntu0.10.04.3) ... ypbind start/running, process 16988 start: Unknown job: ypserv invoke-rc.d: initscript ypserv, action restart failed. dpkg: error processing nis (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nis E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up nis (3.17-31ubuntu0.10.04.3) ... ypbind start/running, process 17062 start: Unknown job: ypserv invoke-rc.d: initscript ypserv, action restart failed. dpkg: error processing nis (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nis 2) Only one upstart jobs is installed in /etc/init: ypbind.conf 3) When I tell aptitude to revert back to the older NIS package, it leaves /etc/init/ypbind.conf behind In BOTH cases, after a server reboot, NIS doesn't come up correctly. I was able to get it working by installing (so it fails) moving the ypbind.conf file to /tmp, reverting/installing again (so it succeeds) and then moving ypbind.conf back to /etc/init. Then after a reboot it worked. ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- 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 569757] Re: NIS upstart dependency broken for lucid
I'm having numerous problems installing the -proposed package on Lucid. Sometimes the upgrade succeeds, sometimes it fails. I haven't been able to figure out why yet (I think I'm starting from the same state each time, but maybe there's a file somewhere I'm not considering). If the package upgrade WORKS: 1) I get the following output: Preparing to replace nis 3.17-31 (using .../nis_3.17-31ubuntu0.10.04.3_i386.deb) ... * Stopping NIS services [ OK ] * Stopping NIS services [ OK ] Removing any system startup links for /etc/init.d/nis ... /etc/rc1.d/K18nis /etc/rc2.d/S18nis /etc/rc3.d/S18nis /etc/rc4.d/S18nis /etc/rc5.d/S18nis Unpacking replacement nis ... Processing triggers for ureadahead ... Processing triggers for man-db ... Setting up nis (3.17-31ubuntu0.10.04.3) ... ypbind start/running, process 18583 ypserv stop/pre-start, process 18612 2) There are several upstart jobs installed in /etc/init: start-ypbind.conf, yppasswd.conf, ypserv.conf, ypxferd.conf 3) Reverting the package to the older version leaves behind the /etc/init/*yp*.conf scripts behind If the package upgrade FAILS: 1) I get the following output: Preparing to replace nis 3.17-31 (using .../nis_3.17-31ubuntu0.10.04.3_i386.deb) ... * Stopping NIS services [ OK ] * Stopping NIS services [ OK ] Removing any system startup links for /etc/init.d/nis ... /etc/rc1.d/K18nis /etc/rc2.d/S18nis /etc/rc3.d/S18nis /etc/rc4.d/S18nis /etc/rc5.d/S18nis Unpacking replacement nis ... Processing triggers for ureadahead ... Processing triggers for man-db ... Setting up nis (3.17-31ubuntu0.10.04.3) ... ypbind start/running, process 16988 start: Unknown job: ypserv invoke-rc.d: initscript ypserv, action restart failed. dpkg: error processing nis (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nis E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up nis (3.17-31ubuntu0.10.04.3) ... ypbind start/running, process 17062 start: Unknown job: ypserv invoke-rc.d: initscript ypserv, action restart failed. dpkg: error processing nis (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nis 2) Only one upstart jobs is installed in /etc/init: ypbind.conf 3) When I tell aptitude to revert back to the older NIS package, it leaves /etc/init/ypbind.conf behind In BOTH cases, after a server reboot, NIS doesn't come up correctly. I was able to get it working by installing (so it fails) moving the ypbind.conf file to /tmp, reverting/installing again (so it succeeds) and then moving ypbind.conf back to /etc/init. Then after a reboot it worked. ** Tags removed: verification-needed ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
Is that what broke? I tried it Monday and my NIS broke and reverting didn't fix it. I never checked the configs though. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- 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 569757] Re: NIS upstart dependency broken for lucid
Is that what broke? I tried it Monday and my NIS broke and reverting didn't fix it. I never checked the configs though. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
Steve/Martin: I'm not seeing the updated nis package in lucid-proposed. Should I be? Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- 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 569757] Re: NIS upstart dependency broken for lucid
Is it in a PPA somewhere I can try it? If getting into -proposed is hard, seems like it should be tested first :) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- 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 569757] Re: NIS upstart dependency broken for lucid
Steve/Martin: I'm not seeing the updated nis package in lucid-proposed. Should I be? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
Is it in a PPA somewhere I can try it? If getting into -proposed is hard, seems like it should be tested first :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
Tested the proposed package in Lucid and it appears to depend on Upstart 0.9.7-2 but Lucid only has 0.6.5-8. So trying to upgrade marks nis as broken and wants to remove it. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- 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 569757] Re: NIS upstart dependency broken for lucid
Tested the proposed package in Lucid and it appears to depend on Upstart 0.9.7-2 but Lucid only has 0.6.5-8. So trying to upgrade marks nis as broken and wants to remove it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
Is that change to CRON backported to Lucid? I'm guessing not, but that would be nice. As for gdm/lightdm/atd I think the crucial one there is atd. The login stuff probably takes long enough to start that NIS will be up by then (plus that's nowhere near an exhaustive list of *dm's and adding all of them is probably the wrong way to go). I'm torn on whether to add the upstart wrappers or completely replace init.d with upstart in Lucid. I guess I'd lean towards the more minimal change to Lucid and having the new system in Precise, but I defer to your expertise. As long as one of them happens I think we're good. Somehow I missed Clint's reply to my message, but since NIS is pretty darn hosed in Lucid without one of these workarounds, I can't see how anyone would mind it actually working out of the box. Even if the change breaks the duct tape things people have done for 2 years to work around this bug, at least they can back those things out once and count on it not breaking again. Also, the type of people who are really going to care are going to check the changelogs before they update :) Thanks guys! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- 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 569757] Re: NIS upstart dependency broken for lucid
Is that change to CRON backported to Lucid? I'm guessing not, but that would be nice. As for gdm/lightdm/atd I think the crucial one there is atd. The login stuff probably takes long enough to start that NIS will be up by then (plus that's nowhere near an exhaustive list of *dm's and adding all of them is probably the wrong way to go). I'm torn on whether to add the upstart wrappers or completely replace init.d with upstart in Lucid. I guess I'd lean towards the more minimal change to Lucid and having the new system in Precise, but I defer to your expertise. As long as one of them happens I think we're good. Somehow I missed Clint's reply to my message, but since NIS is pretty darn hosed in Lucid without one of these workarounds, I can't see how anyone would mind it actually working out of the box. Even if the change breaks the duct tape things people have done for 2 years to work around this bug, at least they can back those things out once and count on it not breaking again. Also, the type of people who are really going to care are going to check the changelogs before they update :) Thanks guys! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
Thanks for working on this! Once you get Oneiric/Precise working, are you planning to fix this in Lucid? Lucid is still going to be around for a few more years :) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- 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 569757] Re: NIS upstart dependency broken for lucid
Thanks for working on this! Once you get Oneiric/Precise working, are you planning to fix this in Lucid? Lucid is still going to be around for a few more years :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790863] Re: Unable to start lxc container after update to 2.6.32-32
Verified. Tag updated to verification-done-lucid ** Tags removed: verification-needed-lucid ** Tags added: verification-done-lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions -- 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 790863] Re: Unable to start lxc container after update to 2.6.32-32
Verified. Tag updated to verification-done-lucid ** Tags removed: verification-needed-lucid ** Tags added: verification-done-lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790863] Re: Unable to start lxc container after update to 2.6.32-32
So far so good. My container is running fine along with everything else. I'll keep running this build and report if I see any issues, but I think it's good. Let me know if there's anything else I need to test. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions -- 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 790863] Re: Unable to start lxc container after update to 2.6.32-32
So far so good. My container is running fine along with everything else. I'll keep running this build and report if I see any issues, but I think it's good. Let me know if there's anything else I need to test. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790863] Re: Unable to start lxc container after update to 2.6.32-32
Tim, Thanks for getting a test version out! I've been swamped the last few weeks but I can test it out this weekend and post my results. I also admit I thought this was a VSFTP patch (from Jamie's note) when I skimmed it the first time, not a new kernel. Oops :) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions -- 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 790863] Re: Unable to start lxc container after update to 2.6.32-32
Tim, Thanks for getting a test version out! I've been swamped the last few weeks but I can test it out this weekend and post my results. I also admit I thought this was a VSFTP patch (from Jamie's note) when I skimmed it the first time, not a new kernel. Oops :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790863] Re: Unable to start lxc container after update to 2.6.32-32
Stefan, I have to agree with Henrik regarding the logic seeming backwards, but I suppose that's because the solution hurt me. Did Serge Hallyn ever take a look at it? I got the impression someone was going to try to backport part of the fix, but it sounds like that path was rejected. Regarding the Maverick and Natty backport kernels, I had the problem Kai had (the Maverick backport was broken and it took a MONTH to fix, which is not what I consider fully supported) along with issues with drivers for my video card and LCD display. I haven't looked for or tried an Oneiric backport kernel yet, but at this point I'm definitely leery. The main source of frustration comes from the sense that Canonical deliberately introduced a regression (disabling a kernel feature that had previously been enabled) to avoid a potential regression (backporting the fix) and the workaround of using a backport kernel would have been fine except that it wasn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790863] Re: Unable to start lxc container after update to 2.6.32-32
I've been pinned at 2.6.32-31 since this began. I experimented with the various backports but each caused more problems than it solved. Bad answer Canonical. Sigh. At least 12.04 is only 6 months away, plus 3 months to stabilize. By the way, where exactly was this decision documented? I'd like to read the reasoning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790863] Re: Unable to start lxc container after update to 2.6.32-32
The Maverick and Natty kernels also work for some people. However, depending on the rest of your configuration, installing backported kernels can break other things. Definitely not the ideal answer. The fact that Maverick backport was broken for a month is an example. I'd complain about how long this fix has taken, but you can pay a lot for an operating system and get worse support, so I won't :) Instead I'll say thanks to everyone at Canonical for all the stuff that DOES work, and please try to fix this properly soon, it's been 4 months. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824913] Re: LUCID linux-headers-generic-lts-backport-maverick 2.6.35.30.38 depends on missing linux-headers-2.6.35-30
Sorry for my ignorance, but if it's released when should I expect to see it in Update Manager? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824913 Title: LUCID linux-headers-generic-lts-backport-maverick 2.6.35.30.38 depends on missing linux-headers-2.6.35-30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/824913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824913] [NEW] LUCID linux-headers-generic-lts-backport-maverick 2.6.35.30.38 depends on missing linux-headers-2.6.35-30
Public bug reported: The linux-headers-generic-lts-backport-maverick package has been updated and wants to upgrade linux-headers-2.6.35-30-generic but that depends on linux-headers-2.6.35-30 which appears to be missing from the LUCID repositories. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824913 Title: LUCID linux-headers-generic-lts-backport-maverick 2.6.35.30.38 depends on missing linux-headers-2.6.35-30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/824913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824913] Re: LUCID linux-headers-generic-lts-backport-maverick 2.6.35.30.38 depends on missing linux-headers-2.6.35-30
Installing the package from https://launchpad.net/ubuntu/lucid/amd64 /linux-headers-2.6.35-30/2.6.35-30.55~lucid1 is a workaround (at least it gets Update Manager to stop complaining) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824913 Title: LUCID linux-headers-generic-lts-backport-maverick 2.6.35.30.38 depends on missing linux-headers-2.6.35-30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/824913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
Ah, I didn't realize that about 10.04.3. Thanks for clearing that up. Also thanks for the quick turnaround on a package update. Unfortunately, installing the new version failed for me: Preparing to replace nis 3.17-31 (using .../nis_3.17-32ubuntu2~lucid1~ppa1_i386.deb) ... * Stopping NIS services [ OK ] Unpacking replacement nis ... Processing triggers for ureadahead ... Processing triggers for man-db ... Setting up nis (3.17-32ubuntu2~lucid1~ppa1) ... Removing any system startup links for /etc/init.d/nis ... /etc/rc1.d/K18nis /etc/rc2.d/S18nis /etc/rc3.d/S18nis /etc/rc4.d/S18nis /etc/rc5.d/S18nis dpkg: error processing nis (--configure): subprocess installed post-installation script returned error exit status 105 E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up nis (3.17-32ubuntu2~lucid1~ppa1) ... Removing any system startup links for /etc/init.d/nis ... dpkg: error processing nis (--configure): subprocess installed post-installation script returned error exit status 105 Errors were encountered while processing: nis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 716438] Re: add-apt-repository should have option to use port 80
Could this be backported to Lucid, or perhaps a simple version of it? This should be enough, applied to python-software-properties version 0.75.10.1: --- /usr/share/pyshared/softwareproperties/ppa.py.orig 2010-04-14 15:05:59.0 -0400 +++ /usr/share/pyshared/softwareproperties/ppa.py 2011-06-27 17:14:13.027023115 -0400 @@ -81,7 +81,7 @@ # FIXME: this needs to go - elmo says the keyserver will not handle #the load res = subprocess.call( -[apt-key, adv, --keyserver, keyserver.ubuntu.com, +[apt-key, adv, --keyserver, hkp://keyserver.ubuntu.com:80, --recv, signing_key_fingerprint[0]]) return (res == 0) except URLError, e: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/716438 Title: add-apt-repository should have option to use port 80 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/716438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
Could this be targeted for 10.04.3? This is really a pretty bad problem with 10.04, and the 10.04.x releases are going to get further apart after 10.04.3. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- 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 569757] Re: NIS upstart dependency broken for lucid
Clint, My attached files based on your original suggestion of two new upstart jobs should do the trick as far as a minimally invasive fix for many users. Anything more substantial would probably be hard to get approved for a point release right? It looks (from Christian's latest comment) like the start line for my nis script should be modified to remove the net-device-up IFACE!=lo condition but otherwise I've been running these scripts for months with no issues on an otherwise untouched 10.04.2. I'm sure you could add these to the existing package faster than I can (and do it right). Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- 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 569757] Re: NIS upstart dependency broken for lucid
Could this be targeted for 10.04.3? This is really a pretty bad problem with 10.04, and the 10.04.x releases are going to get further apart after 10.04.3. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependency broken for lucid
Clint, My attached files based on your original suggestion of two new upstart jobs should do the trick as far as a minimally invasive fix for many users. Anything more substantial would probably be hard to get approved for a point release right? It looks (from Christian's latest comment) like the start line for my nis script should be modified to remove the net-device-up IFACE!=lo condition but otherwise I've been running these scripts for months with no issues on an otherwise untouched 10.04.2. I'm sure you could add these to the existing package faster than I can (and do it right). Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependency broken for lucid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790863] Re: Unable to start lxc container after update to 2.6.32-32
Reading through the discussion on the kernel list, I think the flawed logic in this decision was: Let's avoid a POTENTIAL regression due to lots of lines of code changed by introducing a DEFINITE regression. I think we've all been there. Still, not a great call. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 790863] Re: Unable to start lxc container after update to 2.6.32-32
Seriously guys... What the heck were you thinking? The whole reason people choose to run an LTS is to avoid this kind of thing. I can downgrade for now, but please fix soon! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/790863 Title: Unable to start lxc container after update to 2.6.32-32 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
Hopefully this works. I'm attaching a working nis.conf and nis- wait.conf based on the comments so far. Put the files in /etc/init and that should be all that's necessary for most configurations. You shouldn't even need to remove the /etc/rc?.d nis links since it should just determine it's already started and exit. The start line I used in nis.conf is based on the ypbind.conf file that Paul Elliott wrote, but the rest of the script is from Clint Byrum's suggestion. I also modified the nis-wait.conf to include cron and atd. No, this isn't a perfect answer, but it works for me. I don't know if it's a complete enough suggestion to cover Maciej Puzio's case but it might be. ** Attachment added: NIS upstart job https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+attachment/2070218/+files/nis.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- 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 569757] Re: NIS upstart dependancy broken for lucid
** Attachment added: NIS-wait upstart job https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+attachment/2070219/+files/nis-wait.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- 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 569757] Re: NIS upstart dependancy broken for lucid
Hopefully this works. I'm attaching a working nis.conf and nis- wait.conf based on the comments so far. Put the files in /etc/init and that should be all that's necessary for most configurations. You shouldn't even need to remove the /etc/rc?.d nis links since it should just determine it's already started and exit. The start line I used in nis.conf is based on the ypbind.conf file that Paul Elliott wrote, but the rest of the script is from Clint Byrum's suggestion. I also modified the nis-wait.conf to include cron and atd. No, this isn't a perfect answer, but it works for me. I don't know if it's a complete enough suggestion to cover Maciej Puzio's case but it might be. ** Attachment added: NIS upstart job https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+attachment/2070218/+files/nis.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569757] Re: NIS upstart dependancy broken for lucid
** Attachment added: NIS-wait upstart job https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+attachment/2070219/+files/nis-wait.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/569757 Title: NIS upstart dependancy broken for lucid -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 626027] Re: package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
It looks to me like the problem was with xorg-driver-fglrx, which still had some diversions registered for /usr/lib32/libGL.so.1.2 and /usr/lib/libGL.so.1.2 despite it no longer being a real package. So when fglrx tried to restore the libGL.so stuff it failed causing the entire uninstall to fail. I resolved the problem by forcing a reinstall of fglrx then manually running: sudo dpkg-divert --remove /usr/lib32/libGL.so.1.2 sudo dpkg-divert --remove /usr/lib/libGL.so.1.2 Then I was able to uninstall fglrx successfully. VDPAU still isn't working even with the newer fglrx driver, but that's a different problem I believe. -- package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 https://bugs.launchpad.net/bugs/626027 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 626027] [NEW] package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
Public bug reported: Immediately after upgrading from 9.10 to 10.04.1, VDPAU acceleration wasn't working within XBMC so I attempted to uninstall the fglrx proprietary driver and got this failure. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: fglrx 2:8.723.1-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 NonfreeKernelModules: fglrx AptOrdering: xorg-driver-fglrx: Remove fglrx-amdcccle: Remove fglrx: Remove Architecture: amd64 Date: Sat Aug 28 17:26:09 2010 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=e536d4cc-6673-44cb-aadf-d13a603d7c40 ro quiet splash SourcePackage: fglrx-installer Title: package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 dmi.bios.date: 12/31/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-MA790GP-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790GP-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-24-generic ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 https://bugs.launchpad.net/bugs/626027 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 626027] Re: package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
** Attachment added: BootDmesg.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525890/+files/BootDmesg.txt ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525891/+files/CurrentDmesg.txt ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525892/+files/Dependencies.txt ** Attachment added: Df.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525893/+files/Df.txt ** Attachment added: DkmsStatus.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525894/+files/DkmsStatus.txt ** Attachment added: Dmesg.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525895/+files/Dmesg.txt ** Attachment added: DpkgTerminalLog.gz https://bugs.launchpad.net/bugs/626027/+attachment/1525896/+files/DpkgTerminalLog.gz ** Attachment added: GdmLog.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525897/+files/GdmLog.txt ** Attachment added: GdmLog1.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525898/+files/GdmLog1.txt ** Attachment added: GdmLog2.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525899/+files/GdmLog2.txt ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525900/+files/Lspci.txt ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525901/+files/Lsusb.txt ** Attachment added: PciDisplay.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525902/+files/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525903/+files/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525904/+files/ProcInterrupts.txt ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525905/+files/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525906/+files/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525907/+files/UdevDb.txt ** Attachment added: UdevLog.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525908/+files/UdevLog.txt ** Attachment added: XorgConf.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525909/+files/XorgConf.txt ** Attachment added: XorgLog.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525910/+files/XorgLog.txt ** Attachment added: XorgLogOld.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525911/+files/XorgLogOld.txt ** Attachment added: Xrandr.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525912/+files/Xrandr.txt ** Attachment added: glxinfo.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525913/+files/glxinfo.txt ** Attachment added: setxkbmap.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525914/+files/setxkbmap.txt ** Attachment added: xdpyinfo.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525915/+files/xdpyinfo.txt ** Attachment added: xkbcomp.txt https://bugs.launchpad.net/bugs/626027/+attachment/1525916/+files/xkbcomp.txt -- package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 https://bugs.launchpad.net/bugs/626027 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 546578] Re: black screen after a few user switches
Finally got a chance to test this last night and it works like a charm on my 2 systems. Thanks! -- black screen after a few user switches https://bugs.launchpad.net/bugs/546578 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 584272] Re: boa-constructor fails compilation during upgrade from Hardy to Lucid
I've attached the dist-upgrade directory contents as a tar file. Sorry i didn't get to it sooner! I'm not sure how to read the log, but it kinda looks like some module plugged in to Python failed to parse in the new version and that's why the Python install failed, leading to all the other failures (there were 20 more before the upgrader finally stopped and started itself over again). Another thing that wasn't clear when I submitted these was that the upgraded DID restart and the restart DID fix these install problems. So in the end it worked, it just presented me with a ton of errors on first boot. Another thing (and I think I'll submit this as an enhancement request) is I had no idea how many errors there were when I started submitting them. I just went through and said submit submit submit. If it had popped up with a list of all the errors and let me pick which ones to submit from that list, ideally with a relevant snippet from the log, I probably could have done a better job describing the failure. Thanks for all your work folks! I'm a huge fan! ** Attachment added: dist-upgrade directory contents http://launchpadlibrarian.net/49031108/dist-upgrade.tar.gz -- boa-constructor fails compilation during upgrade from Hardy to Lucid https://bugs.launchpad.net/bugs/584272 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 585057] [NEW] Optionally show user a complete list of failures rather than individually
Public bug reported: Binary package hint: apport This is an enhancement request. Currently when there are multiple failures to report, the Gnome applet shows me one error at a time. I can't go back and forth in the list, my options are 'submit' or not. What I think might be better is if there are more than 2 failures, to display a window with all the failures listed. Allow the user to select failures to ignore, ones to submit and ones to merge (or something along those lines). Ideally the window will also let the user do a little big of digging if they choose, for example looking at a snippet of the log showing the failure (in cases where apport knows this). But just having a windows that lists ALL the failures would be a big start. Example: I recently upgraded Hardy to Lucid. During the upgrade there were about 30 failures. On first boot, I had the crash detected icon, which I clicked. I was presented with a failure dialog, telling me I could submit the report or not. After submitting the first, a second window popped up with a different failure. And so on and so forth. By about the 14th failure I figured I should do a little digging on the command-line to see what happened and found the other 20 failures. This resulted in 12 bug reports that were actually all related to the first one, but it wasn't clear until I looked at the logs and saw them all listed at one time. Seeing them all at once would have made it pretty clear they were all Python-related. Thanks! ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- Optionally show user a complete list of failures rather than individually https://bugs.launchpad.net/bugs/585057 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 584224] [NEW] package python-central 0.6.15ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured
Public bug reported: Binary package hint: python-central Upgrading from Hardy to Lucid there were several failures. This was the second. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: python-central 0.6.15ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 22 05:24:38 2010 ErrorMessage: dependency problems - leaving unconfigured PackageArchitecture: all SourcePackage: python-central Title: package python-central 0.6.15ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured ** Affects: python-central (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package python-central 0.6.15ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584224 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 584224] Re: package python-central 0.6.15ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48923980/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/48923981/DpkgTerminalLog.txt -- package python-central 0.6.15ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584224 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 584221] [NEW] package python 2.6.5-0ubuntu1 failed to install/upgrade:
Public bug reported: Upgrading from Hardy to Lucid there were several errors, this was the first. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: python 2.6.5-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 22 05:24:39 2010 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 4 PackageArchitecture: all SourcePackage: python-defaults Title: package python 2.6.5-0ubuntu1 failed to install/upgrade: ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package python 2.6.5-0ubuntu1 failed to install/upgrade: https://bugs.launchpad.net/bugs/584221 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 584221] Re: package python 2.6.5-0ubuntu1 failed to install/upgrade:
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48923912/Dependencies.txt ** Attachment added: VarLogDistupgrade201005220412.gz http://launchpadlibrarian.net/48923913/VarLogDistupgrade201005220412.gz -- package python 2.6.5-0ubuntu1 failed to install/upgrade: https://bugs.launchpad.net/bugs/584221 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 584225] [NEW] package python-uno 1:3.2.0-7ubuntu4 failed to install/upgrade: dependency problems - leaving unconfigured
Public bug reported: Binary package hint: openoffice.org Upgrading from Hardy to Lucid there were several failures. This was the third. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: python-uno 1:3.2.0-7ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 22 05:24:39 2010 ErrorMessage: dependency problems - leaving unconfigured SourcePackage: openoffice.org Title: package python-uno 1:3.2.0-7ubuntu4 failed to install/upgrade: dependency problems - leaving unconfigured ** Affects: openoffice.org (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package python-uno 1:3.2.0-7ubuntu4 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584225 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 584225] Re: package python-uno 1:3.2.0-7ubuntu4 failed to install/upgrade: dependency problems - leaving unconfigured
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48924053/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/48924054/DpkgTerminalLog.txt -- package python-uno 1:3.2.0-7ubuntu4 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584225 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 584257] [NEW] package checkbox 0.9.1 failed to install/upgrade: dependency problems - leaving unconfigured
Public bug reported: Binary package hint: checkbox Upgrading from Hardy to Lucid there were several failures. This was the fifth. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: checkbox 0.9.1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 22 05:38:12 2010 ErrorMessage: dependency problems - leaving unconfigured PackageArchitecture: all SourcePackage: checkbox Title: package checkbox 0.9.1 failed to install/upgrade: dependency problems - leaving unconfigured ** Affects: checkbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package checkbox 0.9.1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584257 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 584257] Re: package checkbox 0.9.1 failed to install/upgrade: dependency problems - leaving unconfigured
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48928564/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/48928565/DpkgTerminalLog.txt -- package checkbox 0.9.1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584257 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 584260] [NEW] package hwtest 0.9.1 failed to install/upgrade: dependency problems - leaving unconfigured
Public bug reported: Binary package hint: checkbox Upgrading from Hardy to Lucid there were several failures. This was the sixth. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: hwtest 0.9.1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 22 05:38:12 2010 ErrorMessage: dependency problems - leaving unconfigured PackageArchitecture: all SourcePackage: checkbox Title: package hwtest 0.9.1 failed to install/upgrade: dependency problems - leaving unconfigured ** Affects: checkbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package hwtest 0.9.1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584260 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 584260] Re: package hwtest 0.9.1 failed to install/upgrade: dependency problems - leaving unconfigured
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48928788/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/48928789/DpkgTerminalLog.txt -- package hwtest 0.9.1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584260 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 584263] [NEW] package libgksu2-0 2.0.13~pre1-1ubuntu4 failed to install/upgrade: dependency problems - leaving unconfigured
Public bug reported: Upgrading Hardy to Lucid there were several failures. This was the eighth. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: libgksu2-0 2.0.13~pre1-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 22 05:38:26 2010 ErrorMessage: dependency problems - leaving unconfigured SourcePackage: libgksu Title: package libgksu2-0 2.0.13~pre1-1ubuntu4 failed to install/upgrade: dependency problems - leaving unconfigured ** Affects: libgksu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package libgksu2-0 2.0.13~pre1-1ubuntu4 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584263 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 584263] Re: package libgksu2-0 2.0.13~pre1-1ubuntu4 failed to install/upgrade: dependency problems - leaving unconfigured
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48929172/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/48929173/DpkgTerminalLog.txt -- package libgksu2-0 2.0.13~pre1-1ubuntu4 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584263 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 584261] [NEW] package gconf2 2.28.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured
Public bug reported: Binary package hint: gconf Upgrading from Hardy to Lucid there were several failures. This was the seventh. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: gconf2 2.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 22 05:38:18 2010 ErrorMessage: dependency problems - leaving unconfigured SourcePackage: gconf Title: package gconf2 2.28.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package gconf2 2.28.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584261 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 584261] Re: package gconf2 2.28.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48929068/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/48929069/DpkgTerminalLog.txt -- package gconf2 2.28.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584261 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 584265] [NEW] package gksu 2.0.2-2ubuntu2 failed to install/upgrade: dependency problems - leaving unconfigured
Public bug reported: Binary package hint: gksu Upgrading from Hardy to Lucid there were several failures. This was the 10th. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: gksu 2.0.2-2ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 22 05:38:27 2010 ErrorMessage: dependency problems - leaving unconfigured SourcePackage: gksu Title: package gksu 2.0.2-2ubuntu2 failed to install/upgrade: dependency problems - leaving unconfigured ** Affects: gksu (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package gksu 2.0.2-2ubuntu2 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584265 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 584265] Re: package gksu 2.0.2-2ubuntu2 failed to install/upgrade: dependency problems - leaving unconfigured
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48929581/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/48929582/DpkgTerminalLog.txt -- package gksu 2.0.2-2ubuntu2 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584265 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 584264] [NEW] package gnome-keyring 2.92.92.is.2.30.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured
Public bug reported: Binary package hint: gnome-keyring Upgrading from Hardy to Lucid there were several failures. This was the ninth. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: gnome-keyring 2.92.92.is.2.30.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 22 05:38:27 2010 ErrorMessage: dependency problems - leaving unconfigured SourcePackage: gnome-keyring Title: package gnome-keyring 2.92.92.is.2.30.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package gnome-keyring 2.92.92.is.2.30.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584264 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 584264] Re: package gnome-keyring 2.92.92.is.2.30.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48929419/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/48929420/DpkgTerminalLog.txt -- package gnome-keyring 2.92.92.is.2.30.1-0ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584264 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 584267] [NEW] package python-support 1.0.4ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured
Public bug reported: Binary package hint: python-support Upgrading from Hardy to Lucid there were several failures. This was the 11th. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: python-support 1.0.4ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 22 05:38:27 2010 ErrorMessage: dependency problems - leaving unconfigured PackageArchitecture: all SourcePackage: python-support Title: package python-support 1.0.4ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured ** Affects: python-support (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package python-support 1.0.4ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584267 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 584267] Re: package python-support 1.0.4ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48929674/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/48929675/DpkgTerminalLog.txt -- package python-support 1.0.4ubuntu1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584267 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 584272] [NEW] package python-gobject 2.21.1-0ubuntu3 failed to install/upgrade: dependency problems - leaving unconfigured
Public bug reported: Upgrading from Hardy to Lucid there were several failures. This was the 13th ProblemType: Package DistroRelease: Ubuntu 10.04 Package: python-gobject 2.21.1-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 22 05:38:27 2010 ErrorMessage: dependency problems - leaving unconfigured SourcePackage: pygobject Title: package python-gobject 2.21.1-0ubuntu3 failed to install/upgrade: dependency problems - leaving unconfigured ** Affects: pygobject (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package python-gobject 2.21.1-0ubuntu3 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584272 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 584272] Re: package python-gobject 2.21.1-0ubuntu3 failed to install/upgrade: dependency problems - leaving unconfigured
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48929942/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/48929943/DpkgTerminalLog.txt -- package python-gobject 2.21.1-0ubuntu3 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584272 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 584269] [NEW] package python-cairo 1.8.8-1 failed to install/upgrade: dependency problems - leaving unconfigured
Public bug reported: Upgrading from Hardy to Lucid there were several failures. This was the 12th. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: python-cairo 1.8.8-1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 Architecture: i386 Date: Sat May 22 05:38:27 2010 ErrorMessage: dependency problems - leaving unconfigured SourcePackage: pycairo Title: package python-cairo 1.8.8-1 failed to install/upgrade: dependency problems - leaving unconfigured ** Affects: pycairo (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package python-cairo 1.8.8-1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584269 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 584269] Re: package python-cairo 1.8.8-1 failed to install/upgrade: dependency problems - leaving unconfigured
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/48929880/Dependencies.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/48929881/DpkgTerminalLog.txt -- package python-cairo 1.8.8-1 failed to install/upgrade: dependency problems - leaving unconfigured https://bugs.launchpad.net/bugs/584269 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 574909] [NEW] Getting a black/blank screen when switching between users in lucid
Public bug reported: Binary package hint: fast-user-switch-applet Not sure this is the right applet, but it seems to be affecting a number of people. 1) Ubuntu 10.04 LTS (lucid) 2) Unknown (I assumed fast-user-switch-applet, but I can't find a version number for it, so maybe this isn't part of Lucid?) 3) Switching between 2 users repeatedly should work 4) It fails after 1-3 switches with a black/blank screen Steps to repeat: - Boot ubuntu and login to user A - Then Click on power menu (top right corner) and select: Switch from A - I get the login screen - I select user B and enter my password - I hit ok - I am able to login successfully to user B - Now, I Click on power menu (top right corner) and select: Switch from B - I select user A from the login screen and enter my credentials, then hit OK - I get a black screen Alternatively: - Boot ubuntu and login to user A - Then Click on power menu (top right corner) and select: Switch from A... Select B - I get the login screen - I hit ok - I am able to login successfully to user B - Now, I Click on power menu (top right corner) and select: Switch from B... Select A - I get a black screen In my case, Ctrl+Alt+F1-6 is black as well. The computer is NOT hung, I can type blindly and shut down fine. More details: http://ubuntuforums.org/showthread.php?t=1471915 http://ubuntuforums.org/showthread.php?t=1467619 Might be related to this bug reported against Jaunty? https://bugs.launchpad.net/ubuntu/+source/fast-user-switch-applet/+bug/354083 ** Affects: fast-user-switch-applet (Ubuntu) Importance: Undecided Status: New -- Getting a black/blank screen when switching between users in lucid https://bugs.launchpad.net/bugs/574909 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 574909] Re: Getting a black/blank screen when switching between users in lucid
The following workaround does restore the display: Alt+F2 Type: xgamma -gamma 1.0 (for more displays you can use xgamma -display 1.0 -gamma 1.0) More possibly related bug reports: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/549632 https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/555870 https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/546578 -- Getting a black/blank screen when switching between users in lucid https://bugs.launchpad.net/bugs/574909 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 361466] Re: miro.real crashed with TypeError in walk()
Oops! I must have missed the request back when I switch my email to a different system. Sorry about that. I haven't used Miro in 10 months so this is quite safe to close. -- miro.real crashed with TypeError in walk() https://bugs.launchpad.net/bugs/361466 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 467172] Re: WARNING: at /build/buildd/linux-2.6.31/fs/sysfs/dir.c:487 sysfs_add_one+0xc5/0x130()
I haven't seen anything like this in quite a while. I think it's safe to say it's been addressed in the more recent Karmic kernel releases. -- WARNING: at /build/buildd/linux-2.6.31/fs/sysfs/dir.c:487 sysfs_add_one+0xc5/0x130() https://bugs.launchpad.net/bugs/467172 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 456861] Re: [Hewlett-Packard Presario C300 (RH211UA#ABA)] suspend/resume failure
Sorry I didn't come back and close this sooner. It was fixed in one of the early Karmic kernel revisions. I haven't tested on Lucid yet since everything is working so nicely right now :) ** Changed in: linux (Ubuntu) Status: Incomplete = Fix Released -- [Hewlett-Packard Presario C300 (RH211UA#ABA)] suspend/resume failure https://bugs.launchpad.net/bugs/456861 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 546153] Re: ubiquity crashed with AttributeError in __init__()
Same here except I'm using vmware player 3.0.1 to do the install. 2010-03-26 daily desktop x64 cd. -- ubiquity crashed with AttributeError in __init__() https://bugs.launchpad.net/bugs/546153 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 507213] [NEW] UbuntuOne crash
Public bug reported: Binary package hint: ubuntuone-client Sorry, I don't actually know what happened. I didn't witness the crash, it was caught for me. I'm hoping the attached files will have enough info to be useful. ProblemType: Bug .home.jyoder..config.ubuntuone.ubuntuone.client.conf: [ubuntuone] bookmarked = True connected = True connect = 0 show_applet = 1 Architecture: i386 Date: Wed Jan 13 16:24:47 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: ubuntuone-client 1.0.2-0ubuntu2 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic SourcePackage: ubuntuone-client Uname: Linux 2.6.31-17-generic i686 ** Affects: ubuntuone-client (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- UbuntuOne crash https://bugs.launchpad.net/bugs/507213 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 507213] Re: UbuntuOne crash
** Attachment added: .home.jyoder..cache.ubuntuone.log.oauth.login.log.txt http://launchpadlibrarian.net/37863266/.home.jyoder..cache.ubuntuone.log.oauth.login.log.txt ** Attachment added: .home.jyoder..cache.ubuntuone.log.syncdaemon.exceptions.log.txt http://launchpadlibrarian.net/37863267/.home.jyoder..cache.ubuntuone.log.syncdaemon.exceptions.log.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/37863268/Dependencies.txt ** Attachment added: UbuntuoneClientPackages.txt http://launchpadlibrarian.net/37863269/UbuntuoneClientPackages.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/37863270/XsessionErrors.txt -- UbuntuOne crash https://bugs.launchpad.net/bugs/507213 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 467172] [NEW] WARNING: at /build/buildd/linux-2.6.31/fs/sysfs/dir.c:487 sysfs_add_one+0xc5/0x130()
Public bug reported: I was playing some youtube videos full screen. I had one paused for about 20 minutes when this happened. ProblemType: KernelOops Annotation: Your system might become unstable now and might need to be restarted. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: media 1871 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe024000 irq 16' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,1458a102,00100101' Controls : 37 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfdffc000 irq 19' Mixer name : 'ATI RS690/780 HDMI' Components : 'HDA:1002791a,00791a00,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [off] Date: Sat Oct 31 00:25:12 2009 DistroRelease: Ubuntu 9.10 Failure: oops HibernationDevice: RESUME=UUID=9a8ceae1-ac48-48a9-ae41-d6268c8eeff1 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H Package: linux-image-2.6.31-14-generic 2.6.31-14.48 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=e536d4cc-6673-44cb-aadf-d13a603d7c40 ro quiet splash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: linux-backports-modules-2.6.31-14-generic N/A linux-firmware 1.24 RfKill: SourcePackage: linux Tags: kernel-oops Title: WARNING: at /build/buildd/linux-2.6.31/fs/sysfs/dir.c:487 sysfs_add_one+0xc5/0x130() Uname: Linux 2.6.31-14-generic x86_64 dmi.bios.date: 12/31/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-MA790GP-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd12/31/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790GP-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops kernel-oops -- WARNING: at /build/buildd/linux-2.6.31/fs/sysfs/dir.c:487 sysfs_add_one+0xc5/0x130() https://bugs.launchpad.net/bugs/467172 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 467172] Re: WARNING: at /build/buildd/linux-2.6.31/fs/sysfs/dir.c:487 sysfs_add_one+0xc5/0x130()
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/34799250/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/34799251/AplayDevices.txt ** Attachment added: ArecordDevices.txt http://launchpadlibrarian.net/34799252/ArecordDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/34799253/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/34799254/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/34799255/Card0.Codecs.codec.0.txt ** Attachment added: Card1.Codecs.codec.0.txt http://launchpadlibrarian.net/34799256/Card1.Codecs.codec.0.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/34799257/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/34799259/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/34799262/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/34799263/Lsusb.txt ** Attachment added: OopsText.txt http://launchpadlibrarian.net/34799264/OopsText.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/34799266/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/34799267/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/34799268/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/34799269/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/34799270/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/34799271/UdevLog.txt ** Attachment added: WifiSyslog.txt http://launchpadlibrarian.net/34799272/WifiSyslog.txt -- WARNING: at /build/buildd/linux-2.6.31/fs/sysfs/dir.c:487 sysfs_add_one+0xc5/0x130() https://bugs.launchpad.net/bugs/467172 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 454371] Re: Hauppauge HVR-1600 Remote Not Detected
This appears to be a problem with the 2.6.31 kernel drivers. From Jaron Wilson on the LIRC mailing list: The root of the problem is that the i2c client model changed significantly in 2.6.31, and some drivers (such as the cx18 driver for the HVR-1600) weren't updated soon enough for the 2.6.31 window, meaning even ir-kbd- i2c is broken with them as well. What needs to happen is some patchification of those drivers in a 2.6.31.x stable release, I think (going to ping some v4l/dvb folks on that). What we did on Dave's box is build the cx18 driver (well, all v4l-dvb drivers) from v4l-dvb mercurial, and all was well again. Short version: hg clone http://linuxtv.org/hg/v4l-dvb cd v4l-dvb make make install If you get errors about some driver or another not building, if its one you don't need, you can disable it from being built in v4l/ Makefile.media (the firedtv driver was failing on Dave's system for some reason). If you update your kernel to another that still doesn't have the required i2c fixage in it, you'll lose the fixes from v4l-dvb, but can get 'em back by going back into that v4l-dvb checkout and rebuilding (after doing a 'make distclean' so the build uses the new kernel headers instead of the prior one). -- Hauppauge HVR-1600 Remote Not Detected https://bugs.launchpad.net/bugs/454371 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 454843] Re: pvr_150 module is missing in lirc-modules-source
It looks like lirc_pvr150 has been floating around for a long time. I can't find anyone who owns a version. The file contains some firmware code, which is the source of the copyright worries. If someone were to take ownership of it and patch it up for the newest kernel, I think the best distribution method would be creating a PPA for it as opposed to adding it to the Ubuntu LIRC package. It wouldn't be too hard to get it to install a kernel module via dkms and add some config files to the LIRC directory structure. I'd be willing to help anyone who wanted to do that. Unfortunately I don't own any Hauppauge equipment so there's not much I can do myself. -- pvr_150 module is missing in lirc-modules-source https://bugs.launchpad.net/bugs/454843 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 454371] Re: Hauppauge HVR-1600 Remote Not Detected
** Changed in: lirc (Ubuntu) Status: New = Confirmed -- Hauppauge HVR-1600 Remote Not Detected https://bugs.launchpad.net/bugs/454371 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 441150] Re: Please support auto-detection, à la gnome-lirc-properties
Hmmm. I can't assign the bug to me. This is something that I'm working on though. The general goal is to take the detection logic in gnome-lirc-properties and move it to a new package. Then gnome-lirc-properties and lirc can both make use of the autodetection and configuration without requiring the GUI. My attempts to talk to the developers of gnome-lirc-properties have been unsuccessful so far. Hopefully they'll accept a patch when one is ready. -- Please support auto-detection, à la gnome-lirc-properties https://bugs.launchpad.net/bugs/441150 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 441150] Re: Please support auto-detection, à la gnome-lirc-properties
** Changed in: lirc (Ubuntu) Status: New = In Progress -- Please support auto-detection, à la gnome-lirc-properties https://bugs.launchpad.net/bugs/441150 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 441151] Re: /etc/init.d/lirc restart fails
This is probably a false error. The restart works, but reports a failure due to a race condition between loading modules and start-stop- daemon. If you look at the process list, lircd is probably running. Mario: The fix to this is to change /etc/init.d/lirc to pass --oknodo to start-stop-daemon. ** Changed in: lirc (Ubuntu) Status: New = Confirmed -- /etc/init.d/lirc restart fails https://bugs.launchpad.net/bugs/441151 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 456861] Re: [Hewlett-Packard Presario C300 (RH211UA#ABA)] suspend/resume failure
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/34082051/AlsaDevices.txt ** Attachment added: AplayDevices.txt http://launchpadlibrarian.net/34082052/AplayDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/34082053/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt http://launchpadlibrarian.net/34082054/Card0.Amixer.values.txt ** Attachment added: Card0.Codecs.codec.0.txt http://launchpadlibrarian.net/34082056/Card0.Codecs.codec.0.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/34082057/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/34082058/Dependencies.txt ** Attachment added: IwConfig.txt http://launchpadlibrarian.net/34082059/IwConfig.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/34082060/Lspci.txt ** Attachment added: PciMultimedia.txt http://launchpadlibrarian.net/34082061/PciMultimedia.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/34082062/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/34082063/ProcInterrupts.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/34082064/ProcMaps.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/34082065/ProcModules.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/34082066/ProcStatus.txt ** Attachment added: SleepLog.txt http://launchpadlibrarian.net/34082067/SleepLog.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/34082068/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/34082069/UdevLog.txt ** Attachment added: WifiSyslog.gz http://launchpadlibrarian.net/34082070/WifiSyslog.gz -- [Hewlett-Packard Presario C300 (RH211UA#ABA)] suspend/resume failure https://bugs.launchpad.net/bugs/456861 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 456861] [NEW] [Hewlett-Packard Presario C300 (RH211UA#ABA)] suspend/resume failure
Public bug reported: Almost fresh install of 9.10 Karmic. Tried a hibernate and it failed to hibernate at all. I tried a suspend and it suspended but I couldn't resume. ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jeremy 1494 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd034 irq 22' Mixer name : 'Conexant CX20551 (Waikiki)' Components : 'HDA:14f15047,103c30a5,0010' Controls : 15 Simple ctrls : 7 Date: Tue Oct 20 12:59:00 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationMedia: Ubuntu 9.10 Karmic Koala - Release Candidate i386 (20091019.2) InterpreterPath: /usr/bin/python2.6 Lsusb: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard Presario C300 (RH211UA#ABA) Package: linux-image-2.6.31-14-generic 2.6.31-14.48 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=0c8268b8-e7f3-4e41-a7f3-c66c9cbf9add ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.31-14.48-generic RelatedPackageVersions: linux-backports-modules-2.6.31-14-generic N/A linux-firmware 1.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Tags: resume suspend Title: [Hewlett-Packard Presario C300 (RH211UA#ABA)] suspend/resume failure Uname: Linux 2.6.31-14-generic i686 UserGroups: dmi.bios.date: 09/07/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.25 dmi.board.name: 30C6 dmi.board.vendor: Hewlett-Packard dmi.board.version: 78.11 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.25:bd09/07/2007:svnHewlett-Packard:pnPresarioC300(RH211UA#ABA):pvrF.25:rvnHewlett-Packard:rn30C6:rvr78.11:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: Presario C300 (RH211UA#ABA) dmi.product.version: F.25 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume suspend -- [Hewlett-Packard Presario C300 (RH211UA#ABA)] suspend/resume failure https://bugs.launchpad.net/bugs/456861 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 432669] Re: Please update LCDproc to 0.5.3
I just tried an upgrade from a customized 0.5.2 to 0.5.3 to see what would happen. The following user-modifiable config files are updated in 0.5.3: /etc/LCDd.conf /etc/lcdexec.conf /etc/lcdproc.conf /etc/lcdvc.conf Of those, lcdproc and lcdvc changes are inconsequential (comments only). The changes to LCDd.conf look to be completely backwards compatible, so an upgrader can use their old LCDd.conf file without any problems. If they want to use one of the newly supported devices they should choose the new config file. The changes to lcdexec.conf are more substantial. An old lcdexec.conf file should work fine with the new lcdexec. However, quite a bit of functionality was added and one default function changed completely from a placeholder to an actual function (Q). Users who have heavily tweaked their lcdexec.conf file will probably want to manually merge in the new features. -- Please update LCDproc to 0.5.3 https://bugs.launchpad.net/bugs/432669 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
