[Bug 366780] Re: Please provide a mechanism whereby Wi-Fi networks can be prioritized
There won't ever be user-defined priorities in NM. Does that mean that someone needs to create something else than NM, if NM never will solve the problems users have? That's kind of a sad statement. Please confirm. NM connects to the last network you've connected to that it can find. When you connect, NM timestamps the network, and it will first connect to the most recent network you have chosen. This doesn't solve the problem. One problem: I have two networks, 2.4GHz and 5GHz. The 2.4 have better range (of course), but when the 5GHz is available, I want NM to switch to that one. But if it previously connected to the 2.4, it will NEVER switch to 5GHz again. Similar for a wider (public) network that also covers your home. When you're home, you want that network to be picked. But when you leave home and use the public network (eduroam?), NM will never pick your home network again, because it's also covered by the public network. And the public network now have a better timestamp. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/366780 Title: Please provide a mechanism whereby Wi-Fi networks can be prioritized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/366780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559761] Re: mountall needs to flush plymouth message queue before emitting upstart events
I have no idea what's going on, but something is really odd with mountall; the machine I just upgraded to lucid refused to boot until I rewrote /etc/fstab to only contain /. Otherwise I'd hang on some nondescript plymouth/mountall error (each in a different console). -- mountall needs to flush plymouth message queue before emitting upstart events https://bugs.launchpad.net/bugs/559761 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 499881] Re: usb storage with ext4 does not work in lucid
I'm not running lucid, but it _seems_ that the combination of ext4 on USB with karmic makes my machine instable and eventually crashing. ICH8 family USB. Can this be related? -- usb storage with ext4 does not work in lucid https://bugs.launchpad.net/bugs/499881 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 514276] [NEW] mount ext4 noextents option broken
Public bug reported: Binary package hint: util-linux # mount /dev/sdg1 /media6 -t ext4 -o ro,noextents -- [88823.523117] EXT4-fs (sdg1): Unrecognized mount option noextents or missing value Possibly related bug: https://bugs.launchpad.net/ubuntu/+source/util- linux/+bug/427260 (Quite possibly the noextents mount option is a myth?) % lsb_release -rd Description:Ubuntu 9.10 Release:9.10 % apt-cache policy util-linux util-linux: Installed: 2.16-1ubuntu5 Candidate: 2.16-1ubuntu5 Version table: *** 2.16-1ubuntu5 0 500 http://se.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status % uname -a Linux iris 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- mount ext4 noextents option broken https://bugs.launchpad.net/bugs/514276 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 284229] Re: console-kit-daemon using a lot of cpu
Frankly, I can't really find out which problem it's supposed to solve, maybe you can elaborate? Google searches only turn up problems, and # man console-kit-daemon No manual entry for console-kit-daemon doesn't help either. (But there doesn't seem to be many manpages around these days.) I'm sticking to my cron-killall-solution for now. Since it's a problem with data structures leaking it seems to work fine. -- console-kit-daemon using a lot of cpu https://bugs.launchpad.net/bugs/284229 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 284229] Re: console-kit-daemon using a lot of cpu
Is certainly should be backported. I've solved it by killing it regularly though: # crontab -l -u root # m h dom mon dow command 0 10,20 * * * killall console-kit-daemon ... -- console-kit-daemon using a lot of cpu https://bugs.launchpad.net/bugs/284229 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 284229] Re: console-kit-daemon using a lot of cpu
This seems plausible. I have a 5 minute interval cron job (munin). Still need my outputs? -- console-kit-daemon using a lot of cpu https://bugs.launchpad.net/bugs/284229 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 284229] Re: console-kit-daemon using a lot of cpu
Which reminds me, mine is now up to 6.5% cpu (almost 4 cpu-seconds a minute). Attaching new strace, run at this moment: 17226 root 20 0 177m 13m 1648 S0 0.7 176:55.62 console-kit-dae 17226 root 20 0 177m 13m 1648 S 62 0.7 176:57.50 console-kit-dae 17226 root 20 0 177m 13m 1648 S0 0.7 176:57.50 console-kit-dae 17226 root 20 0 177m 13m 1648 S0 0.7 176:57.50 console-kit-dae ... 17226 root 20 0 177m 13m 1648 S0 0.7 176:57.50 console-kit-dae 17226 root 20 0 177m 13m 1648 R 93 0.7 177:00.34 console-kit-dae 17226 root 20 0 177m 13m 1648 R 96 0.7 177:03.22 console-kit-dae 17226 root 20 0 177m 13m 1648 S 98 0.7 177:06.16 console-kit-dae 17226 root 20 0 177m 13m 1648 S0 0.7 177:06.16 console-kit-dae 17226 root 20 0 177m 13m 1648 S0 0.7 177:06.16 console-kit-dae ... 17226 root 20 0 177m 13m 1648 S0 0.7 177:06.16 console-kit-dae 17226 root 20 0 177m 13m 1648 S0 0.7 177:06.16 console-kit-dae 17226 root 20 0 177m 13m 1648 R3 0.7 177:06.24 console-kit-dae 17226 root 20 0 177m 13m 1648 S 29 0.7 177:07.12 console-kit-dae 17226 root 20 0 177m 13m 1648 R1 0.7 177:07.14 console-kit-dae 17226 root 20 0 177m 13m 1648 S 62 0.7 177:09.00 console-kit-dae 17226 root 20 0 177m 13m 1648 S0 0.7 177:09.00 console-kit-dae ... ** Attachment added: console-kit-strace3 http://launchpadlibrarian.net/19113211/console-kit-strace3 -- console-kit-daemon using a lot of cpu https://bugs.launchpad.net/bugs/284229 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 284229] Re: console-kit-daemon using a lot of cpu
It's not using a lot of cpu yet, but it's up to an average of 3% now, 1.8 cpu-seconds per minute on average. PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 17226 root 20 0 175m 9684 1748 R 16 0.5 53:39.34 console-kit-dae From the strace and the way top keeps showing 0% cpu I would say it uses all those cpu-seconds are used in the beginning of the minute... yep. # top -b | grep console 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:40.10 console-kit-dae 17226 root 20 0 175m 9684 1748 R 25 0.5 53:40.85 console-kit-dae 17226 root 20 0 175m 9684 1748 S 18 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:41.39 console-kit-dae 17226 root 20 0 175m 9684 1748 R 34 0.5 53:42.44 console-kit-dae 17226 root 20 0 175m 9684 1748 S 77 0.5 53:44.76 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:44.76 console-kit-dae 17226 root 20 0 175m 9684 1748 S 14 0.5 53:45.19 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:45.19 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:45.19 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:45.19 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:45.19 console-kit-dae 17226 root 20 0 175m 9684 1748 S0 0.5 53:45.19 console-kit-dae ... Can't see anything special in the strace, but here you go... it's run at the same time as the top-b above. ** Attachment added: strace-trace-4 http://launchpadlibrarian.net/18977896/strace-trace-4 -- console-kit-daemon using a lot of cpu https://bugs.launchpad.net/bugs/284229 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 284229] Re: console-kit-dae using a lot of cpu
Seems repeatable, at least: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 28634 root 20 0 179m 17m 1380 S 55 0.9 453:26.99 console-kit-dae Since noone seems interested in this, I will turn off running of console-kit-daemon for now. -- console-kit-dae using a lot of cpu https://bugs.launchpad.net/bugs/284229 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 284229] Re: console-kit-daemon using a lot of cpu
I restarted the process now, so probably everything's normal... 17226 root 20 0 168m 3376 1632 S0 0.2 0:15.08 console- kit-dae It usually takes at least a few days before it uses a noticable amount of cpu. It uses 0.07% cpu on average right now. ** Attachment added: strace of console-kit, using 0.07% cpu (hopefully normal) http://launchpadlibrarian.net/18890123/console-kit-trace -- console-kit-daemon using a lot of cpu https://bugs.launchpad.net/bugs/284229 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 284229] [NEW] console-kit-dae using a lot of cpu
Public bug reported: Binary package hint: consolekit Since the last reboot, a strange and to me unknown process, console-kit- dae, has been using up more and more cpu. Right now it uses on average 10.25% cpu over 5 minutes, steadily and linearly (!) growing in cpu usage and have been using up 7h 36 minutes CPU over 7 days. This doesn't seem to be quite normal. intrepid, some week old since last update. ** Affects: consolekit (Ubuntu) Importance: Undecided Status: New -- console-kit-dae using a lot of cpu https://bugs.launchpad.net/bugs/284229 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 284229] Re: console-kit-dae using a lot of cpu
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 25676 root 20 0 178m 17m 1560 R 71 0.9 457:02.40 console-kit-dae -- console-kit-dae using a lot of cpu https://bugs.launchpad.net/bugs/284229 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 274712] Re: upgrading (acpid) killed network?
Could we add this to network manager instead? It's a more likely culprit than acpid...: Sep 26 09:42:44 iris NetworkManager: info (eth0): deactivating device. -- upgrading (acpid) killed network? https://bugs.launchpad.net/bugs/274712 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 274712] Re: upgrading (acpid) killed network?
The network did not recover. The upgrade stuck some minutes (?) later on asking if I wanted to replace some pulseaudio config files, but I doubt that it would have fixed the network later in the upgrade... I did a manual /etc/init.d/network restart to get it to run again. ** Attachment added: /var/log/apt/term.log http://launchpadlibrarian.net/18002892/term.log -- upgrading (acpid) killed network? https://bugs.launchpad.net/bugs/274712 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 274712] Re: upgrading (acpid) killed network?
relevant parts of the syslog: Sep 26 09:41:01 iris /USR/SBIN/CRON[22288]: (root) CMD (/home/mirar/hack/pingboot.sh) Sep 26 09:41:06 iris init: Re-executing /sbin/init Sep 26 09:41:29 iris kernel: [386485.749734] type=1505 audit(1222414889.776:17): operation=profile_replace name=/usr/sbin/named name2=default pid=22926 Sep 26 09:41:29 iris kernel: [386485.887104] type=1505 audit(1222414889.912:18): operation=profile_replace name=/usr/share/gdm/guest-session/Xsession name2=default pid=22932 Sep 26 09:41:30 iris kernel: [386486.054133] type=1505 audit(1222414890.080:19): operation=profile_replace name=/usr/lib/cups/backend/cups-pdf name2=default pid=22937 Sep 26 09:41:30 iris kernel: [386486.054741] type=1505 audit(1222414890.080:20): operation=profile_replace name=/usr/sbin/cupsd name2=default pid=22937 Sep 26 09:41:30 iris kernel: [386486.106540] type=1505 audit(1222414890.132:21): operation=profile_replace name=/usr/sbin/mysqld name2=default pid=22941 Sep 26 09:41:30 iris kernel: [386486.155654] type=1505 audit(1222414890.180:22): operation=profile_replace name=/usr/sbin/named name2=default pid=22945 Sep 26 09:42:39 iris NetworkManager: info HAL disappeared Sep 26 09:42:40 iris acpid: client connected from 9968[0:0] Sep 26 09:42:40 iris acpid: client connected from 9968[0:0] Sep 26 09:42:43 iris acpid: client connected from 32719[106:110] Sep 26 09:42:44 iris NetworkManager: info HAL re-appeared Sep 26 09:42:44 iris NetworkManager: info (eth0): now unmanaged Sep 26 09:42:44 iris NetworkManager: info (eth0): device state change: 8 - 1 Sep 26 09:42:44 iris NetworkManager: info (eth0): deactivating device. Sep 26 09:42:44 iris NetworkManager: WARN check_one_route(): (eth0) error -34 returned from rtnl_route_del(): Sucess Sep 26 09:42:44 iris NetworkManager: info (eth0): cleaning up... Sep 26 09:42:44 iris NetworkManager: info (eth0): taking down device. Sep 26 09:42:44 iris NetworkManager: info (eth0): carrier now OFF (device state 8) Sep 26 09:42:44 iris NetworkManager: info (eth0): device state change: 8 - 2 Sep 26 09:42:44 iris NetworkManager: info (eth0): deactivating device. Sep 26 09:42:44 iris NetworkManager: nm_device_get_state: assertion `NM_IS_DEVICE (device)' failed Sep 26 09:42:44 iris NetworkManager: nm_device_is_activating: assertion `NM_IS_DEVICE (device)' failed Sep 26 09:42:44 iris NetworkManager: nm_device_get_state: assertion `NM_IS_DEVICE (device)' failed Sep 26 09:42:44 iris NetworkManager: nm_device_is_activating: assertion `NM_IS_DEVICE (device)' failed Sep 26 09:42:44 iris NetworkManager: nm_device_get_state: assertion `NM_IS_DEVICE (device)' failed Sep 26 09:42:44 iris kernel: [386560.598446] NetworkManager[9935]: segfault at 1 ip 7f5139e61a8a sp 7fff434225c0 error 4 in libglib-2.0.so.0.1800.0 (deleted)[7f5139e0a000+c2000] Sep 26 09:42:44 iris avahi-daemon[5592]: Withdrawing address record for 172.16.0.27 on eth0. Sep 26 09:42:44 iris avahi-daemon[5592]: Leaving mDNS multicast group on interface eth0.IPv4 with address 172.16.0.27. Sep 26 09:42:44 iris avahi-daemon[5592]: Interface eth0.IPv4 no longer relevant for mDNS. Sep 26 09:42:44 iris avahi-daemon[5592]: Withdrawing address record for fe80::260:8ff:fe0f:1693 on eth0. Sep 26 09:42:45 iris nm-dispatcher.action: Error in get_property: Message did not receive a reply (timeout by message bus) Sep 26 09:42:46 iris named[5645]: received control channel command 'reconfig' Sep 26 09:42:46 iris named[5645]: loading configuration from '/etc/bind/named.conf' Sep 26 09:42:46 iris kernel: [386562.720002] type=1503 audit(1222414966.768:23): operation=capable name=sys_resource pid=5647 profile=/usr/sbin/named Sep 26 09:42:46 iris named[5645]: no IPv6 interfaces found Sep 26 09:42:46 iris named[5645]: no longer listening on 172.16.0.27#53 Sep 26 09:42:47 iris named[5645]: default max-cache-size (33554432) applies Sep 26 09:42:48 iris named[5645]: default max-cache-size (33554432) applies: view _bind Sep 26 09:42:49 iris named[5645]: reloading configuration succeeded Sep 26 09:42:50 iris named[5645]: any newly configured zones are now loaded Sep 26 09:42:50 iris postfix/master[9762]: reload configuration /etc/postfix Sep 26 09:42:53 iris acpid: exiting Sep 26 09:42:55 iris acpid: client connected from 9968[0:0] Sep 26 09:42:58 iris acpid: client connected from 32719[106:110] Sep 26 09:42:58 iris acpid: client connected from 9968[0:0] Sep 26 09:42:58 iris named[5645]: too many timeouts resolving 'eth1.mirar.org/A' (in '.'?): disabling EDNS Sep 26 09:42:59 iris last message repeated 207 times Sep 26 09:43:13 iris hcid[1146]: Bluetooth HCI daemon Sep 26 09:43:13 iris hcid[1146]: Parsing /etc/bluetooth/main.conf failed: No such file or directory Sep 26 09:43:13 iris hcid[1146]: Starting SDP server Sep 26 09:43:35 iris ntpd[31786]: sendto(172.16.0.1) (fd=18): Invalid argument Sep 26 09:44:40 iris ntpd[31786]: sendto(172.16.0.1) (fd=18): Invalid argument ... and deamon.log: Sep
[Bug 214219] Re: trackerd uses up all available memory
I'm using latest (as of a few days back at least) _Intrepid_. I haven't had any problems with trackerd until recently either, but seriously: top - 09:20:52 up 4 days, 11:00, 7 users, load average: 1.74, 1.12, 0.78 Tasks: 204 total, 3 running, 201 sleeping, 0 stopped, 0 zombie Cpu(s): 15.3%us, 35.0%sy, 3.0%ni, 26.1%id, 19.7%wa, 0.5%hi, 0.5%si, 0.0%st Mem: 2057024k total, 1963356k used,93668k free,15392k buffers Swap: 987988k total, 985836k used, 2152k free, 198340k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 11057 mirar 39 19 1544m 681m 2036 D 32 33.9 606:17.73 trackerd 10 hours+ of cpu time, using a ton of memory, constantly a lot of CPU (constantly around 30%, says my logs) and I/O? Not very friendly, is it? Could it *please* not be installed per default? How do I get rid of it, cleanly? -- trackerd uses up all available memory https://bugs.launchpad.net/bugs/214219 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 274712] [NEW] upgrading (acpid) killed network?
Public bug reported: Intrepid from today. Running an aptitude update/aptitude upgrade, the machine suddenly decided to unplug eth0. Which made it a bit tricky, since I was maintaining it over the network... The last output of the upgrade was: Setting up acpid (1.0.6-9ubuntu4) ... * Stopping Hardware abstraction layer hald ...done. * Loading ACPI modules... ...done. * Starting ACPI services... ...done. * Starting Hardware abstraction layer hald ...done. A lot of packages were upgraded before, and after (the vnc server was still running fine). Not sure what is the culprit... Anything else I can upload to help? ** Affects: ubuntu Importance: Undecided Status: New -- upgrading (acpid) killed network? https://bugs.launchpad.net/bugs/274712 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 256054] Re: [intrepid] new 0.7 branch ignores /etc/network/interfaces
Confirmed. I had a machine go offline saturday because it went dhcp-hunting instead of using the static IP (upgraded on friday). Highly annoying since I was 300km away at that time and really didn't expect that behaviour, so I couldn't find it... :p (Yes, I've done the Right Thing now and added it's MAC to the static DHCP-given IP numbers, but...) -- [intrepid] new 0.7 branch ignores /etc/network/interfaces https://bugs.launchpad.net/bugs/256054 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 119982] Re: amd64 vncconfig crashes
The problem is still there in Intrepid. The version hasn't changed, so I guess that would explain it. :p This bug renders the vnc4server package useless. Thanks for the patch though, Patrick. It allows me to run vnc4server anyway. (However, 8-bit characters in the clipboard - åäö - doesn't seem to work...) -- amd64 vncconfig crashes https://bugs.launchpad.net/bugs/119982 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 173196] Re: Firefox will not start under vnc
Firefox works me under vnc4server 4.1.1+xorg1.0.2-0ubuntu7, running fvwm, i86_64 (AMD64) system. Maybe not a simple vnc4 bug but Gnome in combination with VNC? -- Firefox will not start under vnc https://bugs.launchpad.net/bugs/173196 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 68338] Re: sky2 driver stalls
I still get tx timeout now and then. Sometimes the network manages to get back on track, sometimes it just leaves a complete mess and I have to reboot. Mar 12 15:40:23 iris kernel: [162717.506822] NETDEV WATCHDOG: eth1: transmit timed out Mar 12 15:40:23 iris kernel: [162717.506827] sky2 eth1: tx timeout Mar 12 15:40:23 iris kernel: [162717.506833] sky2 eth1: transmit ring 2 .. 474 report=2 done=2 Mar 12 15:40:23 iris kernel: [162717.506862] sky2 eth1: disabling interface Mar 12 15:40:23 iris kernel: [162717.507201] sky2 eth1: enabling interface Mar 12 15:40:27 iris kernel: [162720.528273] sky2 eth1: Link is up at 1000 Mbps, full duplex, flow control both Tried: Ubuntu Gutsy 2.6.22-14 Ubuntu Hardy 2.6.24-11 kernel.org 2.6.22.1 kernel.org 2.6.24.3 I'm starting to suspect something is fishy with the hardware, actually. But how do I know? [ 58.026424] ACPI: PCI Interrupt :03:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 58.026523] PCI: Setting latency timer of device :03:00.0 to 64 [ 58.027459] sky2 :03:00.0: v1.20 addr 0xf400 irq 17 Yukon-EC Ultra (0xb4) rev 2 [ 58.027882] sky2 eth0: addr 00:16:e6:8c:ec:d9 03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) -- sky2 driver stalls https://bugs.launchpad.net/bugs/68338 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 109629] Re: 3com NIC stops working after some time
Nope, 2.6.22.1 didn't solve the problem. I give up now, as well. -- 3com NIC stops working after some time https://bugs.launchpad.net/bugs/109629 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 109629] Re: 3com NIC stops working after some time
I compiled and installed a plain 2.6.22.1, lets see if the problem remain. -- 3com NIC stops working after some time https://bugs.launchpad.net/bugs/109629 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 109629] ...and affects other parts of the system
This bug is apparently not very important. Anyone knows which kernel/dists that *do* work? I can't run much longer with this... Now the network timeout halted the system long enough to shut down my raid: [608679.074481] NETDEV WATCHDOG: eth0: transmit timed out [608679.074490] eth0: transmit timed out, tx_status 00 status e000. [608679.074499] diagnostics: net 0cc0 media 8802 dma 00a00021 fifo 8800 [608679.074507] Flags; bus-master 1, dirty 40617982(14) current 40617998(14) [608679.074511] Transmit list 7bea4ac0 vs. 81007bea4ac0. ... [608679.074571] eth0: Resetting the Tx ring pointer. [608680.580930] ata7.01: qc timeout (cmd 0xef) [608680.580943] ata7.01: failed to set xfermode (err_mask=0x4) [608680.580948] ata7.01: disabled [608681.084387] ata7: EH complete [608681.088767] VFS: busy inodes on changed media. [608681.089671] VFS: busy inodes on changed media. [608687.622840] ata5.00: qc timeout (cmd 0x27) [608687.622851] ata5.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 0 [608687.622863] ata5.00: failed to set xfermode (err_mask=0x40) [608687.622867] ata5.00: disabled [608688.126318] ata5: EH complete [608688.126382] sd 4:0:0:0: SCSI error: return code = 0x0004 [608688.126386] end_request: I/O error, dev sdc, sector 862369017 [608688.126397] md: super_written gets error=-5, uptodate=0 [608688.126402] raid1: Disk failure on sdc3, disabling device. [608688.126404] Operation continuing on 1 devices [608688.126431] sd 4:0:0:0: SCSI error: return code = 0x0004 [608688.126434] end_request: I/O error, dev sdc, sector 10312065 [608688.126520] EXT3-fs error (device md0): read_inode_bitmap: Cannot read inod e bitmap - block_group = 28, inode_bitmap = 917505 [608688.127978] sdc : READ CAPACITY failed. [608688.127980] sdc : status=0, message=00, host=4, driver=00 [608688.127983] sdc : sense not available. [608688.128338] sdc: Write Protect is off [608688.128341] sdc: Mode Sense: 00 00 00 00 [608688.128575] sdc: asking for cache data failed [608688.128578] sdc: assuming drive cache: write through [608688.148540] RAID1 conf printout: [608688.148546] --- wd:1 rd:2 [608688.148549] disk 0, wo:1, o:0, dev:sdc3 [608688.148552] disk 1, wo:0, o:1, dev:sda3 Arrrg! -- 3com NIC stops working after some time https://bugs.launchpad.net/bugs/109629 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 109629] Re: 3com NIC stops working after some time
Same problem here. Very annoying, this 3c905 has been working perfectly for around 10 years... [ 41.193933] 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html [ 41.193938] :05:01.0: 3Com PCI 3c905 Boomerang 100baseTx at 0001b000. ... [404126.567091] 15: @810059798b60 length 802a status 802a [404126.567096] eth0: Resetting the Tx ring pointer. [404136.556391] NETDEV WATCHDOG: eth0: transmit timed out [404136.556401] eth0: transmit timed out, tx_status 00 status e000. [404136.556410] diagnostics: net 0cc0 media 8802 dma 00880021 fifo 8800 [404136.556418] Flags; bus-master 1, dirty 16(0) current 32(0) [404136.556422] Transmit list 59798200 vs. 810059798200. [404136.556427] 0: @810059798200 length 8099 status 0099 [404136.556431] 1: @8100597982a0 length 818a status 018a ... Anyone knows which kernel to revert to to avoid this problem? -- 3com NIC stops working after some time https://bugs.launchpad.net/bugs/109629 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
