I do not have libhybris and I have never installed it. It is obviously a
separate issue.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1270960
Title:
totem fails to open unable to l
** This bug is no longer a duplicate of bug 1206371
libhybris breaks mesa (cannot find libwayland-egl.so.1)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1270960
Title:
totem fai
*** This bug is a duplicate of bug 1247221 ***
https://bugs.launchpad.net/bugs/1247221
** This bug has been marked a duplicate of bug 1247221
Nautilus doesn't remember setting for showing hidden files correctly when
org.gtk.Settings.FileChooser show-hidden is true
--
You received this bu
In my case (WPA enterprise with TTLS) the password is remembered
independently of the "available to all users" option. The problem is
that since oneiric it is stored in /etc/NetworkManager as plaintext and
not in the keyring.
--
You received this bug notification because you are a member of Ubunt
It is especific of gnome-panel but not of gnome-classic session. Running
gnome-panel on gnome-shell or unity also has the same problem. In all
cases, running gnome-panel from the terminal displays the "Cannot open
display:" error whenever the calendar is clicked.
Additionally, I would like to clar
** Also affects: evolution-data-server
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/885934
Title:
Double clicking on a date in the
h3, it seems that you have a different issue. If you read the bug
description it says that "kills reader device" just means that it stops
being powered and it is not repowered until next reboot. Apparently,
what you experience is a permanent break, so it is something unrelated
to this bug report.
I cannot see a regression here: In up-to-date Jaunty (supported updates,
at least), the "safely remove" option that I see in desktop and nautilus
sidebar is actually called "Unmount" and it does the same as Unmount
does in Karmic: it unmounts the filesystem.
Unmounting the filesystem does not prev
Jouni, the problem is with internal readers, which cannot be reconnected
without disassembling the computer.
Also, the description says "Drive worked fine until last couple of weeks": do
you mean that this has been a regression in a Karmic update? This is not my
case: since the release of the "s
