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
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
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
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
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
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
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
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
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
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
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
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
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
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
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:
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
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
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
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
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
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
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:
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
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
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
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:
26 matches
Mail list logo
