[Desktop-packages] [Bug 736349] Re: "Test speakers" is silent

2018-06-20 Thread OliFre
> For me, installing libcanberra-pulse worked.

So many thanks for this!
This is still required to fix things on Ubuntu 18.04!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-sounds in Ubuntu.
https://bugs.launchpad.net/bugs/736349

Title:
  "Test speakers" is silent

Status in OEM Priority Project:
  Fix Released
Status in gnome-media package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntu-sounds package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-media

  My speakers are working fine (I can year playback with Banshee and
  VLC), but "Test speakers" is silent. I hear nothing when I press on
  the "Test" button.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-media 2.32.0-0ubuntu5
  Uname: Linux 2.6.38-020638-generic x86_64
  Architecture: amd64
  Date: Wed Mar 16 20:30:19 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-media
  UpgradeStatus: Upgraded to natty on 2011-03-11 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/736349/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-06-10 Thread OliFre
@Ads2 Thanks for the link. Sadly, gdm3 is neither in the
autopkgtest-list, nor update-excuses, nor update-list, so it seems
things are stuck at an earlier stage and the documentation does not
clarify where to find out at which point help could be needed.

My intention was not to spam this report, but to find out where things are 
stuck (it's not obvious) and how to give support. 
It's also not about my personal (im)patience, but we have >200 desktops and 
>2000 Ubuntu containers and have had to stop the migration after the first 10 
desktops due to this bug (and three(!) other ones which all have been known 
*before* release and should either have been release blockers or been mentioned 
as "Known Issues" with the new LTS to prevent people from hopping onto the new 
supposedly-stable). For the other critical issues, QA apparently was even 
worse, since Debian and in one case also RHEL have already released fixes 
months or even a year ago, and there has been no reaction on Launchpad 
whatsoever yet. Since we are also still affected by critical bugs in 16.04 
which have been open since 16.04's release and could only be solved by PPA 
(broken OpenAFS), this makes me wonder whether Ubuntu still is a valid choice 
for institutional use, but this discussion certainly goes off topic here. 

Just let us know if there is something people could help with (testing
etc.). As it stands, the status is completely unclear apart from the
statement _to be patient_ - without indicating what the actual point is
where things are stuck.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)

[Desktop-packages] [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)

2018-06-08 Thread OliFre
Since it's still in proposed and a day is mostly over (and Europe is
asleep again) - could somebody outline / point me to the conditions for
a package to be moved from proposed to released?

This would be good to know to understand what is missing (and
potentially help?) instead of entering a lengthy discussion here, with
almost a 100 affected people and hence spamming lots of subscribers.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766137

Title:
  [regression] Password accepted but login fails (blank purple screen
  and mouse pointer only)

Status in gdm:
  Fix Released
Status in Release Notes for Ubuntu:
  Fix Released
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  Due to a refcounting bug, a GDBusConnection was getting disposed when
  it was still required. The symptom of this was that you couldn't log
  in on the second attempt if you'd got your password wrong on the first
  attempt. All you'd see is a blank purple screen and mouse pointer
  only.

  [ Test case ]

  1. Boot to GDM
  2. Click your username
  3. Type the wrong password a couple of times, pressing enter after each time
  4. Type the right password

  If the bug is happening, after 4. the system hangs at a blank screen
  with the mouse cursor. If you then switch to a VT or otherwise connect
  to the machine, you can examine the journal and you'll see a
  G_IS_DBUS_CONNECTION failure.

  [ Fix ]

  Marco and I worked upstream on this fix. We found out that there was a
  problem like this-

  The GdmClient has a shared GDBusConnection for its operations. The
  first time  someone calls for it, it is created and stored in the
  object's private structure. Subsequent calls return *a new reference*
  to this same object. It turned out that the asynchronous method to get
  the connection was accidentally unreferencing its object before giving
  it to the caller if it was returning an already-existing connection.

  For this to work properly, we need to nullify the pointer we stored
  when the connection goes away, so we know when to make a new one.
  There were some cases where we didn't add the weak references required
  to do that. Those are also fixed.

  [ Regression potential ]

  Now we share connections more than we did before. We also more
  carefully track when to clear our object. If we got this wrong, we
  might end up leaking the connection or dropping it in even more cases.

  [ Original report ]

  WORKAROUND: After typing an incorrect password, click Cancel, then
  click your name, then enter your password again.

  ---

  Trying to log into my session (Gnome, Xorg), if I enter the wrong
  password before entering it correctly, the session doesn't load and I
  get a purple screen, a mouse cursor, and an invisible but clickable
  menu in the top right. If I enter it correctly the first time, there
  is no problem.

  I've replicated this from a fresh boot, after logging out and after
  'sudo service gdm restart' from the Ctrl-Alt-F4 console.

  This is a fresh install, and didn't occur when I was using a previous
  install of 18.04 (until Friday).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 22 20:31:13 2018
  InstallationDate: Installed on 2018-04-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp