I confirm that this bug is still affecting Compiz in 14.04LTS. Clean install +
no CCSM.
So, yet another new release (supposedly a stable, conservative and long-term
one) and still this has not been fixed !
It has now been a year and a half - across 4 releases - and still there is no
one
Stats, community comments and user's wishes don't matter to Canonical
nowadays. For all the recent decisions they have taken unilaterally which
caused big turmoil among the community, they have never backed out because of
the noise or widespread disagreement from its user base...
As it has
Thank you Carl-Eric for your idea of monitoring what apps set gsettings and
what do they do exactly.
And also to Fred for indicating how to actually do this monitoring.
Now my question is: how could we execute a shell with the dconf watch command
early enough in the boot process so as to have
For me, it is not only Windows keys that are involved : I also use super,
but along with other regular keys. When I loose my custom shortcuts settings,
all of them are gone; reset to default values (Windows specific keys and
regular keys as well).
As for when this happens, that seems to be part
This is very annoying that this bug was NEVER fixed since it appeared in
12.10...Every now and then there has been a fix released but that changed
nothing and it is generally not available for backport. Also once in a while
appears again in this thead the buggy solution to change CCSM
For information, the problem for me seems to have completely disappeared since
I upgraded to 13.04!
Nota Bene: it was not a clean install, but an upgrade of an existing 12.10.
Conditions where the problem does show up seem to be rather obscure...
--
You received this bug notification because
André,
Thank you for your warning. I had also tried your fix, but Unity got completely
screwed up - same as described by the two other people that reported this
issue. I tried to play a little bit at recovering the situation - but to no
avail. Even trying to reinstall the packages involved
Stegard,
I have tried your autostart solution, but it didn't work for me...I will have
to investigate a little more to see if perhaps I have also a problem with Gnome
keyboard properties. Also: do I have to register the file as an app in some way?
--
You received this bug notification because
I am also begging for a backport to 12.10 !!!
Since upgrading to Quantal, this very annoying behavior of not remembering
shortcuts across logout/logins has forced me to revert to using 12.04LTS...I
have been using two shortcuts for a very long time: one for closing a window
and one for
I do acknowledge that this bug is dead and burried since the Ubuntu team as
decided to drop this handy feature for some unclear and unjustified
reason...still no one answered my question.
Will the libnautilus-gksu.so presently dated feb 23rd 2011 work with Ubuntu
12-04 by simply copying the lib
Ok, thanks for this comment and the download link.
So, in other words, does this mean that just dowloading the current build of
this library and put it inside /usr/lib/nautilus/extensions-3.0 would still
work with 12.04 ? No need to recompile the sources ?
Oddly enough, the libnautilus-gksu.so
You are right and this is quite a discovery!
Now the question is: what exactly are these statically linked executable doing
there in /usr/lib/klibc/bin? To what purpose would they be used instead of the
same basic unix executable inside /bin (which are all dynamically linked) ? Are
they used at
Thank you Jason for this information. I also suspected that this package's
development had stalled...
Our only hope now, is that perhaps this was only a bug introduced by 11.10
Oneiric...and that the coming release of 12.04 would have solved it. We will
see...
--
You received this bug
Fine...but not really a viable solution for using the prelinking tool the
normal way.
May I also add that after 5 months from the notification, this bug is still
undecided and unassigned !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I agree.
But my experience tells me that a kernel crash upon sleep or hibernate is a
very difficult bug to troubleshoot.
Most of the time, these bugs arise only on a specific hardware or BIOS or ACPI
design or other unknown things.
In my case, I really like to have to only close the lid when
Thank you David for your solution. It does work perfectly.
But...I still think this is an issue and not a simplification. Why would a
lambda user be forced to go through dconf-editor (which they probably don't
know anything about) in order to have the laptop shutdown when they close the
lid
I fully agree with Thorsten - people who don't know about this feature and its
potential dangerousity will not be concerned at all as this feature is
unavailable by default with the current build. On the other side, people who
were using this feature are probably knowledgeable enough to know
Public bug reported:
1. Ubuntu 11.10 - kernel 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:50:42 UTC
2011 i686
2. nautilus 1:3.2.0-0ubuntu5
3. I had this convenient right click menu open as root for a very long time
and I expected to keep it while uprading from Natty
4. It disappeared after
Public bug reported:
1. Ubuntu 11.10 kernel 3.0.0-12-generic #20-Ubuntu SMP Fri Oct 7 14:50:42 UTC
2011 i686
2. software-center 5.0.1.5 / power settings menu / gnome-power-manager
3.2.0-0ubuntu1
3.expected to keep this option I had configured in Natty after upgrading to
Oneiric
4. after
Hello James,
Thank you for the workaround you found. I confirm that this actually worked for
me too and that it did solve the problem !
The settings are being remembered across reboots when the proper keyboard is
selected at the GDM greeting (and this is only needed once).
I do agree with you
I have tried what you just described, but it does not work for me...First off,
I never selected the option choose keymap for every window and the
system-wide option was always available and selected.
Still, I cannot get rid of the unwanted keymap, which will always reappear
after reboot. Damn!!
It sounds to me that the installer package is doing weird things and perhaps
adding unwanted keyboard maps as a default...then this layout becomes a
system-wide default that cannot be removed or changed!
At least, I experienced the same problem as your Natty server installation but
with Natty
I did some research and it appears that this is not a bug.
There is a setting in Unity that can be modified using gconf-editor or this
command in a terminal:
gsettings set com.canonical.Unity.Panel systray-whitelist ['all']
...then all apps that send an indicator to the tray works fine.
The
Sorry I made a typo mistake:
- it's not gconf-editor but rather dconf-editor which can be installed with
the package dconf-tools.
(sudo apt-get install dconf-tools)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
With my Natty desktop it shows up in the Add to panel and it works
fine with Ubuntu Classic - but not in Unity...
A possible clue is that I already had it in the panel under Maverick,
and I did a version upgrade to Natty using update-manager (rather than
installing a Natty clean from scratch).
I confirm this bug. Unable to use it with Unity (App launches but is not
accessible via Unity panel).
Note: works fine with Gnome panel...
Ubuntu 11.04
Cryptkeeper 0.9.4-1ubuntu1
It's really too bad that one cannot use cryptkeeper under Natty with the
new Unity Desktop; and would have to revert
Ok...but do you have two keyboard layouts to choose from or only one? Does the
indicator applet show in the tray accordingly?
What keyboard did you choose during Natty first installation? Is it the same
one as the layout you use now or did you add an additional keyboard layout
afterward?
It
Furthermore, I don't see why the mecanism for disabling the indicator from
showing in the tray would not work or would not be implemented (as stated in
other threads about this indicator): in my opinion, the code for handling the
gconf key
What do you mean when you say your Natty Desktop is not affected? Have
you done the same keyboard layout configuration as you described with
the german kb map and everything behaves normally both with Xserver and
the console (and also it keeps the configuration across reboots) ?
--
You received
I have tried your suggestion to reconfigure console-data, but it does not
change the problem. Furthermore, the behavior after reconfiguring console-data
is the same as reported in the bug description: the settings are NOT remembered
across reboots and I always end up with the wrong keyboard in
Public bug reported:
Binary package hint: gnome-settings-daemon
Binary package hint: gnome-settings-daemon
Ubuntu 11.04 (natty)
Kernel 2.6.38-8-generic (#42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011)
Gnome 2.32.1 (Ubuntu 2011-04-14)
gnome-settings-daemon 2.32.1-0ubuntu13.1
Description: the
31 matches
Mail list logo
