I thought of a different way to re-add zero: simply allow it as one of the
usable values. As it is right now, gnome-power-manager's indicated brightness
levels
(100, 85, 71, 57, 42, 28, 14, 0)
no longer match the indicated values in the dsdt:
(100, 87, 75, 62, 50, 37, 25, 12, and a true zero
Thank you! I'm glad to see that the 2.6.24-11-generic kernel I recently
installed has fixed this!
One slightly odd request: sometimes, for a gimmick, it's fun to turn off the
backlight deliberately; is there any way to do this now, perhaps by echoing a
specific negative value into sysfs
Is there any chance of reopening this bug for Hardy? I greatly prefer
the old subpixel rendering method, and before the rendering patches were
moved upstream, I could use my local.conf to enable the old method;
however, as of fontconfig 2.5.0-2ubuntu2, I can no longer do that --
instead, I just
Well, I'm glad I didn't decide to change any attributes of this bug myself.
I followed the link to https://bugs.freedesktop.org/show_bug.cgi?id=13566 and
discovered that the constant had been renamed to 'lcdlegacy'. I then tried
that value in local.conf, and it claimed 'lcdlegacy' was invalid.
Public bug reported:
Binary package hint: gnome-settings-daemon
When a mounted volume becomes low on disk space, something -- notify-osd claims
it's gnome-settings-daemon -- pops up a notification to tell the user.
Under the old notification daemon, this would pop up as a bubble, once per
Another good use case for the difference between unmount and eject:
card readers. With my Kingston USB multri-reader under Karmic, I went
to unmount a CompactFlash card so I could manipulate partitions on it,
using the eject icon in the Nautilus sidebar... and then was confused
when I couldn't
Hmm, something new I just noticed: the latest gnome-settings-daemon FORCES me
to choose either two-finger scrolling OR edge-scrolling, and does not allow
both -- thus overriding my preference I have set in a custom FDI file! In
addition, it's not content to just reset the settings once it
er, correction: key is scroll_method.
--
Touchpad Tap Clicking Broken (scrolling also)
https://bugs.launchpad.net/bugs/404219
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in ubuntu.
--
desktop-bugs mailing list
I'm on Jaunty, and the latest 2.6.28-4.10 generic x86-64 kernel entirely
removes my ability to change brightness levels; the previous kernel
works perfectly.
Under the old kernel, /proc/acpi/video/DGFX/LCD/brightness returns this:
levels: 100 51 30 37 44 51 58 65 72 79 86 93 100
current: 100
** Attachment added: EliteBook-8530w-dsdt
http://launchpadlibrarian.net/21291692/EliteBook-8530w-dsdt
--
2.6.27-11 makes brightness not work
https://bugs.launchpad.net/bugs/315922
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Okay, I just tested, and the same version (but 32-bit) kernel on my old
Gateway M685 also breaks backlight control. Same symptoms: proc has
not supported and sys is empty.
--
2.6.27-11 makes brightness not work
https://bugs.launchpad.net/bugs/315922
You received this bug notification because
** Summary changed:
- 2.6.27-11 makes brightness not work
+ 2.6.27-11 makes brightness not work [2.6.28-4.10 also affected]
--
2.6.27-11 makes brightness not work [2.6.28-4.10 also affected]
https://bugs.launchpad.net/bugs/315922
You received this bug notification because you are a member of
Another system affected: an old Toshiba Satellite 1415 laptop. ACPI
Video module normally gives levels labeled as 0%, 40%, and 100%, but now
gives nothing. For better backlight control, this laptop needs toshiba-
acpi instead of tlsup, but that's an entirely different issue.
--
2.6.27-11 makes
Aah, I see it now in the Intrepid changelogs. Cool, so now I can just
wait, and it'll be fixed with an upcoming Jaunty kernel, right?
(By the way, the tlsup bug is also fixed in intrepid-proposed but not
in jaunty: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/261318 )
linux
For me on Jaunty, the 2.6.28-7-generic kernel has been fixed now -- it
seems they've reverted the don't use _BCM and _BCL patches. I'm not
sure about the Intrepid kernel, though. Also, this is not quite a
duplicate -- it's more of a fixing that one broke this one issue.
--
2.6.27-11 makes
This is still broken for me, if I use a non-default icon theme (such as
Tangerine). The old notification-daemon package worked perfectly fine
with all my icons, but for some reason, this new one only seems to like
Human -- literally NO other icon themes on my system show anything for
it.
--
*** This bug is a duplicate of bug 263779 ***
https://bugs.launchpad.net/bugs/263779
I disagree with marking this as duplicate: this bug is about the going
fullscreen on play; the other bug was about it BLOCKING the play
button from reaching the media player. It may be true that it no longer
*** This bug is a duplicate of bug 263779 ***
https://bugs.launchpad.net/bugs/263779
er, another application, not another computer -- curse the lack of
edit function.
--
Evince goes full screen when pressing play on keyboard
https://bugs.launchpad.net/bugs/339757
You received this bug
*** This bug is a duplicate of bug 263779 ***
https://bugs.launchpad.net/bugs/263779
The thing is, it's not instead of Evince -- I get BOTH actions
happening. The media player (in this case, quodlibet) pauses or
resumes, AND evince takes over the whole screen! If I'm trying to work
on
*** This bug is a duplicate of bug 263779 ***
https://bugs.launchpad.net/bugs/263779
ii evince 2.26.1-0ubuntu
ii gnome-settings 2.26.1-0ubuntu
ii quodlibet 2.0-1ubuntu2
Also note that, because my laptop lacks true media control keys, I have
play/pause, previous, next, and
I have an interesting idea for home folder name: compare the short
username to the first-name in About Me, and if it maches (besides
case), then display the name with capitalization as in About Me. For
example, I have my username as dana (lowercase), and we could display
the folder name as Dana.
*** This bug is a duplicate of bug 453605 ***
https://bugs.launchpad.net/bugs/453605
** Tags added: regression-release
--
Karmic incorrectly mounts USB disk (NTFS) as 700, cannot change behavior.
https://bugs.launchpad.net/bugs/482501
You received this bug notification because you are a
I'm marking this regression-release, because as commented on in the
duplicate, we went from Jaunty (HAL) offering NTFS drives as 777 by
default (I believe), with gconf options to change permissions, to Karmic
(devkit-disks / udisks) offering no way to change permissions from 700
-- and thus no way
Also, I tried to change Nautilus (linked to upstream bug tracker) to gvfs,
and got:
Internal Server Error
NotImplementedError
--
Make default mount umasks configurable
https://bugs.launchpad.net/bugs/453605
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I have the same issue when making udev auto-mount things by label -- I'm
using the following script, tweaked to use blkid instead of vol_id:
http://superuser.com/questions/53978/ubuntu-automatically-mount-
external-drives-to-media-label-on-boot-without-a-us
I've also tweaked the script to use
Another use case for having both: I have both a built-in, single-finger-
except-with-special-windows-driver* touchpad, and a Magic Trackpad. So
I get either edge scrolling on both, or 2-finger on the latter and no
scrolling at all on the former.
*
I disagree. Just because something is consistent, that doesn't mean it
is sensible or intuitive.
That may be true, but it's far more likely to find something
INconsistent, confusing and counter-intuitive.
I would likely find it impossible to adapt to your desired behavior.
Every device I've
This same BadAtom also happens for me with the open-source Radeon driver, yet
does not happen with the binary driver.
It looks like the problem most likely lies in the fallback brightness-control
methods used when the xrandr backlight property is not supported.
Note that fglrx supports
I can confirm this. When I leave the netbook idle, the brightness
control starts spazzing out, flickering back and forth between two
brightness levels, and eating 100% of one CPU core (at least if notify-
osd is running). On the login screen (no notify-osd), it happens fast
enough that it may be
Architecture: i386
DistroRelease: Ubuntu 10.10
EcryptfsInUse: Yes
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N130
Package:
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541573/+files/BootDmesg.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash, even if
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541574/+files/CurrentDmesg.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash,
apport information
** Attachment added: Dependencies.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541575/+files/Dependencies.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash,
apport information
** Attachment added: DevkitPower.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541576/+files/DevkitPower.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash,
apport information
** Attachment added: GConfNonDefault.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541577/+files/GConfNonDefault.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541578/+files/Lspci.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash, even if I only
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541579/+files/Lsusb.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash, even if I only
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541580/+files/ProcCpuinfo.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash,
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541581/+files/ProcInterrupts.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541582/+files/ProcModules.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash,
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541583/+files/UdevDb.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash, even if I
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541584/+files/UdevLog.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator continues to flash, even if I
apport information
** Attachment added: gnome-power-bugreport.txt
https://bugs.edge.launchpad.net/bugs/387269/+attachment/1541585/+files/gnome-power-bugreport.txt
--
If I am using the battery and want to brighten the screen as soon as I increase
the brightness level the level indicator
This misfeature irritates me every time I have to use Evince. I can
understand having the thing skip pages when it's ALREADY in fullscreen
mode... but consider the current behavior:
I'm reading a PDF document while listening to music, and try to skip
tracks what happens? Evince goes to the
evince: 2.30.1-0ubuntu3
gnome-settings-daemon: 2.30.1-0ubuntu1
music player: quodlibet 2.1-4
--
Evince hijacks global multimedia keys
https://bugs.launchpad.net/bugs/263779
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
I'm not sure if this is the same bug, but when using
gnome-stracciatella-session (i.e. no notify-osd), brightness control keys do
not work.
?field.comment=I'm not sure if this is the same bug, but when using
gnome-stracciatella-session (i.e. no notify-osd), brightness control keys do
not work.
Speaking of Nautilus, I get some assertion failures, currently:
(nautilus:3021): Gdk-CRITICAL **: gdk_window_set_back_pixmap: assertion
`pixmap == NULL || gdk_drawable_get_depth (window) ==
gdk_drawable_get_depth (pixmap)' failed
(nautilus:3021): GLib-GObject-CRITICAL **:
On my HP laptop with capacitive volume-control softkeys, zero volume
and mute are two vastly different states: hardware mute is indicated
by the hardware mute button / LED turning orange, and mutes the internal
speakers no matter what state the OS is in.
In Windows 7, the mixer offers a
It looks like radeontool fails silently, instead of telling the user to run it
under sudo. I also had to escape the asterisk to pass it to radeontool:
sudo radeontool match \*
Here's my radeontool output on 2.6.34-rc5 kernel from kernel-ppa -- this
is the broken case.
I can't seem to recall a
More correctly, I can't remember _whether_ it ever worked before.
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I agree... flat volumes are horrible, in terms of user experience.
I managed to blast myself the other day, by turning up Totem's volume
(because it was too quiet) ... and oops, now it turned up the sound
card, too! BAM! I'm just glad I didn't have headphones on at the time!
Windows (Vista,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/40528556/Dependencies.txt
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/40528557/DevkitPower.txt
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/40528558/GConfNonDefault.txt
Public bug reported:
Binary package hint: gnome-power-manager
With the deprecation of hal, gnome-power-manager must rely on the
BACKLIGHT property in xrandr; however, the ATI open-source drivers seem
not to support this property (regardless of whether KMS is enabled).
With HAL removed, g-p-m
To clarify, there are two interacting bugs here: One is that Radeon
doesn't support BACKLIGHT, and the other is that the old HAL-based way
no longer works. The preferred action would be to fix the former,
rather than the latter.
** Also affects: xserver-xorg-video-ati (Ubuntu)
Importance:
apport information
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/41238078/CurrentDmesg.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41238081/Dependencies.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu
apport information
** Tags added: apport-collected
** Description changed:
Binary package hint: gnome-power-manager
With the deprecation of hal, gnome-power-manager must rely on the
BACKLIGHT property in xrandr; however, the ATI open-source drivers seem
not to support this property
apport information
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/41238083/DevkitPower.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/41238084/GConfNonDefault.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of
apport information
** Attachment added: Lspci.txt
http://launchpadlibrarian.net/41238090/Lspci.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
apport information
** Attachment added: Lsusb.txt
http://launchpadlibrarian.net/41238109/Lsusb.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
apport information
** Attachment added: ProcCpuinfo.txt
http://launchpadlibrarian.net/41238110/ProcCpuinfo.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: ProcInterrupts.txt
http://launchpadlibrarian.net/41238111/ProcInterrupts.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of
apport information
** Attachment added: ProcModules.txt
http://launchpadlibrarian.net/41238112/ProcModules.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: RelatedPackageVersions.txt
http://launchpadlibrarian.net/41238115/RelatedPackageVersions.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a
apport information
** Attachment added: UdevDb.txt
http://launchpadlibrarian.net/41238121/UdevDb.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
apport information
** Attachment added: UdevLog.txt
http://launchpadlibrarian.net/41238123/UdevLog.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a member of Ubuntu
Desktop
apport information
** Attachment added: gnome-power-bugreport.txt
http://launchpadlibrarian.net/41238128/gnome-power-bugreport.txt
--
[lucid] Broken backlight control with Radeon open-source drivers
https://bugs.launchpad.net/bugs/534677
You received this bug notification because you are a
This is still true with the Radeon driver in Natty. There's no
BACKLIGHT property exposed on the LVDS interface.
Gnome Power Manager itself now works around it, with gnome-backlight-helper.
KDE also now somehow works around it, as well.
So, the user-facing portion is fixed, but the original
I can confirm: this issue still applies in Ubuntu Natty (64-bit here).
In my case, the song is removed from my library only until I restart Rhythmbox.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
** Changed in: rhythmbox (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/677042
Title:
rhythmbox removes song from library when
*** This bug is a duplicate of bug 947748 ***
https://bugs.launchpad.net/bugs/947748
In my case, I'm using an nvidia card on a Thinkpad, with
EnableBrightnessControl set.
On at least the Intel driver, xrandr --verbose presents both 'BACKLIGHT' and
'Backlight'.
The nvidia driver (with
** This bug is no longer a duplicate of bug 947748
Brightness control not working after latest update
--
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/947919
Title:
More specifically, the critical file from ubuntu-gnome-default-settings is:
/usr/share/glib-2.0/schemas/20_ubuntu-gnome-default-settings.gschema.override
If you remove that file and update schemas (one way is "dpkg-reconfigure
libglib2.0-0"), gdm won't start properly.
If you re-add the file and
** Summary changed:
- Connecting to GDM via XDMCP crashes it
+ Connecting to GDM via XDMCP crashes it (GdmXdmcpDisplay shouldn't be abstract)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
Public bug reported:
I've enabled XDMCP in GDM, and created an xinetd service for VNC via
XDMCP.
Any time I try to connect via VNC, gdm crashes, taking down the local display
as well.
After that, gdm won't start again until I kill the "orphaned" local display.
It looks like the fix is a
** Bug watch added: GNOME Bug Tracker #757714
https://bugzilla.gnome.org/show_bug.cgi?id=757714
** Also affects: gdm via
https://bugzilla.gnome.org/show_bug.cgi?id=757714
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Same for me: I can use xrandr manually in an Xorg session, but not in
the Wayland sesson.
>From some stuff I read online, it seems like Gnome is trying to prevent
you from making the virtual resolution too low, but if it's already too
low, now you're stuck like that, and it really ought to be up
78 matches
Mail list logo
