[Bug 1768235] [NEW] Ifenslave failing when bonding vlans
Public bug reported: There is a problem when running a bond on top of vlans. Running ifup with verbose enabled shows run-parts being executed in (what seems like) alphabetical order, but to enslave a vlan interface, run-part /etc/network/if-pre-up.d/vlan should be executed before run-part /etc/network/if-pre-up.d/ifenslave. Our workaround has been to add "pre-up export IFACE= IF_VLAN_RAW_DEVICE=; /etc/network/if-pre-up.d/vlan" to all vlan slaves, but it would be better to fix this in the ifup scripts themselves by reordering the run-parts. Tested with version 1.9-3ubuntu10.4 ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Description changed: There is a problem when running a bond on top of vlans. Running ifup with verbose enabled shows run-parts being executed in (what seems like) alphabetical order, but to enslave a vlan interface, run-part /etc/network/if-pre-up.d/vlan should be executed before run-part /etc/network/if-pre-up.d/ifenslave. Our workaround has been to add "pre-up export IFACE= IF_VLAN_RAW_DEVICE=; /etc/network/if-pre-up.d/vlan" to all vlan slaves, but it would be better to fix this in the ifup scripts themselves by reordering the run-parts. + + Tested with version 1.9-3ubuntu10.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768235 Title: Ifenslave failing when bonding vlans To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1768235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
Neither issue is fixed by the downgrade. As said, neither seems to have to do with vlan but with ifupdown. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
Hi @ddstreet. Completely understand your need to limit the scope of this bug. Just shared our findings, but feel free to ignore the stuff in #28 under item 2. We did a lot of extensive testing over the weekend with the latest version of your PPA package and here are our main findings: 1) We migrated from separate files in /etc/networking/interfaces.d to just declaring everything in the single /etc/networking/interfaces file. This overcomes a lot of issues with regards to bringing interfaces up in the proper order and "ifup -a" now works perfectly again. Some lessons learned for future reference: (a) to have bonds come up correctly you absolutely have to define slaves before the bond master and the primary slave before secondary slaves in the configuration file, and (b) to have a vlan come up correctly define its raw device before the vlan device. 2) Even though "ifup -a" now works again, bringing bonds up correctly at boot does not. Pretty sure this has to do with the raw interfaces being detected by the kernel and brought up by systemd in a different order at boot. As said under (1) the order really really matters. Bringing up a secondary slave before the primary slave seems to break the bond (looks like due to using the wrong MAC address) and it looks like this is what sometimes happens at boot. Our workaround mentioned in #28 under (3) mitigates this, but it's not very elegant at all. 3) There is a problem when running a bond on top of vlans. Running ifup with verbose enabled shows run-parts being executed in (what seems like) alphabetical order, but to enslave a vlan interface, run-part /etc/network/if-pre-up.d/vlan should be executed before run-part /etc/network/if-pre-up.d/ifenslave. For now we added "pre-up export IFACE= IF_VLAN_RAW_DEVICE=; /etc/network/if-pre- up.d/vlan" to all vlan slaves as a workaround, but it would be better to fix this in the ifupdown package itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
We've been doing a lot more testing and debugging and I'd like to share our findings: 1) Unfortunately it turns out this change does not fix the issue of interfaces not coming up correctly for a bond with a (static) network configuration. The race condition seems to be removed so at least there are no more hangs between bonds and their vlan children. All the interfaces also say they are UP both when running ifup and after reboot. However: - Running "ifup " does bring up the bond (and its vlans) in a working state. - Running "ifup -a" or rebooting don't actually work, causing "network not available" errors and "Destination Host Unreachable" when pinging other machines. Executing "ifdown -a; ifup -a" shows that ifupdown tries to bring up the bond BEFORE the slaves in stead of the other way around. Even though after the 60s timeout the bond and it's slaves say they are UP, they don't actually function. - We're not seeing any issues with bonds that do not have a network configuration of their own 2) The networking script stack / concept seems fundamentally flawed in three areas: 2.A) bonds relying on slaves having "bond-master" and being started by bringing up the slaves, but not supporting the master having "bond- slaves" and being able to start a bond by just bringing up the bond directly. 2.B) bringing a specific interface up automatically brings up it's child vlans. This does not make a lot of sense. The other way around does - e.g. in order to bring up a vlan we need to bring up it's raw device - but why would the ifupdown scripts assume that I want to bring up all of it's vlans when I bring up an interface that (also) serves as a raw device? In that case I would probably run "ifup -a"! 2.C) a vlan running on top of a bond cannot be brought up directly due to /sys/class/net// not existing. This results in the following: > # ifup bo-adm.2 > Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config > cat: /sys/class/net/bo-adm/mtu: No such file or directory > Device "bo-adm" does not exist. > bo-adm does not exist, unable to create bo-adm.2 > run-parts: /etc/network/if-pre-up.d/vlan exited with return code 1 > Failed to bring up bo-adm.2. 3) Our new workaround for boot has become this very intrusive systemd service: > [Unit] > Wants=network-online.target > After=network-online.target > > [Install] > WantedBy=multi-user.target > > [Service] > Type=oneshot > ExecStartPre=/sbin/ifdown bo-adm > ExecStart=/sbin/ifup enp0s3 > ExecStart=/sbin/ifup enp0s10 > ExecStop=/sbin/ifdown bo-adm > RemainAfterExit=yes > TimeoutStartSec=5min -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
@ddstreet tested with the latest version of ifupdown and vlan from your PPA with my 4 testscenario's and can confirm it works as expected. Interfaces come up correctly both when doing an "ifup -a" and during boot. One small thing I've noticed is a variation in the number of "Set name- type for VLAN subsystem. Should be visible in /proc/net/vlan/config" messages in the ifup output depending on the different scenario, even though the number of vlans is the same in all 4 tests. With 2 vlans, the 2 scenario's with bonding generate 1 message, the ones without bonding generate 4. It doesn't hurt, just something I noticed. Please check the attached log for more details on my 4 tests. ** Attachment added: "Test output for 4 different scenario's" https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1701023/+attachment/5124886/+files/vlan-tests.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759573] Re: vlan on top of untagged network won't start
@ddstreet here's how I reproduced: I created a VirtualBox VM with Xenial and 3 interfaces: enp0s3 and enp0s8 on an internal network, enp0s9 on a bridge to my LAN). Then I applied each of the 4 configurations below and ran "ifup -a". Try it and you'll see the same behavior. You are correct: the proper way to bring up the bond is to bring up it's slaves. Running ifup on the bond just hangs as you have already established. This is an entirely different bug I guess, but not my main concern right now. I've had to use "bond-master" for the enp0sX interfaces and set "bond-slaves none" for the bond to get it to work. Guess we need support for setting bond-master and bond-slaves at the same time to be bale to bring up the bond both by bringing up a slave or by bringing up the bond itself. Just to summarize: it is a duplicate of the other bug and it is fixed by your patch! == auto lo iface lo inet loopback auto enp0s9 iface enp0s9 inet static mtu 1500 address 192.168.1.9 gateway 192.168.1.1 netmask 255.255.255.0 dns-nameservers 1.1.1.1 auto enp0s3 iface enp0s3 inet manual mtu 1500 bond-master bo-adm bond-primary enp0s3 auto enp0s8 iface enp0s8 inet manual mtu 1500 bond-master bo-adm auto bo-adm iface bo-adm inet static mtu 1500 address 10.10.10.3 netmask 255.255.0.0 bond-miimon 100 bond-mode active-backup bond-slaves none bond-downdelay 200 bond-updelay 200 auto bo-adm.2 iface bo-adm.2 inet static mtu 1500 address 10.11.10.3 netmask 255.255.0.0 vlan-raw-device bo-adm == auto lo iface lo inet loopback auto enp0s9 iface enp0s9 inet static mtu 1500 address 192.168.1.9 gateway 192.168.1.1 netmask 255.255.255.0 dns-nameservers 1.1.1.1 auto enp0s3 iface enp0s3 inet manual mtu 1500 bond-master bo-adm bond-primary enp0s3 auto enp0s8 iface enp0s8 inet manual mtu 1500 bond-master bo-adm auto bo-adm iface bo-adm inet manual mtu 1500 bond-miimon 100 bond-mode active-backup bond-slaves none bond-downdelay 200 bond-updelay 200 auto bo-adm.2 iface bo-adm.2 inet static mtu 1500 address 10.11.10.3 netmask 255.255.0.0 vlan-raw-device bo-adm == auto lo iface lo inet loopback auto enp0s9 iface enp0s9 inet static mtu 1500 address 192.168.1.9 gateway 192.168.1.1 netmask 255.255.255.0 dns-nameservers 1.1.1.1 auto enp0s3 iface enp0s3 inet manual mtu 1500 auto enp0s3.2 iface enp0s3.2 inet static mtu 1500 address 10.11.10.3 netmask 255.255.0.0 vlan-raw-device enp0s3 == auto lo iface lo inet loopback auto enp0s9 iface enp0s9 inet static mtu 1500 address 192.168.1.9 gateway 192.168.1.1 netmask 255.255.255.0 dns-nameservers 1.1.1.1 auto enp0s3 iface enp0s3 inet static mtu 1500 address 10.10.10.3 netmask 255.255.0.0 bond-miimon 100 bond-mode active-backup bond-slaves none bond-downdelay 200 bond-updelay 200 auto enp0s3.2 iface enp0s3.2 inet static mtu 1500 address 10.11.10.3 netmask 255.255.0.0 vlan-raw-device enp0s3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759573 Title: vlan on top of untagg
[Bug 1759573] Re: vlan on top of untagged network won't start
*** This bug is a duplicate of bug 1701023 *** https://bugs.launchpad.net/bugs/1701023 Totally support marking this as a duplicate. As long as we get this fix pushed a.s.a.p. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759573 Title: vlan on top of untagged network won't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1759573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759573] Re: vlan on top of untagged network won't start
Got right on it! Tested your PPA version on the same testcases and it works perfectly. Indeed the same issue and the same type of resolution. Your ifquery is more elegant though, so definitely go with that! Would love to see this released and pushed a.s.a.p. because this is breaking our production systems! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759573 Title: vlan on top of untagged network won't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1759573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759573] Re: vlan on top of untagged network won't start
Been doing some troubleshooting and we think we've found the fix for this issue: The script /etc/network/if-pre-up.d/vlan contains the following section of code starting at line 62: if [ ! -e "/sys/class/net/$IFACE" ]; then # Try ifup for the raw device, if it fails then bring it up directly # this is required e.g. there is no configuration for the raw device ifup $IF_VLAN_RAW_DEVICE || ip link set up dev $IF_VLAN_RAW_DEVICE vconfig add $IF_VLAN_RAW_DEVICE $VLANID fi In this case it's trying to bring up a raw device that has already been brought up, causing it to wait forever for the lock on the raw interface to be released. It is however lacking a check on the status of the raw interface, which it shouldn't have to bring up if it already exists. So this problem goes away when we put an if-statement around that section of the code: if [ ! -e "/sys/class/net/$IFACE" ]; then if ! `cat /sys/class/net/$IF_VLAN_RAW_DEVICE/operstate 2> /dev/null | grep -q "up"`; then # Try ifup for the raw device, if it fails then bring it up directly # this is required e.g. there is no configuration for the raw device ifup $IF_VLAN_RAW_DEVICE || ip link set up dev $IF_VLAN_RAW_DEVICE fi vconfig add $IF_VLAN_RAW_DEVICE $VLANID fi It seems to work perfectly, tested on these cases: 1) a vlan on top of a single enp0sX interface without untagged network configuration 2) a vlan on top of a single enp0sX interface with its own untagged network configuration 3) a vlan on top of a bond of two enp0sX interfaces, without the bond having its own untagged network configuration 4) a vlan on top of a bond of two enp0sX interfaces, with the bond having its own untagged network configuration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759573 Title: vlan on top of untagged network won't start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1759573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding
@ddstreet I opened a separate ticket as requested a while ago. Some eyes on it would be very welcome. It's bug 1759573 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636708 Title: ifup -a does not start dependants last, causes deadlocks with vlans/bonding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1636708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759573] [NEW] vlan on top of untagged network won't start
Public bug reported:
Due to an upgrade (of probably of the ifupdown or vlan package), this specific
network configuration no longer comes up automatically:
1) Two or more network interfaces bonded
2) An untagged network configured on that bond
3) A vlan on top of that untagged network
What does come up automatically:
1) A single (e.g. unbonded) network interface with an untagged network
configured and a vlan on top of that network
2) Two or more network interfaces bonded with a vlan on top of that untagged
bond
An exact example of the configuration that doesn't work is provided
below. It fails to come up correctly, both during boot and manually. The
problem seems to be a blocking dependency loop between the bond and the
vlan.
As recommended in
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1636708/comments/13
we added dependency ordering using ifup@.service systemd units for all 4
interfaces, but this did not affect the behaviour in any way.
Perhaps related to LP bug 1573272 or bug 1636708 ?
==
Interface configuration
==
auto eno1
iface eno1 inet manual
mtu 1500
bond-master bond1
bond-primary eno1
auto eno2
iface eno2 inet manual
mtu 1500
bond-master bond1
auto bond1
iface bond1 inet static
mtu 1500
address 10.10.10.3
bond-miimon 100
bond-mode active-backup
bond-slaves none
bond-downdelay 0
bond-updelay 0
dns-nameservers 10.10.10.1
gateway 10.10.10.1
netmask 255.255.0.0
auto bond1.2
iface bond1.2 inet static
mtu 1500
address 10.11.10.3
netmask 255.255.0.0
vlan-raw-device bond1
==
When bringing up the bond
==
# ifup bond1 &
Waiting for a slave to join bond1 (will timeout after 60s)
# ps afx
(...)
ifup bond1
\_ /bin/sh -c /bin/run-parts --exit-on-error /etc/network/if-pre-up.d
\_ /bin/run-parts --exit-on-error /etc/network/if-pre-up.d
\_ /bin/sh /etc/network/if-pre-up.d/ifenslave
(...)
/lib/systemd/systemd-udevd
\_ /lib/systemd/systemd-udevd
\_ /bin/sh /lib/udev/vlan-network-interface
\_ /bin/sh /etc/network/if-pre-up.d/vlan
\_ ifup bond1
(...)
==> After waiting 60 seconds:
# ip link | grep -E 'eno[1|2]|bond1*'
eno1: mtu 1500 qdisc mq state DOWN mode DEFAULT group
default qlen 1000
eno2: mtu 1500 qdisc mq state DOWN mode DEFAULT group
default qlen 1000
bond1: mtu 1500 qdisc noqueue state
DOWN mode DEFAULT group default qlen 1000
bond1.2@bond1: mtu 1500 qdisc noqueue state
LOWERLAYERDOWN mode DEFAULT group default qlen 1000
==
When bringing up a slave
==
# ifup eno1
Waiting for bond master bond1 to be ready
# ps afx
(...)
/lib/systemd/systemd-udevd
\_ /lib/systemd/systemd-udevd
\_ /bin/sh /lib/udev/vlan-network-interface
\_ /bin/sh /etc/network/if-pre-up.d/vlan
\_ ifup bond1
\_ /bin/sh -c /bin/run-parts --exit-on-error
/etc/network/if-pre-up.d
\_ /bin/run-parts --exit-on-error /etc/network/if-pre-up.d
\_ /bin/sh /etc/network/if-pre-up.d/ifenslave
\_ /bin/sh /lib/udev/vlan-network-interface
\_ /bin/sh /etc/network/if-pre-up.d/vlan
\_ ifup bond1
(...)
# ip link | grep -E 'eno[1|2]|bond1*'
eno1: mtu 1500 qdisc mq master bond1
state UP mode DEFAULT group default qlen 1000
eno2: mtu 1500 qdisc mq state DOWN mode DEFAULT group
default qlen 1000
bond1: mtu 1500 qdisc noqueue state UP
mode DEFAULT group default qlen 1000
==
Only workaround that works
==
# ifup eno1
Waiting for bond master bond1 to be ready
# kill $(ps -ef | grep 'ifup bond1' | sed -n 2p | awk '{ print $2}')
# ifup eno2
# ip link | grep -E 'eno[1|2]|bond1*'
eno1: mtu 1500 qdisc mq master bond1
state UP mode DEFAULT group default qlen 1000
eno2: mtu 1500 qdisc mq master bond1
state UP mode DEFAULT group default qlen 1000
bond1: mtu 1500 qdisc noqueue state UP
mode DEFAULT group default qlen 1000
bond1.2@bond1: mtu 1500 qdisc noqueue state
UP mode DEFAULT group default qlen 1000
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
** Affects: vlan (Ubuntu)
Importance: Undecided
Status: New
** Tags: bonding ifupdown vlan xenial
** Also affects: vlan (Ubuntu)
Importance: Undecided
Status: New
** Tags added: ifupdown
** Tags added: vlan xenial
** Tags added: bonding
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759573
Title:
[Bug 1573272] Re: default gateway route not installed for bond interfaces through reboot
Found this bug ticket while troubleshooting a networking issue with bonding and vlans after upgrading the vlan package. Reported it here: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1636708/comments/11 Any chance this change caused that issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573272 Title: default gateway route not installed for bond interfaces through reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlan/+bug/1573272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding
We upgraded to the vlan 1.9-3.2ubuntu1.16.04.3 package and our networking broke horribly in a very similar way. Let me start with our networking configuration. Two slaves, a bond and a vlan on top of that bond: auto eno1 iface eno1 inet manual mtu 1500 bond-master bond1 bond-primary eno1 auto eno2 iface eno2 inet manual mtu 1500 bond-master bond1 auto bond1 iface bond1 inet static mtu 1500 address 10.10.10.3 bond-miimon 100 bond-mode active-backup bond-slaves none bond-downdelay 200 bond-updelay 200 dns-nameservers 10.10.0.1 netmask 255.255.0.0 auto bond1.2 iface bond1.2 inet static mtu 1500 address 10.11.10.3 netmask 255.255.0.0 vlan-raw-device bond1 This fails to come up correctly, both during boot and manually. Bringing up either eno1, eno2, bond1 or bond1.2 all result in the same problem: "ifup: waiting for lock on /run/network/ifstate.bond1". Problem seems to be that ifup tries to bring up the base bond1 interface *again*. Even if it is already up. And it gets stuck waiting for the bond1 interface to be unlocked so it can bring it up, but it is already up and thus locked so that will never happen. We also tried bringing all interfaces down and just running "ifup bond1.2" but that results in the same behavior. Only workaround that seemed to work for us was to: 1) temporarily remove the bond1.2.cfg from /etc/network/interfaces.d 2) bring up eno1, eno2 and bond1 3) put the bond1.2.cfg back in its place 4) run "ifup bond1.2" 5) using another terminal, list all open processes using "ps -ef | grep ifup" 6) kill the "ifup bond1" process The "ps -ef | grep ifup" during step 5, outputs two ifup processes. One for bond1 and one for bond1.2. As soon as we kill the "ifup bond1" process, the "ifup bond1.2" process completes immediately and correctly configures the vlan 2 subinterface. This is clearly linked to vlan, because our infiniband interfaces work just fine. Also it worked just fine before upgrading the package. So my best guess would be that something broke in the code that detects if the vlan-raw-device is up. Perhaps related to LP #1573272 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1636708 Title: ifup -a does not start dependants last, causes deadlocks with vlans/bonding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1636708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1525800] Re: [SRU] ceilometer client error when create Alarm
I see the 5.0.1. release is from Jan 19 and there have been up to 43 merges in the stable/liberty since, including this one. Could the Heat team please do a maintenance release soon? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1525800 Title: [SRU] ceilometer client error when create Alarm To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1525800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384555] Re: SQL error during alembic.migration when populating Neutron database on MariaDB 10.0
Due to this bug Neutron will only work with version <= 5.5 of mysql/mariadb, e.g. older versions. Downgrading to 5.5 isn't a solution, it's a workaround! It also means there is no database upgrade path for OpenStack, and this version limitation isn't mentioned anywhere in the documentation. I'd say that's a pretty big deal that somebody should look at! If not a Neutron core developer, then somebody that works on SQLAlchemy. If nobody is willing to address the actual technical issue then at least the version limitation should be added to the documentation. Can't force you to work on this, just saying that I think ignoring this would be a mistake. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384555 Title: SQL error during alembic.migration when populating Neutron database on MariaDB 10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1384555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384555] Re: SQL error during alembic.migration when populating Neutron database on MariaDB 10.0
** Summary changed: - Openstack Neutron Database error on filling database + SQL error during alembic.migration when populating Neutron database on MariaDB 10.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384555 Title: SQL error during alembic.migration when populating Neutron database on MariaDB 10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1384555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384555] Re: Openstack Neutron Database error on filling database
So this is indeed a bug, but the real problem is not so much the neutron database model itself but SQLAlchemy/Alembic generating SQL that doesn't work on MariaDB 10.0. Has MariaDB 10.0 broken SQL syntax? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384555 Title: Openstack Neutron Database error on filling database To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1384555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384555] Re: Openstack Neutron Database error on filling database
Can confirm that I've got the same problem on Ubuntu 14.04, Openstack Juno using the cloud-archive repository (juno-staging), ML2 with OVS and L2population plugins, flat and vxlan network(s), L3 HA and DVR enabled. Used puppet-neutron to deploy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384555 Title: Openstack Neutron Database error on filling database To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1384555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384555] Re: Openstack Neutron Database error on filling database
** Changed in: neutron Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1384555 Title: Openstack Neutron Database error on filling database To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1384555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384555] Re: Openstack Neutron Database error.
** Also affects: neutron (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/1384555 Title: Openstack Neutron Database error. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1384555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303876] Re: VPN agent dependencies are foobar
Unlike the l3 agent package the vpn agent package is lacking the /etc/init/neutron-l3-agent.conf file required to start the l3 agent. Does the vpn agent provide a superset of functionality which means that if you're already running the vpn agent you don't need to separately run the l3 agent? Or is this a mistake which means this bug needs to be reopened? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303876 Title: VPN agent dependencies are foobar To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1303876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 573659] Re: Compose new email window incorrectly resizes when viewing attachment bar
** Attachment added: "what happens to the not maximized window when the attachment bar is hidden again" http://launchpadlibrarian.net/47258986/window%20no%20attachment%20again.png -- Compose new email window incorrectly resizes when viewing attachment bar https://bugs.launchpad.net/bugs/573659 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 573659] Re: Compose new email window incorrectly resizes when viewing attachment bar
** Attachment added: "What happens to the not maximized window when the attachment bar is opened" http://launchpadlibrarian.net/47257742/window%20with%20attachment.png -- Compose new email window incorrectly resizes when viewing attachment bar https://bugs.launchpad.net/bugs/573659 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 573659] Re: Compose new email window incorrectly resizes when viewing attachment bar
** Attachment added: "The basic 'compose email' window but not maximized" http://launchpadlibrarian.net/47257111/window%20no%20attachment.png -- Compose new email window incorrectly resizes when viewing attachment bar https://bugs.launchpad.net/bugs/573659 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 573659] Re: Compose new email window incorrectly resizes when viewing attachment bar
** Attachment added: "What happens to the full screen window when the attachment bar is opened" http://launchpadlibrarian.net/47256996/full%20screen%20attachment.png -- Compose new email window incorrectly resizes when viewing attachment bar https://bugs.launchpad.net/bugs/573659 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 573659] [NEW] Compose new email window incorrectly resizes when viewing attachment bar
Public bug reported: Binary package hint: evolution Upgraded to Lucid and now consistently experiencing the following bug with Evolution: Steps to recreate: 1. Start a new email message (ctrl+N) 2. Display the "attachment bar" at the bottom of the window, either by clicking the + bottom left or by attaching a file to the message which will automatically show the attachment bar. Effect: Displaying the attachment bar (e.g. the white area which displays the attached files) increases the height of the window, even if the window is already as high as the available desktop height. I lose the metacity window controls if the window was already maximized and the window jumps up or down every time i click anywhere on it. A high 'windowed' compose window will extend beond the desktop height. Closing the attachment bar will reduce the window height back to the original height. It will just keep it the same height, making the regular text area higher. This is a mess and forces me to use keyboard shortcuts only after attaching files. Will add some screenshots to show what happens. Details: Ubuntu version: Lucid UNE Desktop session: regular GNOME session Evolution version: 2.28.3 Screen resolution: 1024 x 576 Desktop size: screen resolution minus a 24 pixel high GNOME top panel ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: attachement bar evolution window -- Compose new email window incorrectly resizes when viewing attachment bar https://bugs.launchpad.net/bugs/573659 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 573659] Re: Compose new email window incorrectly resizes when viewing attachment bar
** Attachment added: "Regular 'compose new email' full screen window" http://launchpadlibrarian.net/47256902/full%20screen%20no%20attachment%20bar.png -- Compose new email window incorrectly resizes when viewing attachment bar https://bugs.launchpad.net/bugs/573659 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 256478] Re: Support contact grouping (metacontacts)
Nice quote by Paul Kishimoto on the related bug on GNOME bugzilla: So the following have all been mentioned: People (0.0.6 release two years old, https://launchpad.net/people-core) Soylent (no commits for 20+ months, http://git.gnome.org/browse/soylent) Galago (unmaintained, per comment #19) EDS-feed (unmaintained, per comment #19) EDS-sync (apparently no releases in 2+ years? http://vcs.maemo.org/svn/eds/trunk/eds-sync/ChangeLog) GNOME Online Desktop (apparently not actively developed) ...unless there is better evidence that these are or will become usable, that leaves: * No outside library to wait on, * One developer who thinks "metacontacts like in pidgin" are "stupid", and * 50+ others (including https://bugs.launchpad.net/bugs/392507 & duplicates) who want such "stupid" metacontacts. I would grant that, *if* any of the above projects actually was usable, they would be a better solution than Pidgin-style contact grouping. No one has explained how contact grouping is worse than no contact grouping. -- Support contact grouping (metacontacts) https://bugs.launchpad.net/bugs/256478 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 563879] Re: evolution-data-server consumes massive amounts of memory, invokes OOM killer
Running Lucid Beta. Have 4 evolution-data-server processes when I just logged in without even having opened Evolution that each consume about 50 MB. This means e-d-s is using 200 MB of my 1 GB just to run in the background I have configured in Evolution: 1 regular POP3 account 2 GMail accounts 2 Google Calendar accounts 3 Google Calendar read-only accounts (they have authorized read-only access to one of those 2 regular Google Calendar accounts) 1 GMail addressbook -- evolution-data-server consumes massive amounts of memory, invokes OOM killer https://bugs.launchpad.net/bugs/563879 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 80855] Re: greasemonkey plugin does not work
Confirmed on Lucid. -- greasemonkey plugin does not work https://bugs.launchpad.net/bugs/80855 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 528887] Re: maximus does not give default focus to newly started apps in combination with efl launcher
This screenshot shows what happens in my case. I was using Evolution and then opened Getting Things GNOME through its tray icon. The screen pops up, but the title bar retains its focus on Evolution. ** Attachment added: "Schermafdruk.png" http://launchpadlibrarian.net/43512234/Schermafdruk.png -- maximus does not give default focus to newly started apps in combination with efl launcher https://bugs.launchpad.net/bugs/528887 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 528887] Re: maximus does not give default focus to newly started apps in combination with efl launcher
I think I have the same problem in Lucid Beta1: Sometimes windows open maximized and on top, but do not seem to have focus. This means the "title bar" part in the UNE top bar does not display the name of the newly raised window, but of the one previously having focus. If you click the close button (e.g. the X on the right), the wrong windown gets closed (the one below having focus, not the one on top that you're looking at). Clicking no the application window after it was raised then does give it focus after all, and consequently behaves as expected. I had this issue a couple of days ago when double-clicking on images in Nautilus. It raises a maximized Eye Of Gnome window but the title bar keeps saying Nautilus. If I push the close button I close the Nautilus window, not EOG. Unfortunately I seem to be unable to reproduce this issue right now. Another one I do still have and am able to reproduce consistently right now is with "Getting Things Gnome". I have enabled its tray icon. If the application is minimized to tray, I click on the tray icon and click on "Display main window" (roughly translated from Dutch) it opens a new GTG window, maximized, on top, but not focussed. The title bar still refers to the window that had focus before opening the GTG window. This issue is quite confusing, especially for novice users. Before you know it they start complaining about "disappearing windows" and turn their back on Ubuntu. Also, let me know if this is not the same bug as reported earliers so I can repost this as a seperate bug. -- maximus does not give default focus to newly started apps in combination with efl launcher https://bugs.launchpad.net/bugs/528887 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 433651] Re: no text wrap when typing in the message entry
I can confirm this bug in Lucid Beta 1. Text wrap works as it should if the IRC room contactlist is disabled (uncheck Conversation > Show contactlist). If you enable the contactlist, the window automatically grows (width only) when typing texts longer than the window width. It does not wrap text in the input field anymore. Also, I noticed that the window already starts widening before you've reached the end of the input field. Looks like the right part of the input field that remains blank is about the same width as the default width of the contactlist. Can't confirm that though, because I had already made it smaller. This bug is really annoying, especially on small screens like netbooks. The window is able to grow beond the size of the desktop itself. I've tried maximizing the window, but even then it still widens further. A part just drops off the screen. This makes it a real usability bug so I think the importance should be higher than the current 'low'. -- no text wrap when typing in the message entry https://bugs.launchpad.net/bugs/433651 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 216353] Re: 2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() )
I'm unable to test this. Fixed the issue a long time ago by changing cables as described in the comment by Spohl (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/216353/comments/14). -- 2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() ) https://bugs.launchpad.net/bugs/216353 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 179047] Re: user friendy monitor/tv-out hotplugging support: a display manager applet?
Very well, moved to Brainstorm. I would like to invite everyone that supports (or dislikes) this suggestion to vote: http://brainstorm.ubuntu.com/idea/13656 -- user friendy monitor/tv-out hotplugging support: a display manager applet? https://bugs.launchpad.net/bugs/179047 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 218931] Re: liferea can't open epiphany browser when click on a news
Confirm this bug is "caused by" favicon extension of epiphany. Disabling this extension "solved" it for me. Not sure whether this then is a liferea bug at all. Maybe this is strictly an epiphany(-extensions) bug? ** Changed in: epiphany-extensions (Ubuntu) Sourcepackagename: liferea => epiphany-extensions -- liferea can't open epiphany browser when click on a news https://bugs.launchpad.net/bugs/218931 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 175503] Re: User-friendly automounting of ntfs partitions with an unclean logfile
I like the suggestion by Ric Flomag. It didn't make it into Hardy so I've marked it for Intrepid. Hope it makes it this time. -- User-friendly automounting of ntfs partitions with an unclean logfile https://bugs.launchpad.net/bugs/175503 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 216353] Re: 2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() )
Just updated the computer that I've experienced this bug on and it is not fixed in the 2.6.24-19 kernel release. -- 2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() ) https://bugs.launchpad.net/bugs/216353 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 159026] Re: Lenovo Thinkpad x41 Tablet and X60 Tablet rotate events
forgot one: http://ostebaronen.dk/?p=32 -- Lenovo Thinkpad x41 Tablet and X60 Tablet rotate events https://bugs.launchpad.net/bugs/159026 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 159026] Re: Lenovo Thinkpad x41 Tablet and X60 Tablet rotate events
These pages contain some nice insights and scripts as well: * http://www.thinkwiki.org/wiki/Installing_Ubuntu_6.10_on_a_ThinkPad_X41_Tablet * http://www.krizka.net/2008/02/13/thinkpad-x61-tablet-automatic-screen-rotation-under-linux/ * http://www.krizka.net/2008/01/23/thinkpad-x61-tablet-tilt-detection-and-ubuntu-hardy-heron/ * http://luke.no-ip.org/x60tablet/ -- Lenovo Thinkpad x41 Tablet and X60 Tablet rotate events https://bugs.launchpad.net/bugs/159026 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 159026] Re: Lenovo Thinkpad x41 Tablet and X60 Tablet rotate events
I'm not a programmer so excuse me if this remark is completely illogical. I was reading this and wondering why we need a rotate_daemon? There seem to be a number of actions related to screen rotation: * rotating the screen to and from tablet mode * vertically rotating the laptop itself * pushing the rotate display button on the screen edge If all these actions trigger ACPI events, couldn't they just be handled by an ACPI action script that executes xrandr and xsetwacom rotate commands? If we do need a rotate daemon, can't it then handle all these actions so it can just be started at boot? If not, I guess it will be responsible for handling the accelerometer-driven events. It should be able to detect whether the laptop is in tablet mode or not, right? This way it could be enabled at all times (e.g. loaded at boot). p.s. other distributions either support it already or are not paying much attention to it: * https://bugzilla.redhat.com/show_bug.cgi?id=366211 * http://en.opensuse.org/TabletPCs -- Lenovo Thinkpad x41 Tablet and X60 Tablet rotate events https://bugs.launchpad.net/bugs/159026 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 216353] Re: 2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() )
Not fixed in 2.6.24-17 kernel release. ** Changed in: linux (Ubuntu) Status: Triaged => Confirmed -- 2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() ) https://bugs.launchpad.net/bugs/216353 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 216353] Re: 2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() )
I see the status has been set to 'Triaged'. Don't know what was done but the -17 kernel does not solve this error. I manually have to set this to the -12 series again! I'm sorry to have to say this but this is unacceptable, most certainly for a LTS release. The only reason I can run Hardy on this machine is because I started using it when it was still Beta, otherwise I wouldn't have a 2.6.24-12 kernel. This is a critical bug because people with older machines won't get Ubuntu to boot. Please fix this a.s.a.p. -- 2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() ) https://bugs.launchpad.net/bugs/216353 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 205060] Re: Random gnome freeze when attempting to logout/restart computer
I had a resembling issue before on Gutsy. Strange thing was that I was the only one of the four users on the computer that had this issue. When upgrading to Hardy I backed up my home dir, emptied it and only put back the config files I really needed. Have you tried adding a new user and logging in and out with that "empty" account? -- Random gnome freeze when attempting to logout/restart computer https://bugs.launchpad.net/bugs/205060 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 229043] Re: System freezes when login out
Have about the same issue: * Shutting down always works as expected * Logging out often results in a black screen when restarting GDM. - The default Ubuntu sound is played just like when the login box is presented, only nothing is displayed. - The complete system freezes. nothing responds: monitor is in standby mode, I see no mouse pointer and the keyboard does nothing. Not even the light of the NumLock or CapsLock light when pushing those buttons. - Only a hard reset is possible. no ctrl+alt+del, ctrl+alt+backspace, ctrl+alt+f1, etc. * Often it doesn't hang and I do get the login screen. Then logging in almost always results in the computer freezing just after that with just a yellow screen. No GNOME menu bars, windows or messages yet. Just like above, nothing works except a hard reset. This happens regardless of whether I'm logging in the same user again or a different one. I have no idea how to provide additional debug information, because it freezes completely. This problem only applies to Hardy. Had Dapper, Edgy, Feisty and Gutsy on the same hardware before and it worked fine. Running amd64 and the nvdia propriatary video driver. -- System freezes when login out https://bugs.launchpad.net/bugs/229043 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 218931] Re: liferea can't open epiphany browser when click on a news
I can confirm this issue on Hardy x86. Been using it from Flight6 and now running the new stable release and this has been an issue in every Hardy release. -- liferea can't open epiphany browser when click on a news https://bugs.launchpad.net/bugs/218931 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 159026] Re: Lenovo Thinkpad x41 Tablet and X60 Tablet rotate events
I support this request. Florian, there is also a sensor on my X60 that senses which side of the screen is down when holding it vertically (in stead of laying it down on a table). Windows uses it to rotate the screen accordingly automatically. Is that included in your scripts? If not, could you look in to this? -- Lenovo Thinkpad x41 Tablet and X60 Tablet rotate events https://bugs.launchpad.net/bugs/159026 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 216353] Re: 2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() )
** Attachment added: "DSCN2262.JPG" http://launchpadlibrarian.net/13380778/DSCN2262.JPG -- 2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() ) https://bugs.launchpad.net/bugs/216353 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 216353] [NEW] 2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() )
Public bug reported: I'm testing Hardy and ran into the following issue: The 2.6.24-12 kernel boots and the system works just fine. Both the 2.6.24-14 and -16 do not boot. Immediately after selecting the kernel in GRUB, it hangs while loading the kernel, giving a load of ATA related errors and endig with the message: ldm_validate_partition_table(): Disk read failed. I've taken a picture of the screen output and added it as an attachment to this bug report. The hard disk uses PATA. Below is the lspci for some info about the hardware it's running on. $ lsb_release -rd Description:Ubuntu hardy (development branch) Release:8.04 $ uname -r 2.6.24-12-generic $ lspci 00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2) 00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1) 00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2) 00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3) 00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3) 00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1) 00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 04:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 2.6.24 Kernel boot hangs on disk read ( ldm_validate_partition_table() ) https://bugs.launchpad.net/bugs/216353 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 205440] Re: package language-pack-en 1:8. 04+20080308 failed to install/upgrade: Versuche, »/usr/share/locale-langpack/en_GB/LC_MESSAGES/sha red-mime-info.mo« zu überschreiben, welches auch in
** Also affects: language-pack-nl (Ubuntu) Importance: Undecided Status: New ** Also affects: language-pack-fr (Ubuntu) Importance: Undecided Status: New -- package language-pack-en 1:8.04+20080308 failed to install/upgrade: Versuche, »/usr/share/locale-langpack/en_GB/LC_MESSAGES/shared-mime-info.mo« zu überschreiben, welches auch in Paket language-pack-gnome-en ist https://bugs.launchpad.net/bugs/205440 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 205850] Re: package conflict: language-pack-gnome-zh and language-pack-zh
*** This bug is a duplicate of bug 205440 *** https://bugs.launchpad.net/bugs/205440 ** This bug has been marked a duplicate of bug 205440 package language-pack-en 1:8.04+20080308 failed to install/upgrade: Versuche, »/usr/share/locale-langpack/en_GB/LC_MESSAGES/shared-mime-info.mo« zu überschreiben, welches auch in Paket language-pack-gnome-en ist -- package conflict: language-pack-gnome-zh and language-pack-zh https://bugs.launchpad.net/bugs/205850 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 191281] Re: [hardy] Xorg freezes on 945GM to black screen with artifacts and mouse pointer, no compiz active
I have an Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (according to lspci) and get this issue just as well. The screen turns black and nothing helps except rebooting. I am using compiz. This issue did not exist under Gutsy. Found out that I can ctrl+alt+f1 to the terminal as soon as it turns black and then trigger a reboot using ctrl+alt+del. nothing else seems to work. There have got to be more issues submitted about this... -- [hardy] Xorg freezes on 945GM to black screen with artifacts and mouse pointer, no compiz active https://bugs.launchpad.net/bugs/191281 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 179047] user friendy monitor/tv-out hotplugging support: a display manager applet?
Public bug reported: Yesterday I got tv-out working on my laptop running Ubuntu Gutsy. It's great to see that display hotplugging is finally supported but to turn tv-out on and off I need to enter several xrandr commands. I believe this does not comply with the "it just works" idea behind Ubuntu. So I think we need a GUI tool to make hotplugging of displays easier than Windows or MacOS. Can we get something like a "Display manager applet", comparable to the NetworkManager and Bluetooth manager, that notifies the user whenever a new display is connected? The user can then click on the applet icon, which pop up a window which allows the user to configure the new display (turn screen on/off, set to clone mode or extended desktop) for the current session. Limiting these settings to the current session removes the need for the user to have admin privileges, whilst allowing ad-hoc display support. To me this seems desirable, especially for laptop and other portable device users which regularly want to connect their fixed office monitor to work on, a TV to play a movie or a beamer to show a presentation. The infrastructure seems to be in place already: xorg/xrandr already supports hotplugging, DBUS can relay the new (and removed) connection notification to the applet and the window i mentioned could be the same as the screens tab of the current "Screens and graphics preferences window" (http://www.phoronix.net/image.php?id=814&image=ubuntu_displayconfig_1), all though there would be two changes needed: * it does not seem to support tv-out (composite or s-video) as a screen yet. * opening this preference window requires admin privileges for it currently only allows changing permanent, system-wide display settings. I know it all sounds very easy and if I were a programmer I'd try to build it. Unfortunately I'm unable to do so. Could someone please help a bunch of Ubuntu users out with this feature? ** Affects: ubuntu Importance: Undecided Status: New -- user friendy monitor/tv-out hotplugging support: a display manager applet? https://bugs.launchpad.net/bugs/179047 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 37239] Re: VPN connection should alter /etc/resolv.conf
I've read the thread and concluded that I think we might be talking about several different bugs which appear alike but might have to be split (disclaimer: i am not a programmer so I'm not sure!). The things I've read about: 1) Which DNS servers (resolv.conf) and routes NM should set for: 1A) A VPN connection through which ALL traffic should be tunneled. (= nameservers in resolv.conf should be replaced by those obtained from the VPN server and the default route should refer traffic to the tun/tap interface) 1B) A VPN connection through which traffic only for specific IP ranges, like for example 192.168.1.x/24, should be tunneled. (= no nameserver changes, only update routes to refer all traffic for those IP ranges to the tun/tap interface) 2) If NM rightfully sets resolv.conf (for example due to new DNS servers from the VPN connection) the dhcp client should be prevented from overwriting resolv.conf when updating the lease. (e.g. all resolv.conf setting should be managed by NM when used). -- I can confirm one bug, being the OpenVPN bug on the latest Gutsy: Trying to do the 1B thing and as soon as i connect, resolv.conf gets updated to only containing the line "# generated by NetworkManager, do not edit!". As soon as I disconnect VPN, resolv.conf contains the proper nameservers provided by the fixed network's dhcp server again. I've also got a Windows VPN (PPTP) connection which is also only supposed to reroute traffic for a specific IP range and that works fine. To me this means that this is an OpenVPN-plugin specific bug. -- VPN connection should alter /etc/resolv.conf https://bugs.launchpad.net/bugs/37239 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175503] User-friendly automounting of ntfs partitions with an unclean logfile
Public bug reported: Binary package hint: ntfs-3g When you try to mount a ntfs drive that was not safely removed last time you'll get the following error: > Cannot mount volume > unable to mount the volume > > Details: > $LogFile indicates unclean shutdown (0,0) Failed to mount '/dev/hda1/': > Operation not supported > Mount is denied because NTFS is marked to be in use. Choose one action: > > Choice 1: If you have Windows then disconnect the external devices by > clicking on the 'Safely > Remove Hardware' icon in the Windows taskbar then shutdown Windows cleanly. > > Choice 2: If you don't have Windows then you can use the 'force' option for > your own responsibility. > For example type on the command line: mount -t ntfs-3g /dev/hda1 /media/disk > -o force or add the > option to the relevant row in the /etc/fstab file: /dev/hda1 /media/disk > ntfs-3g defaults,force 0 0 This is particularly annoying when working with external harddisks which Ms Windows users often just unplug without properly unmounting. The thing that suprises me is that both Ms Windows and Apple's OS X do not complain about this while linux does. To me this does not seem comply with the "it just works" idea behind the Ubuntu distribution. Both choices do not offer a real solution: going back to Windows to cleanly unmount both requires having Windows and if you do, this is not a user-friendly solution. Adding a line to fstab also is not user- friendly, it won't work when you're faced with different external drives all the time and adding a drive to fstab also seems to hinder the automounting process of GNOME, which again is not user-friendly. I'm sure there is a risk when ignoring the unclean logfile but to me this seems like punishing the user after the damage is already done. So the question of this bug is: how can this be solved? Three solutions I can think of at this time could be: 1) Fix handeling of unclean logfiles in upstream ntfs-3g. If this was easy I guess it would already have been done. 2) Removing the unclean logfile check completely from the upstream ntfs-3g package in a next version so it won't complain and just mount, like Windows and OS X do. 3) Adding a config file feature to the next version of ntfs-3g that contains a variable like ignore_unclean_logfile which allows you (or then preferably enabled by default in the ubuntu package) to set the "force" flag globally in stead of per-disk. Hope this is a clear description of my (and many other peoples) annoyance. I hope this can be solved! Thanks! ** Affects: ntfs-3g (Ubuntu) Importance: Undecided Status: New -- User-friendly automounting of ntfs partitions with an unclean logfile https://bugs.launchpad.net/bugs/175503 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 94068] Re: Can't configure IP addr's on multiple NICs
Have the same problem: My computer has got 2 regular network cards and a wifi card. Of the regular cards, one uses DHCP and the other has a static NIC. In Edgy, NetworkManager let me choose between the DHCP card or a wifi connection and thus not touching the static card. It worked like a charm. In Feisty, NetworkManager shows all 3 options and blocks setting the IP address of the static card at boot or enabling it by switching to it in GNOME. This renders it useless. NetworkManager was supposed to disregard connections configured manually in the interfaces file but apparently it no longer does. This makes it a critical issue for me, forcing me to manually disable NetworkManager and finding a new wifi roaming solution. Required solution: 1. automatically enable static NICs as was done before! 2. either have NetworkManager keep its hands off static networks or have it allow multiple active network connections at the same time (or preferently enable both solutions!) -- Can't configure IP addr's on multiple NICs https://bugs.launchpad.net/bugs/94068 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66900] Re: APIC error on CPU0: 40(40)
I've got the same errors on my Asus L5800C laptop. Even worse: i've had no problems running breezy and dapper but I am since recently experiencing random hangups in Edgy. This results in the keyboards (1 onboard, 1 ps/2 through usb) not responding (mouse and touchpad still do). Then either no program in gnome starts anymore or when I can make it reboot it hangs on errors from the bcm43xx Broadcom wifi driver. I have to do a hard reset and then at boot when I have to enter my boot password set in the bios only the laptop keyboard works, the external one does not until linux boots. Just did a completely clean install of Edgy yesterday and this still seems to occur. Sometimes nothing happens for two days straight and sometimes it hangs three times in one day. I hope these data will help: $ uname -a Linux toMeloos 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux $ uptime 10:29:13 up 9:11, 2 users, load average: 0.14, 0.10, 0.09 $ dmesg |grep "APIC error on CPU0:" | wc --lines 56 => please note that during this uptime it was idle for all but about one hour. $ lspci 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 645xx (rev 03) 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP) 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 14) 00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller 00:02.3 FireWire (IEEE 1394): Silicon Integrated Systems [SiS] FireWire Controller 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] 00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0) 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0) 00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller 00:0a.0 CardBus bridge: ENE Technology Inc CB-720/2/4 Cardbus Controller (rev 01) 00:0a.1 CardBus bridge: ENE Technology Inc CB-720/2/4 Cardbus Controller (rev 01) 00:0a.2 FLASH memory: ENE Technology Inc CB710 Memory Card Reader Controller 00:0c.0 Network controller: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller (rev 02) 00:0d.0 Ethernet controller: 3Com Corporation 3c940 10/100/1000Base-T [Marvell] (rev 12) 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf [FireGL 9000] (rev 01) 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) $ lsmod Module Size Used by binfmt_misc13448 1 rfcomm 42260 2 l2cap 27136 5 rfcomm nfs 250316 1 lockd 67976 2 nfs sunrpc165948 3 nfs,lockd ipv6 272288 12 radeon118816 2 drm74644 3 radeon speedstep_lib 5764 0 cpufreq_userspace 5408 0 cpufreq_stats 7744 0 freq_table 6048 1 cpufreq_stats cpufreq_powersave 2944 0 cpufreq_ondemand8876 0 cpufreq_conservative 8712 0 video 17540 0 tc1100_wmi 8324 0 sbs16804 0 sony_acpi 6412 0 pcc_acpi 14080 0 i2c_ec 6272 1 sbs hotkey 11556 0 dev_acpi 12292 0 button 7952 0 battery11652 0 container 5632 0 ac 6788 0 asus_acpi 17688 0 af_packet 24584 2 fuse 43912 0 sbp2 24584 0 scsi_mod 144648 1 sbp2 lp 12964 0 8139cp 24832 0 8139too29056 0 mii 6912 2 8139cp,8139too joydev 11200 0 tsdev 9152 0 hci_usb18068 1 bluetooth 53476 7 rfcomm,l2cap,hci_usb usbhid 45152 0 snd_intel8x0 34844 1 snd_ac97_codec 97696 1 snd_intel8x0 snd_ac97_bus3456 1 snd_ac97_codec usblp 15488 0 bcm43xx 127252 0 snd_pcm_oss47360 0 snd_mixer_oss 19584 1 snd_pcm_oss pcmcia 40380 0 irtty_sir 10112 0 sir_dev18308 1 irtty_sir irda 214332 2 irtty_sir,sir_dev evdev 11392 3 crc_ccitt 3200 1 irda ieee80211softmac 33792 1 bcm43xx ieee80211 35272 2 bcm43xx,ieee80211softmac ieee80211_crypt 7552 1 ieee80211 serio_raw 8452 0 snd_pcm84612 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 25348 1 sn
[Bug 59946] Re: Admin tools require admin group membership
Instructions by Justin Dugger solved my problem. I guess some kind of check script should be pushed as an update of some sort, to make sure this is solved on all systems. Not that this matters in my case, I need to completely re-install Ubuntu because of all the upgrade issues :( -- Admin tools require admin group membership https://launchpad.net/bugs/59946 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59946] Re: Admin tools require admin group membership
Breezy -> Dapper -> Edgy Rebooted several times. Still not solved. Maybe this helps. The username I'm using is 'tom' which was created during the breezy installation. This user is in the following groups: $ cat /etc/group |grep "tom" adm:x:4:tom dialout:x:20:tom,cupsys cdrom:x:24:tom,hal,haldaemon floppy:x:25:tom,hal,haldaemon audio:x:29:tom dip:x:30:tom video:x:44:tom plugdev:x:46:tom,hal,haldaemon tom:x:1000: lpadmin:x:104:tom scanner:x:105:tom,cupsys,hplip -- Admin tools require admin group membership https://launchpad.net/bugs/59946 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69029] Re: The configuration could not be loaded
*** This bug is a duplicate of bug 59946 *** There is no output. just the pop-up with the "The configuration could not be loaded, You are not allowed to access the system configuration." message. I'm running the user that was created during the installation. It worked fine under dapper, but not under edgy. This user is in the groups: $ cat /etc/group |grep tom adm:x:4:tom dialout:x:20:tom,cupsys cdrom:x:24:tom,hal,haldaemon floppy:x:25:tom,hal,haldaemon audio:x:29:tom dip:x:30:tom video:x:44:tom plugdev:x:46:tom,hal,haldaemon tom:x:1000: lpadmin:x:104:tom scanner:x:105:tom,cupsys,hplip -- The configuration could not be loaded https://launchpad.net/bugs/69029 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50477] Re: Please backport newer rhythmbox to dapper-backports
Tested the deb posted by John Dong and it has been working fine on my dapper environment for weeks now. -- Please backport newer rhythmbox to dapper-backports https://launchpad.net/bugs/50477 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
