[Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
** Changed in: ubuntu-power-systems Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1779815/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
abdhalee, Looks like you have successfully verified, could you please change the tag to verification-done-bionic ? ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: linux (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1779815/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1651518] Re: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create
** Also affects: ubuntu-power-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1651518 Title: systemd/logind parsing problem: HTX exercisers stopped on error: rc 11, errno 11 from main(): pthread_create To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1651518/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1279380] [NEW] [14.04] [Gnome-Settings-Daemon] unable to save default audio output device
Public bug reported: When more than one audio output source are available, gnome-settings usually picks the 1st one on the list. There is no way to save any alternate choice. For example I have: HDMI/DisplayPort2 Built-in Audio Digital Output (S/PDIF) Built-in Audio Analog Output Built-in Audio. The default output each time the system boots is set to HDMI/DisplayPort2 Built-in Audio and I have to manually change it to Analog Output Built-in Audio to which my PC speakers are connected. There is no "save this as default" option on this screen. So, I have do this each time I boot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-settings-daemon 3.8.6.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 12 09:18:30 2014 InstallationDate: Installed on 2013-04-10 (308 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-02-08 (3 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug trusty ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1279380 Title: [14.04] [Gnome-Settings-Daemon] unable to save default audio output device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1279380/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 534684] Re: Suspend Fails to Resume
** Changed in: gnome-power-manager (Ubuntu) Status: New => Incomplete -- Suspend Fails to Resume https://bugs.launchpad.net/bugs/534684 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 513654] Re: Blank screen on (otherwise successful) resume from suspend (when suspend was initiated by closing the lid)
** Changed in: gnome-power-manager (Ubuntu) Status: New => Incomplete -- Blank screen on (otherwise successful) resume from suspend (when suspend was initiated by closing the lid) https://bugs.launchpad.net/bugs/513654 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 534684] Re: Suspend Fails to Resume
I have noticed that sometimes if you switch to VT1 and back to VT7 the gdm login screen comes back. Can you try that? ie after you resume, switch to VT1 and back to VT7. -- Suspend Fails to Resume https://bugs.launchpad.net/bugs/534684 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 534684] Re: Suspend Fails to Resume
Also, please run apport-collect to collect more information. -- Suspend Fails to Resume https://bugs.launchpad.net/bugs/534684 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 513654] Re: Blank screen on (otherwise successful) resume from suspend (when suspend was initiated by closing the lid)
can you please try with the latest lucid kernel and report back here. Also, this time can you collect full system information. You can do that by doing apport-collect 513654. -- Blank screen on (otherwise successful) resume from suspend (when suspend was initiated by closing the lid) https://bugs.launchpad.net/bugs/513654 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
