The bug is still present in 12.04. The workaround of disabling GPU
scaling through the nvidia-settings utility still works. But that still
leaves the login screen with an incorrect resolution. Additionally guest
sessions will always start with an incorrect setting, so after starting
a guest
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/959343
Title:
Incorrect screen resolution
To manage notifications about this bug go to:
Public bug reported:
I'm using an Elysion U1 computer together with a BenQ projector. Ubuntu
reports that the monitor is not detected and defaults to a screen
resolution of 1280x800 pixels.
When I use the monitor preferences to change the resolution to 1024x768
(which is the correct resolution
I tested the 1024x768 resolution with all the possible refresh rates
that gnome-display-properties permits for this resolution. It makes no
difference which of the refresh rates from 52 to 56 Hz I choose, the
output always ends up being 1280x800 at 59Hz.
--
You received this bug notification
I finally found a way to get the correct screen resolution on the
output. In the nvidia-settings utility there is a section called DFP-0
where there is a Flat Panel Scaling box. In that box I disabled Force
Full GPU Scaling
The Flat Panel Information claims the native resolution of my
projector
Public bug reported:
When handling truetype fonts evince creates temporary files in /tmp.
When things are working correctly the files are automatically unlinked.
When something fails evince will print out an error message and forget
to clean up the temporary files.
Each time it happens the
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/904699
Title:
Empty files left in /tmp when some font thing fails
To manage notifications about this bug go to:
Public bug reported:
If a shell is launched through the menu SSH_AUTH_SOCK will have a value
of the form /tmp/keyring-xx/ssh. If a keyboard shortcut is created
through System Preferences Keyboard Shortcuts and that shortcut is
used to launch a shell, then SSH_AUTH_SOCK will have a value of
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/839444
Title:
Gnome uses two different ssh agents depending on how program is
launched
To manage notifications about this
Public bug reported:
Disk Usage Analyzer (/usr/bin/baobab) produce incorrect numbers on home
directories. When the tool is run from the command line it outputs an
error message saying:
glibtop: statvfs '/home/kasperd/.gvfs' failed
** (baobab:31935): WARNING **: error in dir /home/kasperd: Error
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-utils in Ubuntu.
https://bugs.launchpad.net/bugs/822792
Title:
Disk Usage Analyzer produce incorrect numbers on home directories
To manage notifications about this bug go to:
The home directory is encrypted with ecryptfs, but that does not seem to
be a problem for baobab. I can choose any other directory under the home
directory, and baobab reports correct usage information.
I don't know what .gvfs is. It is something that was set up automatically, I
don't know which
Public bug reported:
Binary package hint: gnome-power-manager
The Dell Latitude 13 (and possibly other models) have a key combination
to disable charging of battery. This combination is easy to hit by
accident when adjusting speaker volume. Currently there is no visible
indication that this
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/772017
Title:
Warn when battery is not being charged
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
A bit of additional information. Here are what the pseudofiles in
/proc/acpi/battery/BAT0 look like. As far as I can tell, the only way to
tell the difference between the case where the battery is fully charged,
and the case where it is not being charged, is from the remaining
capacity
15 matches
Mail list logo
