** Branch linked: lp:~george-edison55/gnome-settings-daemon/871133
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/871133
Title:
Volume Step not changeable in Unity and
"...just attached the patch done by Nathan Osman"
I didn't create the patch either, though I did need to tweak it a bit to
fix some compilation errors.
"First I see reports (mostly in the upstream report) that people are
getting 10-30% steps in volume instead of the defin
Oops - I meant to write "If so" instead of "If not" in the fourth
paragraph of the last message.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/871133
Title:
Volume
** Also affects: unity-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/871133
Title:
Ubuntu Oneric
I decided to take some initiative and apply the patch myself. Naturally,
it needed to be applied to both gnome-settings-daemon and unity-
settings-daemon. The new setting is exposed at "org.gnome.settings-
daemon.plugins.sound.volume-step" and can easily be changed with dconf.
I've uploaded the
Since the patch attached in the bug report hasn't been accepted upstream
(and probably won't ever be), can we please add it to the Debian
packaging?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
I'm afraid that this bug seems to have disappeared and I can no longer
reproduce the issue. An update must have fixed the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1382845
Is there any way at all to create an application indicator from a Qt 5.1
application then? I tried doing this once before a while back and I
remember that there was some sort of problem with event loops.
--
You received this bug notification because you are a member of Desktop
Packages, which is
I backported the appmenu-qt5 package to Utopic and gave it a go, but
unfortunately it doesn't seem to work. The tray icons still apear in the
upper-left corner of the desktop.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sni-qt in
Ah. Would it be difficult to modify it to support Qt 5.1? Alternatively,
do you know if there are plans to backport Qt 5.4 to Utopic and/or
Trusty?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sni-qt in Ubuntu.
I want to add that the switch-VT trick works when you have a single
video card but fails to work with multiple video cards in a multi-seat
configuration. This means that one of the seats is completely unusable.
I literally can't click anything.
--
You received this bug notification because you
Public bug reported:
I have just performed a completely clean installation of Utopic from the
daily ISO. After installation, however, I was unable to use the mouse
buttons. Neither the left nor right mouse buttons have any effect when
pressed. I tried connecting another mouse but it exhibits the
Hey... it actually did solve the problem - at least temporarily. Not
only that, but I noticed something else interesting before I tried that.
If two windows are open, the active one doesn't receive the clicks, but
the one underneath does.
--
You received this bug notification because you are a
This is still not fixed. I just installed postgresql-9.1 on a brand new
installation of Ubuntu 13.04 (64-bit) and received the following error
when attempting to start the server:
* Starting PostgreSQL 9.1 database server
* The PostgreSQL server failed to start. Please check the log
Public bug reported:
ALSA fails to recognize the internal FCH Azalia Controller (rev 01) in
my system. It was recognized and worked properly until a bunch of
updates were installed last night.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: alsa-base 1.0.25+dfsg-0ubuntu4
After some further investigation, it appears that the keyboard input is
actually captured by the application running in the foreground behind
GDM. So if I leave a text editor open, lock the display, come back later
and try to enter my password, whatever I type on the keyboard is entered
into the
Public bug reported:
I left my computer unattended for a few minutes and the display shut
off. Upon returning, I attempted to unlock the computer by entering my
password with the keyboard. None of the keys seemed to have any effect -
I couldn't enter anything in the password entry box and
17 matches
Mail list logo
