I haven't tried 4.16 but it is present in mainline 4.15.8
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
** Changed in: systemd (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I've been getting this error message lately when running some programs.
I'm running Xubuntu 12.04 64-bit. Do I really need gnome-keyring or can
I disable/uninstall it?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in
Mint, the workaround is mint.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1018718
Title:
columns width redrawn by multiple events
To manage notifications about this bug go
** Description changed:
In unity 5.2 RC1:
- revealing the launcher by putting mouse on the edge and pushing seems very
hard (the distance to push it long). This is even worse on trackpad.
Related issue:
on multimonitor setup, going from one monitor to the edge suffer from the
same
Rick,
The drivers are the primary reason this isn't working for some people.
Some touchpads are scaling inputs incorrectly, resulting in very low
velocity pressures. This should not prevent it from working for these
people, but it does make revealing take a bit more effort than intended.
I have
The idea is that you are sustaining a push over a period of time. The
important factor is the time. If you open CCSM and adjust the
responsiveness slider you will have a shorter required sustained push.
We dont have to expose this slider if we can decide on a value for it.
Currently it defaults to
Im getting this in natty too, or something similar. Suspend/resume work
fine and are fast, but after resuming, hard drive access speed is
limited to ~4MB/s. USB hard drives plugged into the system are not
affected though. It's not quite unusable, but extremely frustrating
when doing anything
** Changed in: unity
Status: Invalid = Triaged
** Changed in: unity
Assignee: (unassigned) = Didier Roche (didrocks)
** Changed in: unity
Importance: Low = Medium
** Changed in: unity-2d (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because
** Changed in: unity
Status: Confirmed = Invalid
** Changed in: unity (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/723865
** Changed in: unity
Milestone: backlog = ux-backlog-2
** Changed in: unity
Milestone: ux-backlog-2 = ux-backlog-1
** Changed in: unity
Assignee: (unassigned) = Didier Roche (didrocks)
** Also affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
You received
More precisely, the Backlight atom is not being set. Also GPM checks
the BACKLIGHT atom and not the Backlight atom which is deprecated.
--
gnome-power-manager:2651: GLib-GObject-WARNING **:
/build/buildd/glib2.0-2.25.11/gobject/gsignal.c:2275: signal `proxy-status' is
invalid for instance
This bug is caused by failed hardware recognition somewhere in uPower or
the Kernel. This causes gpm to (rather awkwardly) pass a null off to
xrandr, resulting in a crash. Fixing the crash will not restore
functionality however.
--
gnome-power-manager:2651: GLib-GObject-WARNING **:
** Changed in: netbook-remix-launcher
Status: Fix Committed = Fix Released
--
On startup Gnome Keyring asks for password in the background
https://bugs.launchpad.net/bugs/447886
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Fixed it :)
** Changed in: netbook-remix-launcher
Status: Triaged = Fix Committed
--
On startup Gnome Keyring asks for password in the background
https://bugs.launchpad.net/bugs/447886
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I am still having significant issues duplicating this bug despite
following instructions posted here. I do strongly believe this bug to be
a race condition however. I have attached a branch that may help in this
regard, if anyone can beta test it that is effected by the bug, please
let me know.
This is somewhat confusing. After looking at the code for nl-window, it
appears it doesn't actually call gtk_window_present on itself at all. It
does that for transient windows assigned to itself but not on itself. I
think the keyring is actually getting minimized(?) rather than being
obstructed
Ok I have a more in depth break down of the bugs behavior.
1) Gnome Keyring window is opened (in the forground)
2) Netbook Remix Launcher is opened (in the background)
3) Window manager, for some reason performs a focus event on NL (netbook
launcher)
4) In response, NL performs a
It's been fixed in bzr for a while now
--
Jaunty, drag and drop doens't work sometimes
https://bugs.launchpad.net/bugs/382843
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: totem
Using totem 2.23.4-0ubuntu2 on Intrepid Ibex, when opening an m3u file,
totem opens, but then says An error occurred GstDecodeBin: This
appears to be a text file.
** Affects: totem (Ubuntu)
Importance: Undecided
Status: New
--
For me, double-clicking in nautilus opens totem and produces the error An
error occurred GstDecodeBin: This appears to be a text file. The same happens
with FileOpen...
In both cases, the content of the m3u is not shown, only the filename of the
m3u.
--
totem no longer able to play m3u
Public bug reported:
Compiz/Beryl both need a patched libwnck to have a proper context menu.
These patches to add always on current viewport, move to current
viewport, setting the appearance of a window and moving the window.
Without them several features of compiz/beryl are not accessable. On a
** Description changed:
Compiz/Beryl both need a patched libwnck to have a proper context menu.
These patches to add always on current viewport, move to current
viewport, setting the appearance of a window and moving the window.
Without them several features of compiz/beryl are not
The above patch fixes the above checkbox to work with compiz... from within the
patch itself:
There's no _NET_WM_ACTION_ABOVE hint so always add it if window manager claims
to support_NET_WM_STATE_ABOVE
The viewport patch gives libwnck support for viewports which are used by
compiz/beryl
23 matches
Mail list logo
