It seems to be a timing issue.
I put smbfs into /etc/modules to get the module loaded early in the boot
process. This seems to help sometimes, but most of the time, it doesn't
help either.
> I don't get it. Doesn't the developers automount their shares???
Perhaps they have faster machines where
If worked here - at least for now (I restarted the system a few times
without problems).
In my opinion, this work-around also points to a timing issue between
starting the ethernet network, starting the samba system and mouting the
network shares.
Most of most of the above mentioned suggestions i
It seems to be a timing issue.
I put smbfs into /etc/modules to get the module loaded early in the boot
process. This seems to help sometimes, but most of the time, it doesn't
help either.
> I don't get it. Doesn't the developers automount their shares???
Perhaps they have faster machines where
If worked here - at least for now (I restarted the system a few times
without problems).
In my opinion, this work-around also points to a timing issue between
starting the ethernet network, starting the samba system and mouting the
network shares.
Most of most of the above mentioned suggestions i
It seems to be a timing issue.
I put smbfs into /etc/modules to get the module loaded early in the boot
process. This seems to help sometimes, but most of the time, it doesn't
help either.
> I don't get it. Doesn't the developers automount their shares???
Perhaps they have faster machines where
If worked here - at least for now (I restarted the system a few times
without problems).
In my opinion, this work-around also points to a timing issue between
starting the ethernet network, starting the samba system and mouting the
network shares.
Most of most of the above mentioned suggestions i
It seems to be a timing issue.
I put smbfs into /etc/modules to get the module loaded early in the boot
process. This seems to help sometimes, but most of the time, it doesn't
help either.
> I don't get it. Doesn't the developers automount their shares???
Perhaps they have faster machines where
If worked here - at least for now (I restarted the system a few times
without problems).
In my opinion, this work-around also points to a timing issue between
starting the ethernet network, starting the samba system and mouting the
network shares.
Most of most of the above mentioned suggestions i
It seems to be a timing issue.
I put smbfs into /etc/modules to get the module loaded early in the boot
process. This seems to help sometimes, but most of the time, it doesn't
help either.
> I don't get it. Doesn't the developers automount their shares???
Perhaps they have faster machines where
If worked here - at least for now (I restarted the system a few times
without problems).
In my opinion, this work-around also points to a timing issue between
starting the ethernet network, starting the samba system and mouting the
network shares.
Most of most of the above mentioned suggestions i
It seems to be a timing issue.
I put smbfs into /etc/modules to get the module loaded early in the boot
process. This seems to help sometimes, but most of the time, it doesn't
help either.
> I don't get it. Doesn't the developers automount their shares???
Perhaps they have faster machines where
If worked here - at least for now (I restarted the system a few times
without problems).
In my opinion, this work-around also points to a timing issue between
starting the ethernet network, starting the samba system and mouting the
network shares.
Most of most of the above mentioned suggestions i
Public bug reported:
Binary package hint: gnome-system-monitor
The first time I noticed that bug was during the pop-ups of the
notifier ("connected to network", etc.). The attached file shows what
that looks like.
I get a similar pattern when I try to open the gnome-system-monitor.
When I sw
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36746138/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/36746139/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/36746140/ProcStatus.txt
** Attachm
** Attachment added: "Notification area without compiz"
http://launchpadlibrarian.net/36746428/notifier.png
--
gnome-system-monitor and notification area not readable without compiz
https://bugs.launchpad.net/bugs/496214
You received this bug notification because you are a member of Ubuntu
De
15 matches
Mail list logo
