This seems to be a gdm package bug. Before installing gdm, my
/etc/X11/default-display-manager file contains:
/usr/sbin/lightdm
After installing gdm, the file contains:
/usr/sbin/gdm
After uninstalling gdm, the file contains:
lightdm
And now lightdm doesn't start on boot. If you fix it back to
People are giving feedback to this issue. Some developers would be
interested in that. It's frustrating to have the usability of a program
hurt so badly by such a seemingly small thing. (It seems like it should
be able to qualify as a Papercut.)
And this bug report has a whole 7 comments in the
I've updated today and done as you said, but no luck.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I've done that multiple times and it doesn't work, unfortunately.
--
[Maverick] Sound is always muted on startup; unmuting makes the volume at
lowest level
https://bugs.launchpad.net/bugs/592016
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Daniel, but how would I fix the problem for an existing user? I've
already tried stopping pulse and deleting .pulse* from the home
directory.
I'm glad that when I start my computer and login to my username, my
sound isn't muted upon entering my session anymore. But I'm still
troubled by the fact
This is now fixed for me after the latest update to alsa-utils this
morning.
* debian/init: Restore change from 1.0.21-1ubuntu2 lost during merge
that skips muting and zeroing levels prior to shutdown/reboot,
which was a hack for broken drivers. This change closes LP: #21804,
LP:
I'm also getting this issue. (1440x900 monitor being incorrectly given
1280x1024 resolution). I filed LP: #638103 as I thought it was a gdm
problem, since I started getting the issue after upgrading gdm a couple
days ago.
gdm (2.30.5-0ubuntu4) maverick; urgency=low
* debian/gdm.upstart: Do not
Perhaps I spoke a little too soon. It does indeed appear to be *mostly*
fixed (sound isn't muted now upon boot), but I just logged out of one
user and into another, and the second user had muted sound. The levels
weren't zeroed, but it was indeed muted when it shouldn't have been. (No
login sound
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/638103/+attachment/1583254/+files/Dependencies.txt
--
gdm 2.30.5-0ubuntu4 regression - wrong resolution
https://bugs.launchpad.net/bugs/638103
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: gdm
Since upgrading gdm to 2.30.5-0ubuntu4 from the previous version, it
fails to set the correct resolution at bootup. This is the first time
it's ever done this. In the past it has always chosen my monitor's
correct native widescreen resolution of
This isn't completely fixed. It's still here in a strange way.
For my account, the issue is gone. But for the second user account on my
machine, the bug still exists. Here are peculiar things I can easily
reproduce:
Consider user A my account - sound always works fine. User B is the
account
Hi Luke, I tried your suggestion and it didn't help. I actually did it
for both accounts, and now the one that was working is back to having
the muted problem again too. :/
If you yourself try what you suggested, does it make the problem come
back? Or for anyone else?
Is there anything else I
I can confirm Luke's observations.
Doug, I've never fiddled with alsamixer and still have the bug.
** Attachment added: pulseverbose.log
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/592016/+attachment/1520263/+files/pulseverbose.log
--
[Maverick] Sound is always muted on
Thanks for the PPA. It let me fix GNOME's/Ubuntu's bad/idiosyncratic
touchpad defaults. I couldn't understand why in the world double-tapping
was resulting in a right-click when I started using Ubuntu on my
netbook. It's a real pain. Hopefully this will be fixed in 10.10.
--
Touchpad: Action for
Ugh. So yeah, these Compiz/Workspace Switcher bugs still obviously
exist.
1. Can't use mouse wheel to scroll workspaces in the switcher.
2. Can't drag from the window list to the workspace switcher to send a window
to another workspace.
3. Can't drag a window from the window switcher and drop it
This is one reason I also can't seriously switch from Pidgin to Empathy.
I remember trying Empathy out last year (I believe) and running into
this issue and finding this same (I assume) open bug report. Knowing
whether or not my friends are on their mobile plays a large part in
how/if I
16 matches
Mail list logo
