I can confirm that this fix works on Ubuntu 20.04. To reiterate:
sudo apt install libblockdev-crypto2
sudo service udisks2 restart
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.ne
I can confirm this bug.
I was playing Elevator in Aisleriot, and experienced the same issues
that others are experiencing: screen froze momentarily while I was
dragging a card, X crashed, X tried to restart and failed, computer
needed hard shutdown.
I would love to see this resolved as I think Ai
To quote https://wiki.ubuntu.com/Bugs/Importance
-
Low: Bugs which affect functionality, but to a lesser extent than most bugs,
examples are:
* Ones that can be easily worked around
* Ones that affect unusual configurations or uncommon hardware
* A bug that has a moderate impact o
There is another bug which doesn't seem to have been mentioned.
Using the [Fn + Up] and [Fn + Dn] keystrokes changes the brightness in
huge increments. The keystrokes basically allow me three separate
brightness levels: very dim, medium, and very bright. By comparison, my
Dell's sound buttons all
Regarding Toby's comment - The problems I have been experiencing (see
bug description above) are also happening on a Dell E1505.
--
Brightness control still has major bugs
https://bugs.launchpad.net/bugs/223954
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
As bgcommon notes, the bug is easily triggered. Set your brightness to a
certain level with the Brightness Applet. Alter the brightness with the
[Fn + Up] or [Fn + Down] key. Close/reopen the laptop lid and the level
will revert to that which had originally been set in the Brightness
Applet.
As yo
Hardy fixed some of these issues, but introduced more at the same time.
I haven't done extensive testing, but I can provide you with my
observations.
In Gutsy, I had the following problem. If I set the brightness with the
[Fn + Up] or [Fn + Down] keystroke, the brightness would at some point
rever
** Description changed:
gnome-power-manager and the brightness applet had some very annoying
bugs in Gutsy (see https://bugs.launchpad.net/ubuntu/+source/gnome-
power-manager/+bug/137598).
For a while after upgrading to Hardy, it seemed as through the
aforementioned bug had been resol
I'm not sure if it is technically the same bug. That is, I don't know
that it is caused by the same code or even the same package.
--
Brightness control still has major bugs
https://bugs.launchpad.net/bugs/223954
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Public bug reported:
gnome-power-manager and the brightness applet had some very annoying
bugs in Gutsy (see https://bugs.launchpad.net/ubuntu/+source/gnome-
power-manager/+bug/137598).
For a while after upgrading to Hardy, it seemed as through the
aforementioned bug had been resolved. I was able
@Jochem - As far as I know, the applet has never been a problem. At
least I have never experienced any problems with the brightness applet.
The problem for me has always been, and continues to be, the hotkeys (I
am not running any of the patches, I'm still on Gutsy).
--
Screen brightness resets t
I don't know anything about gconf, but I am certain that this problem only
happens to me when I use hotkeys. I discussed this matter in the following
post, under the section "Steps to repeat issue 1":
https://bugs.launchpad.net/ubuntu/+bug/155485/comments/1
--
Screen brightness resets to defaul
I think that it would be best to remove "Software Sources" because that
application can be easily reached from Synaptic. Most of the people who
use "Software Sources" probably already use Synaptic, so it is a bit
redundant.
But if "Software Sources" has to stay, I would agree that a submenu
would
Thanks for really getting involved with resolving this issue.
How would I go about applying your patch, and how could I revert the
changes should I need to? Thanks alot.
--
Launchers under "System > Preferences" and "System > Administration" have
similar names, leads to confusion.
https://bugs.
** Summary changed:
- Launchers under "System => Preferences" and "System => Administration" have
similar names, leads to confusion.
+ Launchers under "System > Preferences" and "System > Administration" have
similar names, leads to confusion.
--
Launchers under "System > Preferences" and "Sys
I'd be more than willing to help you out with this one if would like
some help. I don't know the technical aspects of GNOME or anything like
that, but I am ridiculously organized. If you need help cleaning up the
names, descriptions, and overall organization of everything I would
definitely be able
It would really be a shame if this bug made it into Hardy, considering
Hardy will be and LTS. LTS releases are supposed to solve problems just
like this one.
--
Screen brightness resets to default (maximum) on idle with AC plugged in
https://bugs.launchpad.net/bugs/137598
You received this bug no
*** This bug is a duplicate of bug 137598 ***
https://bugs.launchpad.net/bugs/137598
@ali_deren - Yes, use the brightness applet (right click on a panel >
click add to panel > select the brightness applet) to control
brightness. Only the brightness applet "fastens" the brightness level.
--
S
** Description changed:
OS: Ubuntu Gutsy amd64
Hardware: Dell Inspiron E1505n (can provide specific details if necessary)
I use the Brightness Applet to set the brightness to a specific value
(let's just say 75%). I later use [Fn + Down Arrow] to lower the
- brightness to be below 75%.
** Changed in: gnome-panel (Ubuntu)
Sourcepackagename: None => gnome-panel
--
Brightness is automatically readjusted to match Brightness Applet
https://bugs.launchpad.net/bugs/155485
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for gno
20 matches
Mail list logo
