[Desktop-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
@Gabriel Can you also check linux-image-generic-hwe-20.04 on focal ? it's 5.11 as well. linux-image-generic-hwe-20.04 5.11.0.27.29~20.04.11 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+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 1869641] [NEW] Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0
Public bug reported: Description:Ubuntu Focal Fossa (development branch) Release:20.04 ibus 1.5.22-2ubuntu1 Steps to reproduce 1. Upgrade to GNOME 3.36.0. 2. Restart Ubuntu 20.04 daily with Wayland What did you expect to happen The ibus daemon is launched. What happened The ibus daemon is not running. I can confirm I have an exact same issue in https://gitlab.gnome.org/GNOME/gnome-shell/issues/2341 when login with wayland selected. After applying this: https://github.com/ibus/ibus/commit/8ce25208c3f4adfd290a032c6aa739d2b7580eb1 patch locally I can confirm it fixed my issue. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: focal gnome-shell ibus wayland ** Tags added: focal gnome-shell ibus wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1869641 Title: Failed to launch ibus daemon in Xwayland + gnome-shell 3.36.0 Status in ibus package in Ubuntu: New Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ibus 1.5.22-2ubuntu1 Steps to reproduce 1. Upgrade to GNOME 3.36.0. 2. Restart Ubuntu 20.04 daily with Wayland What did you expect to happen The ibus daemon is launched. What happened The ibus daemon is not running. I can confirm I have an exact same issue in https://gitlab.gnome.org/GNOME/gnome-shell/issues/2341 when login with wayland selected. After applying this: https://github.com/ibus/ibus/commit/8ce25208c3f4adfd290a032c6aa739d2b7580eb1 patch locally I can confirm it fixed my issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869641/+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 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
I've verified trusty unity-control- center14.04.3+14.04.20140922-0ubuntu1.1 from trusty-proposed archive, verification-done. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1417034 Title: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in unity-control-center package in Ubuntu: Fix Released Status in unity-control-center source package in Trusty: Fix Committed Bug description: Trusty (and Utopic) SRU Request: [Impact] * Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Test Case] * System with glxinfo installed (in mesa-utils) will show glxinfo's result first for Details - Overview - Graphics info in Unity Control Center. * System without glxinfo will still parse Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Regression Potential] * Should be minimal, the info showed in glxinfo is more accurate. [Original Bug Info] In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. Private bugs were filed at: https://bugs.launchpad.net/bugs/1369859 https://bugs.launchpad.net/bugs/1415303 A merge proposal is submitted at https://code.launchpad.net/~timchen119/unity-control-center/unity- control-center.lp1417034/+merge/248220 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1417034/+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 1471708] Re: SRU: For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
@Alberto
It was originally a quick workaround for the possible race condition so
could you help to modify the code with what Iain had suggested? Totally
agree that making it asynchronous, adding more verbose log and finding
out the root cause are better ways to fix this issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1471708
Title:
SRU: For skylake system, u-s-d cause a black screen when resume from
S3 via Lid Close
Status in OEM Priority Project:
New
Status in OEM Priority Project trusty series:
New
Status in unity-settings-daemon package in Ubuntu:
In Progress
Bug description:
OEM LP private bug: https://bugs.launchpad.net/bugs/1466441
Title: Sometimes system turns a black screen when resume from S3 via
Lid Close
[Impact]
Sometimes system turns a black screen when resume from S3 via Lid Close
It only has cursor on screen but still can switch to tty1.
Failure rate ~ 1/5
[Test Case]
1. install Ubuntu 14.04.2 3.19+ kernel and boot to OS
2. Close the lid
3. Open the lid
4. check the display status
Expected results: System should resume to the log in screen when open
the lid
Actual results:
System sometimes fails to resume back to the log in screen but blackscreen
instead.
(Failure rate~ 1/5)
[Regression Potential]
Low. Killing touchscreen mapping after 3 seconds should not affect any other
input device.
Details:
unity-settings-deamon will call xinput --map-to-output 11 eDP1 at
background,
and it's being blocked so only cursor will show on screen.
1. Switch to tty1 when this happen
2. Login with user account on tty1.
3. Use DISPLAY=:0 xrandr on commandline you'll see it's being blocked.
Since xinput is being blocked for some unknown reason (in gdb it shows
polling on xcb_connect_to_fd() in XOpenDisplay() ),
a possible workaround is to set a timeout for xinput in u-s-d.
=== modified file 'plugins/xrandr/gsd-xrandr-manager.c'
--- plugins/xrandr/gsd-xrandr-manager.c 2014-06-05 11:56:15 +
+++ plugins/xrandr/gsd-xrandr-manager.c 2015-07-01 08:59:56 +
@@ -2199,7 +2199,7 @@
if (gnome_rr_output_info_is_active(output)) {
g_debug (Mapping touchscreen %d onto output %s,
device_id, name);
- sprintf (command, xinput --map-to-output %d %s,
+ sprintf (command, timeout 3s xinput --map-to-output %d %s,
device_id, name);
status = system (command);
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1471708/+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 1471708] [NEW] For skylake system, u-s-d cause a black screen when resume from S3 via Lid Close
Public bug reported:
OEM LP private bug: https://bugs.launchpad.net/bugs/1466441
Title: Sometimes system turns a black screen when resume from S3 via Lid
Close
Summary:
Sometimes system turns a black screen when resume from S3 via Lid Close
It only has cursor on screen but still can switch to tty1.
Failure rate ~ 1/5
Steps:
1. install Ubuntu 14.04.2 3.19+ kernel and boot to OS
2. Close the lid
3. Open the lid
4. check the display status
Expected results: System should resume to the log in screen when open
the lid
Actual results:
System sometimes fails to resume back to the log in screen but blackscreen
instead.
(Failure rate~ 1/5)
Details:
unity-settings-deamon will call xinput --map-to-output 11 eDP1 at background,
and it's being blocked so only cursor will show on screen.
1. Switch to tty1 when this happen
2. Login with user account on tty1.
3. Use DISPLAY=:0 xrandr on commandline you'll see it's being blocked.
Since xinput is being blocked for some unknown reason (in gdb it shows
polling on xcb_connect_to_fd() in XOpenDisplay() ),
a possible workaround is to set a timeout for xinput in u-s-d.
=== modified file 'plugins/xrandr/gsd-xrandr-manager.c'
--- plugins/xrandr/gsd-xrandr-manager.c 2014-06-05 11:56:15 +
+++ plugins/xrandr/gsd-xrandr-manager.c 2015-07-01 08:59:56 +
@@ -2199,7 +2199,7 @@
if (gnome_rr_output_info_is_active(output)) {
g_debug (Mapping touchscreen %d onto output %s,
device_id, name);
- sprintf (command, xinput --map-to-output %d %s,
+ sprintf (command, timeout 3s xinput --map-to-output %d %s,
device_id, name);
status = system (command);
}
** Affects: oem-priority
Importance: Critical
Status: New
** Affects: oem-priority/trusty
Importance: Critical
Status: New
** Affects: unity-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/trusty
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided = Critical
** Changed in: oem-priority/trusty
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1471708
Title:
For skylake system, u-s-d cause a black screen when resume from S3 via
Lid Close
Status in OEM Priority Project:
New
Status in OEM Priority Project trusty series:
New
Status in unity-settings-daemon package in Ubuntu:
New
Bug description:
OEM LP private bug: https://bugs.launchpad.net/bugs/1466441
Title: Sometimes system turns a black screen when resume from S3 via
Lid Close
Summary:
Sometimes system turns a black screen when resume from S3 via Lid Close
It only has cursor on screen but still can switch to tty1.
Failure rate ~ 1/5
Steps:
1. install Ubuntu 14.04.2 3.19+ kernel and boot to OS
2. Close the lid
3. Open the lid
4. check the display status
Expected results: System should resume to the log in screen when open
the lid
Actual results:
System sometimes fails to resume back to the log in screen but blackscreen
instead.
(Failure rate~ 1/5)
Details:
unity-settings-deamon will call xinput --map-to-output 11 eDP1 at
background,
and it's being blocked so only cursor will show on screen.
1. Switch to tty1 when this happen
2. Login with user account on tty1.
3. Use DISPLAY=:0 xrandr on commandline you'll see it's being blocked.
Since xinput is being blocked for some unknown reason (in gdb it shows
polling on xcb_connect_to_fd() in XOpenDisplay() ),
a possible workaround is to set a timeout for xinput in u-s-d.
=== modified file 'plugins/xrandr/gsd-xrandr-manager.c'
--- plugins/xrandr/gsd-xrandr-manager.c 2014-06-05 11:56:15 +
+++ plugins/xrandr/gsd-xrandr-manager.c 2015-07-01 08:59:56 +
@@ -2199,7 +2199,7 @@
if (gnome_rr_output_info_is_active(output)) {
g_debug (Mapping touchscreen %d onto output %s,
device_id, name);
- sprintf (command, xinput --map-to-output %d %s,
+ sprintf (command, timeout 3s xinput --map-to-output %d %s,
device_id, name);
status = system (command);
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1471708/+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 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Description changed: + Trusty (and Utopic) SRU Request: + + [Impact] + + * Set higher priority of glxinfo's result then Xorg's log for Details + - Overview - Graphics info in Unity Control Center. + + [Test Case] + + * System with glxinfo installed (in mesa-utils) will show glxinfo's + result first for Details - Overview - Graphics info in Unity + Control Center. + + * System without glxinfo will still parse Xorg's log for Details - + Overview - Graphics info in Unity Control Center. + + [Regression Potential] + + * Should be minimal, the info showed in glxinfo is more accurate. + + [Original Bug Info] + In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. Private bugs were filed at: https://bugs.launchpad.net/bugs/1369859 https://bugs.launchpad.net/bugs/1415303 A merge proposal is submitted at https://code.launchpad.net/~timchen119 /unity-control-center/unity-control-center.lp1417034/+merge/248220 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1417034 Title: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in unity-control-center package in Ubuntu: Fix Released Bug description: Trusty (and Utopic) SRU Request: [Impact] * Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Test Case] * System with glxinfo installed (in mesa-utils) will show glxinfo's result first for Details - Overview - Graphics info in Unity Control Center. * System without glxinfo will still parse Xorg's log for Details - Overview - Graphics info in Unity Control Center. [Regression Potential] * Should be minimal, the info showed in glxinfo is more accurate. [Original Bug Info] In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. Private bugs were filed at: https://bugs.launchpad.net/bugs/1369859 https://bugs.launchpad.net/bugs/1415303 A merge proposal is submitted at https://code.launchpad.net/~timchen119/unity-control-center/unity- control-center.lp1417034/+merge/248220 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1417034/+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 1417034] [NEW] Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
Public bug reported: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. A private bug is filed at: https://bugs.launchpad.net/bugs/1369859 A merge proposal is submitted. ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1417034 Title: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center. Status in unity-control-center package in Ubuntu: New Bug description: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. A private bug is filed at: https://bugs.launchpad.net/bugs/1369859 A merge proposal is submitted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1417034/+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 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Description changed: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. - A private bug is filed at: https://bugs.launchpad.net/bugs/1369859 + Private bugs were filed at: + https://bugs.launchpad.net/bugs/1369859 + https://bugs.launchpad.net/bugs/1415303 A merge proposal is submitted. ** Description changed: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. Private bugs were filed at: - https://bugs.launchpad.net/bugs/1369859 + https://bugs.launchpad.net/bugs/1369859 https://bugs.launchpad.net/bugs/1415303 - A merge proposal is submitted. + A merge proposal is submitted at https://code.launchpad.net/~timchen119 + /unity-control-center/unity-control-center.lp1417034/+merge/248220 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1417034 Title: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in unity-control-center package in Ubuntu: New Bug description: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. Private bugs were filed at: https://bugs.launchpad.net/bugs/1369859 https://bugs.launchpad.net/bugs/1415303 A merge proposal is submitted at https://code.launchpad.net/~timchen119/unity-control-center/unity- control-center.lp1417034/+merge/248220 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1417034/+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 1417034] Re: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center.
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority/trusty Importance: Undecided = High ** Changed in: oem-priority Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1417034 Title: Set higher priority of glxinfo's result then Xorg's log for Details - Overview - Graphics info in control center. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in unity-control-center package in Ubuntu: New Bug description: In some of OEM's AMD platforms, open System setting-Details-Graphics from control center, find the Graphics Driver show VESA: XX strings , not as accurate as what glxinfo -l | grep OpenGL renderer string shows. The VESA: string displayed in System Settings--Details-Graphics was because unity-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log, I've asked AMD and their reply is that the VESA BIOS message is traced by VBEInit (libvbe.so) , which is out of fglrx’s control. Curently this VESA:X string instead of the more accurate string from glxinfo was being shown in the panel. I think Use glxinfo's information (when available) first is more accurate. Private bugs were filed at: https://bugs.launchpad.net/bugs/1369859 https://bugs.launchpad.net/bugs/1415303 A merge proposal is submitted. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1417034/+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 1308515] Re: black screen when enabling rotation on a gpu screen
https://bugs.launchpad.net/bugs/1386620 this issue is fixed by Maarten Lankhorst (mlankhorst) and the option will be re-enabled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1308515 Title: black screen when enabling rotation on a gpu screen Status in HWE Next Project: Fix Released Status in OEM Priority Project: Fix Released Status in X.Org X server: New Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server-lts-saucy” package in Ubuntu: Invalid Status in “xorg-server-lts-saucy” source package in Precise: Fix Released Status in “xorg-server” source package in Saucy: Fix Released Status in “xorg-server” source package in Trusty: Fix Released Status in “xorg-server” source package in Vivid: Fix Released Status in “xorg-server-lts-saucy” source package in Vivid: Invalid Bug description: Running with the proprietary nvidia drivers in an optimus config works, but enabling reflection or rotation on the intel screen causes a black screen to appear. [Impact] * Causes a black screen if rotation or reflection is enabled. [Test Case] * Run xrandr --output SOMEOUTPUT --rotation left - Expected: Screen should rotate, or the call should fail. - Bad behavior: Succeeds, but causes a black screen. [Regression Potential] * The affected codepaths have reflection and rotation disabled for gpu screens. Another fix could be fixing reflection/rotation, but that will be more involved and likely require driver fixes. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1308515/+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 131964] Re: search for files.. entry in gnome-menu should launch tracker-search-tool
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/131964 Title: search for files.. entry in gnome-menu should launch tracker-search- tool Status in “gnome-panel” package in Ubuntu: Invalid Bug description: Binary package hint: gnome-panel With up to date Gutsy, tracker is installed by default. Yet the Search for Files.. entry on the places menu still launches gnome-search-tool. When you install Beagle, beagle-search takes over that menu-entry in the places menu. See also, the bug about that: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/38986 This wishlist-bug was fixed, and I think, considering the choice to install tracker by default, it is even more important that this behavior is duplicated for tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/131964/+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 131964] Re: search for files.. entry in gnome-menu should launch tracker-search-tool
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/131964 Title: search for files.. entry in gnome-menu should launch tracker-search- tool Status in “gnome-panel” package in Ubuntu: Invalid Bug description: Binary package hint: gnome-panel With up to date Gutsy, tracker is installed by default. Yet the Search for Files.. entry on the places menu still launches gnome-search-tool. When you install Beagle, beagle-search takes over that menu-entry in the places menu. See also, the bug about that: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/38986 This wishlist-bug was fixed, and I think, considering the choice to install tracker by default, it is even more important that this behavior is duplicated for tracker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/131964/+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 1035431] Re: bluetooh-wizard failed to connect to a keyboard(logitech)
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1035431 Title: bluetooh-wizard failed to connect to a keyboard(logitech) Status in “bluez” package in Ubuntu: New Status in “gnome-bluetooth” package in Ubuntu: Confirmed Bug description: When I try to connect my bluetooth keyboard using bluetooth-wizard, it ever fails: ** (bluetooth-wizard:11367): WARNING **: Setting up 'Logitech K760' failed: Authentication Failed This keyboard works fine with another computer under ubuntu 11.04. This keyboard works fine with this computer and Windows 7 (arghhh). This computer ubuntu 12.04 works fine with my bluetooth mouse. I can attach manually this keyboard to this computer using : sudo hidd --search My computer is a Samsung 305U1A My bluetooth interface is : Bus 003 Device 002: ID 0a5c:219c Broadcom Corp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1035431/+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 1310518] [NEW] Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
Public bug reported: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen, Installed 14.04, still have same issue. Quickly tapped dash home more than three times by touch screen.Found touch screen and touchpad lost click function. Note: 1.When this issue occured, cursor still can be moved by touch screen/touchpad. 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. Steps to Reproduce: 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. 2.Quickly tapped dash home more than three times by touch screen. 3.Found touch screen and touchpad lost click function. This bug is reported from private OEM project, also check https://launchpad.net/bugs/1297067 == using xinput --query-state can actually see the button press event ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ syntp id=6 [slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11 [slave pointer (2)] #xinput --query-state 11 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=398 valuator[1]=1652 valuator[2]=5 valuator[3]=3 valuator[4]=0 valuator[5]=399 valuator[6]=1653 #xinput --query-state 6 2 classes : ButtonClass button[1]=down button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up button[8]=up ValuatorClass Mode=Relative Proximity=In valuator[0]=1 valuator[1]=394 touchpad's button and touchpanel's valuator[2] and valuator[3] will changed after we press the button (or monitor) Also I found press super on keyboard will recover the touchscreen/touchpad loss. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 21 16:50:04 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-daan2-precise-amd64-20140416-1 InstallationMedia: Ubuntu 12.04 Precise - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52 MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen Status in “unity” package in Ubuntu: New Bug description: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen, Installed 14.04, still have same issue. Quickly tapped dash home more than three times by touch screen.Found touch screen and touchpad lost click function. Note: 1.When this issue occured, cursor still can be moved by touch screen/touchpad. 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. Steps to Reproduce: 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. 2.Quickly tapped dash home more than three times by touch screen. 3.Found touch screen and touchpad lost click function. This bug is reported from private OEM project, also check https://launchpad.net/bugs/1297067 == using xinput --query-state can actually see the button press event ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ syntp id=6[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)] #xinput --query-state 11 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=398 valuator[1]=1652 valuator[2]=5 valuator[3]=3 valuator[4]=0 valuator[5]=399 valuator[6]=1653 #xinput --query-state 6 2 classes : ButtonClass button[1]=down button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up button[8]=up ValuatorClass Mode=Relative Proximity=In
[Desktop-packages] [Bug 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = High ** Changed in: oem-priority/trusty Importance: Undecided = High ** Changed in: oem-priority Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in OEM Priority Project trusty series: New Status in “unity” package in Ubuntu: New Bug description: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen, Installed 14.04, still have same issue. Quickly tapped dash home more than three times by touch screen.Found touch screen and touchpad lost click function. Note: 1.When this issue occured, cursor still can be moved by touch screen/touchpad. 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. Steps to Reproduce: 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. 2.Quickly tapped dash home more than three times by touch screen. 3.Found touch screen and touchpad lost click function. This bug is reported from private OEM project, also check https://launchpad.net/bugs/1297067 == using xinput --query-state can actually see the button press event ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ syntp id=6[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)] #xinput --query-state 11 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=398 valuator[1]=1652 valuator[2]=5 valuator[3]=3 valuator[4]=0 valuator[5]=399 valuator[6]=1653 #xinput --query-state 6 2 classes : ButtonClass button[1]=down button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up button[8]=up ValuatorClass Mode=Relative Proximity=In valuator[0]=1 valuator[1]=394 touchpad's button and touchpanel's valuator[2] and valuator[3] will changed after we press the button (or monitor) Also I found press super on keyboard will recover the touchscreen/touchpad loss. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 21 16:50:04 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-daan2-precise-amd64-20140416-1 InstallationMedia: Ubuntu 12.04 Precise - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52 MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1310518/+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 1210077] Re: Screen freeze and garbled after resume from suspend
it also can reproduce in Unity 2D + 331.20 driver + nvidia-prime on 12.04 + Saucy LTS HWE stack. (3.11 kernel) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1210077 Title: Screen freeze and garbled after resume from suspend Status in “nvidia-prime” package in Ubuntu: Confirmed Bug description: Perform regular suspend, either from system menu or close laptop lid, when system resuming from suspend, it will freeze. Switch to VT and back to X can solve freeze issue, but the screen are gabled and some character rendering are strange, however whole system can perform usual task. found affected graphics: gf108m gf117m gk107glm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1210077/+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 1244065] Re: Add more options to the power settings menu
works fine to me with gnome-control-center/1:3.4.2-0ubuntu0.13.1 on Precise. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1244065 Title: Add more options to the power settings menu Status in OEM Priority Project: Confirmed Status in OEM Priority Project precise series: Fix Committed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Precise: Fix Committed Bug description: [Impact] * Currently, the power option system sleep settings menu in Ubuntu precise has the following options: 5 minutes, 10 minutes, 30 minutes, 1 hour and don't suspend. The plan is to add an option for 20 minutes and 2 hours options to give the user morefine-grained controls. This request came from OEM projects, requested additional options to be add in the power option system sleep settings menu. [Test Case] * Under the session-indicator choose System Settings -- Power * For the Susend when inactive for question, this patch will add two 20 minutes and 2 hours items * The strings have been already been uploaded and translators warned [Regression Potential] * This patch will not change the user's originall settings, only add additional options when user want to choose different suspend time. * This patch is already tested on some OEM projects. * The patch now submitted in Trusty (14.04) bzr devel branch. [Other Info] https://launchpad.net/bugs/1238727 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1244065/+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 1055874] Re: Automatic sleep settings are not followed precisely
** Description changed: + [Impact] + + * User can choose the suspend time and blank time in the gnome control + center (system settings). + +Also, there's a gsetting called org.gnome.settings-daemon.plugins.power idle-dim-time which default in Ubuntu is 30 secs and will dim the screen after idle for 30 secs. + (which the value user can not adjust in the default UI but only using the CLI) + +This two categories of values (dim time/suspendblank time) should + not be related at all, however,the current Ubuntu Precise (12.04)'s + gnome settings daemon (3.4.2) it actually suspend or blank the screen on + user set time plus the dim time, which added additional 30 secs by + default. + +In some OEM projects, in order to fulfill the OEM requests for Energy + Star standard, the dim time is set to 5 minutes default (instead of 30 + secs), and this make the suspend time and screen blank time very + inaccurate, because user will have additional 5 minutes to wait before + the screen blank or system suspend. (Inactive time to suspend is about 5 + minutes more than setting.) + + * The User do not need modify anything for this patch. + + [Test Case] + + * Please use Ubuntu Precise (12.04) to test, this issue is already fixed + in Ubuntu Raring (13.04) + + * Set idle-dim-time to 300 first (5 minutes), it's much easier to find out this issue. + (the default is 30 secs and it's somehow not as easy to observe, but the result should be same.) + Command: + #gsettings set org.gnome.settings-daemon.plugins.power idle-dim-time 300 + + *In settings: + Turn screen off: 10 minutes + Suspend: 10 minutes on battery power, 30 minutes when plugged in. + + Actual: + On battery: Screen turned off after 10 minutes, suspend after about 5 more minutes(15 minutes total). + When plugged in: Screen turned off after 10 minutes, suspend after about 25 more minutes(35 minutes total). + + Steps: + 1. Check power settings and brightness settings + 2. Leave the system inactive + + Expected results: Inactive time to suspend is same as setting + + Actual results: Inactive time to suspend is about 5 minutes more than + setting + + [Regression Potential] + + * This do not need to modify any user settings. + + * The impact should be minimal for an inaccurate timing of + suspend/blanking. + + [Other Info] + + Original bug description: + When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Sep 25 09:43:50 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to precise on 2012-04-29 (148 days ago) ** Description changed: [Impact] - * User can choose the suspend time and blank time in the gnome control + * User can choose the suspend time and blank time in the gnome control center (system settings). -Also, there's a gsetting called org.gnome.settings-daemon.plugins.power idle-dim-time which default in Ubuntu is 30 secs and will dim the screen after idle for 30 secs. + Also, there's a gsetting called org.gnome.settings-daemon.plugins.power idle-dim-time which default in Ubuntu is 30 secs and will dim the screen after idle for 30 secs. (which the value user can not adjust in the default UI but only using the CLI) -This two categories of values (dim time/suspendblank time) should + This two categories of values (dim time/suspendblank time) should not be related at all, however,the current Ubuntu Precise (12.04)'s gnome settings daemon (3.4.2) it actually suspend or blank the screen on user set time plus the dim time, which added additional 30 secs by default. -In some OEM projects, in order to fulfill the OEM requests for Energy + In some OEM projects, in order to fulfill the OEM requests for Energy Star standard, the dim time is set to 5 minutes default
[Desktop-packages] [Bug 1055874] Re: Automatic sleep settings are not followed precisely
** Description changed: [Impact] - * User can choose the suspend time and blank time in the gnome control - center (system settings). + According to the current design in Ubuntu Precise, users can choose the + suspend time and blank time in the gnome control center (system + settings). However, there's another gsetting called org.gnome.settings- + daemon.plugins.power idle-dim-time which controls the screen dim time. + The default value of idle-dim-time in Ubuntu is 30 secs and this makes + the screen dim after idle for 30 secs. This part (idle-dim-time) is not + accessible to users in the default UI but can only be accessed by using + the CLI. - Also, there's a gsetting called org.gnome.settings-daemon.plugins.power idle-dim-time which default in Ubuntu is 30 secs and will dim the screen after idle for 30 secs. - (which the value user can not adjust in the default UI but only using the CLI) - - This two categories of values (dim time/suspendblank time) should - not be related at all, however,the current Ubuntu Precise (12.04)'s +This two categories of values (dim time/suspendblank time) should + not be related at all, however, the current Ubuntu Precise (12.04)'s gnome settings daemon (3.4.2) it actually suspend or blank the screen on user set time plus the dim time, which added additional 30 secs by - default. + default. Since dim time is not accessible by users in default UI, this + confusing users why extra 30 secs is added to the total time on top of + the selected suspend/blank time. - In some OEM projects, in order to fulfill the OEM requests for Energy +In some OEM projects, in order to fulfill the OEM requests for Energy Star standard, the dim time is set to 5 minutes default (instead of 30 secs), and this make the suspend time and screen blank time very inaccurate, because user will have additional 5 minutes to wait before the screen blank or system suspend. (Inactive time to suspend is about 5 minutes more than setting.) * User do not need modify anything for this patch. [Test Case] * Please use Ubuntu Precise (12.04) to test, this issue is already fixed in Ubuntu Raring (13.04) * Set idle-dim-time to 300 first (5 minutes), it's much easier to find out this issue. (the default is 30 secs and it's somehow not as easy to observe, but the result should be same.) Command: #gsettings set org.gnome.settings-daemon.plugins.power idle-dim-time 300 *In settings: Turn screen off: 10 minutes Suspend: 10 minutes on battery power, 30 minutes when plugged in. Actual: On battery: Screen turned off after 10 minutes, suspend after about 5 more minutes(15 minutes total). When plugged in: Screen turned off after 10 minutes, suspend after about 25 more minutes(35 minutes total). Steps: 1. Check power settings and brightness settings 2. Leave the system inactive Expected results: Inactive time to suspend is same as setting Actual results: Inactive time to suspend is about 5 minutes more than setting [Regression Potential] * This do not need to modify any user settings. * The impact should be minimal for an inaccurate timing of suspend/blanking. [Other Info] Original bug description: When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Sep 25 09:43:50 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to precise on 2012-04-29 (148 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1055874 Title: Automatic sleep settings are not followed precisely Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project:
[Desktop-packages] [Bug 1244065] Re: Add more options to the power settings menu
** Description changed: - Some Canonical OEM partners have requested additional options be added - to the power option system sleep settings menu. + [Impact] + + * Currently, the power option system sleep settings menu in Ubuntu precise has the following options: +5 minutes, 10 minutes, 30 minutes, 1 hour and don't suspend. + +The plan is to add an option for 20 minutes and 2 hours options to + give the user morefine-grained controls. + + This request came from OEM projects, requested additional options to be + add in the power option system sleep settings menu. + + [Test Case] + + * Under the session-indicator choose System Settings +-- Power + + * For the Susend when inactive for question, +this patch will add two 20 minutes and 2 hours items + + * The strings in this patch is being translated automatically. + + [Regression Potential] + + * This patch will not change the user's originall settings, only add additional options when user want to choose different suspend time. + * This patch is already tested on some OEM projects. + * The patch now submitted in Trusty (14.04) bzr devel branch. + + [Other Info] https://launchpad.net/bugs/1238727 - - Currently, the power option system sleep settings menu has the following options: - 5 minutes, 10 minutes, 30 minutes, 1 hour and don't suspend. - - The plan is to add an option for 20 minutes and 2 hours options to give - the user more fine-grained controls. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1244065 Title: Add more options to the power settings menu Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “gnome-control-center” package in Ubuntu: New Bug description: [Impact] * Currently, the power option system sleep settings menu in Ubuntu precise has the following options: 5 minutes, 10 minutes, 30 minutes, 1 hour and don't suspend. The plan is to add an option for 20 minutes and 2 hours options to give the user morefine-grained controls. This request came from OEM projects, requested additional options to be add in the power option system sleep settings menu. [Test Case] * Under the session-indicator choose System Settings -- Power * For the Susend when inactive for question, this patch will add two 20 minutes and 2 hours items * The strings in this patch is being translated automatically. [Regression Potential] * This patch will not change the user's originall settings, only add additional options when user want to choose different suspend time. * This patch is already tested on some OEM projects. * The patch now submitted in Trusty (14.04) bzr devel branch. [Other Info] https://launchpad.net/bugs/1238727 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1244065/+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 1244065] [NEW] Add more options to the power settings menu
Public bug reported: Some Canonical OEM partners have requested additional options be added to the power option system sleep settings menu. https://launchpad.net/bugs/1238727 Currently, the power option system sleep settings menu has the following options: 5 minutes, 10 minutes, 30 minutes, 1 hour and don't suspend. The plan is to add an option for 20 minutes and 2 hours options to give the user more fine-grained controls. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1244065 Title: Add more options to the power settings menu Status in “gnome-control-center” package in Ubuntu: New Bug description: Some Canonical OEM partners have requested additional options be added to the power option system sleep settings menu. https://launchpad.net/bugs/1238727 Currently, the power option system sleep settings menu has the following options: 5 minutes, 10 minutes, 30 minutes, 1 hour and don't suspend. The plan is to add an option for 20 minutes and 2 hours options to give the user more fine-grained controls. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244065/+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 1244065] Re: Add more options to the power settings menu
** Patch added: oem-power-suspend-options.patch https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244065/+attachment/3889368/+files/oem-power-suspend-options.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1244065 Title: Add more options to the power settings menu Status in “gnome-control-center” package in Ubuntu: New Bug description: Some Canonical OEM partners have requested additional options be added to the power option system sleep settings menu. https://launchpad.net/bugs/1238727 Currently, the power option system sleep settings menu has the following options: 5 minutes, 10 minutes, 30 minutes, 1 hour and don't suspend. The plan is to add an option for 20 minutes and 2 hours options to give the user more fine-grained controls. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244065/+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 1244065] Re: Add more options to the power settings menu
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1244065 Title: Add more options to the power settings menu Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “gnome-control-center” package in Ubuntu: New Bug description: Some Canonical OEM partners have requested additional options be added to the power option system sleep settings menu. https://launchpad.net/bugs/1238727 Currently, the power option system sleep settings menu has the following options: 5 minutes, 10 minutes, 30 minutes, 1 hour and don't suspend. The plan is to add an option for 20 minutes and 2 hours options to give the user more fine-grained controls. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1244065/+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 951000] Re: disable guest session screen lock using gsettings
And also set X-GNOME-Autostart-Phase=Initialization so the menu will not have the entry. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/951000 Title: disable guest session screen lock using gsettings Status in OEM Priority Project: New Status in “lightdm” package in Ubuntu: Triaged Bug description: bug # 275768 seems to be back in precise. My guest session is locking, when there is no password to unlock. I switched to the guest session from my admin account. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/951000/+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 951000] Re: disable guest session screen lock using gsettings
Since gconf is deprecated, could we just modify /usr/sbin/guest-account , add an autostart script in the guest $HOME/.config/autostart/ and let gsettings set the correct default value for disable-lock-screen? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/951000 Title: disable guest session screen lock using gsettings Status in OEM Priority Project: New Status in “lightdm” package in Ubuntu: Triaged Bug description: bug # 275768 seems to be back in precise. My guest session is locking, when there is no password to unlock. I switched to the guest session from my admin account. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/951000/+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 1080514] Re: Click-and-drag in eye of gnome crashes X
check with fglrx 13.3 beta didn't fix the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1080514 Title: Click-and-drag in eye of gnome crashes X Status in HWE Next Project: New Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: If I open any image with eog (I tried several different .png and .svg files), then click and drag with the left mouse button inside the window, X immediately crashes and I get taken back to the login screen. If no image file is open, nothing happens. The behaviour is the same in Unity and Xfce. I'm running 64-bit Ubuntu 12.04, fully updated, on a Dell Inspiron 15R 5520 laptop with an AMD Radeon HD 7600M graphics card and the official 64-bit AMD driver (not sure how to tell which version - it was the latest a couple of months ago anyway). xorg's version is 1:7.6+12ubuntu1, and eog's is 3.4.2-0ubuntu1.1. If I redirect the output from eog to a file, I get: (eog:22355): Gdk-WARNING **: eog: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. /var/log/Xorg.0.log.old contains the following backtrace: [ 37534.034] (II) fglrx(0): EDID vendor LGD, prod id 826 [ 37534.034] (II) fglrx(0): Printing DDC gathered Modelines: [ 37534.034] (II) fglrx(0): Modeline 1366x768x0.0 76.50 1366 1402 1450 1546 768 771 776 824 -hsync -vsync (49.5 kHz) [ 37534.034] (II) fglrx(0): Modeline 1366x768x0.0 51.00 1366 1402 1450 1564 768 771 776 814 -hsync -vsync (32.6 kHz) [ 37534.113] (II) fglrx(0): EDID vendor LGD, prod id 826 [ 37534.113] (II) fglrx(0): Printing DDC gathered Modelines: [ 37534.113] (II) fglrx(0): Modeline 1366x768x0.0 76.50 1366 1402 1450 1546 768 771 776 824 -hsync -vsync (49.5 kHz) [ 37534.113] (II) fglrx(0): Modeline 1366x768x0.0 51.00 1366 1402 1450 1564 768 771 776 814 -hsync -vsync (32.6 kHz) [ 37536.071] (II) XKB: reuse xkmfile /var/lib/xkb/server-4E634B280B0E5C069EA80E39EF9080F0A8FC0600.xkm [ 37554.682] (II) fglrx(0): EDID vendor LGD, prod id 826 [ 37554.682] (II) fglrx(0): Printing DDC gathered Modelines: [ 37554.682] (II) fglrx(0): Modeline 1366x768x0.0 76.50 1366 1402 1450 1546 768 771 776 824 -hsync -vsync (49.5 kHz) [ 37554.682] (II) fglrx(0): Modeline 1366x768x0.0 51.00 1366 1402 1450 1564 768 771 776 814 -hsync -vsync (32.6 kHz) [ 41235.982] (II) fglrx(0): EDID vendor LGD, prod id 826 [ 41235.982] (II) fglrx(0): Printing DDC gathered Modelines: [ 41235.982] (II) fglrx(0): Modeline 1366x768x0.0 76.50 1366 1402 1450 1546 768 771 776 824 -hsync -vsync (49.5 kHz) [ 41235.982] (II) fglrx(0): Modeline 1366x768x0.0 51.00 1366 1402 1450 1564 768 771 776 814 -hsync -vsync (32.6 kHz) [ 49260.131] Backtrace: [ 49260.131] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f96c3ba2876] [ 49260.131] 1: /usr/bin/X (0x7f96c3a1a000+0x18c71a) [0x7f96c3ba671a] [ 49260.131] 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f96c2d4+0xfcb0) [0x7f96c2d4fcb0] [ 49260.131] 3: /usr/bin/X (miResolveColor+0x3) [0x7f96c3b7fda3] [ 49260.131] 4: /usr/bin/X (FakeAllocColor+0x62) [0x7f96c3a5ab72] [ 49260.131] 5: /usr/bin/X (0x7f96c3a1a000+0x1779d8) [0x7f96c3b919d8] [ 49260.131] 6: /usr/bin/X (0x7f96c3a1a000+0x1797c1) [0x7f96c3b937c1] [ 49260.131] 7: /usr/bin/X (miPointerUpdateSprite+0x29d) [0x7f96c3b8d93d] [ 49260.131] 8: /usr/bin/X (0x7f96c3a1a000+0x173c2d) [0x7f96c3b8dc2d] [ 49260.131] 9: /usr/bin/X (0x7f96c3a1a000+0xdb9f9) [0x7f96c3af59f9] [ 49260.131] 10: /usr/bin/X (0x7f96c3a1a000+0x1119ca) [0x7f96c3b2b9ca] [ 49260.131] 11: /usr/bin/X (0x7f96c3a1a000+0x560a9) [0x7f96c3a700a9] [ 49260.131] 12: /usr/bin/X (0x7f96c3a1a000+0x5e7a7) [0x7f96c3a787a7] [ 49260.131] 13: /usr/bin/X (0x7f96c3a1a000+0x58000) [0x7f96c3a72000] [ 49260.131] 14: /usr/bin/X (0x7f96c3a1a000+0x126caa) [0x7f96c3b40caa] [ 49260.132] 15: /usr/bin/X (0x7f96c3a1a000+0x4e8a1) [0x7f96c3a688a1] [ 49260.132] 16: /usr/bin/X (0x7f96c3a1a000+0x3d7ba) [0x7f96c3a577ba] [ 49260.132] 17: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f96c1bd176d] [ 49260.132] 18: /usr/bin/X (0x7f96c3a1a000+0x3daad) [0x7f96c3a57aad] [ 49260.132] Segmentation fault at address 0x7f86c55810e6 [ 49260.132] Caught signal 11 (Segmentation fault). Server aborting [ 49260.132] Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 49260.132] Please also check the log file at /var/log/Xorg.0.log for additional information. [ 49260.132] [ 49260.177] (II) evdev: Power Button: Close [ 49260.177] (II) UnloadModule: evdev [ 49260.177] (II) Unloading evdev [ 49260.178] (II) evdev: Video Bus: Close [ 49260.178] (II) UnloadModule: evdev [ 49260.178] (II) Unloading evdev [ 49260.181] (II) evdev: Power Button: Close [ 49260.181] (II) UnloadModule: evdev [ 49260.181] (II) Unloading evdev
[Desktop-packages] [Bug 1134028] Re: [Dell Vostro 3560, Inspiron 5520] fglrx does not provide glx for Radeon HD 7600M Series
** Tags added: 201210-11863 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1134028 Title: [Dell Vostro 3560, Inspiron 5520] fglrx does not provide glx for Radeon HD 7600M Series Status in “fglrx-installer” package in Ubuntu: New Bug description: cid:201202-10402, 201201-10378 There are no glx support with fglrx_experimental_9 for Advanced Micro Devices [AMD] nee ATI Thames XT/GL [Radeon HD 7600M Series] [1002:6840]. Checking unity compatibility by following command: $ /usr/lib/nux/unity_support_test -c -p X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 Pacakages that installed by jockey: ii fglrx-amdcccle-experimental-92:9.010-0ubuntu0.3 Catalyst Control Center for the AMD graphics accelerators ii fglrx-experimental-9 2:9.010-0ubuntu0.3 Experimental AMD binary Xorg driver and kernel module rc fglrx-updates2:9.000-0ubuntu0.3 Video driver for the AMD graphics accelerators However it can be fix by using latest stable driver[0] from amd website[1], following this guide: https://help.ubuntu.com/community/BinaryDriverHowto/ATI GLX will be loaded without error. [0]http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-13.1-linux-x86.x86_64.zip [1]http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Wed Feb 27 01:37:19 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx-experimental-9, 9.010, 3.5.0-23-generic, x86_64: installed GraphicsCard: Intel Corporation Ivy Bridge Graphics Controller [8086:0166] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:056e] Advanced Micro Devices [AMD] nee ATI Thames XT/GL [Radeon HD 7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:056e] InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) JockeyStatus: xorg:fglrx_experimental_9 - ATI/AMD proprietary FGLRX graphics driver (**experimental** beta) (Proprietary, Enabled, Not in use) xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: Dell Inc. Vostro 3560 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=644b13de-02c4-40f5-afa6-3b8cbcf262c9 ro quiet splash initcall_debug vt.handoff=7 SourcePackage: fglrx-installer UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X44 dmi.board.name: 0C05GV dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X44 dmi.modalias: dmi:bvnDellInc.:bvrX44:bd08/03/2012:svnDellInc.:pnVostro3560:pvrX44:rvnDellInc.:rn0C05GV:rvrX01:cvnDellInc.:ct8:cvrX44: dmi.product.name: Vostro 3560 dmi.product.version: X44 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Desktop-packages] [Bug 1076840] Re: [CS4213, Dell Inspiron 3420] Internal speaker does not show up in Sound settings
** Tags added: 201202-10593 taipei-lab -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1076840 Title: [CS4213, Dell Inspiron 3420] Internal speaker does not show up in Sound settings Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Released Status in OEM Priority Project quantal series: Fix Released Status in “linux” package in Ubuntu: Fix Released Status in “pulseaudio” package in Ubuntu: Invalid Status in “linux” source package in Precise: Won't Fix Status in “pulseaudio” source package in Precise: Fix Released Status in “linux” source package in Quantal: Fix Released Status in “pulseaudio” source package in Quantal: Invalid Status in “linux” source package in Raring: Fix Released Status in “pulseaudio” source package in Raring: Invalid Bug description: [SRU Justification] Impact: The internal speaker does not show up in the sound settings, which causes this to block certification. Test case: With the affected machines, open sound settings without headphones plugged in. If the Internal Speaker does not show up, the bug is present. Regression risk (Quantal): Cirrus is a rare codec, mostly used in macbooks. Upstream has reviewed and blessed the patch. Regression risk (Precise): These machines are quirked individually and won't affect other machines (and even if they did, the worst thing that could happen would be a speaker output that shouldn't be there). This is due to the Internal Speaker Phantom Jack kctrl not being created. the same issue occurs in the following sysyems: cid:201202-10591, Dell Inspiron 3420 (PCI SSID: 1028:0553) cid:201202-10590, Dell Inspiron 3420 (PCI SSID: 1028:0553) cid:201202-10557, Dell Inspiron 3520 (PCI SSID: 1028:0555) cid:201202-10593, Dell Vostro 2420 (PCI SSID: 1028:0556) cid:201202-10558, Dell Vostro 2520 (PCI SSID: 1028:0558) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1605 F pulseaudio /dev/snd/pcmC0D0c: ubuntu 1605 F...m pulseaudio Date: Thu Nov 8 21:35:36 2012 HibernationDevice: RESUME=UUID=47ccd585-7def-4658-a811-0740ccc8d313 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Inspiron 3420 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=414de9d1-6779-4d25-94ee-402d7d076b1e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/15/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1076840/+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 1086720] Re: After installed of fglrx or fglrx-update, can't boot to desktop
** Tags added: taipei-lab -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1086720 Title: After installed of fglrx or fglrx-update, can't boot to desktop Status in “fglrx-installer” package in Ubuntu: New Bug description: System: HP Heineken 10 ( 201206-11396) After installed of fglrx and fglrx, can't boot to desktop, only the background and mouse pointer are shown. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1742 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 15.589071] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Wed Dec 5 04:26:34 2012 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard a654 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=58211ec4-f36a-4614-b688-d509d7109a6f ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.name: 2AEE dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/24/2012:svnHewlett-Packard:pna654:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr: dmi.product.name: a654 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1086720/+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 838659] Re: [Inspiron M4110] can't output to external monitor via VGA
** Changed in: fglrx-installer (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/838659 Title: [Inspiron M4110] can't output to external monitor via VGA Status in “fglrx-installer” package in Ubuntu: Fix Released Bug description: Can't output to external monitor via VGA, however HDMI output is ok. Error message is: can't output to VGA, error message: Could not switch the monitor configuration, requested position/size for CRTC 148 is outside the allowed limit: position=(1366,0),size=(1280,768), maximum=(1600,1600) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-11-generic 2.6.38-11.48 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 1: Generic_1 [HD-Audio Generic], device 0: ALC269VB Analog [ALC269VB Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1442 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0x90244000 irq 50' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 4 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'Generic_1'/'HD-Audio Generic at 0x9024 irq 16' Mixer name : 'Realtek ALC269VB' Components : 'HDA:10ec0269,102804c2,00100100' Controls : 13 Simple ctrls : 8 Date: Thu Sep 1 04:43:52 2011 HibernationDevice: RESUME=UUID=f2130dd7-adb2-437d-ae53-54a47faf510d InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MachineType: Dell Inc. Dell System Inspiron M4110 ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=e821c321-3de8-4e44-bf40-f2950d2435f2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-11-generic N/A linux-backports-modules-2.6.38-11-generic N/A linux-firmware 1.52 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: X14 dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Q4E3A1 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrX14:bd05/30/2011:svnDellInc.:pnDellSystemInspironM4110:pvr:rvnDellInc.:rnQ4E3A1:rvrA11:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System Inspiron M4110 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/838659/+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 1086720] Re: After installed of fglrx or fglrx-update, can't boot to desktop
** Tags removed: cid201206-11396 cid201206-11418 ** Tags added: 201206-11396 201206-11418 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1086720 Title: After installed of fglrx or fglrx-update, can't boot to desktop Status in “fglrx-installer” package in Ubuntu: New Bug description: System: HP Heineken 10 ( 201206-11396) After installed of fglrx and fglrx, can't boot to desktop, only the background and mouse pointer are shown. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1742 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 15.589071] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Wed Dec 5 04:26:34 2012 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard a654 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=58211ec4-f36a-4614-b688-d509d7109a6f ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.name: 2AEE dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/24/2012:svnHewlett-Packard:pna654:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr: dmi.product.name: a654 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1086720/+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 1037483] Re: [SRU] Needs NVIDIA driver 304.43 [HW-Certification blocker]
The system, Dell Precision M4700, still has the suspend problem with installed ii nvidia-current-updates 304.64-0ubuntu0.1 NVIDIA binary Xorg driver, kernel module and VDPAU library ii nvidia-settings-updates304.43-0ubuntu0.2 Tool of configuring the NVIDIA graphics driver After the installation, the screen resolution is still the minimal. The driver seems failed to install. I see there's interesting log when installing as below, not sure if it related to this bug. update-initramfs: deferring update (trigger activated)^M update-initramfs: Generating /boot/initrd.img-3.2.0-35-virtual^M INFO:Enable nvidia-current-updates^M DEBUG:Parsing /usr/share/nvidia-common/quirks/dell_latitude^M DEBUG:Parsing /usr/share/nvidia-common/quirks/put_your_quirks_here^M DEBUG:Parsing /usr/share/nvidia-common/quirks/lenovo_thinkpad^M DEBUG:Processing quirk Latitude E6530^M DEBUG:Failure to match Precision M4700 with Latitude E6530^M DEBUG:Quirk doesn't match^M DEBUG:Processing quirk ThinkPad T420s^M DEBUG:Failure to match Dell Inc. with LENOVO^M DEBUG:Quirk doesn't match^M Loading new nvidia-current-updates-304.64 DKMS files...^M First Installation: checking all kernels...^M Building only for 3.2.0-35-virtual^M Building for architecture x86_64^M Module build for the currently running kernel was skipped since the^M kernel source for this kernel does not seem to be installed.^M Setting up nvidia-settings-updates (304.43-0ubuntu0.2) ...^M ** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-updates/+bug/1037483/+attachment/3491887/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1037483 Title: [SRU] Needs NVIDIA driver 304.43 [HW-Certification blocker] Status in “nvidia-graphics-drivers” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-updates” package in Ubuntu: Fix Released Status in “nvidia-settings” package in Ubuntu: Fix Released Status in “nvidia-settings-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers” source package in Precise: In Progress Status in “nvidia-graphics-drivers-updates” source package in Precise: Fix Released Status in “nvidia-settings” source package in Precise: In Progress Status in “nvidia-settings-updates” source package in Precise: Fix Released Status in “nvidia-graphics-drivers” source package in Quantal: Fix Released Status in “nvidia-graphics-drivers-updates” source package in Quantal: Fix Released Status in “nvidia-settings” source package in Quantal: Fix Released Status in “nvidia-settings-updates” source package in Quantal: Fix Released Bug description: The current nvidia driver in Precise does not work for some newer nvidia graphics cards. Without the driver, system will fail to resume from suspend, which is a certification blocker, such as bug 1036617. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1037483/+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 946232] Re: [Meta-bug] Missing speaker and/or internal mic port
Confirmed bug is fixed on my Vostro 2420. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/946232 Title: [Meta-bug] Missing speaker and/or internal mic port Status in “pulseaudio” package in Ubuntu: Fix Released Status in “pulseaudio” source package in Precise: Fix Committed Bug description: Read me first If you're suffering from one of the following problems: 1) In the sound settings dialog, when you plug your headphones into the designated 3.5 mm jack, there is a Headphones device correctly shown, but when you unplug it, there is no Speaker device shown, even though you have internal speakers on your computer. 2) In the sound settings dialog, when you plug your external microphone into the designated 3.5 mm jack, there is a Microphone (or similar) device correctly shown, but when you unplug it, there is no Internal Mic device shown, even though you have an internal mic on your computer. If so, please try the workaround in comment #32. IF AND ONLY IF that is working for you, please attach alsa info (see https://wiki.ubuntu.com/Audio/AlsaInfo ) to this bug, together with the name of your machine (e g Dell Latitude D620). I'll try to include it in a list of devices that we have to manually enable and release it as an update to 12.04. Thanks! - and sorry for causing the bug in the first place :-/ // David Henningsson The following machines are known to be affected (no more alsa-info needed) : # Acer AOA150 # Acer Aspire 4810TZ # Acer Aspire 1810TZ # Packard bell dot m/a # Acer AOD260, AO532h # Dell MXC051 # Dell Inspiron 6400 and E1505 # Dell Latitude D620 # Dell Latitude D820 # Dell Latitude D520 # Dell Latitude D420 # Dell Inspiron 1525 # Dell Inspiron 1011 # Dell XPS 14 (L401X) # Dell XPS 15 (L501X) # Dell XPS 15 (L502X) # Asus 904HA (1000H) # Asus T101MT # Sony Vaio VGN-SR21M # Sony Vaio VPC-W115XG # Fujitsu Lifebook S7110 # Fujitsu Lifebook A530 # Toshiba A200 # MSI X360 # Lenovo 3000 Y410 SRU Justification === First, sorry if this bug is a bit messy, but I think it would be even more messy if I spread the information across several bugs. Here's some explanation: The long-term fix is already in Quantal, because we backported the Phantom Jack support into Ubuntu's 3.5 kernel. Together with that comes a small PulseAudio patch, http://bazaar.launchpad.net/~ubuntu- audio-dev/pulseaudio/ubuntu.precise/revision/519/debian/patches/0624 -alsa-mixer-Add-Phantom-Jack-support.patch - the reason I want this in 12.04 is to provide a better experience for users running the quantal kernel on precise, i e, the backport kernel coming with 12.04.2. In addition to that, while doing an SRU I could just as well add a few more quirks for affected machines showing up after the previous SRU, so that is now done in http://bazaar.launchpad.net/~ubuntu-audio- dev/pulseaudio/ubuntu.precise/revision/520/debian/patches/0625-alsa- mixer-Add-a-few-more-machines-to-internal-mic-w.patch [Impact] Several laptops (see above list) are missing mostly internal mics, but sometimes also speakers in the Sound Settings / PulseAudio. This leads to an inability to control volume for these devices, and often not being able to use them at all. [Test Case] * Have an affected machine * Notice that when your mic is unplugged, the internal mic is correctly shown in the sound settings [Regression Potential] The quirk-style fix only affects the machines above. The long-term fix affects only users of a newer (quantal or later) kernel. I have an DELL Inspiron 6400. As it seems ubuntu precise beta1 thinks it has a digital ouput. In the audio settings it says Play sound through: »Digital Output (S/PDIF)« As you can see there → http://support.dell.com/support/edocs/systems/ins6400/en/om/specs.htm#wp1054816 it has no S/PDIF output. The audio Settings doesn't let me change the mode. Sometime the system sets the mode to »Digital Stereo (IEC958) Output« but the drop-down list menu is grayed out so I can't change it. If I plug in and out my headphones the system changes the mode to »Analog Stereo Output« and I can hear Sound again. If you need more Information please let me know. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.94-0ubuntu1 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID
[Desktop-packages] [Bug 1086345] Re: Quantal-LTS-stack: Showing low-resolution screen on shutdown/reboot
We got some haswell platforms here and met same issues. It keeps showing the warning plymouthd: intel_bufmgr_gem.c:2783: drm_intel_bufmgr_gem_init: Assertion `0' failed. in the log, however there's no such code in the libdrm-ltsq2. Track it a bit It seems that libdrm-ltsq-intel1 didn't replaced libdrm-intel1 then I repack libdrm from the quantal's branch for precise , and it fixed the issue. the logo did appear again. I'm thinking maybe there should be a plymouth lts version which links to libdrm-ltsq2 or those libdrm-ltsq2 version should replace all the old version of libdrm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1086345 Title: Quantal-LTS-stack: Showing low-resolution screen on shutdown/reboot Status in “lightdm” package in Ubuntu: Confirmed Bug description: Hardware is an Hashwell SDP with an Intel SSD. Fresh install from 12.04.1 alternate image, then added the quantal-lts kernel and the x-stack (ppa:ubuntu-x-swat/q-lts-backport, pulled via xserver-xorg- lts-quantal meta package). Monitor is connected to VGA. With the new stack graphics on VGA does actually work and the system snaps from the grub-efi prompt to lightdm in a blink (2s at most which probably can be attributed to the Intel SSD). Everything is fine and the system definitely is running in a high resolution mode. However when shutting down or rebooting, the system drops into a screen telling me it is running in low-resolution mode instead of showing plymouth (or the terminal). The system will continue to shut down or reboot even without pressing the ok button, but it can be done for a bit and then would show the next screen about how to resolve the issue. I was not quick or daring enough to go on from the second screen. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: plymouth 0.8.2-2ubuntu30 ProcVersionSignature: Ubuntu 3.5.0-20.31~hswv4-generic 3.5.7 Uname: Linux 3.5.0-20-generic x86_64 ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Tue Dec 4 12:44:55 2012 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120822.4) Lsusb: Bus 001 Device 002: ID 0b39:cd02 Omnidirectional Control Technology, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Intel Corporation Shark Bay Client platform MarkForUpload: True ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-20-generic root=UUID=b77c2e0f-0611-4b74-9319-0c5c92b55a69 ro quiet splash ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-20-generic root=UUID=b77c2e0f-0611-4b74-9319-0c5c92b55a69 ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2012 dmi.bios.vendor: Intel Corporation dmi.bios.version: HSWLPTU1.86C.0086.R00.1208052028 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Flathead Creek Crb dmi.board.vendor: Intel Corp. dmi.board.version: 1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnIntelCorporation:bvrHSWLPTU1.86C.0086.R00.1208052028:bd08/05/2012:svnIntelCorporation:pnSharkBayClientplatform:pvr0.1:rvnIntelCorp.:rnFlatheadCreekCrb:rvr1:cvnIntelCorporation:ct3:cvr0.1: dmi.product.name: Shark Bay Client platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1086345/+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 1086720] Re: After installed of fglrx or fglrx-update, can't boot to desktop
system: 201205-11418(Dell Inspiron 14s) also affected by this bug. ** Tags added: cid201206-11396 cid201206-11418 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1086720 Title: After installed of fglrx or fglrx-update, can't boot to desktop Status in “fglrx-installer” package in Ubuntu: New Bug description: System: HP Heineken 10 ( 201206-11396) After installed of fglrx and fglrx, can't boot to desktop, only the background and mouse pointer are shown. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1742 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 15.589071] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Wed Dec 5 04:26:34 2012 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard a654 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=58211ec4-f36a-4614-b688-d509d7109a6f ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.name: 2AEE dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/24/2012:svnHewlett-Packard:pna654:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr: dmi.product.name: a654 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1086720/+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 1038084] Re: Bluetooth devices are muted after suspend/resume
Hello, I have tried two systems in our lab, but both of them have no built-in BT module, so I can't verify this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1038084 Title: Bluetooth devices are muted after suspend/resume Status in “pulseaudio” package in Ubuntu: Fix Released Status in “pulseaudio” source package in Precise: Fix Committed Bug description: [SRU Justification] Impact: Users need to manually unmute bluetooth devices after a S3 cycle. Note that this is probably some kind of race between pulseaudio and bluez - so the bug does is not consistenly reproducible. Testcase: Connect a bluetooth audio device and play back some music through pulseaudio to the device. Then suspend/resume. Now check if the device has suddenly become muted. If so, the bug is not fixed. Regression potential: As the bluetooth audio devices are self-powered units, there shouldn't be a risk that this would lead to pops and clicks on S3 (which was the original reason for adding this distro- specific script in the first place). Like bug 665314, but only for Bluetooth. We're splitting them up because I fix only Bluetooth devices for 12.04. This is because a regression was reported when dropping the script completely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1038084/+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 1076840] Re: [CS4213, Dell Inspiron 3420] Internal speaker does not show up in Sound settings
The bug is fixed with pulseaudio 1.1-0ubuntu15.2 under Precise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1076840 Title: [CS4213, Dell Inspiron 3420] Internal speaker does not show up in Sound settings Status in OEM Priority Project: Fix Committed Status in OEM Priority Project precise series: Fix Committed Status in OEM Priority Project quantal series: Fix Committed Status in “linux” package in Ubuntu: Fix Released Status in “pulseaudio” package in Ubuntu: Invalid Status in “linux” source package in Precise: Won't Fix Status in “pulseaudio” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Released Status in “pulseaudio” source package in Quantal: Invalid Status in “linux” source package in Raring: Fix Released Status in “pulseaudio” source package in Raring: Invalid Bug description: [SRU Justification] Impact: The internal speaker does not show up in the sound settings, which causes this to block certification. Test case: With the affected machines, open sound settings without headphones plugged in. If the Internal Speaker does not show up, the bug is present. Regression risk (Quantal): Cirrus is a rare codec, mostly used in macbooks. Upstream has reviewed and blessed the patch. Regression risk (Precise): These machines are quirked individually and won't affect other machines (and even if they did, the worst thing that could happen would be a speaker output that shouldn't be there). This is due to the Internal Speaker Phantom Jack kctrl not being created. the same issue occurs in the following sysyems: cid:201202-10591, Dell Inspiron 3420 (PCI SSID: 1028:0553) cid:201202-10590, Dell Inspiron 3420 (PCI SSID: 1028:0553) cid:201202-10557, Dell Inspiron 3520 (PCI SSID: 1028:0555) cid:201202-10593, Dell Vostro 2420 (PCI SSID: 1028:0556) cid:201202-10558, Dell Vostro 2520 (PCI SSID: 1028:0558) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1605 F pulseaudio /dev/snd/pcmC0D0c: ubuntu 1605 F...m pulseaudio Date: Thu Nov 8 21:35:36 2012 HibernationDevice: RESUME=UUID=47ccd585-7def-4658-a811-0740ccc8d313 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Inspiron 3420 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=414de9d1-6779-4d25-94ee-402d7d076b1e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/15/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1076840/+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 1076840] Re: [CS4213, Dell Inspiron 3420] Internal speaker does not show up in Sound settings
I have verified it on Quantal, kernel 3.5.0-21.32, but bugs remains, internal speaker interface disappears, but sound actually works. @kentb: you want me to test with updated pulseaudio under Quantal? The pulseaudio I installed on the system is 2.1-0ubuntu4. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1076840 Title: [CS4213, Dell Inspiron 3420] Internal speaker does not show up in Sound settings Status in OEM Priority Project: Fix Committed Status in OEM Priority Project precise series: Fix Committed Status in OEM Priority Project quantal series: Fix Committed Status in “linux” package in Ubuntu: Fix Released Status in “pulseaudio” package in Ubuntu: Invalid Status in “linux” source package in Precise: Won't Fix Status in “pulseaudio” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Released Status in “pulseaudio” source package in Quantal: Invalid Status in “linux” source package in Raring: Fix Released Status in “pulseaudio” source package in Raring: Invalid Bug description: [SRU Justification] Impact: The internal speaker does not show up in the sound settings, which causes this to block certification. Test case: With the affected machines, open sound settings without headphones plugged in. If the Internal Speaker does not show up, the bug is present. Regression risk (Quantal): Cirrus is a rare codec, mostly used in macbooks. Upstream has reviewed and blessed the patch. Regression risk (Precise): These machines are quirked individually and won't affect other machines (and even if they did, the worst thing that could happen would be a speaker output that shouldn't be there). This is due to the Internal Speaker Phantom Jack kctrl not being created. the same issue occurs in the following sysyems: cid:201202-10591, Dell Inspiron 3420 (PCI SSID: 1028:0553) cid:201202-10590, Dell Inspiron 3420 (PCI SSID: 1028:0553) cid:201202-10557, Dell Inspiron 3520 (PCI SSID: 1028:0555) cid:201202-10593, Dell Vostro 2420 (PCI SSID: 1028:0556) cid:201202-10558, Dell Vostro 2520 (PCI SSID: 1028:0558) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1605 F pulseaudio /dev/snd/pcmC0D0c: ubuntu 1605 F...m pulseaudio Date: Thu Nov 8 21:35:36 2012 HibernationDevice: RESUME=UUID=47ccd585-7def-4658-a811-0740ccc8d313 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Inspiron 3420 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=414de9d1-6779-4d25-94ee-402d7d076b1e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/15/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1076840/+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 1038084] Re: Bluetooth devices are muted after suspend/resume
I have the system, but it's still occupied by others, I will test the system when it's available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1038084 Title: Bluetooth devices are muted after suspend/resume Status in “pulseaudio” package in Ubuntu: Fix Released Status in “pulseaudio” source package in Precise: Fix Committed Bug description: [SRU Justification] Impact: Users need to manually unmute bluetooth devices after a S3 cycle. Note that this is probably some kind of race between pulseaudio and bluez - so the bug does is not consistenly reproducible. Testcase: Connect a bluetooth audio device and play back some music through pulseaudio to the device. Then suspend/resume. Now check if the device has suddenly become muted. If so, the bug is not fixed. Regression potential: As the bluetooth audio devices are self-powered units, there shouldn't be a risk that this would lead to pops and clicks on S3 (which was the original reason for adding this distro- specific script in the first place). Like bug 665314, but only for Bluetooth. We're splitting them up because I fix only Bluetooth devices for 12.04. This is because a regression was reported when dropping the script completely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1038084/+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 1073420] Re: [Dell Inspiron One 2020] No Microphone Interface
this bug is fixed by installing package,pulseaudio-1.1-0ubuntu15.2. I can see the mic interface now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1073420 Title: [Dell Inspiron One 2020] No Microphone Interface Status in “alsa-driver” package in Ubuntu: Fix Released Status in “pulseaudio” package in Ubuntu: Fix Released Status in “alsa-driver” source package in Precise: Invalid Status in “pulseaudio” source package in Precise: Fix Committed Bug description: [SRU Justification] Impact: Internal Mic not visible in sound settings Test case: With the hardware and without a external mic plugged in, see if there is a Internal Mic option in sound settings Regression risk: Individual quirk. It will not affect other machines. cid: 201201-10396 Screenshot of Sound Setting is as attachment. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-29-generic 3.2.0-29.46 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC662 rev3 Analog [ALC662 rev3 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC662 rev3 Analog [ALC662 rev3 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1481 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c0 irq 45' Mixer name : 'Realtek ALC662 rev3' Components : 'HDA:10ec0662,10280579,00100300' Controls : 15 Simple ctrls : 8 Date: Tue Oct 30 23:23:15 2012 HibernationDevice: RESUME=UUID=2e028e23-1571-4400-a9a5-caae0faa8498 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. Inspiron One 2020 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=f1b7b485-ec30-4b1c-93b2-22e39aeae682 ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-29-generic N/A linux-backports-modules-3.2.0-29-generic N/A linux-firmware1.79 RfKill: SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X21 dmi.board.name: 03HC21 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrX21:bd07/23/2012:svnDellInc.:pnInspironOne2020:pvr:rvnDellInc.:rn03HC21:rvrX02:cvnDellInc.:ct3:cvr: dmi.product.name: Inspiron One 2020 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1073420/+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 1073420] Re: [Dell Inspiron One 2020] No Microphone Interface
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1073420 Title: [Dell Inspiron One 2020] No Microphone Interface Status in “alsa-driver” package in Ubuntu: Fix Released Status in “pulseaudio” package in Ubuntu: Fix Released Status in “alsa-driver” source package in Precise: Invalid Status in “pulseaudio” source package in Precise: Fix Committed Bug description: [SRU Justification] Impact: Internal Mic not visible in sound settings Test case: With the hardware and without a external mic plugged in, see if there is a Internal Mic option in sound settings Regression risk: Individual quirk. It will not affect other machines. cid: 201201-10396 Screenshot of Sound Setting is as attachment. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-29-generic 3.2.0-29.46 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC662 rev3 Analog [ALC662 rev3 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC662 rev3 Analog [ALC662 rev3 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1481 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7c0 irq 45' Mixer name : 'Realtek ALC662 rev3' Components : 'HDA:10ec0662,10280579,00100300' Controls : 15 Simple ctrls : 8 Date: Tue Oct 30 23:23:15 2012 HibernationDevice: RESUME=UUID=2e028e23-1571-4400-a9a5-caae0faa8498 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Dell Inc. Inspiron One 2020 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=f1b7b485-ec30-4b1c-93b2-22e39aeae682 ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.2.0-29-generic N/A linux-backports-modules-3.2.0-29-generic N/A linux-firmware1.79 RfKill: SourcePackage: linux StagingDrivers: mei UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X21 dmi.board.name: 03HC21 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrX21:bd07/23/2012:svnDellInc.:pnInspironOne2020:pvr:rvnDellInc.:rn03HC21:rvrX02:cvnDellInc.:ct3:cvr: dmi.product.name: Inspiron One 2020 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1073420/+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 1020471] Re: Front Headphone Jack ALSA kcontrol name not picked up by PulseAudio
This bug is fixed with pulseaudio 1.1-0ubuntu15.2, the jack detection works now. ** Tags added: verification-done ** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1020471 Title: Front Headphone Jack ALSA kcontrol name not picked up by PulseAudio Status in “pulseaudio” package in Ubuntu: Fix Released Status in “pulseaudio” source package in Precise: Fix Committed Status in “pulseaudio” source package in Quantal: Fix Released Bug description: [SRU Justification] Impact: Some hardware have no automatic jack detection for headphone to userspace, so when you plug headphones in, your media keys and indicator will still control the speaker's volume. This affects several machines currently being enabled by the HWE team. Testcase: Have an affected machine, i e one that has a Front Headphone Jack kcontrol (as seen by amixer contents), open gnome sound settings, and plug headphones in. If the bug is fixed, the headphone port will now be visible and selected. Regression potential: If there is a Front Headphone Jack, but for some reason this is non-functional due to a kernel driver or hardware problem, there is a chance that the headphone port, which was manually selectable, now is always invisible. Many desktops have headphone on the front and line outs on the back. Sometimes this means that the alsa kcontrol for the headphone jack is labelled Front Headphone Jack, but the volume controls are only Headphone Playback Volume, i e, without the Front prefix. Consider backporting http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=12a53524b3bdbae2dce7c9fd507561633d3beaec http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=47b31ce6ad744de9595eb4d5366d25b40c5d3455 ..to fix it. It would enable jack detection between speakers and headphones for these devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1020471/+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 1086720] Re: After installed of fglrx or fglrx-update, can't boot to desktop
After the linux-headers-3.5.0-17-generic installed and reinstalled fglrx fglrx-amdcccle, system is able to boot to desktop without problem. I see there're two problem. 1. It seems linux-headers-3.5.0-17-generic is not installed by default 2. The fglrx package finishes installation without the necessary header, and there's no error occurred to user. So user doesn't know the driver failed the installation actually. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1086720 Title: After installed of fglrx or fglrx-update, can't boot to desktop Status in “fglrx-installer” package in Ubuntu: New Bug description: System: HP Heineken 10 ( 201206-11396) After installed of fglrx and fglrx, can't boot to desktop, only the background and mouse pointer are shown. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1742 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 15.589071] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Wed Dec 5 04:26:34 2012 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard a654 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=58211ec4-f36a-4614-b688-d509d7109a6f ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.name: 2AEE dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/24/2012:svnHewlett-Packard:pna654:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr: dmi.product.name: a654 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1086720/+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 1076840] Re: [CS4213, Dell Inspiron 3420] Internal speaker does not show up in Sound settings
3.5.0-20.31 has just been superseded by 3.5.0-20.32, I will test it when 3.5.0-20.32 is ready. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1076840 Title: [CS4213, Dell Inspiron 3420] Internal speaker does not show up in Sound settings Status in OEM Priority Project: Fix Committed Status in OEM Priority Project precise series: Fix Committed Status in OEM Priority Project quantal series: Fix Committed Status in “linux” package in Ubuntu: Fix Released Status in “pulseaudio” package in Ubuntu: Invalid Status in “linux” source package in Precise: Won't Fix Status in “pulseaudio” source package in Precise: Fix Committed Status in “linux” source package in Quantal: Fix Committed Status in “pulseaudio” source package in Quantal: Invalid Status in “linux” source package in Raring: Fix Released Status in “pulseaudio” source package in Raring: Invalid Bug description: [SRU Justification] Impact: The internal speaker does not show up in the sound settings, which causes this to block certification. Test case: With the affected machines, open sound settings without headphones plugged in. If the Internal Speaker does not show up, the bug is present. Regression risk (Quantal): Cirrus is a rare codec, mostly used in macbooks. Upstream has reviewed and blessed the patch. Regression risk (Precise): These machines are quirked individually and won't affect other machines (and even if they did, the worst thing that could happen would be a speaker output that shouldn't be there). This is due to the Internal Speaker Phantom Jack kctrl not being created. the same issue occurs in the following sysyems: cid:201202-10591, Dell Inspiron 3420 (PCI SSID: 1028:0553) cid:201202-10590, Dell Inspiron 3420 (PCI SSID: 1028:0553) cid:201202-10557, Dell Inspiron 3520 (PCI SSID: 1028:0555) cid:201202-10593, Dell Vostro 2420 (PCI SSID: 1028:0556) cid:201202-10558, Dell Vostro 2520 (PCI SSID: 1028:0558) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1605 F pulseaudio /dev/snd/pcmC0D0c: ubuntu 1605 F...m pulseaudio Date: Thu Nov 8 21:35:36 2012 HibernationDevice: RESUME=UUID=47ccd585-7def-4658-a811-0740ccc8d313 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Inspiron 3420 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=414de9d1-6779-4d25-94ee-402d7d076b1e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/15/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1076840/+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 1086720] [NEW] After installed of fglrx or fglrx-update, can't boot to desktop
Public bug reported: System: HP Heineken 10 ( 201206-11396) After installed of fglrx and fglrx, can't boot to desktop, only the background and mouse pointer are shown. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1742 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 15.589071] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Wed Dec 5 04:26:34 2012 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard a654 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=58211ec4-f36a-4614-b688-d509d7109a6f ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.name: 2AEE dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/24/2012:svnHewlett-Packard:pna654:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr: dmi.product.name: a654 dmi.sys.vendor: Hewlett-Packard ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Assignee: Anthony Wong (anthonywong) Status: New ** Tags: amd64 apport-bug blocks-hwcert quantal staging ** Package changed: linux (Ubuntu) = fglrx-installer (Ubuntu) ** Changed in: fglrx-installer (Ubuntu) Assignee: (unassigned) = Anthony Wong (anthonywong) ** Summary changed: - After installed of fglrx and fglrx, can't boot to desktop + After installed of fglrx or fglrx-update, can't boot to desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1086720 Title: After installed of fglrx or fglrx-update, can't boot to desktop Status in “fglrx-installer” package in Ubuntu: New Bug description: System: HP Heineken 10 ( 201206-11396) After installed of fglrx and fglrx, can't boot to desktop, only the background and mouse pointer are shown. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1742 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 15.589071] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Wed Dec 5 04:26:34 2012 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard a654 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=58211ec4-f36a-4614-b688-d509d7109a6f ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.name: 2AEE dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/24/2012:svnHewlett-Packard:pna654:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr: dmi.product.name: a654 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to:
[Desktop-packages] [Bug 1086720] Re: After installed of fglrx or fglrx-update, can't boot to desktop
** Attachment added: Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1086720/+attachment/3452059/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1086720 Title: After installed of fglrx or fglrx-update, can't boot to desktop Status in “fglrx-installer” package in Ubuntu: New Bug description: System: HP Heineken 10 ( 201206-11396) After installed of fglrx and fglrx, can't boot to desktop, only the background and mouse pointer are shown. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1742 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 15.589071] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Wed Dec 5 04:26:34 2012 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard a654 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=58211ec4-f36a-4614-b688-d509d7109a6f ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.name: 2AEE dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/24/2012:svnHewlett-Packard:pna654:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr: dmi.product.name: a654 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1086720/+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 1086720] Re: After installed of fglrx or fglrx-update, can't boot to desktop
201206-11396 fails the suspend without fglrx. After fglrx installed, the system can wake up from suspend, but still can't boot to desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1086720 Title: After installed of fglrx or fglrx-update, can't boot to desktop Status in “fglrx-installer” package in Ubuntu: New Bug description: System: HP Heineken 10 ( 201206-11396) After installed of fglrx and fglrx, can't boot to desktop, only the background and mouse pointer are shown. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1742 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 15.589071] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Wed Dec 5 04:26:34 2012 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard a654 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=58211ec4-f36a-4614-b688-d509d7109a6f ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.name: 2AEE dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/24/2012:svnHewlett-Packard:pna654:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr: dmi.product.name: a654 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1086720/+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 1086720] Re: After installed of fglrx or fglrx-update, can't boot to desktop
ii fglrx 2:9.000-0ubuntu3 amd64Video driver for the AMD graphics accelerators ii fglrx-amdcccle2:9.000-0ubuntu3 amd64Catalyst Control Center for the AMD graphics accelerators -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1086720 Title: After installed of fglrx or fglrx-update, can't boot to desktop Status in “fglrx-installer” package in Ubuntu: New Bug description: System: HP Heineken 10 ( 201206-11396) After installed of fglrx and fglrx, can't boot to desktop, only the background and mouse pointer are shown. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1742 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: [ 15.589071] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Date: Wed Dec 5 04:26:34 2012 HibernationDevice: RESUME=UUID=ccd7a21f-7a71-4fa5-b95d-e2898c3dae24 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard a654 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=58211ec4-f36a-4614-b688-d509d7109a6f ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: rts_pstor UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.name: 2AEE dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.03 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/24/2012:svnHewlett-Packard:pna654:pvr:rvnPEGATRONCORPORATION:rn2AEE:rvr1.03:cvnHewlett-Packard:ct3:cvr: dmi.product.name: a654 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1086720/+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 1076840] Re: [CS4213, Dell Inspiron 3420] Internal speaker does not show up in Sound settings
@diwic: the 5 systems are currently we have tested and found the bugs. We will continue to test more systems, if we found systems have this bug, I will comment on this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1076840 Title: [CS4213, Dell Inspiron 3420] Internal speaker does not show up in Sound settings Status in OEM Priority Project: New Status in OEM Priority Project precise series: Incomplete Status in OEM Priority Project quantal series: New Status in “linux” package in Ubuntu: Fix Released Status in “pulseaudio” package in Ubuntu: Invalid Status in “linux” source package in Precise: Won't Fix Status in “pulseaudio” source package in Precise: In Progress Status in “linux” source package in Quantal: Fix Committed Status in “pulseaudio” source package in Quantal: Invalid Status in “linux” source package in Raring: Fix Released Status in “pulseaudio” source package in Raring: Invalid Bug description: [SRU Justification (Quantal)] Impact: The internal speaker does not show up in the sound settings, which causes this to block certification. Test case: With the affected machines, open sound settings without headphones plugged in. If the Internal Speaker does not show up, the bug is present. Regression risk: Cirrus is a rare codec, mostly used in macbooks. Upstream has reviewed and blessed the patch. This is due to the Internal Speaker Phantom Jack kctrl not being created. the same issue occurs in the following sysyems: cid:201202-10591, Dell Inspiron 3420 (PCI SSID: 1028:0553) cid:201202-10590, Dell Inspiron 3420 (PCI SSID: 1028:0553) cid:201202-10557, Dell Inspiron 3520 (PCI SSID: 1028:0555) cid:201202-10593, Dell Vostro 2420 (PCI SSID: 1028:0556) cid:201202-10558, Dell Vostro 2520 (PCI SSID: 1028:0558) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1605 F pulseaudio /dev/snd/pcmC0D0c: ubuntu 1605 F...m pulseaudio Date: Thu Nov 8 21:35:36 2012 HibernationDevice: RESUME=UUID=47ccd585-7def-4658-a811-0740ccc8d313 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Inspiron 3420 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=414de9d1-6779-4d25-94ee-402d7d076b1e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/15/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1076840/+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 1076835] Re: [Dell Inspiron 4320]Bluetooth/browses-files doesn't work
** Project changed: gvfs = gvfs (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1076835 Title: [Dell Inspiron 4320]Bluetooth/browses-files doesn't work Status in “gvfs” package in Ubuntu: Incomplete Bug description: cid:201202-10591 Bluetooth can't browse files The same issue occurs in: cid:201206-11167, HP Pavilion Sleekbook 14 (Quantal) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1605 F pulseaudio Date: Thu Nov 8 21:06:13 2012 HibernationDevice: RESUME=UUID=47ccd585-7def-4658-a811-0740ccc8d313 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Dell Inc. Inspiron 3420 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=414de9d1-6779-4d25-94ee-402d7d076b1e ro quiet splash initcall_debug vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/15/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1076835/+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 1081007] [NEW] [Radeon HD6310] jockey can't install the fglrx driver
Public bug reported: VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310] [1002:9802] jockey.log is attached. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: jockey-common 0.9.7-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Tue Nov 20 02:23:31 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MachineType: Dell Inc. Inspiron M4040 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=ad570c08-07c8-4af4-a013-da1916ffad2e ro quiet splash initcall_debug vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X28 dmi.board.vendor: Dell Inc. dmi.board.version: X28 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrX28:bd01/11/2012:svnDellInc.:pnInspironM4040:pvrNotSpecified:rvnDellInc.:rn:rvrX28:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron M4040 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: jockey (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity ** Attachment added: jockey.log https://bugs.launchpad.net/bugs/1081007/+attachment/3439242/+files/jockey.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1081007 Title: [Radeon HD6310] jockey can't install the fglrx driver Status in “jockey” package in Ubuntu: New Bug description: VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Wrestler [Radeon HD 6310] [1002:9802] jockey.log is attached. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: jockey-common 0.9.7-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Tue Nov 20 02:23:31 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MachineType: Dell Inc. Inspiron M4040 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=ad570c08-07c8-4af4-a013-da1916ffad2e ro quiet splash initcall_debug vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X28 dmi.board.vendor: Dell Inc. dmi.board.version: X28 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrX28:bd01/11/2012:svnDellInc.:pnInspironM4040:pvrNotSpecified:rvnDellInc.:rn:rvrX28:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron M4040 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1081007/+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 1040456] Re: System info tab for graphic info should use glxinfo -l 's result first
** Bug watch added: GNOME Bug Tracker #688220 https://bugzilla.gnome.org/show_bug.cgi?id=688220 ** Also affects: gnome-control-center via https://bugzilla.gnome.org/show_bug.cgi?id=688220 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1040456 Title: System info tab for graphic info should use glxinfo -l 's result first Status in GNOME Control Center: Unknown Status in “gnome-control-center” package in Ubuntu: New Bug description: Open the system setting-Details-Graphics, find the Graphics Driver show VESA: XX strings , not the accurate information from glxinfo -l | grep OpenGL renderer string The VESA: string displayed in System Settings--Details-Graphics is because gnome-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log so this VESA:X string instead of the more accurate string from glxinfo will being shown in the panel. Use glxinfo's information (when available) first is more accurate. A proposed patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1040456/+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 1055874] Re: Automatic sleep settings are not followed precisely
** Changed in: gnome-power-manager (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1055874 Title: Automatic sleep settings are not followed precisely Status in Gnome Settings Daemon: Fix Released Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Sep 25 09:43:50 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to precise on 2012-04-29 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1055874/+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 1055874] Re: Automatic sleep settings are not followed precisely
@sparhawkthesecond what is your idle-delay ? org.gnome.desktop.session idle-delay may affect on this. as I said in #2, idle-delay setting must be same with sleep-display-(ac|battery). I think g-c-c UI have this check but if you use gsettings to cheange the value then it may not that easy to find out this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1055874 Title: Automatic sleep settings are not followed precisely Status in Gnome Settings Daemon: Fix Released Status in “gnome-power-manager” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Sep 25 09:43:50 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to precise on 2012-04-29 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1055874/+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 1055874] Re: Automatic sleep settings are not followed precisely
** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=668703 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1055874 Title: Automatic sleep settings are not followed precisely Status in Gnome Settings Daemon: Unknown Status in “gnome-power-manager” package in Ubuntu: New Bug description: When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Sep 25 09:43:50 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to precise on 2012-04-29 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1055874/+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 1055874] Re: Automatic sleep settings are not followed precisely
** Project changed: gnome-settings-daemon = gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1055874 Title: Automatic sleep settings are not followed precisely Status in “gnome-power-manager” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Unknown Bug description: When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Sep 25 09:43:50 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to precise on 2012-04-29 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1055874/+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 1055874] Re: Automatic sleep settings are not followed precisely
** Package changed: gnome-settings-daemon (Ubuntu) = gnome-settings- daemon ** Also affects: gnome-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-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1055874 Title: Automatic sleep settings are not followed precisely Status in Gnome Settings Daemon: Unknown Status in “gnome-power-manager” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Sep 25 09:43:50 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to precise on 2012-04-29 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1055874/+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 1055874] Re: Automatic sleep settings are not followed precisely
@Sparhawk what's the result of #gsettings get org.gnome.settings-daemon.plugins.power idle-dim-time ? idle-dim-time will affect the time you set on those settings, you need to plus the dim time. if idle-dim-time is 30, and sleep-display-ac is 60 your monitor will turn off after 90 secs inactive. and whenever you set sleep-display-ac by gsettings , you also need to set [org.gnome.settings-daemon.plugins.power] sleep-display-ac sleep-display-battery and [org.gnome.desktop.session] idle-delay these 3 values need to be same in the gsettings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1055874 Title: Automatic sleep settings are not followed precisely Status in “gnome-power-manager” package in Ubuntu: New Bug description: When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Sep 25 09:43:50 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to precise on 2012-04-29 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1055874/+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 1055874] Re: Automatic sleep settings are not followed precisely
@Sparhawk and if your sleep-inactive-(ac|battery)-type is suspend the actual suspend time will be sleep-inactive-(ac|battery)-timeout + idle-dim-time but if your sleep-display-(ac|battery) sleep- inactive-(ac|battery)-timeout the actual suspend time will be sleep-display-(ac|battery) + idle-dim-time hope these explains the default behavior in ubuntu now. btw, this should related to gnome-setttings-daemon not gnome-power- manager , and it's indeed has some design issue, there is a upstream fix already submitted. ( https://bugzilla.gnome.org/show_bug.cgi?id=668703 ) but not yet in precise (and quantel), I'd assume this is going to be changed in 13.04. ** Bug watch added: GNOME Bug Tracker #668703 https://bugzilla.gnome.org/show_bug.cgi?id=668703 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1055874 Title: Automatic sleep settings are not followed precisely Status in “gnome-power-manager” package in Ubuntu: New Bug description: When I set the various timeouts via dconf-editor, my computer does not follow them precisely. I'm referring to these settings: org.gnome.settings-daemon.plugins.power sleep-display-ac org.gnome.settings-daemon.plugins.power sleep-display-battery org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout For example if I set all to 5, then the display sleeps at 30 seconds, and the computer at 70 seconds. Similarly, if I set them all to 60, the computer suspends around 90 seconds. I've only tried these shorter settings. These are clearly values that are low for normal usage, but this bug is very frustrating if one attempts to troubleshoot unrelated automatic-sleep bugs. Firstly, I think I missed the case when automatic sleep might have worked. Secondly, it increases the time it takes to troubleshoot by a lot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-power-manager 3.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Tue Sep 25 09:43:50 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to precise on 2012-04-29 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1055874/+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 1040456] [NEW] System info tab for graphic info should use glxinfo -l 's result first
Public bug reported: Open the system setting-Details-Graphics, find the Graphics Driver show VESA: XX strings , not the accurate information from glxinfo -l | grep OpenGL renderer string The VESA: string displayed in System Settings--Details-Graphics is because gnome-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log so this VESA:X string instead of the more accurate string from glxinfo will being shown in the panel. Use glxinfo's information (when available) first is more accurate. A proposed patch is attached. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1040456 Title: System info tab for graphic info should use glxinfo -l 's result first Status in “gnome-control-center” package in Ubuntu: New Bug description: Open the system setting-Details-Graphics, find the Graphics Driver show VESA: XX strings , not the accurate information from glxinfo -l | grep OpenGL renderer string The VESA: string displayed in System Settings--Details-Graphics is because gnome-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log so this VESA:X string instead of the more accurate string from glxinfo will being shown in the panel. Use glxinfo's information (when available) first is more accurate. A proposed patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1040456/+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 1040456] Re: System info tab for graphic info should use glxinfo -l 's result first
** Attachment added: gnome-control-center-graphics-info.patch https://bugs.launchpad.net/bugs/1040456/+attachment/3272883/+files/gnome-control-center-graphics-info.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1040456 Title: System info tab for graphic info should use glxinfo -l 's result first Status in “gnome-control-center” package in Ubuntu: New Bug description: Open the system setting-Details-Graphics, find the Graphics Driver show VESA: XX strings , not the accurate information from glxinfo -l | grep OpenGL renderer string The VESA: string displayed in System Settings--Details-Graphics is because gnome-control-center will find the driver information via: (1) parse /var/log/Xorg.0.log and find VESA VBE OEM Product: String (2) if (1) is not found, parse the result of glxinfo -l and find OpenGL renderer string, and use this info as the string being shown. There're some of AMD's fglrx driver will show VESA VBE OEM Product: X string in /var/log/Xorg.0.log so this VESA:X string instead of the more accurate string from glxinfo will being shown in the panel. Use glxinfo's information (when available) first is more accurate. A proposed patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1040456/+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 869799] Re: [Dell inspiron M5110] no output while external VGA is connected
** Tags added: cid201105-8043 taipei
--
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/869799
Title:
[Dell inspiron M5110] no output while external VGA is connected
Status in “gnome-settings-daemon” package in Ubuntu:
Confirmed
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
no output while external VGA is connected, hdmi output is fine.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-11-generic 2.6.38-11.50
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic_1 [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1435 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xff744000 irq 57'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 4
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic_1'/'HD-Audio Generic at 0xff74 irq 16'
Mixer name : 'IDT 92HD87B1/3'
Components : 'HDA:111d76d1,102804b1,00100205'
Controls : 14
Simple ctrls : 9
Date: Fri Oct 7 03:38:38 2011
HibernationDevice: RESUME=UUID=c0387b11-d7a5-4b41-8687-65b94ee5be3c
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
MachineType: Dell Inc. Inspiron M5110
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic
root=UUID=40a14de6-8af6-45d9-b386-f024d1818675 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-2.6.38-11-generic N/A
linux-backports-modules-2.6.38-11-generic N/A
linux-firmware 1.52
SourcePackage: linux
StagingDrivers: brcm80211
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X16
dmi.board.name: 4IE010
dmi.board.vendor: Dell Inc.
dmi.board.version: X16
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrX16:bd05/31/2011:svnDellInc.:pnInspironM5110:pvrNotSpecified:rvnDellInc.:rn4IE010:rvrX16:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron M5110
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/869799/+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 869799] Re: [Dell inspiron M5110] no output while external VGA is connected
** Tags removed: taipei
** Tags added: lab-taipei
--
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/869799
Title:
[Dell inspiron M5110] no output while external VGA is connected
Status in “gnome-settings-daemon” package in Ubuntu:
Confirmed
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
no output while external VGA is connected, hdmi output is fine.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-11-generic 2.6.38-11.50
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic_1 [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1435 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xff744000 irq 57'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 4
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic_1'/'HD-Audio Generic at 0xff74 irq 16'
Mixer name : 'IDT 92HD87B1/3'
Components : 'HDA:111d76d1,102804b1,00100205'
Controls : 14
Simple ctrls : 9
Date: Fri Oct 7 03:38:38 2011
HibernationDevice: RESUME=UUID=c0387b11-d7a5-4b41-8687-65b94ee5be3c
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
MachineType: Dell Inc. Inspiron M5110
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic
root=UUID=40a14de6-8af6-45d9-b386-f024d1818675 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-2.6.38-11-generic N/A
linux-backports-modules-2.6.38-11-generic N/A
linux-firmware 1.52
SourcePackage: linux
StagingDrivers: brcm80211
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X16
dmi.board.name: 4IE010
dmi.board.vendor: Dell Inc.
dmi.board.version: X16
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrX16:bd05/31/2011:svnDellInc.:pnInspironM5110:pvrNotSpecified:rvnDellInc.:rn4IE010:rvrX16:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron M5110
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/869799/+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 869799] Re: [Dell inspiron M5110] no output while external VGA is connected
The gsd-debug-randr.log while bug happened.
** Attachment added: gsd-debug-randr.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/869799/+attachment/2632778/+files/gsd-debug-randr.log
--
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/869799
Title:
[Dell inspiron M5110] no output while external VGA is connected
Status in “gnome-settings-daemon” package in Ubuntu:
Confirmed
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
no output while external VGA is connected, hdmi output is fine.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-11-generic 2.6.38-11.50
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic_1 [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1435 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xff744000 irq 57'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 4
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic_1'/'HD-Audio Generic at 0xff74 irq 16'
Mixer name : 'IDT 92HD87B1/3'
Components : 'HDA:111d76d1,102804b1,00100205'
Controls : 14
Simple ctrls : 9
Date: Fri Oct 7 03:38:38 2011
HibernationDevice: RESUME=UUID=c0387b11-d7a5-4b41-8687-65b94ee5be3c
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
MachineType: Dell Inc. Inspiron M5110
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic
root=UUID=40a14de6-8af6-45d9-b386-f024d1818675 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-2.6.38-11-generic N/A
linux-backports-modules-2.6.38-11-generic N/A
linux-firmware 1.52
SourcePackage: linux
StagingDrivers: brcm80211
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X16
dmi.board.name: 4IE010
dmi.board.vendor: Dell Inc.
dmi.board.version: X16
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrX16:bd05/31/2011:svnDellInc.:pnInspironM5110:pvrNotSpecified:rvnDellInc.:rn4IE010:rvrX16:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron M5110
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/869799/+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 869799] Re: [Dell inspiron M5110] no output while external VGA is connected
The output log from xrandr.
log above is before the external display plugged, after
that is after external display connected.
-
If I connected the external monitor first, then boot the system. The external
display is ok.
If I switch to console mode(ctrl+alt+F1) then come back to x-windows. The
external display is ok.
** Attachment added: xrandr.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/869799/+attachment/2632795/+files/xrandr.log
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Incomplete = Confirmed
--
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/869799
Title:
[Dell inspiron M5110] no output while external VGA is connected
Status in “gnome-settings-daemon” package in Ubuntu:
Confirmed
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
no output while external VGA is connected, hdmi output is fine.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-11-generic 2.6.38-11.50
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic_1 [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1435 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xff744000 irq 57'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 4
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic_1'/'HD-Audio Generic at 0xff74 irq 16'
Mixer name : 'IDT 92HD87B1/3'
Components : 'HDA:111d76d1,102804b1,00100205'
Controls : 14
Simple ctrls : 9
Date: Fri Oct 7 03:38:38 2011
HibernationDevice: RESUME=UUID=c0387b11-d7a5-4b41-8687-65b94ee5be3c
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
MachineType: Dell Inc. Inspiron M5110
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic
root=UUID=40a14de6-8af6-45d9-b386-f024d1818675 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-2.6.38-11-generic N/A
linux-backports-modules-2.6.38-11-generic N/A
linux-firmware 1.52
SourcePackage: linux
StagingDrivers: brcm80211
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X16
dmi.board.name: 4IE010
dmi.board.vendor: Dell Inc.
dmi.board.version: X16
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrX16:bd05/31/2011:svnDellInc.:pnInspironM5110:pvrNotSpecified:rvnDellInc.:rn4IE010:rvrX16:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron M5110
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/869799/+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 869799] Re: [Dell inspiron M5110] no output while external VGA is connected
As I see from the xrandr.log, there is two preferred mode (1366x768,
1440x900, marked with +), but no current mode(marked with *).
CRT1: 1366x768@0 +1366+0 (Unknown)
Automatically configured outputs to deal with event
Got RANDR event with timestamps change=14722 config=160860
Ignored event as old and new config timestamps are the same
Got RANDR event with timestamps change=14722 config=198939
Automatically configured outputs to deal with event
Got RANDR event with timestamps change=198939 = config=198939
Ignoring event since change = config
Got RANDR event with timestamps change=198939 config=209747
Could not switch to the following configuration (timestamp 209747): requested
position/size for CRTC 148 is outside the allowed limit: position=(1366, 0),
size=(1366, 768), maximum=(1600, 1600)
CRT1 connected (normal left inverted right x axis y axis)
1366x768 75.0 + 59.8
1440x900 59.9 + 75.0 59.9
1600x1200 60.0
1400x1050 60.0
1600x900 60.0
1280x1024 75.0 60.0
1280x960 60.0
1360x768 75.0 60.0
1280x800 75.0 59.8
1152x864 75.0 60.0
1280x768 75.0 59.9
1280x720 75.0 60.0
1024x768 75.0 70.1 60.0
1024x600 75.0 60.0
800x60072.2 75.0 60.3 56.2
800x48075.0 60.0
720x48075.0 60.0
640x48075.0 72.8 75.0 67.0 59.9
--
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/869799
Title:
[Dell inspiron M5110] no output while external VGA is connected
Status in “gnome-settings-daemon” package in Ubuntu:
Confirmed
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
no output while external VGA is connected, hdmi output is fine.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-11-generic 2.6.38-11.50
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic_1 [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1435 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xff744000 irq 57'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 4
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic_1'/'HD-Audio Generic at 0xff74 irq 16'
Mixer name : 'IDT 92HD87B1/3'
Components : 'HDA:111d76d1,102804b1,00100205'
Controls : 14
Simple ctrls : 9
Date: Fri Oct 7 03:38:38 2011
HibernationDevice: RESUME=UUID=c0387b11-d7a5-4b41-8687-65b94ee5be3c
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
MachineType: Dell Inc. Inspiron M5110
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic
root=UUID=40a14de6-8af6-45d9-b386-f024d1818675 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-2.6.38-11-generic N/A
linux-backports-modules-2.6.38-11-generic N/A
linux-firmware 1.52
SourcePackage: linux
StagingDrivers: brcm80211
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X16
dmi.board.name: 4IE010
dmi.board.vendor: Dell Inc.
dmi.board.version: X16
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrX16:bd05/31/2011:svnDellInc.:pnInspironM5110:pvrNotSpecified:rvnDellInc.:rn4IE010:rvrX16:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron M5110
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/869799/+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 869799] Re: [Dell inspiron M5110] no output while external VGA is connected
If I changed the mode with below command, the external display looks good. But
the bottom of main display of laptop will be cut-off.
xrandr --output --mode 1440x900.
mode 1366x768 is ok with command: xrandr --output --mode 1336x768.
No matter which mode it switched to, the external monitor can display
correctly.
--
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/869799
Title:
[Dell inspiron M5110] no output while external VGA is connected
Status in “gnome-settings-daemon” package in Ubuntu:
Confirmed
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
no output while external VGA is connected, hdmi output is fine.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-11-generic 2.6.38-11.50
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 1: Generic_1 [HD-Audio Generic], device 0: STAC92xx Analog [STAC92xx
Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1435 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Generic'/'HD-Audio Generic at 0xff744000 irq 57'
Mixer name : 'ATI R6xx HDMI'
Components : 'HDA:1002aa01,00aa0100,00100200'
Controls : 4
Simple ctrls : 1
Card0.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Card1.Amixer.info:
Card hw:1 'Generic_1'/'HD-Audio Generic at 0xff74 irq 16'
Mixer name : 'IDT 92HD87B1/3'
Components : 'HDA:111d76d1,102804b1,00100205'
Controls : 14
Simple ctrls : 9
Date: Fri Oct 7 03:38:38 2011
HibernationDevice: RESUME=UUID=c0387b11-d7a5-4b41-8687-65b94ee5be3c
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
MachineType: Dell Inc. Inspiron M5110
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic
root=UUID=40a14de6-8af6-45d9-b386-f024d1818675 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-2.6.38-11-generic N/A
linux-backports-modules-2.6.38-11-generic N/A
linux-firmware 1.52
SourcePackage: linux
StagingDrivers: brcm80211
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X16
dmi.board.name: 4IE010
dmi.board.vendor: Dell Inc.
dmi.board.version: X16
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrX16:bd05/31/2011:svnDellInc.:pnInspironM5110:pvrNotSpecified:rvnDellInc.:rn4IE010:rvrX16:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron M5110
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/869799/+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
