[Desktop-packages] [Bug 1965648] Re: Autorotate initiates but doesn't reset in Wayland sessions (Xorg sessions work fine)
Test pass on Ubuntu 23.10.01
[Additonal information]
Ubuntu Version: 23.10.01
Mode: Wayland
Gnome: gnome-42-2204
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1965648
Title:
Autorotate initiates but doesn't reset in Wayland sessions (Xorg
sessions work fine)
Status in Mutter:
New
Status in OEM Priority Project:
New
Status in mutter package in Ubuntu:
Confirmed
Bug description:
In jammy I can get mutter's auto-rotate to switch to portrait mode
("right-up") by rotating the device (this only worked in impish if I
installed the autorotate gnome-shell extension).
However, putting it back into "normal" orientation doesn't put the
screen back in landscape mode. Flipping it around ("left-up") does
swap to the reverse portrait mode, but still can't get back to
"normal" afterward.
running `monitor-sensor` does show the accelerometer orientation
change events (including the "normal" ones) triggering properly, just
the desktop doesn't respond.
Plugging in an external monitor does seem to trigger the desktop to go
back to normal landscape mode.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter 42~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Mar 19 15:41:42 2022
InstallationDate: Installed on 2019-08-17 (945 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: mutter
UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1965648/+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 1936703] Re: screen keyboard doesn't work on authentication window
Test pass on Ubuntu 23.10.01 [Additonal information] Ubuntu Version: 23.10.01 Mode: Wayland Gnome: gnome-42-2204 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1936703 Title: screen keyboard doesn't work on authentication window Status in GNOME Shell: New Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Before reporting the bug, lets me mention my hate about you, abandoned 'onboard'. Bug description: pressing key on screen keyboard doesn't work on authentication window, until you press [Enter]. See screenshot ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 17 04:41:09 2021 EcryptfsInUse: Yes InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent file=/cdrom/preseed/ubuntu.seed quiet splash --- InstallationDate: Installed on 2021-06-17 (29 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1936703/+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 1966637] Re: don't have good text copy method like on android / ios as using touch monitor, firefox snap
Test on Uuntu 23.10.01 the copy and paste behavior is as below: 1. Long any place in the URL, A context will shown up to let user to perform cut, copy, Paste, Paste and Go, Delete, Select All 2. Click "Select All" 3. Click URL again, the same context menu will shown up again. 4. Click "Copy" to copy the link. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966637 Title: don't have good text copy method like on android / ios as using touch monitor, firefox snap Status in OEM Priority Project: New Status in firefox package in Ubuntu: Incomplete Bug description: don't have a good text copy method like on android/ios as using a touch monitor OS: jammy update @ 2022/03/28 firefox snap: 98.0.2-1 r1154 it's not good on URL entry or text entry box on the HTML page. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966637/+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 1966629] Re: swipe up from the bottom of the touch monitor won't bring the OSK
This is partially fixed in Ubuntu 23.10.01 After the launch terminal, OSK will not show automatically. User will need to touch Terminal again, then OSK will show in order to input in Terminal. OS: Ubuntu 23.10.01 Mode: Wayland Gnome: gnome-42-2204 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966629 Title: swipe up from the bottom of the touch monitor won't bring the OSK Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: OS: jammy update on 2022/03/28, Wayland mode, tablet or screen keyboard enable. Steps: 1. touch gnome-terminal and see OSK 2. hide OSK 3. swipe up from the bottom of the touch monitor Expected: OSK re-appears Actually: OSK does not re-appear. Is this by a design change, or a new bug? On focal, can't reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966629/+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 1964091] Re: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor
Pass on Ubuntu 23.04.01 nautilus: 45-rc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964091 Title: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor Status in Nautilus: Fix Released Status in OEM Priority Project: New Status in nautilus package in Ubuntu: New Bug description: Long press/touch a directory won't trigger the context menu for it. OS: 22.04, up to date @ Mar 8, 2022. nautilus: 1:42~beta-1ubuntu1 mode: wayland With a touch monitor, it will be useful if we can do more operation with it. If I long press a file (for about 1 second), a context menu will appear just like we right-click mouse button on it. Then we can do file deleting, copy and move. We can also do the same as we long touch the empty space, and then we can create directory, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+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 1966635] Re: can't move file/directory by drag and drop by using touch monitor
Still fail on Ubuntu 23.10.01 nautilus: 45-rc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+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 1966628] Re: touch on any place that can do text entry won't trigger OSK, libreoffice
The issue could not be reproduced on Ubuntu 23.10 OS: Ubuntu 23.10.01 Liber Office: 7.6.2.1 Mode: Wayland Gnome: gnome-42-2204 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1966628 Title: touch on any place that can do text entry won't trigger OSK, libreoffice Status in OEM Priority Project: New Status in libreoffice package in Ubuntu: New Bug description: OS: jammy (fully updated on 2022/03/28) Libreoffice version: 1:7.3.2~rc1~0ubuntu2 Mode: wayland Screen Keyboard: On gnome-control-center, goes Accessibility, goes Typing. - or, on a 2-in-1 machines, flip more than 180 degree between keyboard and monitor. Touch any place that can do text input, can't see OSK appears. (OSK appears properly as touch on gnome-terminal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966628/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Test pass with Dell DW5821e [413C:81D7] on hirsute * The version of the packages tested: ModemManager: 1.16.6 libmbim: 1.24.8 libqmi: 1.28.6 ** Attachment added: "DW5821e.log" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1934286/+attachment/5520406/+files/DW5821e.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: *
[Desktop-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Test Pass on WWAN Test: https://certification.canonical.com/hardware/202010-28324/submission/223136/ ACPI Stress Test: https://certification.canonical.com/hardware/202010-28324/submission/223167/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the
[Desktop-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.
Test pass on https://certification.canonical.com/hardware/202010-28320/submission/223095/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1934286 Title: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases. Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Focal: Fix Committed Status in libqmi source package in Focal: Fix Committed Status in modemmanager source package in Focal: Fix Committed Status in libmbim source package in Hirsute: Fix Committed Status in libqmi source package in Hirsute: Fix Committed Status in modemmanager source package in Hirsute: Fix Committed Bug description: [Impact] Some IOT products use wireless modems which can be working only when recent versions of the ModemManager suite are used. The following 2 modems need the ModemManager suite to be upgraded: * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The main fix requested is to add the FCC unlock mechanism for Foxconn modems. * FCC unlock operation for Foxconn modems https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits * dms: new 'Foxconn Set FCC authentication' command https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits The minimum versions of the ModemManager suite required to enable the support for the above 2 mentioned modems have been verified: (LP: #1928665) * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 The ModemManager suite in the Impish release meets the requirements. [Test Plan] = How to Reproduce the Bug = Execute the following commands to list the modems detected by ModemManager in Hirsute and Focal releases: $ mmcli --list-modems No modems were found = Test Procedure = 1. Install the Ubuntu system on the tested hardware The following images will be used to verify the version of the ModemManager suite: * Impish: https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso * Focal: https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso 2. Upgrade the kernel and driver ( for Foxconn and Quectel modem ) The kernel needs to get some patches from 5.13 and includes a back ported Quectel driver to support these 2 modems. We have prepared a kernel packages for testing: https://people.canonical.com/~mschiu77/lp1928665/v2/ 3. Install the ModemManager suite ( for Hirsute and Focal releases ) The ModemManager suite will be installed from the -proposed component: $ sudo apt update $ sudo apt install modemmanager $ sudo apt install libqmi-utils 4. Execute the following commands 4.1 Get the run-time environment $ uname -ar $ lsb_release -a $ mmcli -V $ qmicli -V 4.2 Check the status of the ModemManager service $ sudo systemctl status ModemManager.service 4.3 List the detected modems $ mmcli --list-modems 4.4 Check the modem’s status $ mmcli --modem 0 4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only ) $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan- test_amd64.snap 4.6 Enable the detected modem $ sudo mmcli --modem 0 --enable 4.7 Check the modem’s status $ mmcli --modem 0 = Analyze the Tested Result = 1. Check if installed packages are working The result of test procedure 4.1 and 4.2 can be used to make sure the installed packages are working. If the Modemmanager.service is active(running), the packages are working. 2. Check if the supported modem can be detected The result of test procedure 4.3 can be used to see if the modem can be detected by ModemManager or not. The supported modems should be listed. 3. Check if the modem can be enabled If the modem can be enabled, the state of the modem in the test procedure 4.7 will be set to be registered. = Certification Validation = Additionally to the aforementioned test cases, the Certification Team will perform some coverage testing across supported devices to make sure the other modems still work as expected. [Where problems could occur] There is a risk that modems supported in the old versions of ModemManager suite may not be supported in the newer versions. [Other Info] We need to upgrade to these 3 packages (in Impish) at the same time: * ModemManager: 1.16.6 * libmbim: 1.24.8 * libqmi : 1.28.6 To support the mentioned 2 modems, the system needs to use kernels which include specific patches and kernel config options . For ex., there
[Desktop-packages] [Bug 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1897530 Title: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Invalid Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Bug description: [Impact] On a hybrid machine where NVIDIA is rendering the screen, if a display attached to a dock is removed while on suspend mode, on resume X crashes. [Test case] Test hot-unplug during suspend and resume, X shouldn't crash. [Regression potential] This replaces a patch we had with two commits that got merged upstream after a fairly extensive review process: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/ And we ship it in groovy. If there were issues caused by it, they would be around hot-unplugging a dock while on suspend and such. -- Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
The comment#12 is tested on Focal. -- 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/1897530 Title: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Invalid Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Bug description: [Impact] On a hybrid machine where NVIDIA is rendering the screen, if a display attached to a dock is removed while on suspend mode, on resume X crashes. [Test case] Test hot-unplug during suspend and resume, X shouldn't crash. [Regression potential] This replaces a patch we had with two commits that got merged upstream after a fairly extensive review process: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/ And we ship it in groovy. If there were issues caused by it, they would be around hot-unplugging a dock while on suspend and such. -- Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1897530] Re: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
Test WD19TB with Dell Precision 7750 Kernel: 5.6.0-1035-OEM#37 xorg-server (2:1.20.8-2ubuntu2.5) NV driver:450.80.02 The issue is fixed. -- 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/1897530 Title: [modeset][nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Invalid Status in xorg-server-hwe-18.04 source package in Bionic: Confirmed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Bug description: [Impact] On a hybrid machine where NVIDIA is rendering the screen, if a display attached to a dock is removed while on suspend mode, on resume X crashes. [Test case] Test hot-unplug during suspend and resume, X shouldn't crash. [Regression potential] This replaces a patch we had with two commits that got merged upstream after a fairly extensive review process: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/ And we ship it in groovy. If there were issues caused by it, they would be around hot-unplugging a dock while on suspend and such. -- Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1897530] Re: The modesetting driver does not gracefully handle missing connectors on EnterVT
Original bug: https://bugs.launchpad.net/somerville/+bug/1857443 -- 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/1897530 Title: The modesetting driver does not gracefully handle missing connectors on EnterVT Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Invalid Status in xorg-server-hwe-18.04 source package in Bionic: New Status in xorg-server source package in Focal: New Status in xorg-server-hwe-18.04 source package in Focal: Invalid Bug description: [Impact] On a hybrid machine where NVIDIA is rendering the screen, if a display attached to a dock is removed while on suspend mode, on resume X crashes. [Test case] Test hot-unplug during suspend and resume, X shouldn't crash. [Regression potential] This replaces a patch we had with two commits that got merged upstream after a fairly extensive review process: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/443/ And we ship it in groovy. If there were issues caused by it, they would be around hot-unplugging a dock while on suspend and such. -- Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1897530] Re: The modesetting driver does not gracefully handle missing connectors on EnterVT
The “real” fix has been released by Intel and has also been merged. https://gitlab.freedesktop.org/xorg/xserver/-/issues/1010 Could Canonical consider to revert follow temporary patch. 0001-WIP-modesetting-check-the-kms-state-on-EnterVT.patch 0002-WIP-modesetting-do-not-reset-the-mode-on-disconnecte.patch -- 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/1897530 Title: The modesetting driver does not gracefully handle missing connectors on EnterVT Status in xorg-server package in Ubuntu: New Status in xorg-server source package in Focal: New Bug description: Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1897530/+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 1897530] [NEW] The modesetting driver does not gracefully handle missing connectors on EnterVT
Public bug reported: Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu Focal) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1010 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1010 -- 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/1897530 Title: The modesetting driver does not gracefully handle missing connectors on EnterVT Status in xorg-server package in Ubuntu: New Status in xorg-server source package in Focal: New Bug description: Expectation: on removal of external display during S3, after resume eDP rendering should still continue by Nvidia. Symptom description: Plug out DP cable when suspension, when resume, X will crash. 1. Before S3 entry, eDP and external panel(via dock) were driven by Intel but NV was rendering for eDP. 2. After S3 entry dock was removed. 3. On resume, Linux kernel tried to find dock but couldn’t find it, so fails resume of TB3 devices and logs confirm that. 4. X fails to enter VT due to Null meta mode. To address the explanation, X is not failing to enter the VT due to NVIDIA’s NULL MetaMode. It’s the Intel (modesetting) driver that is failing to enter the VT. It’s expected that NVIDIA would have a NULL MetaMode, since there are no displays connected to it. Our driver is pretty robust to head state changes – even if we have to fall back to a NULL MetaMode, we will still enter the VT successfully. The logs clearly show that the failure is originating from the Intel (modesetting) driver, not the NVIDIA driver. The relevant path in X is driver.c:EnterVT() => drmmode_display.c:drmmode_set_desired_modes(). In this function, the Intel driver tries to set a mode on each of the previously connected/enabled displays, and it tries to find the closest possible mode using xf86OutputFindClosestMode(). This is similar to our driver’s functionality, but unlike us, they don’t support a NULL fallback. If there are no modes supported on one of the displays, it simply fails, which causes X to terminate: DisplayModePtr mode = xf86OutputFindClosestMode(output, pScrn->currentMode); if (!mode) return FALSE; Since we removed one of the displays via the dock, it fails. It doesn’t matter if the internal panel is still available, Intel will fail if it can’t re-enable ANY of the previously connected displays. Technically the modesetting driver isn’t specifically an Intel driver, it’s a generic driver that can be used by any DRM device – it’s just that Intel has chosen to use the modesetting driver as their standard Linux X driver going forward. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1847219] Re: HDMI audio lost function after the dGPU did runtime suspend. (AMD RX 580)
5.0 Kernel + following patched [1] + AMD 19.30 driver [2], the issue is fixed. [1] Takashi Iwai's sound component support patch for AMDGPU - https://patchwork.kernel.org/patch/10540417/ [2] AMD 19.30 driver: https://www.amd.com/en/support/kb/release-notes /rn-amdgpu-unified-linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1847219 Title: HDMI audio lost function after the dGPU did runtime suspend. (AMD RX 580) Status in OEM Priority Project: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: On Dell Precision 7740, after installed amdgpu-pro 19.10-793418, the HDMI audio will lose function after the dGPU did runtime suspend. How to check the AMD dGPU is in runtime suspend: $ lspci -s 01:00.0 -xxvv When the AMD dGPU is in runtime suspend, all of the registers will be 0xf. Release: 18.04 LTS kernel: 4.15.0-1037-oem amdgpu-pro: 19.10-793418 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847219/+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 1641889] Re: The network indicator shows the wrong status
** Changed in: oem-priority/xenial Assignee: (unassigned) => Aron Xu (happyaron) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1641889 Title: The network indicator shows the wrong status Status in Network Manager Applet: Unknown Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager-applet package in Ubuntu: Triaged Bug description: [Summary] The network indicator shows the wrong status [Reproduce Steps] 1.Boot into Ubuntu OS , remove wireless connection Note : the issue can't be reproduced with wifi connection 2.Enable/disable wifi function by hotkey the check wifi manager status [Results] Expected: "Enable Wi-Fi" option should be OFF Actual:"Enable Wi-Fi" option is ON [Additional Information] Product Name:Inspiron-7460 BIOS Version:1.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1641889/+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 1651019] Re: nm-applet not show wwan options on menu after logout/in
The issue is fixed in network-manager upstream bug status, the solution was be merged to nm-applet, ver 1.2. cherry-peak the patches to ubuntu's nm-applet package and it works. Need to include those fix to Ubuntu's nm-applet package -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1651019 Title: nm-applet not show wwan options on menu after logout/in Status in Network Manager Applet: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager-applet package in Ubuntu: Triaged Bug description: With DW5811e(EM7455), mobile data connection not show on nm indicator after logout -> login. packages which be used: network-manager: network-manager_1.2.2-0ubuntu0.16.04.3_amd64 nm-applet: network-manager-gnome_1.2.0-0ubuntu0.16.04.4_amd64 Steps to reproduce: 1. boot device with 4G sim card + DW5811e(EM7455) wwan card 2. check nm-applet indicator then "Mobile Braodband" could be found in menu in normal cases. 3. logout then login 4. check nm-applet indicator then "Mobile Braodband" not shows in menu anymore. 5. but still could connect to wwan by nmcli, so looks device and networkmanager work fine. investigation: * In nm-applet, it caused by device-added signal comes before mm_new_ready() which is the call back of mm_manager_new(). And that asynchronous way was added by 408b88cc (Dan Williams 2014-05-01: http://paste.ubuntu.com/23639247/ * revert 408b88cc fixed this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1651019/+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 1651019] Re: nm-applet not show wwan options on menu after logout/in
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority/xenial Importance: Undecided => High ** Changed in: oem-priority/xenial Assignee: (unassigned) => Aron Xu (happyaron) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1651019 Title: nm-applet not show wwan options on menu after logout/in Status in Network Manager Applet: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager-applet package in Ubuntu: Triaged Bug description: With DW5811e(EM7455), mobile data connection not show on nm indicator after logout -> login. packages which be used: network-manager: network-manager_1.2.2-0ubuntu0.16.04.3_amd64 nm-applet: network-manager-gnome_1.2.0-0ubuntu0.16.04.4_amd64 Steps to reproduce: 1. boot device with 4G sim card + DW5811e(EM7455) wwan card 2. check nm-applet indicator then "Mobile Braodband" could be found in menu in normal cases. 3. logout then login 4. check nm-applet indicator then "Mobile Braodband" not shows in menu anymore. 5. but still could connect to wwan by nmcli, so looks device and networkmanager work fine. investigation: * In nm-applet, it caused by device-added signal comes before mm_new_ready() which is the call back of mm_manager_new(). And that asynchronous way was added by 408b88cc (Dan Williams 2014-05-01: http://paste.ubuntu.com/23639247/ * revert 408b88cc fixed this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1651019/+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 1641889] Re: The network indicator shows the wrong status
It's being merged into master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=0d7bf7dee31175d3eeab2bd5a9eef8e7b6618016 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1641889 Title: The network indicator shows the wrong status Status in Network Manager Applet: Unknown Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager-applet package in Ubuntu: Triaged Bug description: [Summary] The network indicator shows the wrong status [Reproduce Steps] 1.Boot into Ubuntu OS , remove wireless connection Note : the issue can't be reproduced with wifi connection 2.Enable/disable wifi function by hotkey the check wifi manager status [Results] Expected: "Enable Wi-Fi" option should be OFF Actual:"Enable Wi-Fi" option is ON [Additional Information] Product Name:Inspiron-7460 BIOS Version:1.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1641889/+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 1641889] Re: The network indicator shows the wrong status
** Changed in: oem-priority/xenial Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1641889 Title: The network indicator shows the wrong status Status in Network Manager Applet: Unknown Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager-applet package in Ubuntu: Triaged Bug description: [Summary] The network indicator shows the wrong status [Reproduce Steps] 1.Boot into Ubuntu OS , remove wireless connection Note : the issue can't be reproduced with wifi connection 2.Enable/disable wifi function by hotkey the check wifi manager status [Results] Expected: "Enable Wi-Fi" option should be OFF Actual:"Enable Wi-Fi" option is ON [Additional Information] Product Name:Inspiron-7460 BIOS Version:1.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1641889/+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 1641889] Re: The network indicator shows the wrong status
The original issue is reported against Xenial. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1641889 Title: The network indicator shows the wrong status Status in Network Manager Applet: Unknown Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager-applet package in Ubuntu: Confirmed Bug description: [Summary] The network indicator shows the wrong status [Reproduce Steps] 1.Boot into Ubuntu OS , remove wireless connection Note : the issue can't be reproduced with wifi connection 2.Enable/disable wifi function by hotkey the check wifi manager status [Results] Expected: "Enable Wi-Fi" option should be OFF Actual:"Enable Wi-Fi" option is ON [Additional Information] Product Name:Inspiron-7460 BIOS Version:1.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1641889/+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 1641889] Re: The network indicator shows the wrong status
Tested Zesty daily build 2016-12-02 the issue still could be reproduced. The "Enable Wifi" in pull downlist will not reflect the wifi status time to time if use hotkey to enable and disable wifi. Network manager version: network-manager 1.2.4-0ubuntu1 network-manager-gnome 1.2.4-0ubuntu2 network-manager-openvpn 1.2.6-2ubuntu1 network-manager-pptp 1.2.4-1 network-manager-pptp-gnome 1.2.4-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1641889 Title: The network indicator shows the wrong status Status in Network Manager Applet: Unknown Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager-applet package in Ubuntu: Confirmed Bug description: [Summary] The network indicator shows the wrong status [Reproduce Steps] 1.Boot into Ubuntu OS , remove wireless connection Note : the issue can't be reproduced with wifi connection 2.Enable/disable wifi function by hotkey the check wifi manager status [Results] Expected: "Enable Wi-Fi" option should be OFF Actual:"Enable Wi-Fi" option is ON [Additional Information] Product Name:Inspiron-7460 BIOS Version:1.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1641889/+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 1641889] Re: The network indicator shows the wrong status
This issue can be reproduced on Yakkety live image, which uses, network-manager 1.2.2-0ubuntu6 network-manager-gnome 1.2.2-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1641889 Title: The network indicator shows the wrong status Status in Network Manager Applet: Unknown Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager-applet package in Ubuntu: Incomplete Bug description: [Summary] The network indicator shows the wrong status [Reproduce Steps] 1.Boot into Ubuntu OS , remove wireless connection Note : the issue can't be reproduced with wifi connection 2.Enable/disable wifi function by hotkey the check wifi manager status [Results] Expected: "Enable Wi-Fi" option should be OFF Actual:"Enable Wi-Fi" option is ON [Additional Information] Product Name:Inspiron-7460 BIOS Version:1.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1641889/+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 1645065] Re: gnome-software (Ubuntu Software) crashed after system update on Xenial
** Also affects: gnome-software Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1645065 Title: gnome-software (Ubuntu Software) crashed after system update on Xenial Status in GNOME Software: New Status in OEM Priority Project: New Status in gnome-software package in Ubuntu: New Bug description: Ubuntu Xenial [Step to Reproduce] 1. install the system 2. click the dash to launch "system updater" GUI 3. update the system with GUI ( so I could update the system to 4.4.0-47-generic #68-Ubuntu) 4. reboot 5. after reboot, click the Ubuntu Software icon on the launcher. [Expected Result] Ubuntu Software is opened and ready to use. [Actual Result] Ubuntu Software could not be opened. dmesg shows: [ 616.684884] do_trap: 45 callbacks suppressed [ 616.684895] traps: pool[4815] trap int3 ip:7f9620707a6b sp:7f95fe0375b0 error:0 [ 1269.764553] traps: gnome-software[6688] trap int3 ip:7f62fd88ba6b sp:7ffdb0921d00 error:0 [ 1718.319194] traps: gnome-software[8640] trap int3 ip:7ffb5c6a7a6b sp:7ffde6130e60 error:0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.20.1+git20160426.1.a976144-ubuntu-xenial-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 27 10:39:22 2016 InstallationDate: Installed on 2016-04-22 (218 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1645065/+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 1641889] Re: The network indicator shows the wrong status
** Also affects: network-manager-applet Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Importance: Critical => High ** Also affects: oem-priority/xenial Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1641889 Title: The network indicator shows the wrong status Status in Network Manager Applet: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager-applet package in Ubuntu: Confirmed Bug description: [Summary] The network indicator shows the wrong status [Reproduce Steps] 1.Boot into Ubuntu OS , remove wireless connection Note : the issue can't be reproduced with wifi connection 2.Enable/disable wifi function by hotkey the check wifi manager status [Results] Expected: "Enable Wi-Fi" option should be OFF Actual:"Enable Wi-Fi" option is ON [Additional Information] Product Name:Inspiron-7460 BIOS Version:1.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1641889/+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 1560162] Re: Xenial: scaling is horribly out on xps13 install session
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1560162 Title: Xenial: scaling is horribly out on xps13 install session Status in OEM Priority Project: New Status in metacity package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Confirmed Bug description: STEPS: Requirements laptop desktop with a hidpi screen (Here xps 13) 1. Grab the latest daily image and trigger an install 2. On the first page notice the of centre and over scaled window EXPECTED: I expect to see something resembling a normal scaled desktop install ACTUAL: Things are not quite correct see attached screenshots ubiquity/xenial 2.21.49 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1560162/+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 1585863] Re: WiFi malfunction after suspend & resume stress
** Also affects: network-manager Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/xenial Importance: Undecided Status: New ** Changed in: oem-priority/xenial Importance: Undecided => Critical ** Changed in: oem-priority Importance: Undecided => Critical -- 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/1585863 Title: WiFi malfunction after suspend & resume stress Status in NetworkManager: New Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: New Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=10 --s3-max-delay=10 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1562822] Re: Bluetooth Browse Files... not working
** Changed in: oem-priority Status: Won't Fix => 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/1562822 Title: Bluetooth Browse Files... not working Status in OEM Priority Project: New Status in indicator-bluetooth package in Ubuntu: In Progress Status in unity-control-center package in Ubuntu: In Progress Bug description: * Impact The bluetooth settings include a non working "browse files..." items * Test case connect/pair a phone which does obex, open settings->bluetooth, the only action listed should be "send" * Regression potential none, it's removing a widget which was doing nothing -- Mobile phone: LG L40 Android 4.4.2 1. Connecting to Phone is successful shown. 2. Click on Button "Browse Files... " nothing happen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 28 13:31:39 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2016-02-04 (52 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1562822/+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 1574347] Re: WiFi network list disappears from network manager applet
** Changed in: oem-priority Importance: Undecided => Critical -- 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/1574347 Title: WiFi network list disappears from network manager applet Status in NetworkManager: Fix Released Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Confirmed Bug description: Issue is in Ubuntu 16.04 LTS amd64 version. Steps to reproduce: - 1. Connect to a WiFi AP. 2. Switch off the AP OR switch off the wifi in the computer. 3. Switch point (2) back on. 4. The network will get connected to the AP it was connected to in point (1). Problems:- 1. The network manager applet does not show the list of WiFI APs it can find. 2. The network manager applet does not the name of the AP to which it is connected 3. The icon of the applet shows two vertical arrows in opposite direction - the wired connection symbol and NOT the wifi connected icon. Temporary Workaround:- Log out and again log back in. Please solve this issue asap. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 23:15:34 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp18s0 proto static metric 600 169.254.0.0/16 dev wlp18s0 scope link metric 1000 192.168.1.0/24 dev wlp18s0 proto kernel scope link src 192.168.1.99 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Airtel-201 d263b201-9281-427e-94e2-762fa620813c 802-11-wireless 1461519922 Sunday 24 April 2016 11:15:22 PM IST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp18s0 activated /org/freedesktop/NetworkManager/ActiveConnection/8 Wired connection 1 142942d4-d247-4880-9bab-1eeafc29ca86 802-3-ethernet 1461508904 Sunday 24 April 2016 08:11:44 PM IST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp18s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 Airtel-201 d263b201-9281-427e-94e2-762fa620813c /org/freedesktop/NetworkManager/ActiveConnection/8 enp19s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1490937] Re: Unavailable port selected by default
** Also affects: pulseaudio 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 -- 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/1490937 Title: Unavailable port selected by default Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Bug description: In case one card has only unavailable ports, it might be still be selected as default, even though there are available ports on other cards. E g, on a HTPC which have only Headphone and HDMI outputs, and these two outputs are on separate cards, the headphone port might be selected even if the HDMI port is available and the headphone port is not. Probably PulseAudio's routing system needs to be rewritten to be more port based to fix this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1490937/+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 1376540] [NEW] All wireless access points are not list on System Settings /Network/Wireless when change the Wireless button from off to on.
Public bug reported: When turn off wireless from settingsNetwork and then turn it on again, the AP list does not refresh. There is no options in the list. But wireless function does enable and work. Still can see available AP in top menu net work icon and establish connection without problem. When click any AP (SSID) in top menu, the list in Network interface will flash. Can see available AP in the interface. Step to reproduce: 1. Make sure system does not connect to any wireless access point. 2. Go to settingsNetwork 3. Change wireless button to off, verify there is not list access point. 4. Change wireless button to on, the AP list does not refresh ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1376540 Title: All wireless access points are not list on System Settings /Network/Wireless when change the Wireless button from off to on. Status in “network-manager-applet” package in Ubuntu: New Bug description: When turn off wireless from settingsNetwork and then turn it on again, the AP list does not refresh. There is no options in the list. But wireless function does enable and work. Still can see available AP in top menu net work icon and establish connection without problem. When click any AP (SSID) in top menu, the list in Network interface will flash. Can see available AP in the interface. Step to reproduce: 1. Make sure system does not connect to any wireless access point. 2. Go to settingsNetwork 3. Change wireless button to off, verify there is not list access point. 4. Change wireless button to on, the AP list does not refresh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1376540/+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 1354987] Re: Can not stop wired network via All Setting-Network-Wired on Ubuntu OS
** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Description changed: - Config an UUT and DASH Ubuntu OS. - After DASH pass and go through OOBE to desktop, connect wired network cable to the UUT, and then open All Setting-Network-Wired, find that the wired network can not be stopped. + Install Ubuntu 14.04 on the machine. + After installation complete and go through OOBE to desktop, connect wired network cable to the UUT, and then open All Setting-Network-Wired, find that the wired network can not be stopped. Please see the attached file for detail. Note: 1 .Ubuntu 14.04 LTS 2. Can start or stop wired network via check or uncheck Enable Networking item at the top right corner. Steps to Reproduce: - 1.Config an UUT,DASH a Ubuntu OS. + 1.Install Ubuntu 14.04 on the machine. 2.Go through OOBE to desktop. 3.Connect wired network,try to stop wired network atAll Setting-Network-Wired. -- 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/1354987 Title: Can not stop wired network via All Setting-Network-Wired on Ubuntu OS Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “network-manager” package in Ubuntu: New Bug description: Install Ubuntu 14.04 on the machine. After installation complete and go through OOBE to desktop, connect wired network cable to the UUT, and then open All Setting-Network-Wired, find that the wired network can not be stopped. Please see the attached file for detail. Note: 1 .Ubuntu 14.04 LTS 2. Can start or stop wired network via check or uncheck Enable Networking item at the top right corner. Steps to Reproduce: 1.Install Ubuntu 14.04 on the machine. 2.Go through OOBE to desktop. 3.Connect wired network,try to stop wired network atAll Setting-Network-Wired. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1354987/+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 1354987] Re: Can not stop wired network via All Setting-Network-Wired on Ubuntu OS
** Changed in: oem-priority Importance: Undecided = Medium ** Changed in: oem-priority/trusty Importance: Undecided = Medium -- 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/1354987 Title: Can not stop wired network via All Setting-Network-Wired on Ubuntu OS Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “network-manager” package in Ubuntu: New Bug description: Install Ubuntu 14.04 on the machine. After installation complete and go through OOBE to desktop, connect wired network cable to the UUT, and then open All Setting-Network-Wired, find that the wired network can not be stopped. Please see the attached file for detail. Note: 1 .Ubuntu 14.04 LTS 2. Can start or stop wired network via check or uncheck Enable Networking item at the top right corner. Steps to Reproduce: 1.Install Ubuntu 14.04 on the machine. 2.Go through OOBE to desktop. 3.Connect wired network,try to stop wired network atAll Setting-Network-Wired. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1354987/+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 1069964] Re: Unable to mount Blank CD-R disc. Location is already mounted.
** 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-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Unable to mount Blank CD-R disc. Location is already mounted. Status in OEM Priority Project: New Status in “glib2.0” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1069964/+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
** Also affects: xorg-server Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = Critical ** Changed in: oem-priority Importance: Critical = High -- 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: Triaged Status in OEM Priority Project: New 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: In Progress Status in “xorg-server” source package in Saucy: Fix Committed Status in “xorg-server” source package in Trusty: Fix Released 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 1318875] Re: Airplane mode cannot save the previous status after reboot
** Also affects: gnome-control-center Importance: Undecided Status: New ** Also affects: oem-priority 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/1318875 Title: Airplane mode cannot save the previous status after reboot Status in GNOME Control Center: New Status in OEM Priority Project: New Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: Airplane mode cannot save the previous status after reboot. Steps to reproduce: 1. open network settings 2. turn on airplane mode 3. reboot - issue occurs, airplane mode is off --- ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-daan2-precise-amd64-20140502-1 DistroRelease: Ubuntu 12.04 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 20140502-06:48 MarkForUpload: True NonfreeKernelModules: nvidia Package: gnome-control-center 1:3.4.2-0ubuntu0.13.1stella1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Tags: precise running-unity Uname: Linux 3.11.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3.2 deja-dup22.0-0ubuntu4 gnome-bluetooth 3.2.2-0ubuntu5.1stella2 indicator-datetime 0.3.94-0ubuntu2 --- To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1318875/+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 1158296] Re: Systems with AMD 6660 discrete will hang up while doing poweroff and reboot tests by pm_test tool.
@ Jammy, HP Pavilion 15 Notebook PC. ** Attachment added: pm_test https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1158296/+attachment/3589613/+files/pm_test -- 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/1158296 Title: Systems with AMD 6660 discrete will hang up while doing poweroff and reboot tests by pm_test tool. Status in amd: New Status in “fglrx-installer” package in Ubuntu: New Bug description: Steps to Reproduce: 1. GM -B21 image, go through OOBE,boot into OS. 2. Copy pm_test file to Home Folder, open terminal to run sudo python pm_test -r 30 poweroff command. 3. After 20 minutes, find system hang up with backlight off. Oops: Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080151] Hardware name: HP Pavilion 15 Notebook PC Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080152] kobject_add_internal failed for msi_irqs with -EEXIST, don't try to register things with the same name in the same directory. Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080153] Modules linked in: fglrx(PO) amd_iommu_v2 snd_hda_codec_hdmi(O) snd_hda_codec_realtek(O) coretemp kvm ghash_clmulni_intel cryptd joydev hp_wmi sparse_keymap dm_multipath scsi_dh microcode snd_hda_intel(O) snd_hda_codec(O) snd_hwdep hp_accel snd_pcm lis3lv02d input_polldev uvcvideo videobuf2_core videodev videobuf2_vmalloc videobuf2_memops snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq wmi(O) rfcomm snd_timer snd_seq_device mac_hid psmouse serio_raw i915 snd drm_kms_helper parport_pc bnep drm soundcore i2c_algo_bit ppdev lpc_ich bluetooth video snd_page_alloc mei lp parport binfmt_misc r8169 dm_raid45 xor dm_mirror dm_region_hash dm_log btrfs zlib_deflate libcrc32c [last unloaded: amd_iommu_v2] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080177] Pid: 1328, comm: Xorg Tainted: P W O 3.5.0-22-generic #33~precise1-Ubuntu Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080178] Call Trace: Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080180] [81052c9f] warn_slowpath_common+0x7f/0xc0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080182] [81052d96] warn_slowpath_fmt+0x46/0x50 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080185] [811f8dee] ? release_sysfs_dirent+0x7e/0x100 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080187] [81332594] kobject_add_internal+0x1f4/0x210 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080189] [81332ac8] ? kobject_set_name+0x38/0x40 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080191] [813328a6] kset_register+0x46/0x70 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080193] [81332b46] kset_create_and_add+0x76/0xb0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080195] [81373d4e] populate_msi_sysfs+0x2e/0x120 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080197] [8137433f] msi_capability_init+0x12f/0x1f0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080199] [81374510] pci_enable_msi_block+0x90/0xe0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080222] [a02d9c93] KCL_RequestMSI+0x13/0x20 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080254] [a02fa9ff] IRQMGR_initialize+0x24f/0x380 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080285] [a02fa757] ? IRQMGR_alloc_context+0xb7/0x110 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080317] [a02f992e] ? irqmgr_wrap_initialize+0x1e/0xb0 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080348] [a02fa5c5] ? firegl_irqmgr_init+0x55/0x100 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080381] [a030b3ff] ? hal_init_gpu+0x1cf/0x480 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080409] [a02e687b] ? firegl_open+0x2db/0x310 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080430] [a02d6b27] ? ip_firegl_open+0x17/0x20 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080450] [a02d5f7e] ? firegl_stub_open+0xae/0x120 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080453] [8118bd92] ? chrdev_open+0xb2/0x1a0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080455] [8118bce0] ? cdev_put+0x30/0x30 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080457] [811855ee] ? do_dentry_open+0x22e/0x2b0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080459] [81186b48] ? __dentry_open+0x18/0x70 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080461]
[Desktop-packages] [Bug 1158296] Re: Systems with AMD 6660 discrete will hang up while doing poweroff and reboot tests by pm_test tool.
@ Jimmy, The tool is attached in last command. ** Attachment added: stress_test_guide.pdf https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1158296/+attachment/3589614/+files/stress_test_guide.pdf -- 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/1158296 Title: Systems with AMD 6660 discrete will hang up while doing poweroff and reboot tests by pm_test tool. Status in amd: New Status in “fglrx-installer” package in Ubuntu: New Bug description: Steps to Reproduce: 1. GM -B21 image, go through OOBE,boot into OS. 2. Copy pm_test file to Home Folder, open terminal to run sudo python pm_test -r 30 poweroff command. 3. After 20 minutes, find system hang up with backlight off. Oops: Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080151] Hardware name: HP Pavilion 15 Notebook PC Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080152] kobject_add_internal failed for msi_irqs with -EEXIST, don't try to register things with the same name in the same directory. Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080153] Modules linked in: fglrx(PO) amd_iommu_v2 snd_hda_codec_hdmi(O) snd_hda_codec_realtek(O) coretemp kvm ghash_clmulni_intel cryptd joydev hp_wmi sparse_keymap dm_multipath scsi_dh microcode snd_hda_intel(O) snd_hda_codec(O) snd_hwdep hp_accel snd_pcm lis3lv02d input_polldev uvcvideo videobuf2_core videodev videobuf2_vmalloc videobuf2_memops snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq wmi(O) rfcomm snd_timer snd_seq_device mac_hid psmouse serio_raw i915 snd drm_kms_helper parport_pc bnep drm soundcore i2c_algo_bit ppdev lpc_ich bluetooth video snd_page_alloc mei lp parport binfmt_misc r8169 dm_raid45 xor dm_mirror dm_region_hash dm_log btrfs zlib_deflate libcrc32c [last unloaded: amd_iommu_v2] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080177] Pid: 1328, comm: Xorg Tainted: P W O 3.5.0-22-generic #33~precise1-Ubuntu Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080178] Call Trace: Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080180] [81052c9f] warn_slowpath_common+0x7f/0xc0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080182] [81052d96] warn_slowpath_fmt+0x46/0x50 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080185] [811f8dee] ? release_sysfs_dirent+0x7e/0x100 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080187] [81332594] kobject_add_internal+0x1f4/0x210 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080189] [81332ac8] ? kobject_set_name+0x38/0x40 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080191] [813328a6] kset_register+0x46/0x70 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080193] [81332b46] kset_create_and_add+0x76/0xb0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080195] [81373d4e] populate_msi_sysfs+0x2e/0x120 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080197] [8137433f] msi_capability_init+0x12f/0x1f0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080199] [81374510] pci_enable_msi_block+0x90/0xe0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080222] [a02d9c93] KCL_RequestMSI+0x13/0x20 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080254] [a02fa9ff] IRQMGR_initialize+0x24f/0x380 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080285] [a02fa757] ? IRQMGR_alloc_context+0xb7/0x110 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080317] [a02f992e] ? irqmgr_wrap_initialize+0x1e/0xb0 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080348] [a02fa5c5] ? firegl_irqmgr_init+0x55/0x100 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080381] [a030b3ff] ? hal_init_gpu+0x1cf/0x480 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080409] [a02e687b] ? firegl_open+0x2db/0x310 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080430] [a02d6b27] ? ip_firegl_open+0x17/0x20 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080450] [a02d5f7e] ? firegl_stub_open+0xae/0x120 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080453] [8118bd92] ? chrdev_open+0xb2/0x1a0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080455] [8118bce0] ? cdev_put+0x30/0x30 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080457] [811855ee] ? do_dentry_open+0x22e/0x2b0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080459] [81186b48] ? __dentry_open+0x18/0x70 Feb 1 14:19:28
[Desktop-packages] [Bug 1158296] Re: Systems with AMD 6660 discrete will hang up while doing poweroff and reboot tests by pm_test tool.
@ Jammy, Test steps: 1. Copy pm_test file to Home Folder, open terminal to run sudo python pm_test -r 30 poweroff command. 2. After 20 minutes, find system hang up with backlight off. OS: Ubuntu 12.04.02 Kernel: 3.5.0-23-generic #35 AMD Driver: 12.102RC1. -- 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/1158296 Title: Systems with AMD 6660 discrete will hang up while doing poweroff and reboot tests by pm_test tool. Status in amd: New Status in “fglrx-installer” package in Ubuntu: New Bug description: Steps to Reproduce: 1. GM -B21 image, go through OOBE,boot into OS. 2. Copy pm_test file to Home Folder, open terminal to run sudo python pm_test -r 30 poweroff command. 3. After 20 minutes, find system hang up with backlight off. Oops: Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080151] Hardware name: HP Pavilion 15 Notebook PC Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080152] kobject_add_internal failed for msi_irqs with -EEXIST, don't try to register things with the same name in the same directory. Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080153] Modules linked in: fglrx(PO) amd_iommu_v2 snd_hda_codec_hdmi(O) snd_hda_codec_realtek(O) coretemp kvm ghash_clmulni_intel cryptd joydev hp_wmi sparse_keymap dm_multipath scsi_dh microcode snd_hda_intel(O) snd_hda_codec(O) snd_hwdep hp_accel snd_pcm lis3lv02d input_polldev uvcvideo videobuf2_core videodev videobuf2_vmalloc videobuf2_memops snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq wmi(O) rfcomm snd_timer snd_seq_device mac_hid psmouse serio_raw i915 snd drm_kms_helper parport_pc bnep drm soundcore i2c_algo_bit ppdev lpc_ich bluetooth video snd_page_alloc mei lp parport binfmt_misc r8169 dm_raid45 xor dm_mirror dm_region_hash dm_log btrfs zlib_deflate libcrc32c [last unloaded: amd_iommu_v2] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080177] Pid: 1328, comm: Xorg Tainted: P W O 3.5.0-22-generic #33~precise1-Ubuntu Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080178] Call Trace: Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080180] [81052c9f] warn_slowpath_common+0x7f/0xc0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080182] [81052d96] warn_slowpath_fmt+0x46/0x50 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080185] [811f8dee] ? release_sysfs_dirent+0x7e/0x100 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080187] [81332594] kobject_add_internal+0x1f4/0x210 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080189] [81332ac8] ? kobject_set_name+0x38/0x40 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080191] [813328a6] kset_register+0x46/0x70 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080193] [81332b46] kset_create_and_add+0x76/0xb0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080195] [81373d4e] populate_msi_sysfs+0x2e/0x120 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080197] [8137433f] msi_capability_init+0x12f/0x1f0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080199] [81374510] pci_enable_msi_block+0x90/0xe0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080222] [a02d9c93] KCL_RequestMSI+0x13/0x20 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080254] [a02fa9ff] IRQMGR_initialize+0x24f/0x380 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080285] [a02fa757] ? IRQMGR_alloc_context+0xb7/0x110 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080317] [a02f992e] ? irqmgr_wrap_initialize+0x1e/0xb0 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080348] [a02fa5c5] ? firegl_irqmgr_init+0x55/0x100 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080381] [a030b3ff] ? hal_init_gpu+0x1cf/0x480 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080409] [a02e687b] ? firegl_open+0x2db/0x310 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080430] [a02d6b27] ? ip_firegl_open+0x17/0x20 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080450] [a02d5f7e] ? firegl_stub_open+0xae/0x120 [fglrx] Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080453] [8118bd92] ? chrdev_open+0xb2/0x1a0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080455] [8118bce0] ? cdev_put+0x30/0x30 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080457] [811855ee] ? do_dentry_open+0x22e/0x2b0 Feb 1 14:19:28 sit-HP-Pavilion-15-Notebook-PC kernel: [ 11.080459] [81186b48] ?
[Desktop-packages] [Bug 1071561] Re: [sound-nua] Bluetooth device not listed if change mode to Off
@ James, Nara help test it. It is good for OEM. Thank you. -- 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/1071561 Title: [sound-nua] Bluetooth device not listed if change mode to Off Status in GNOME Control Center: New Status in OEM Priority Project: Fix Committed 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: users can turn off bluetooth devices without being able to turn them back on * Test Case: - connect a bluetooth audio device (headset for example) - go to system settings - sound (under Unity) - look at the profiles for the bluetooth device off shouldn't be listed * Regression potential: limited, check that other profiles are listed are they should - I've accidentally changed the operation mode of my Bluetooth phone from A2DP to Off, then the device is removed from the list. Instead, it should be marked as disabled, and kept on list, so I could reactivate it later. To reactivate, I needed to install tdbtools, open tdb file that store this settings (pulseaudio), then remove my device from records. After that, the device was listed again on Sound Settings as A2DP sound output. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1071561/+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 1041432] Re: cheese and camorama freeze system when recording video
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/quantal Importance: Undecided Status: New ** Also affects: oem-priority/r-series Importance: Undecided Status: New ** Changed in: oem-priority/quantal Importance: Undecided = High ** Changed in: oem-priority/r-series Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1041432 Title: cheese and camorama freeze system when recording video Status in OEM Priority Project: New Status in OEM Priority Project quantal series: New Status in OEM Priority Project r-series series: New Status in “cheese” package in Ubuntu: Confirmed Bug description: Quantal 3.5.0-11 becomes totally unresponsive when starting a video from the built in webcam. Both mouse and keyboard are frozen. I tried both 32 and 64 bit versions of both cheese and camorama and the result was the same. This was not an issue with Precise. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cheese 3.5.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic i686 NonfreeKernelModules: wl ApportVersion: 2.5.1-0ubuntu2 Architecture: i386 Date: Fri Aug 24 21:57:00 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) SourcePackage: cheese UpgradeStatus: Upgraded to quantal on 2012-08-17 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1041432/+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 1071922] Re: double tap does not open folders or files in Nautilus
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/quantal Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = Medium ** Changed in: oem-priority/quantal Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1071922 Title: double tap does not open folders or files in Nautilus Status in Nautilus: New Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in OEM Priority Project quantal series: New Status in Ubuntu on the Nexus 7: Confirmed Status in “nautilus” package in Ubuntu: Confirmed Bug description: On the Nexus7 device double-tapping does not work in Nautilus. Even single taps are not always registered. In thunar navigating via double tap works fine. The mouse settings panel's double tap timeout test works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1071922/+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 1071561] Re: [sound-nua] Bluetooth device not listed if change mode to Off
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = Medium ** Changed in: oem-priority Importance: Undecided = Medium -- 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/1071561 Title: [sound-nua] Bluetooth device not listed if change mode to Off 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: I've accidentally changed the operation mode of my Bluetooth phone from A2DP to Off, then the device is removed from the list. Instead, it should be marked as disabled, and kept on list, so I could reactivate it later. To reactivate, I needed to install tdbtools, open tdb file that store this settings (pulseaudio), then remove my device from records. After that, the device was listed again on Sound Settings as A2DP sound output. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.5 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Thu Oct 25 23:36:30 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to precise on 2012-04-24 (184 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1071561/+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 951827] Re: Power Statistics window blank
Hi James, Please see the comment #19. Nara has tested it and confirm it is fixed. -- 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/951827 Title: Power Statistics window blank Status in Gnome Powermanager: Fix Released Status in OEM Priority Project: Confirmed Status in OEM Priority Project precise series: Confirmed Status in “gnome-power-manager” package in Ubuntu: Fix Released Status in “gnome-power-manager” source package in Precise: Fix Committed Bug description: [Summary] Patch: https://code.launchpad.net/~ossug-hychen/ubuntu/precise/gnome- power-manager/fix-951827 bzr branch: lp:~ossug-hychen/ubuntu/precise/gnome-power- manager/fix-951827 [IMPACT] * To precise users, their Power Statistics often gets completely blank. No buttons, no information, nothing! It doesn't fix itself by closing the window and reopen it. [TESTCASE] 1. open power statics window from power indicator 2. close and reopen power statics window several times 3. after step2, the power statics window displays information correctly [Regression Potential] * the patch is from upstream git repository and already include in quntal gnome-power-manager package, so the risk should be low. [Original Report] The Power Statistics often gets completely blank. No buttons, no information, nothing! It doesn't fix itself by closing the window and reopen it. Steps to reproduce: 1. Open the Power Statistics dialog from the power indicator. The windows appears normal. 2. Close using the close button in the lower right. 3. Reopen the window. The window appears normal. 4. Close using either the Launcher item or the title bar close button. 5. Reopen the window. The window is blank. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/951827/+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 1032433] Re: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
@James, I have asked Nara help to provide more information in comment#4 and comment#5 -- 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/1032433 Title: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established Status in OEM Priority Project: Incomplete Status in OEM Priority Project precise series: Incomplete Status in “network-manager” package in Ubuntu: Incomplete Bug description: When setting up an ad-hoc wifi connection, if choose WEP 128-bit Passphrase, the connection cannot be established. If choose None or WEP 40/128-bit Key, it can be established successfully. Steps to reproduce: 1. Choose Create new Wireless Network in network applet 2. Choose WEP 128-bit Passphrase and create an ad-hoc connection 3. Use another computer to connect the same ad-hoc ESSID 4. The connection cannot be established To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1032433/+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 853137] Re: The page 'gkr-keyring' was not found in the document 'ghelpseahorse'.
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = Medium ** Changed in: oem-priority Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/853137 Title: The page 'gkr-keyring' was not found in the document 'ghelpseahorse'. Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in Seahorse: New Status in “seahorse” package in Ubuntu: Triaged Bug description: seahorse (Passsword and Keyss) [tab] Passwords Passwors: default [right-click] Properties Passwords:default (dialog window Passwords:default) Keyring Name:=default, Created:=(empty) Help (Help) PageNotFound: The page 'gkr- keyring' was not found in the document 'ghelpseahorse'. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: seahorse 3.1.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-server 3.0.4 Uname: Linux 3.0.0-11-server x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Sun Sep 18 12:12:06 2011 InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 (20110426) ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: seahorse UpgradeStatus: Upgraded to oneiric on 2011-08-28 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/853137/+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 1032433] [NEW] Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
Public bug reported: When setting up an ad-hoc wifi connection, if choose WEP 128-bit Passphrase, the connection cannot be established. If choose None or WEP 40/128-bit Key, it can be established successfully. Steps to reproduce: 1. Choose Create new Wireless Network in network applet 2. Choose WEP 128-bit Passphrase and create an ad-hoc connection 3. Use another computer to connect the same ad-hoc ESSID 4. The connection cannot be established ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1032433 Title: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established Status in “network-manager” package in Ubuntu: New Bug description: When setting up an ad-hoc wifi connection, if choose WEP 128-bit Passphrase, the connection cannot be established. If choose None or WEP 40/128-bit Key, it can be established successfully. Steps to reproduce: 1. Choose Create new Wireless Network in network applet 2. Choose WEP 128-bit Passphrase and create an ad-hoc connection 3. Use another computer to connect the same ad-hoc ESSID 4. The connection cannot be established To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1032433/+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 1032433] Re: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = High -- 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/1032433 Title: Using WEP 128-bit Passphrase, Ad-hoc connection cannot be established Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “network-manager” package in Ubuntu: New Bug description: When setting up an ad-hoc wifi connection, if choose WEP 128-bit Passphrase, the connection cannot be established. If choose None or WEP 40/128-bit Key, it can be established successfully. Steps to reproduce: 1. Choose Create new Wireless Network in network applet 2. Choose WEP 128-bit Passphrase and create an ad-hoc connection 3. Use another computer to connect the same ad-hoc ESSID 4. The connection cannot be established To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1032433/+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 951827] Re: Power Statistics window blank
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = High -- 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/951827 Title: Power Statistics window blank Status in OEM Priority Project: New Status in “gnome-power-manager” package in Ubuntu: Triaged Bug description: The Power Statistics often gets completely blank. No buttons, no information, nothing! It doesn't fix itself by closing the window and reopen it. Steps to reproduce: 1. Open the Power Statistics dialog from the power indicator. The windows appears normal. 2. Close using the close button in the lower right. 3. Reopen the window. The window appears normal. 4. Close using either the Launcher item or the title bar close button. 5. Reopen the window. The window is blank. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/951827/+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 1011436] Re: Sound recorder can not play after recording and saving the first one
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-media in Ubuntu. https://bugs.launchpad.net/bugs/1011436 Title: Sound recorder can not play after recording and saving the first one Status in OEM Priority Project: New Status in “gnome-media” package in Ubuntu: New Bug description: This issue can be reproduced both in standard Ubuntu 11.10 and Ubuntu 12.04. How to reproduce: 1. First open Sound Recorder (gnome-sound-recorder), press Record button to record for seconds. 2. Press Stop button to stop record 3. Press Play button to play the sound, it is OK by now. 4. Now press Record again, it will prompt you to save the previous record, just save it. 5. After saving the last record, it will start to record. Seconds later, press Stop button to stop record. 6. Press Play button Expect result: It will play the record Actual result: It showed an error dialog with Resource not found (In Chinese: 资源未找到) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1011436/+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 948347] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings()
** Also affects: oem-priority/precise Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/948347 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings() Status in OEM Priority Project: Confirmed Status in OEM Priority Project precise series: New Status in “gnome-settings-daemon” package in Ubuntu: Incomplete Status in “gnome-settings-daemon” source package in Quantal: Incomplete Bug description: This error happened on a fairly new install of Beta 1. Fully updated. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.94-0ubuntu2 Architecture: i386 Date: Tue Mar 6 14:04:32 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: SHELL=/bin/false PATH=(custom, no user) LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SegvAnalysis: Segfault happened at: 0xb3fad7a0:mov(%eax),%eax PC (0xb3fad7a0) ok source (%eax) (0x) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so g_cclosure_marshal_VOID__STRINGv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/948347/+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 948347] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings()
@Sebastien The error message is attached. ** Attachment added: Screenshot from 2012-06-04 05_49_39.png https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/948347/+attachment/3175705/+files/Screenshot%20from%202012-06-04%2005_49_39.png -- 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/948347 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings() Status in OEM Priority Project: New Status in “gnome-settings-daemon” package in Ubuntu: Incomplete Bug description: This error happened on a fairly new install of Beta 1. Fully updated. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.94-0ubuntu2 Architecture: i386 Date: Tue Mar 6 14:04:32 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: SHELL=/bin/false PATH=(custom, no user) LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SegvAnalysis: Segfault happened at: 0xb3fad7a0:mov(%eax),%eax PC (0xb3fad7a0) ok source (%eax) (0x) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so g_cclosure_marshal_VOID__STRINGv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/948347/+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 948347] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings()
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = High -- 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/948347 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in xft_settings_set_xsettings() Status in OEM Priority Project: New Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Bug description: This error happened on a fairly new install of Beta 1. Fully updated. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.94-0ubuntu2 Architecture: i386 Date: Tue Mar 6 14:04:32 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: SHELL=/bin/false PATH=(custom, no user) LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SegvAnalysis: Segfault happened at: 0xb3fad7a0:mov(%eax),%eax PC (0xb3fad7a0) ok source (%eax) (0x) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so g_cclosure_marshal_VOID__STRINGv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/948347/+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 992303] Re: Cannot play mp3 or ogg files in Rhythmbox after upgrade to 64-bit 12.04 Precise
** Changed in: oem-priority/precise Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/992303 Title: Cannot play mp3 or ogg files in Rhythmbox after upgrade to 64-bit 12.04 Precise Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in OEM Priority Project quantal series: New Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: Right-click on mp3/ogg file, select Open With Rhythmbox Music Player. Application opens but does not play. Clicking on Play button produces window error message, Couldn't start playback (null). Clicking on Play button a second time produces a different window error message, Couldn't start playback - Failed to create playbin2 element; check your GStreamer installation. Expected mp3 files to play normally as they did with Rhythmbox on 11.10 Oneiric prior to upgrade. Can still play these audio files ok with VLC media player. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Tue May 1 11:41:22 2012 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/992303/+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 988580] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()
It seems the bug is fixed in https://bugs.launchpad.net/ubuntu/+source /gnome-settings-daemon/+bug/948347 -- 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/988580 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv() Status in OEM Priority Project: Incomplete Status in OEM Priority Project precise series: Incomplete Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Hello this happens at the first boot of a fresh installation in OEM mode from usb+persistence Thanks Fabio ProblemType: BugDistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Wed Apr 25 23:40:59 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bashSourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) #0 0x7f4be968d98c in ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so No symbol table info available. #1 0x7f4c01af4c30 in g_cclosure_marshal_VOID__STRINGv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #2 0x7f4c01af1eca in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #3 0x7f4c01b0a741 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #4 0x7f4c01b0b242 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #5 0x7f4c01dd9401 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 No symbol table info available. #6 0x7f4bfe319a14 in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 No symbol table info available. #7 0x7f4bfe319435 in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 No symbol table info available. #8 0x7f4c01af2b16 in g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #9 0x7f4c01af1eca in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #10 0x7f4c01b0a741 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #11 0x7f4c01b0b242 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #12 0x7f4c01dd9ed8 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 No symbol table info available. #13 0x7f4c01dd5a9a in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 No symbol table info available. #14 0x7f4c01834c9a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #15 0x7f4c01835060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #16 0x7f4c0183545a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #17 0x7f4c021fa25d in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 No symbol table info available. #18 0x00403801 in main () No symbol table info available. Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv() UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/988580/+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 992303] Re: Cannot play mp3 or ogg files in Rhythmbox after upgrade to 64-bit 12.04 Precise
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/992303 Title: Cannot play mp3 or ogg files in Rhythmbox after upgrade to 64-bit 12.04 Precise Status in OEM Priority Project: New Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: Right-click on mp3/ogg file, select Open With Rhythmbox Music Player. Application opens but does not play. Clicking on Play button produces window error message, Couldn't start playback (null). Clicking on Play button a second time produces a different window error message, Couldn't start playback - Failed to create playbin2 element; check your GStreamer installation. Expected mp3 files to play normally as they did with Rhythmbox on 11.10 Oneiric prior to upgrade. Can still play these audio files ok with VLC media player. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Tue May 1 11:41:22 2012 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/992303/+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 988580] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()
** Attachment added: gnome-settings-daemon_1.png https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/988580/+attachment/3141291/+files/gnome-settings-daemon_1.png -- 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/988580 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv() Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Hello this happens at the first boot of a fresh installation in OEM mode from usb+persistence Thanks Fabio ProblemType: BugDistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Wed Apr 25 23:40:59 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bashSourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) #0 0x7f4be968d98c in ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so No symbol table info available. #1 0x7f4c01af4c30 in g_cclosure_marshal_VOID__STRINGv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #2 0x7f4c01af1eca in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #3 0x7f4c01b0a741 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #4 0x7f4c01b0b242 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #5 0x7f4c01dd9401 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 No symbol table info available. #6 0x7f4bfe319a14 in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 No symbol table info available. #7 0x7f4bfe319435 in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 No symbol table info available. #8 0x7f4c01af2b16 in g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #9 0x7f4c01af1eca in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #10 0x7f4c01b0a741 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #11 0x7f4c01b0b242 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #12 0x7f4c01dd9ed8 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 No symbol table info available. #13 0x7f4c01dd5a9a in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 No symbol table info available. #14 0x7f4c01834c9a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #15 0x7f4c01835060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #16 0x7f4c0183545a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #17 0x7f4c021fa25d in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 No symbol table info available. #18 0x00403801 in main () No symbol table info available. Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv() UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/988580/+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 988580] Re: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv()
/var/crash/_usr_lib_gnome-settings-daemon_gnome-settings- daemon.104.crash is attached ** Attachment added: _usr_lib_gnome-settings-daemon_gnome-settings-daemon.104.txt https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/988580/+attachment/3141290/+files/_usr_lib_gnome-settings-daemon_gnome-settings-daemon.104.txt -- 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/988580 Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv() Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Hello this happens at the first boot of a fresh installation in OEM mode from usb+persistence Thanks Fabio ProblemType: BugDistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Wed Apr 25 23:40:59 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bashSourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) #0 0x7f4be968d98c in ?? () from /usr/lib/gnome-settings-daemon-3.0/libxsettings.so No symbol table info available. #1 0x7f4c01af4c30 in g_cclosure_marshal_VOID__STRINGv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #2 0x7f4c01af1eca in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #3 0x7f4c01b0a741 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #4 0x7f4c01b0b242 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #5 0x7f4c01dd9401 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 No symbol table info available. #6 0x7f4bfe319a14 in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 No symbol table info available. #7 0x7f4bfe319435 in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 No symbol table info available. #8 0x7f4c01af2b16 in g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #9 0x7f4c01af1eca in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #10 0x7f4c01b0a741 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #11 0x7f4c01b0b242 in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 No symbol table info available. #12 0x7f4c01dd9ed8 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 No symbol table info available. #13 0x7f4c01dd5a9a in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 No symbol table info available. #14 0x7f4c01834c9a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #15 0x7f4c01835060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #16 0x7f4c0183545a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #17 0x7f4c021fa25d in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 No symbol table info available. #18 0x00403801 in main () No symbol table info available. Title: [xsettings]: gnome-settings-daemon crashed with SIGSEGV in g_cclosure_marshal_VOID__STRINGv() UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/988580/+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 962860] Re: The prompt for installing MP3 playback support dialogue box does not fit in a 1024x600 display
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/962860 Title: The prompt for installing MP3 playback support dialogue box does not fit in a 1024x600 display Status in OEM Priority Project: New Status in “rhythmbox” package in Ubuntu: New Bug description: * Ubuntu Release: 12.04 Beta1 * Steps to reproduce it: 1. Click on link to Ubuntu One music store 2. Click on any album link to open up its play list 3. Try to trial play any of the songs in the list Please see the attached screen shots for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/962860/+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 962860] Re: The prompt for installing MP3 playback support dialogue box does not fit in a 1024x600 display
** Changed in: oem-priority Importance: High = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/962860 Title: The prompt for installing MP3 playback support dialogue box does not fit in a 1024x600 display Status in OEM Priority Project: New Status in “rhythmbox” package in Ubuntu: New Bug description: * Ubuntu Release: 12.04 Beta1 * Steps to reproduce it: 1. Click on link to Ubuntu One music store 2. Click on any album link to open up its play list 3. Try to trial play any of the songs in the list Please see the attached screen shots for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/962860/+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 883791] Re: Sound recorder reports that gnome-volume-control is not installed in the path
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-media in Ubuntu. https://bugs.launchpad.net/bugs/883791 Title: Sound recorder reports that gnome-volume-control is not installed in the path Status in OEM Priority Project: New Status in “gnome-media” package in Ubuntu: Confirmed Bug description: File|Open volume control returns error message: gnome-volume-control is not installed in the path. What should happen: volume control should open ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-media 2.91.2-2ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sun Oct 30 12:54:13 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) SourcePackage: gnome-media UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/883791/+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 893851] Re: Brightness adjustment gauge in gnome-control-center screen not responding to brightness hot-keys
Change to confirm as Chih has provided the explanation of the bug ** Changed in: oem-priority Status: Incomplete = Confirmed ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete = Confirmed -- 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/893851 Title: Brightness adjustment gauge in gnome-control-center screen not responding to brightness hot-keys Status in OEM Priority Project: Confirmed Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: For systems equipped with hot keys to adjust screen brightness, the brightness gauge in gnome-control-center screen is not responding to brightness hot-key actions. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/893851/+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
