In lucid the bud still persists, even though it shows in a different
manner. As maverick is coming out in a few days, I will not comment in
detail on the lucid bug. I will update my system only after the official
release and report back then if the bug is still present in maverick
--
[jaunty]
seems to fix it for me to. Since the bug was random on my machine I
can't be sure yet, but it looks good.
madbiologist schrieb:
Could everyone please check if the cairo 1.8.8-2ubuntu1.1 package in
karmic-proposed fixes their PDF printing issue?
Just in case anyone doesn't know how to enable
No, on my computer, the bug does not seem to be related to the length of
the file. At least, at the moment, I can't get it evince to print a
small (16,4 kB) one-page pdf. However, a few days ago, I could print
exactly this file without a problem.
asheenlevrai schrieb:
to Uwe: isn't that related
I can also confirm this bug. Printing works fine with every program
except with evince. When printing in evince, the printer icon appears in
the notification area and disappears again after a while telling me that
printing has been successful, even though nothing was actually printed.
To make
Public bug reported:
Binary package hint: evince
Since I updated to karmic, evince won't print anymore on my network
printer (no printer available to test it locally). Whenever I try to
print something in evince, everything seems fine, the jop is sent to the
printer and a little printer icon
Same problem here. On my machine, it affects the search bar as well as
the url bar, and, as Ricket described it, not only after the screen
saver, but also after locking the screen or resuming.
--
Firefox search bar bug -Auto highlight
https://bugs.launchpad.net/bugs/428703
You received this bug
The behavior has changed already under jaunty: now working on battery
power always allows for medium brightness, and only not touching the
keyboard for a while dims the screen completely. I guess that is the
desired behavior. I didn't notice this change since I haven't tried
working on battery
Yes, it is reproducible. Some further testing showed that gnome starts
to mix up the shortcut after log out - log in or after a reboot
Steps to reproduce:
1. Go to system - Preferences - Keyboard, change the behavior of the
capslock key there to swap capslock and esc
2. Go to System -
Yes, if I bind maximise window to ctrl+esc, the same problem arises
for that action. I guess with interface, you are talking about System -
Preferences - Shortcuts: the keybinding written there is ctrl+esc
--
[jaunty] gnome sometimes uses keycodes instead of characters
Public bug reported:
Binary package hint: gnome-power-manager
Since I updated to from hardy to jaunty, the behavior of the screen
brightness on battery power is strange. On unplugging, the overall
brightness goes down (expected), but cannot be brought up to the level
without battery power
Actually, it is not always switching to the cyclic mode. This time,
the screen went black right after unplugging, and I could bring it with
the hotkeys to a level at which it was barely usable in a completely
dark room. However, it did not become brighter by itself this time, as
described above.
** Attachment added: gpm.gconf.values.txt
http://launchpadlibrarian.net/26423116/gpm.gconf.values.txt
--
[jaunty] screen brightness level on battery power unsteady and too dark
https://bugs.launchpad.net/bugs/373096
You received this bug notification because you are a member of Ubuntu
Logging this information, I had again the cyclic behavior.
** Attachment added: gpm.debug.log.txt
http://launchpadlibrarian.net/26423224/gpm.debug.log.txt
--
[jaunty] screen brightness level on battery power unsteady and too dark
https://bugs.launchpad.net/bugs/373096
You received this bug
The bug gets ever more confusing: while logging this information, I had
the expected bahavior (for the first time ever, I think). The monitor
went a little darker after unplugging, and I could turn it up to maximum
brightness using the hotkeys. I'll rerecord that information trying to
reproduce
Ok, here the same log with the cyclic behavior.
** Attachment added: dbus-monitor.backlight.log.txt
http://launchpadlibrarian.net/26423383/dbus-monitor.backlight.log.txt
--
[jaunty] screen brightness level on battery power unsteady and too dark
https://bugs.launchpad.net/bugs/373096
You
Public bug reported:
I have set the shortcut ctrl+esc for opening a new gnome-terminal. In
the following I will refer with the lower key to the capslock-key
itself and with capslock to the behavior, also the upper key is the
escape key itself, esc is its behavior.
I swapped the capslock-key and
My first bug report was not quite accurate: there actually is an extra
entry in my xorg.conf specifying a virtual resolution of 1280 x 1024. I
commented it out and have now my native resolution back. However, it
should be possible to get back the native resolution via GUI tools
without resorting
Public bug reported:
I used the screen settings to change my resolution to a lower value
(because I could not get a projector to work). In order to change to the
lower resolution, I was asked for the system password, because Monitor
Resolution Settings has detected that the virtual resolution
Yes, it is reproducible. Steps to take:
1. have a folder with music in your library, for example jbo
2. start rhythmbox
3. I cannot directly rename a folder if only case changes, so I rename
jbo to jbo2
4. rename jbo2 to JBO
5. now every song appears three times in the rhythmbox library, once
Public bug reported:
Binary package hint: rhythmbox
I have my files on a fat32 partition so that I can also access them in
case I have to boot windows. I noticed that all songs that are in
folders with just three upper case letters appear twice in the playlist.
If I check the properties of both
I updated my system to jaunty and can't reproduce the bug anymore.
--
Keyboard shortcut for the power symbol not working in gcalctool
https://bugs.launchpad.net/bugs/236764
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
Deleting the file ~/.local/share/rhythmdb.xml solved the issue.
Unfortunately, all the play counts are gone. It still seems to be a non-
issue, sorry filing the bug report.
--
songs from folders with only three letters in upper case appear twice in
playlist
Same grievance here. Whenever the pointer is accidentally over the
taskbar and I only slightly touch the scroll area of my touchpad, I'm
instantly desoriented for a few seconds. On a touchpad, this feature is
unusable (at least, obviously to a lot of people) and it should be
possible to disable
I can confirm this bug. It is not only the ^-shortcut which is broken
but also a lot of others, like }, @, and so on. To me, this bug seems to
be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/238508 , which
unfortunately has been closed.
I am also working with a German
*** This bug is a duplicate of bug 119636 ***
https://bugs.launchpad.net/bugs/119636
I had the same problem. I backed up the .evolution-folder in my home
directory and then deleted it. I started evolution, which was suddenly
no problem. Putting the whole old .evolution folder back in place
Public bug reported:
https://launchpad.net/malone/bugs/30824
Affects: rhythmbox (Ubuntu)
Severity: Normal
Priority: (none set)
Status: Unconfirmed
Description:
rhythmbox 0.9.1 on breezy: when I add a folder twice the songs will
appear twice in the playlist, even though
26 matches
Mail list logo
