As of today, issue is still in 14.04, but is fixed in 14.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997743
Title:
gradle depends on libtomcat6-java
To manage notifications about this bug go
I now have the machines running 13.10 with LXDE as a desktop
environment. I don't have org.gnome.settings-daemon.plugins.media-keys
switch-input-source set. One of them doesn't have this bug present and
two other have. I would appreciate any hints how to find a root-cause
for this problem.
--
I had the same problem after upgrade from 13.04 to 13.10. I was able to find a
workaround for a problem:
I did apt-get purge libibus-1.0-0:i386, which was installed along with
libibus-1.0-5:i386.
Then I selected option IBus Preferences - Advanced - Use system keyboard
layout and restarted IBus.
I've installed terminus-fonts and then set Terminus as a fonts to be
used in Kate. All these resulted in the same colour aberration as in
new Firefox 18. So this it is probably something with font rendering of
specific fonts, rather than Firefox problem.
--
You received this bug notification
static-network-up is not emitted because there some auto interfaces in
/etc/network/interfaces, which cannot be configured during startup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663735
Title:
My issue is clearly connected to static-network-up not being emitted due to my
network configuration.
There are quite a few bugs on this issue, for example bug 900903.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Probably the real root-cause for this that static-network-up is not emitted
anywhere
$ grep static-network-up /etc/init/*
failsafe.conf:stop on static-network-up or starting rc-sysinit
failsafe.conf:# these messages. currently only static-network-up counts for
that.
networking.conf:emits
This bug seems to be a duplicate of bug 940485.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994862
Title:
Random Waiting for network configuration
To manage notifications about this bug go to:
This bug seems to be a duplicate of bug 940485.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/924380
Title:
Waiting for network configuration message during boot is unclear and
unnecessary
To
This bug seems to be a duplicate of bug 940485.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/916890
Title:
Waiting for network configuration on every boot
To manage notifications about this bug
This bug seems to be a duplicate of bug 950662.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/950662
Title:
Waiting for network message on bootup when all network devices are up
To manage
Sorry, this is already the bug 950662.
I also experience this issue and here is my findings:
The delays are caused by failsafe boot delay (/etc/init/failsafe.conf)
which is started on:
start on filesystem and net-device-up IFACE=lo
and stopped on:
stop on static-network-up or starting rc-sysinit
Here is the content of ~/.xsession-errors
** (nm-applet:2128): WARNING **: Could not initialize NMClient
/org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was
not provided by any .service files
** Message: applet now removed from the notification area
(nm-applet:2128):
I was able to workaround the problem by changing start on condition in
cat /etc/init/network-manager.conf to the following:
start on (started dbus
or static-network-up)
I removel local-filesystems as dbus itselef starts on that signal and
NetworkManager is useless without DBus.
--
I observe the same situation after upgrading from 11.10 to 12.04.
NetworkManager is not in the list of processes after boot and executing
sudo NetworkManager fixes the defect.
** Changed in: network-manager (Ubuntu)
Status: Expired = New
--
You received this bug notification because you
I've checked nm-applet.desktop file and it has OnlyShowIn=GNOME;XFCE;
and it comes from Ubuntu/Debian patch
$ cat /etc/xdg/autostart/nm-applet.desktop
[Desktop Entry]
Name=Network Manager
Comment=Control your network connections
Icon=nm-device-wireless
Exec=nm-applet --sm-disable
Terminal=false
Public bug reported:
Binary package: network-manager-gnome
Add LXDE in the /etc/xdg/autostart/nm-applet.desktop file so the LXDE will
launch it
OnlyShowIn=GNOME;XFCE;LXDE;
** Affects: network-manager-applet (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
On the other hand listing all possible DEs in desktop file is not
robust. Thus, OnlyShownIn option usage should be avoided.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753300
Title:
add LXDE (and
** Changed in: network-manager-applet (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/729914
Title:
nm-applet doesn't show up in notification area
--
So basically nm-applet is not running after login un.
.xsession-errors do not contain anything interesting from this issue point of
view:
divanov@t61p:~$ cat .xsession-errors
Xsession: X session started for divanov at Fri Apr 1 10:59:13 EEST 2011
Setting IM through im-switch for locale=en_US.
I observe the same issue on two Kubuntu 10.10 machines. I'm using LXDE
as my desktop environment and nm-applet doesn't show up. However, ibus
applet is visible in system tray, thus, this is not a problem of system
tray not being visible.
** Changed in: network-manager-applet (Ubuntu)
I'm using LXDE, not KDE and the former uses the same applet (nm-applet)
as Gnome. On the other hand, I'm using LXDE on Fedora 14 and there is no
problem with nm-applet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
22 matches
Mail list logo
