@Brian: just FYI, the /etc/X11/Xsession.d/50_check_unity_support file is
actually checking for ubuntu, not xubuntu: if [ "x$DESKTOP_SESSION" =
"xubuntu" ] will be true if $DESKTOP_SESSION is "ubuntu", because it's
prepending "x" to $DESKTOP_SESSION.
My unity_support_check was failing (it returns 1
Alt-F8 triggers resizing windows in compiz/Unity as well! That's good to
know.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/160311
Title:
Resizing windo
Seems to be fixed for me now - at least, the geeqie icon is shown
correctly now.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1407192
Title:
firefox ico
And I just had my permanently-locked firefox icon in the launcher
replaced with the placeholder, so it's definitely not fixed in that
version of bamf.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-
geeqie still displays the placeholder icon with bamfdaemon
0.5.1+14.10.20140925-0ubuntu2, though, so I suspect it isn't fixed.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.la
I find the launchbar always displays the grey question mark icon for
geeqie so long as it's not already locked to the launchbar.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.
This bug is still present in the latest Ubuntu 14.10 as of 2014-12-29.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1284981
Title:
Locally-integrated me
I just suspended a second time before restoring one of the windows to
the primary workspace, and when I resumed it was neither on the primary
nor the secondary workspace. I disabled workspaces and it reappeared on
the primary one. My guess is that unity restored the window to its
workspace+1 each t
Public bug reported:
When I suspend and resume my latop, my windows, which were originally
all in one workspace, are restored to different workspaces (apparently
at random).
For windows not in the current workspace after resume, the unity
launcher indicates that they are running, but clicking on
Public bug reported:
In Ubuntu 14.10 (upgraded from 14.04), the screen does not lock or turn
off after the designated time in System Settings / Brightness and Lock.
The screen lock can still be activated manually from the System menu or
keyboard shortcut (although I notice that the default has ch
+1 for what Guillaume F said in comment #45. Sometimes the dash takes so
long to populate that it tells me "Sorry, there is nothing that matches
your search", even though I know there are matches. And at random times
it resets the search filters to include Files and Folders - I turn this
off as soo
@Marco, thanks, I went back to gnome-screensaver 3.6.1-0ubuntu9 and this
restores the proper monitor dpms behaviour. The new screen locker does
look nicer, though, so I'm looking forward to when it handles dpms
properly.
--
You received this bug notification because you are a member of DX
Package
It affects the monitor. Is the monitor really non-essential?
And is there a way to use the old screen locker until this is fixed?
It's a pretty big regression.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscrip
Is there a setting available that lets the user disable this? It has a
nasty regression in that the new screen locker disables the screen power
down (ref https://bugs.launchpad.net/unity/+bug/1292041) so I'd rather
use the old screen locker until this regression is fixed.
--
You received this bug
Is there a way to disable the unity-greeter screen locker and revert
back to the old gnome-screensaver screen locker? Much as I like the look
of the unity-greeter screen lock, I prefer the power saving obtained by
turning the screen off while it's locked.
--
You received this bug notification bec
Reading the changes from https://launchpad.net/ubuntu/+source/gnome-
screensaver/3.6.1-0ubuntu10 and https://bugs.launchpad.net/ayatana-
design/+bug/878836, it looks like the unity-greeter is now being used to
implement the lock screen (not gnome-screensaver), so unity-greeter is
blocking the power
Which package implements the new lock screen? The regression is in this
package.
The old screensaver (gnome-screensaver?) used to power the monitor off
as soon you manually activate the lock screen (eg when you press the key
combination to lock the screen).
The new 14.04 screen locker (which pack
It looks the missing Transmission menus are appearing in the unity bar
(ie like the old global menus). When you focus away from Transmission
and back they appear in the usual place.
That's not the case with VirtualBox, however - the menus just vanish
completely until you focus away and then back.
This is also quite repeatable in Transmission. When I first show it
using the indicator menu, there are no menus displayed. In this
instance, the only way I can find to get the menus to work is to
maximize Transmission and then un-maximize it - the menus then appear,
at least until I open a pop-up
Public bug reported:
With (the absolutely awesome) locally-integrated menus enabled, if you
open the VirtualBox the menus initially work as expected, ie they appear
in VirtualBox's titlebar when you hover the mouse over it.
But if you open a popup window by clicking on New or Settings and then
cl
glxinfo on Ubuntu 13.10 shows this:
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile
OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.1
so perhaps the problem is in mesa 10.0.1. Maybe this thread is relevant
- i
Public bug reported:
I just upgraded to 14.04, and I'm seeing 50%-500% cpu usage from compiz.
Strangely, glxinfo reports this, which is totally incorrect - I'm
running on Intel Sandy Bridge HD3000 graphics and VMware isn't even
installed on this PC:
OpenGL vendor string: VMware, Inc.
OpenGL rend
Would unity-panel-indicator be able to detect when an indicator is
spamming dbus and log the name of the offending indicator?
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.lau
I watched rss to monitor the leak while opening and closing files in
gimp, and the process started going at 100% cpu somewhere around the
256k-270k range.
Interestingly, the rss goes up even if you just zoom in and out in gimp
- you don't even have to open a new file.
--
You received this bug no
24 matches
Mail list logo
