[Desktop-packages] [Bug 1235991] Re: Can't “use system keyboard layout” in Saucy

2014-05-26 Thread Daniil Ivanov
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

[Desktop-packages] [Bug 1201679] Re: ibus' Super+Space shortcut (usually) doesn't work

2014-05-26 Thread Daniil Ivanov
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. -- Y

[Desktop-packages] [Bug 1097763] Re: Firefox 18 anti-aliasing does not render correctly some text

2013-01-20 Thread Daniil Ivanov
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 bec

[Desktop-packages] [Bug 663735] Re: After upgrade to 12.04 NetworkManager does not start automatically on boot

2012-08-22 Thread Daniil Ivanov
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 Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad

[Desktop-packages] [Bug 663735] Re: After upgrade to 12.04 NetworkManager does not start automatically on boot

2012-06-24 Thread Daniil Ivanov
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 Desktop Packages, which is subscribed to network-manager in Ub

[Desktop-packages] [Bug 663735] Re: After upgrade to 12.04 NetworkManager does not start automatically on boot

2012-06-21 Thread Daniil Ivanov
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 stat

[Desktop-packages] [Bug 663735] Re: NetworkManager is not running

2012-06-20 Thread Daniil Ivanov
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. -- Y

[Desktop-packages] [Bug 663735] Re: NetworkManager is not running

2012-06-20 Thread Daniil Ivanov
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): Gd

[Desktop-packages] [Bug 663735] Re: NetworkManager is not running

2012-06-19 Thread Daniil Ivanov
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 yo