An update on this bug... I have two raring installs. For one of them the
brightness controls work, one doesn't.
The one that doesn't work is a vanilla upgrade to Raring 13.04 from
Quantal 12.10.
The one that works is also an upgrade from 12.10, but there are two major
differences:
1. I
Just noticed my brightness controls are working again.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1105604
Title:
Brightness control stopped working
To manage
Retested this. The problem doesn't occur on 12.10 or 13.04.
It still happens on 12.04.2, which is using with nautilus 3.4.2.
Actually 12.10 is also using nautilus 3.4.2. So maybe this isn't a
nautilus bug after all. In 12.04.2 the window pops up but nothing
changes in the Unity bar.
In 12.10,
Latest update... the brightness control keys 'work'. The slider moves up
and down, but there is no impact to the actual brightness. I'm
controlling the brightness manually by setting it automatically after
bootup and resume|thaw via scripts.
I'm running raring with the Mir ppa, but I have another
Now on Raring, the backlight is off after resuming from suspend. I have to run
the following (blind type) after resuming each time:
echo 978 | sudo tee /sys/class/backlight/intel_backlight/brightness
Also, the function keys to control the brightness setting still don't
work. They do on Quantal.
Here is the syslog during the suspend/wake. This maybe a separate bug...
but will move later if nec:
Mar 8 18:49:30 malraux kernel: [ 593.626366] composite sync not supported
Mar 8 18:49:31 malraux kernel: [ 593.787884] composite sync not supported
Mar 8 18:49:31 malraux
Public bug reported:
Just ran latest raring updates. Screen on full brightness, Fn keys
didn't move the slider. Going to the Brightness settings I can move the
slider but it has no effect.
Setting it manually still works: echo 978
/sys/class/backlight/intel_backlight/brightness
ProblemType:
I downgraded to confirm the old version was working (it was). Upgraded
again and this time the Fn keys weren't working, but the brightness
slider was present. There is also so much general instability (multiple
crash reports and lockups) I couldn't confirm that the problem is
related to g-s-d.
--
Public bug reported:
After today's update my brightness controls aren't working anymore.
After checking the System Settings, Brightness and Lock there is no
longer any brightness slider bar shown for manual setting either. So my
screen is fixed on full brightness.
The same thing happened during
Elijah, open a new issue or look for an existing issue e.g. I think bug
776590 covers this problem.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/947748
Title:
I think this is a Unity action, not Nautilus
** Package changed: nautilus (Ubuntu) = unity
** Summary changed:
- Unable to open a folder for 10 GB Filesystem, No application is registered
as handling this file... Nautilus pops browser on bash partition mount
+ Unable to open a folder for 10 GB
** Summary changed:
- Nautilus pops browser on bash partition mount
+ Unable to open a folder for 10 GB Filesystem, No application is registered
as handling this file... Nautilus pops browser on bash partition mount
** Description changed:
I first noticed this behaviour in Ubuntu 11.10. When
Public bug reported:
I first noticed this behaviour in Ubuntu 11.10. When I run my bash
script that mounts partitions on my hard drive (e.g /dev/sda5), Nautilus
pops up with a browser window. This is an illogical action, since I've
not 'inserted a drive', it's already there, and it's just been
Public bug reported:
After today's update my brightness controls aren't working anymore.
After checking the System Settings, Brightness and Lock there is no
longer any brightness slider bar shown for manual setting either. So my
screen is fixed on full brightness. I'll attach screen shots showing
** Attachment added: After update pic of brightness and lock settings
https://bugs.launchpad.net/bugs/947748/+attachment/2820806/+files/brightness2.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in
** Attachment added: Before today's update pic of Brightness and Lock settings
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/947748/+attachment/2820809/+files/brightness.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
FYI, I ran a successful upgrade since the fix was released - the fix
obviously didn't make it into the release candidate .iso, so running the
upgrade from RC alternate cd (using cdromupgrade) gives the same gnome
keyring error, however allowing cdromupgrade to pull the latest packages
from the net
I should add that this was a wubi upgrade... and the wubi failed to
start following the upgrade (rebooted without showing any error messages
or grub menu). I am considering this to be unrelated since my previous
upgrade of wubi that showed the gnome-keyring error and specifically
stated that the
Public bug reported:
Binary package hint: gnome-keyring
Running upgrade from 10.04.1 to 10.10 using the alternate daily .iso
(running the cdromupgrade).
A couple of errors related to the keyring popped up - the Take screen
shot tool didn't work as it said .png file type unknown and terminated
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/650790/+attachment/1651633/+files/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
https://bugs.launchpad.net/bugs/650790/+attachment/1651634/+files/VarLogDistupgradeAptlog.gz
** Attachment added:
** Description changed:
Binary package hint: gnome-keyring
Running upgrade from 10.04.1 to 10.10 using the alternate daily .iso
(running the cdromupgrade).
- A couple of errors related to the keyring popped up - the Take screen
- shot tool didn't work as it said .png file type unknown
Same thing happened to me after adding 5 new locations. Not using amd64.
I couldn't reproduce the bug, either by adding additional locations, or
removing all but the default and adding back the ones that caused the
first crash.
--
clock-applet crashed with SIGSEGV in g_main_context_dispatch()
22 matches
Mail list logo
