[Desktop-packages] [Bug 2025538] Update Released
The verification of the Stable Release Update for nvidia-graphics- drivers-535 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+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 1988836] Re: LRMv6: Enable the open NVIDIA kernel modules
** Summary changed: - Enable the open NVIDIA kernel modules + LRMv6: Enable the open NVIDIA kernel modules ** Summary changed: - LRMv6: Enable the open NVIDIA kernel modules + LRMv7: Enable the open NVIDIA kernel modules -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Re: Enable the open NVIDIA kernel modules
Kernel rework is proposed at: https://lists.ubuntu.com/archives/kernel- team/2022-September/133205.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp
Hello Timo, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.19 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1945227 Title: drm/amdgpu: Add support for Yellow Carp Status in linux-firmware package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Bug description: [Impact] New hardware support for AMD's Yellow Carp need five commits backported to mesa and new firmware. This is only needed on focal, skipping hirsute (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1898601] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1
[Desktop-packages] [Bug 1931514] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Status in ubuntu-drivers-common source package in Hirsute: Fix Committed Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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 1913651] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted ubuntu-drivers-common into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.9.0~0.18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1913651 Title: /usr/bin/ubuntu-drivers:PermissionError:/usr/bin/ubuntu- drivers@480:__call__:main:invoke:invoke:invoke:new_func:invoke:autoinstall:command_install Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-drivers-common. This problem was most recently seen with package version 1:0.8.6.3~0.20.10.1, the problem page at https://errors.ubuntu.com/problem/a5320fbf71298787ff2595cc2b8227783b068dae contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. There is also this bucket: https://errors.ubuntu.com/problem/fb18ad88544e0c025b2c9ec591b91c080d23401d If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1913651/+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 1914051] Please test proposed package
Hello Iain, or anyone else affected, Accepted ubuntu-drivers-common into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.9.0~0.18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914051 Title: `ubuntu-drivers list-oem --package-list` is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: This is the call Ubiquity is making to decide what OEM packages to install. With the current focal-updates version root@ubuntu-drivers-common-test:~# apt policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.6.3~0.20.04.2 Candidate: 1:0.8.6.3~0.20.04.2 Version table: *** 1:0.8.6.3~0.20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo Usage: ubuntu-drivers list-oem [OPTIONS] [LIST_OEM]... Try "ubuntu-drivers list-oem -h" for help. Error: no such option: --package-list With the focal release version: root@ubuntu-drivers-common-test:~# ubuntu-drivers list-oem --package-list=/tmp/foo root@ubuntu-drivers-common-test:~# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1914051/+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 1914374] Please test proposed package
Hello Lukas, or anyone else affected, Accepted ubuntu-drivers-common into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.9.0~0.18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1914374 Title: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image Status in OEM Priority Project: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubiquity source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubiquity source package in Groovy: Won't Fix Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: I've installed the focal-desktop-amd64.iso image with SHA-256 sum b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook 15 G7 laptop (CID 202009-28216). There are multiple issues: * The graphical desktop isn't launched. The screen remains black except for a cursor blinking erratically in the top left corner of the screen. If I hammer Control+Alt+F[12345] for a while, the graphical desktop starts eventually. * The screen resolution is 3840x2160 but there is no scaling, so everything is tiny. * The touchpad does not work. * WLAN does not work. * Ethernet does not work. I tried two dongles (a USB A as well as a USB C dongle). * No sound. $ cat /proc/version_signature Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1914374/+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 1898601] Please test proposed package
Hello Jeff, or anyone else affected, Accepted ubuntu-drivers-common into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.9.0~0.18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data
[Desktop-packages] [Bug 1931514] Please test proposed package
Hello Bin, or anyone else affected, Accepted ubuntu-drivers-common into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers- common/1:0.9.0~0.18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Groovy: Fix Committed Status in ubuntu-drivers-common source package in Hirsute: Fix Committed Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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 1930567] Re: popup menu handling broken with multiple monitors
** Attachment added: "Screenshot from 2021-06-02 10-41-35.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930567/+attachment/5501856/+files/Screenshot%20from%202021-06-02%2010-41-35.png -- 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/1930567 Title: popup menu handling broken with multiple monitors Status in gnome-shell package in Ubuntu: New Bug description: I have two (hopefully related) problems with popup-menus for applications on an external monitor. For background I have two displays, the first a builtin LCD panel, the second and HDMI connected LCD monitor. The external monitor is stacked "above" the internal LCD panel, the internal LCD panel is the "primary" display from a where the dash et al are placed. The first issue occurs with gnome-terminal. When using right-click on an element in the window such as a link, a menu is shown to allow OpenURL et al. This menu will not appear when the link it too close to the bottom of the upper display (the external one); the cursor changes to the arrow menu item selector cursor but not menu is rendered. This occurs regardless of whether the window is maximised and it related to proximity to the boundary of the display. It behaves correctly at the bottom boundary of the lower display. Two screenshots attached showing it working/not-working. The second issue occurs in firefox. When it is rendered on the upper displays its internal menus are displayed at the top of the lower display rather than on the upper display rooted at the menu item itself. This also does not occur on the lower display. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930567/+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 1930567] Re: popup menu handling broken with multiple monitors
** Attachment added: "Screenshot from 2021-06-02 10-40-15.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930567/+attachment/5501854/+files/Screenshot%20from%202021-06-02%2010-40-15.png -- 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/1930567 Title: popup menu handling broken with multiple monitors Status in gnome-shell package in Ubuntu: New Bug description: I have two (hopefully related) problems with popup-menus for applications on an external monitor. For background I have two displays, the first a builtin LCD panel, the second and HDMI connected LCD monitor. The external monitor is stacked "above" the internal LCD panel, the internal LCD panel is the "primary" display from a where the dash et al are placed. The first issue occurs with gnome-terminal. When using right-click on an element in the window such as a link, a menu is shown to allow OpenURL et al. This menu will not appear when the link it too close to the bottom of the upper display (the external one); the cursor changes to the arrow menu item selector cursor but not menu is rendered. This occurs regardless of whether the window is maximised and it related to proximity to the boundary of the display. It behaves correctly at the bottom boundary of the lower display. Two screenshots attached showing it working/not-working. The second issue occurs in firefox. When it is rendered on the upper displays its internal menus are displayed at the top of the lower display rather than on the upper display rooted at the menu item itself. This also does not occur on the lower display. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930567/+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 1930567] Re: popup menu handling broken with multiple monitors
** Attachment added: "Screenshot from 2021-06-02 10-40-59.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930567/+attachment/5501855/+files/Screenshot%20from%202021-06-02%2010-40-59.png -- 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/1930567 Title: popup menu handling broken with multiple monitors Status in gnome-shell package in Ubuntu: New Bug description: I have two (hopefully related) problems with popup-menus for applications on an external monitor. For background I have two displays, the first a builtin LCD panel, the second and HDMI connected LCD monitor. The external monitor is stacked "above" the internal LCD panel, the internal LCD panel is the "primary" display from a where the dash et al are placed. The first issue occurs with gnome-terminal. When using right-click on an element in the window such as a link, a menu is shown to allow OpenURL et al. This menu will not appear when the link it too close to the bottom of the upper display (the external one); the cursor changes to the arrow menu item selector cursor but not menu is rendered. This occurs regardless of whether the window is maximised and it related to proximity to the boundary of the display. It behaves correctly at the bottom boundary of the lower display. Two screenshots attached showing it working/not-working. The second issue occurs in firefox. When it is rendered on the upper displays its internal menus are displayed at the top of the lower display rather than on the upper display rooted at the menu item itself. This also does not occur on the lower display. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930567/+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 1930567] [NEW] popup menu handling broken with multiple monitors
Public bug reported: I have two (hopefully related) problems with popup-menus for applications on an external monitor. For background I have two displays, the first a builtin LCD panel, the second and HDMI connected LCD monitor. The external monitor is stacked "above" the internal LCD panel, the internal LCD panel is the "primary" display from a where the dash et al are placed. The first issue occurs with gnome-terminal. When using right-click on an element in the window such as a link, a menu is shown to allow OpenURL et al. This menu will not appear when the link it too close to the bottom of the upper display (the external one); the cursor changes to the arrow menu item selector cursor but not menu is rendered. This occurs regardless of whether the window is maximised and it related to proximity to the boundary of the display. It behaves correctly at the bottom boundary of the lower display. Two screenshots attached showing it working/not-working. The second issue occurs in firefox. When it is rendered on the upper displays its internal menus are displayed at the top of the lower display rather than on the upper display rooted at the menu item itself. This also does not occur on the lower display. Screenshot attached. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute multimonitor -- 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/1930567 Title: popup menu handling broken with multiple monitors Status in gnome-shell package in Ubuntu: New Bug description: I have two (hopefully related) problems with popup-menus for applications on an external monitor. For background I have two displays, the first a builtin LCD panel, the second and HDMI connected LCD monitor. The external monitor is stacked "above" the internal LCD panel, the internal LCD panel is the "primary" display from a where the dash et al are placed. The first issue occurs with gnome-terminal. When using right-click on an element in the window such as a link, a menu is shown to allow OpenURL et al. This menu will not appear when the link it too close to the bottom of the upper display (the external one); the cursor changes to the arrow menu item selector cursor but not menu is rendered. This occurs regardless of whether the window is maximised and it related to proximity to the boundary of the display. It behaves correctly at the bottom boundary of the lower display. Two screenshots attached showing it working/not-working. The second issue occurs in firefox. When it is rendered on the upper displays its internal menus are displayed at the top of the lower display rather than on the upper display rooted at the menu item itself. This also does not occur on the lower display. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930567/+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 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
** Tags added: kqa-blocker -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+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 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
Hello Meluco, or anyone else affected, Accepted nvidia-graphics-drivers-340 into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-340/340.108-0ubuntu5.20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Bug description: [Impact] nvidia-340 dkms fails to build against the current HWE kernel in focal, regressing the user experience. [Test case] Install the update, check that the dkms builds and works. [Where things could go wrong] The changes only add support for newer kernels so that the module can build, and it's identical to what's in groovy. In theory it could break the build against 5.4 but that's highly unlikely. -- Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult:
[Desktop-packages] [Bug 1872230] Re: The left Ctrl key does not work when using pointer location
Bah wrong bug. -- 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/1872230 Title: The left Ctrl key does not work when using pointer location Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: I am using 20.04 Focal. I am using a US international keyboard layout with dead keys, so that I can enter text in many different languages. After I had rebooted my system today and so loaded the newest GNOME Shell, the left Ctrl key stopped working in the terminal windows and also in emacs, while the right Ctrl still works. To get the left Ctrl working again I have to switch to a plain US English keyboard layout, without dead keys. I have also tried the different alternatives of US International keyboard layouts, each of them seems to work as intended but the left Ctrl key is not working. Only with plain US English layout I get the left Ctrl working. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1872230/+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 1872230] Re: The left Ctrl key does not work when using pointer location
I am seeing this with Pointer Location turned off; this being the super key not doing activited. -- 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/1872230 Title: The left Ctrl key does not work when using pointer location Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: I am using 20.04 Focal. I am using a US international keyboard layout with dead keys, so that I can enter text in many different languages. After I had rebooted my system today and so loaded the newest GNOME Shell, the left Ctrl key stopped working in the terminal windows and also in emacs, while the right Ctrl still works. To get the left Ctrl working again I have to switch to a plain US English keyboard layout, without dead keys. I have also tried the different alternatives of US International keyboard layouts, each of them seems to work as intended but the left Ctrl key is not working. Only with plain US English layout I get the left Ctrl working. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1872230/+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 1871416] Re: alt-TAB hightlight colour almost indistinguishable from the background
Image of the alt-TAB bar with the second item selected. ** Attachment added: "IMG_20200407_160128764.jpg" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871416/+attachment/5348783/+files/IMG_20200407_160128764.jpg -- 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/1871416 Title: alt-TAB hightlight colour almost indistinguishable from the background Status in gnome-shell package in Ubuntu: New Bug description: Almost impossible to see which item is highlighted. See attached image. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 15:53:23 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-02-28 (1500 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160226) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871416/+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 1871416] [NEW] alt-TAB hightlight colour almost indistinguishable from the background
Public bug reported: Almost impossible to see which item is highlighted. See attached image. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 15:53:23 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-02-28 (1500 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160226) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1871416 Title: alt-TAB hightlight colour almost indistinguishable from the background Status in gnome-shell package in Ubuntu: New Bug description: Almost impossible to see which item is highlighted. See attached image. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 7 15:53:23 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-02-28 (1500 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160226) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871416/+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 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
** Changed in: linux-restricted-modules (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Bionic: In Progress Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-440 source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in linux-restricted-modules source package in Eoan: In Progress Status in nvidia-graphics-drivers-340 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Committed Status in nvidia-graphics-drivers-440 source package in Eoan: Fix Committed Status in nvidia-settings source package in Eoan: Fix Committed Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Enabled parallel GLSL shader linking by default; i.e., allow GL_ARB_parallel_shader_compile to work without first calling glMaxShaderCompilerThreadsARB(). - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC Compatible monitors on supported GPUs.For more details, see "Configuring Multiple Display Devices on One X Screen" in the README. Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast extensions.For more details, see the "Configuring SLI and Multi-GPU FrameRendering" chapter of the README, and the extension specifications: https://www.khronos.org/registry/OpenGL/extensions/NV/GLX_NV_multigpu_context.txt
[Desktop-packages] [Bug 1780680] Re: Older version in bionic than in xenial
** Changed in: linux-meta-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-meta-gcp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780680 Title: Older version in bionic than in xenial Status in fuse-umfuse-ext2 package in Ubuntu: New Status in libclc package in Ubuntu: Won't Fix Status in libdrm package in Ubuntu: Won't Fix Status in linux-meta-azure package in Ubuntu: Fix Released Status in linux-meta-gcp package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Won't Fix Status in patch package in Ubuntu: Invalid Status in python-pyvmomi package in Ubuntu: Invalid Status in snapcraft package in Ubuntu: Fix Released Status in wireless-regdb package in Ubuntu: Fix Released Bug description: These packages have an older version in artful than in xenial. fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1 libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1 libdrm 2.4.83-1 < 2.4.91-2~16.04.1 mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1 patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1 python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1 snapcraft 2.42+17.10 < 2.42.1 wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1 Some of these are older in bionic than in xenial too. Shouldn’t there be an automated check for this? (See also: bug 1780679, bug 1780681.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+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 461260] Re: No sound was heard when running System Testing on a new Intel Apple iMac
** Changed in: linux-backports-modules-2.6.31 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/461260 Title: No sound was heard when running System Testing on a new Intel Apple iMac Status in alsa-driver package in Ubuntu: Confirmed Status in linux-backports-modules-2.6.31 package in Ubuntu: Won't Fix Bug description: I preformed a new install, updated, and upgraded Karmic Beta on a new Intel Apple iMac. No non-free drivers are in use. I ran System Testing and heard no sound. ProblemType: Bug Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scottmaccal 1690 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x5060 irq 20' Mixer name : 'Realtek ALC889A' Components : 'HDA:10ec0885,106b3c00,00100103' Controls : 29 Simple ctrls : 15 CheckboxCommand: alsa_record_playback CheckboxTest: alsa_record_playback_alternates Date: Mon Oct 26 13:16:59 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3) Package: alsa-base 1.0.20+dfsg-1ubuntu5 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: alsa-driver Tags: checkbox-bug Uname: Linux 2.6.31-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/461260/+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 1856414] Re: installing linux-modules-nvidia does not remove nvidia-dkms, and the kernel prioritizes the wrong version of the module from disk
** Changed in: linux-restricted-modules (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1856414 Title: installing linux-modules-nvidia does not remove nvidia-dkms, and the kernel prioritizes the wrong version of the module from disk Status in linux-restricted-modules package in Ubuntu: New Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: Installing nvidia-driver-430 pulls in nvidia-dkms-430 as a dependency. Installing linux-modules-nvidia-430-generic does not satisfy this dependency in its place; so nvidia-dkms-430 can't be removed without also removing nvidia-driver-430, and then a bunch of other packages also want to be removed as unused: $ sudo apt purge nvidia-dkms-430 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libatomic1:i386 libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm9:i386 libnvidia-cfg1-430 libnvidia-common-430 libnvidia-compute-430 libnvidia-compute-430:i386 libnvidia-decode-430 libnvidia-decode-430:i386 libnvidia-encode-430 libnvidia-encode-430:i386 libnvidia-fbc1-430 libnvidia-fbc1-430:i386 libnvidia-gl-430 libnvidia-gl-430:i386 libnvidia-ifr1-430 libnvidia-ifr1-430:i386 libpciaccess0:i386 libsensors5:i386 libstdc++6:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 nvidia-compute-utils-430 nvidia-kernel-source-430 nvidia-prime nvidia-settings nvidia-utils-430 screen-resolution-extra xserver-xorg-video-nvidia-430 Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: nvidia-dkms-430* nvidia-driver-430* 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. After this operation, 1,269 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. $ And it's not sufficient to leave both linux-modules-nvidia and nvidia- dkms installed, because when both are present, the kernel erroneously picks up the modules from nvidia-dkms first, and fails to load them if SecureBoot is on and the local MOK is not enrolled. linux-modules-nvidia-430-generic probably needs a versioned Provides: so that it can be installed in place of nvidia-dkms-430. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1856414/+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 1837834] Update Released
The verification of the Stable Release Update for nvidia-graphics- drivers-340 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1837834 Title: Add support for Linux 5.0-5.2 Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Bug description: Backport the compatibility patches available in 19.10. SRU Request: [Impact] Linux 5.0 is not supported by nvidia-driver-340 in bionic. [Test Case] 1) Enable the -proposed repository, and install the new 340 NVIDIA driver (340.107-0ubuntu0.16.04.3). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only fixes build issues with Linux versions 5.0 - 5.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1837834/+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 1817537] Please test proposed package
Hello Lars, or anyone else affected, Accepted libsoup2.4 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libsoup2.4/2.62.1-1ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 Status in libsoup2.4 package in Ubuntu: Fix Released Status in libsoup2.4 source package in Bionic: Fix Committed Bug description: * Impact Without NTLMv2 support evolution-ews can't connect to some exchange servers * Test case Try connecting from evolution-ews to an exchange server which enforces NTLMV2 * Regression potential The change adds extra cases in the ntlm handling support, it should impact existing feature but check out for any potential regression in libsoup user (check at least evolution and epiphany-browser). Note that the patch include additional code tests --- Our Exchange admins recently made NTLMv2 obligatory. Since then interaction with Exchange through Evolution isn't possible anymore. In newer versions of libsoup that has been implemented, see https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 Could that be backported to Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsoup2.4-1 2.62.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 25 12:10:26 2019 SourcePackage: libsoup2.4 UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+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 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04
Hello Roman, or anyone else affected, Accepted mesa into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/19.0.2-1ubuntu1.1~18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836721 Title: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04 Status in mesa package in Ubuntu: Won't Fix Status in mesa source package in Bionic: Fix Committed Bug description: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04. ~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ~# uname -a Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 i686 i686 GNU/Linux ~# lspci -nn -k -d ::0300 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90] Subsystem: ASUSTeK Computer Inc. Device [1043:8694] Kernel driver in use: i915 Kernel modules: i915 mesa: 19.0.2-1ubuntu1.1~18.04.1 X crashes with message: i965: Failed to submit batchbuffer: Invalid argument The same issue was after updating mesa from 18.0 to 18.2: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172 I have tried the same fix and it works for me: https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836721/+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 1731318] Please test proposed package
Hello Jeremy, or anyone else affected, Accepted gnome-desktop3 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- desktop3/3.28.2-0ubuntu1.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1731318 Title: NVIDIA systems will not suspend with lid close and no external monitors Status in gnome-desktop: Confirmed Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Bionic: Fix Committed Status in gnome-desktop3 source package in Disco: Fix Committed Bug description: [ Description ] With the NVIDIA driver, nvidia-384, the system will not sleep when the lid is closed due to gnome_rr_output_is_builtin_display incorrectly returning false. [ Fix ] mutter provides a more reliable API to get the "type" of a connector (output). The fix switches gnome-desktop to use this API instead of looking at the output's name - which can be anything apparently. (This drops a visible symbol, but it was only one which you could have used if you included "libgnome-desktop/gnome-rr-private.h", which is not shipped in the -dev package.) [ QA ] If you have an affected system - an NVIDIA-using laptop which doesn't sleep if the lid is closed: install the update, and check if the laptop does now sleep. [ Regression potential ] Changes the heuristic-based scheme for detecting if a display is "built-in" to a method based on the reported connector type. There's a low chance that this could be wrong for some machines which were right previously. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1731318/+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 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
** Tags removed: verification-failed-xenial ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: SRU Request: [Impact] A commit that was backported to the latest 4.4 kernel, broke compatibility with the NVIDIA drivers in Xenial and in Trusty. [Test Case] 1) Enable the -proposed repository, and install the new 4.4 kernel image and headers, and one of the NVIDIA drivers (304, 340, 384) 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. ___ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 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 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1573508/+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 1573508] Please test proposed package
Hello khanpak...@gmail.com, or anyone else affected, Accepted nvidia-graphics-drivers-304 into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-304/304.135-0ubuntu0.14.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 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 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1573508/+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 1573508] Please test proposed package
Hello khanpak...@gmail.com, or anyone else affected, Accepted nvidia-graphics-drivers-340 into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-340/340.107-0ubuntu0.14.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 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 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1573508/+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 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
Hello khanpak...@gmail.com, or anyone else affected, Accepted nvidia-graphics-drivers-384 into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-384/384.130-0ubuntu0.14.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed-trusty ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-340 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 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 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1573508/+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 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
Hello khanpak...@gmail.com, or anyone else affected, Accepted nvidia-graphics-drivers-340 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-340/340.107-0ubuntu0.16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: In Progress Status in nvidia-graphics-drivers-340 source package in Trusty: In Progress Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: Fix Committed Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 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 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1573508/+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 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
Hello khanpak...@gmail.com, or anyone else affected, Accepted nvidia-graphics-drivers-384 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-384/384.130-0ubuntu0.16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: In Progress Status in nvidia-graphics-drivers-340 source package in Trusty: In Progress Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: In Progress Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: In Progress Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: Fix Committed Bug description: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 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 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1573508/+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 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]
Hello khanpak...@gmail.com, or anyone else affected, Accepted nvidia-graphics-drivers-304 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-304/304.135-0ubuntu0.16.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1573508 Title: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] Status in nvidia-graphics-drivers-304 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-304 source package in Trusty: In Progress Status in nvidia-graphics-drivers-340 source package in Trusty: In Progress Status in nvidia-graphics-drivers-361 source package in Trusty: Invalid Status in nvidia-graphics-drivers-384 source package in Trusty: In Progress Status in nvidia-graphics-drivers-304 source package in Xenial: Fix Committed Status in nvidia-graphics-drivers-340 source package in Xenial: In Progress Status in nvidia-graphics-drivers-361 source package in Xenial: Invalid Status in nvidia-graphics-drivers-384 source package in Xenial: In Progress Bug description: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 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 DKMSKernelVersion: 4.6.0-040600rc4-lowlatency Date: Fri Apr 22 15:43:10 2016 DuplicateSignature: dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many arguments to function ‘get_user_pages’ InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageVersion: 361.42-0ubuntu2 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1573508/+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 1789924] Re: Missing Intel GPU pci-id's
This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed. ** Tags removed: verification-needed-bionic ** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1815579] Please test proposed package
Hello Leopoldo, or anyone else affected, Accepted nvidia-graphics-drivers-390 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-390/390.77-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: xserver-xorg-core-hwe-18.04 xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-video-all-hwe-18.04 xserver-xorg-video-amdgpu-hwe-18.04 xserver-xorg-video-ati-hwe-18.04
[Desktop-packages] [Bug 1815579] Re: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic
Hello Leopoldo, or anyone else affected, Accepted nvidia-graphics-drivers-340 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-340/340.107-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1815579 Title: Broken dependencies with nvidia-driver-390 and xserver-xorg-hwe-18.04 in bionic Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Bug description: I am trying to test new HWE stack from 18.10 in my destkop Ubuntu 18.04.1 (expected release 18.04.2 this week) and I have broken dependencies when installing `xserver-xorg-hwe-18.04` package with NVidia drivers: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 xserver-xorg-video-nvidia-390 Reading package lists... Done Building dependency tree Reading state information... Done xserver-xorg-video-nvidia-390 is already the newest version (390.77-0ubuntu0.18.04.1). xserver-xorg-video-nvidia-390 set to manually installed. Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-hwe-18.04 : Depends: xserver-xorg-core-hwe-18.04 (>= 2:1.17.2-2) but it is not going to be installed Conflicts: xserver-xorg-core (>= 0~) Recommends: xserver-xorg-video-all-hwe-18.04 but it is not going to be installed E: Unable to correct problems, you have held broken packages. Otherwise, if I try to install it without `xserver-xorg-video-nvidia-390` this happens: me@me-H110M-DS2:~$ sudo apt install xserver-xorg-hwe-18.04 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: dkms libbsd0:i386 libdrm-amdgpu1:i386 libdrm-intel1:i386 libdrm-nouveau2:i386 libdrm-radeon1:i386 libdrm2:i386 libedit2:i386 libelf1:i386 libexpat1:i386 libffi6:i386 libgl1:i386 libgl1-mesa-dri:i386 libglapi-mesa:i386 libglvnd0:i386 libglx-mesa0:i386 libglx0:i386 libllvm7:i386 libnvidia-cfg1-390 libnvidia-common-390 libnvidia-compute-390 libnvidia-compute-390:i386 libnvidia-decode-390 libnvidia-decode-390:i386 libnvidia-encode-390 libnvidia-encode-390:i386 libnvidia-fbc1-390 libnvidia-fbc1-390:i386 libnvidia-gl-390 libnvidia-gl-390:i386 libnvidia-ifr1-390 libnvidia-ifr1-390:i386 libpciaccess0:i386 libsensors4:i386 libstdc++6:i386 libvdpau1 libwayland-client0:i386 libwayland-server0:i386 libx11-6:i386 libx11-xcb1:i386 libxau6:i386 libxcb-dri2-0:i386 libxcb-dri3-0:i386 libxcb-glx0:i386 libxcb-present0:i386 libxcb-sync1:i386 libxcb1:i386 libxdamage1:i386 libxdmcp6:i386 libxext6:i386 libxfixes3:i386 libxnvctrl0 libxshmfence1:i386 libxxf86vm1:i386 mesa-vdpau-drivers nvidia-compute-utils-390 nvidia-dkms-390 nvidia-kernel-common-390 nvidia-kernel-source-390 nvidia-prime nvidia-settings nvidia-utils-390 pkg-config screen-resolution-extra vdpau-driver-all Use 'sudo apt autoremove' to remove them. The following
[Desktop-packages] [Bug 1803142] Proposed package upload rejected
An upload of libreoffice to cosmic-proposed has been rejected from the upload queue for the following reason: "Includes unexpected config file change.". -- 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/1803142 Title: [SRU] libreoffice 6.1.3 for cosmic Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Cosmic: Fix Committed Status in libreoffice-l10n source package in Cosmic: Fix Committed Bug description: [Impact] * LibreOffice 6.1.3 is the third bugfix release of the fresh 6.1 line. Version 6.1.2 is currently in cosmic. For a list of fixed bugs compared to 6.1.2 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.1.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.1.3/RC2#List_of_fixed_bugs (that's a total of 66 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 66 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1803142/+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 1808147] Proposed package upload rejected
An upload of libreoffice to cosmic-proposed has been rejected from the upload queue for the following reason: "Includes unexpected config file change.". -- 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/1808147 Title: autopkgtests fail on s390x Status in libreoffice package in Ubuntu: Fix Released Bug description: libreoffice autopkgtests on s390x started failing reliably on 2018-12-11. This corresponds to when a new version of autopkgtest was deployed to the production infrastructure: https://lists.ubuntu.com/archives /ubuntu-devel/2018-December/040564.html The failing test is "smoketest". It has the "skippable" restriction, which was previously unknown, and as a result the test was skipped altogether. "skippable" is now a valid and understood restriction, so the test is being run, but it fails: […] mkdir -p /tmp/autopkgtest.A1jy64/build.urp/src/workdir/CustomTarget/i18npool/textconversion/ S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libcollator_data.so S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libdict_ja.so S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libdict_zh.so S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libindex_data.so S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/liblocaledata_en.so /tmp/autopkgtest.A1jy64/build.urp/src/solenv/gbuild/Package.mk:82: *** Something depends on package test_unittest which does not exist.. Stop. make[1]: *** Waiting for unfinished jobs S=/tmp/autopkgtest.A1jy64/build.urp/src && I=$S/instdir && W=$S/workdir && touch $W/Headers/Library/libtextconv_dict.so [build PKG] test_unittest make[1]: Leaving directory '/tmp/autopkgtest.A1jy64/build.urp/src' make: *** [Makefile:112: i18npool.all] Error 2 autopkgtest [13:27:33]: test smoketest: ---] autopkgtest [13:27:34]: test smoketest: - - - - - - - - - - results - - - - - - - - - - smoketestFAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1808147/+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 1743094] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Artful) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1743094 Title: [regression] hibernation (freezes on resume) since 4.13.0-25.29 Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Status in linux source package in Artful: Won't Fix Bug description: After hibernating the system and than resuming it the system reboots notifying that it is resuming and than stops/freezes. The system does not respond to anything (no tty's other notifying textg are available). After booting kernel 4.10-042 the hibernation and hibride hibernation/sleep functions as proposed. --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jb 1717 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=00059f88-0cf2-44a0-a23d-f0a995cb1478 InstallationDate: Installed on 2017-12-10 (34 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: Acer Aspire S3-391 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic root=UUID=5397ffb7-8114-45c4-824f-b1da7cce468c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-26-generic N/A linux-backports-modules-4.13.0-26-generic N/A linux-firmware 1.157.14 Tags: sylvia Uname: Linux 4.13.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Hummingbird2 dmi.board.vendor: Acer dmi.board.version: V2.10 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.10:bd10/31/2012:svnAcer:pnAspireS3-391:pvrV2.10:rvnAcer:rnHummingbird2:rvrV2.10:cvnAcer:ct10:cvrV2.10: dmi.product.family: ChiefRiver System dmi.product.name: Aspire S3-391 dmi.product.version: V2.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743094/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Hello Markus, or anyone else affected, Accepted console-setup into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/console- setup/1.178ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: console-setup (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Fix Committed Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1737053] Re: [MIR] brotli
$ change-override -S -s cosmic -c main brotli Override component to main brotli 1.0.3-1ubuntu1 in cosmic: universe/misc -> main brotli 1.0.3-1ubuntu1 in cosmic amd64: universe/python/optional/100% -> main brotli 1.0.3-1ubuntu1 in cosmic arm64: universe/python/optional/100% -> main brotli 1.0.3-1ubuntu1 in cosmic armhf: universe/python/optional/100% -> main brotli 1.0.3-1ubuntu1 in cosmic i386: universe/python/optional/100% -> main brotli 1.0.3-1ubuntu1 in cosmic ppc64el: universe/python/optional/100% -> main brotli 1.0.3-1ubuntu1 in cosmic s390x: universe/python/optional/100% -> main libbrotli-dev 1.0.3-1ubuntu1 in cosmic amd64: universe/libdevel/optional/100% -> main libbrotli-dev 1.0.3-1ubuntu1 in cosmic arm64: universe/libdevel/optional/100% -> main libbrotli-dev 1.0.3-1ubuntu1 in cosmic armhf: universe/libdevel/optional/100% -> main libbrotli-dev 1.0.3-1ubuntu1 in cosmic i386: universe/libdevel/optional/100% -> main libbrotli-dev 1.0.3-1ubuntu1 in cosmic ppc64el: universe/libdevel/optional/100% -> main libbrotli-dev 1.0.3-1ubuntu1 in cosmic s390x: universe/libdevel/optional/100% -> main libbrotli1 1.0.3-1ubuntu1 in cosmic amd64: universe/libs/optional/100% -> main libbrotli1 1.0.3-1ubuntu1 in cosmic arm64: universe/libs/optional/100% -> main libbrotli1 1.0.3-1ubuntu1 in cosmic armhf: universe/libs/optional/100% -> main libbrotli1 1.0.3-1ubuntu1 in cosmic i386: universe/libs/optional/100% -> main libbrotli1 1.0.3-1ubuntu1 in cosmic ppc64el: universe/libs/optional/100% -> main libbrotli1 1.0.3-1ubuntu1 in cosmic s390x: universe/libs/optional/100% -> main python-brotli 1.0.3-1ubuntu1 in cosmic amd64: universe/python/optional/100% -> main python-brotli 1.0.3-1ubuntu1 in cosmic arm64: universe/python/optional/100% -> main python-brotli 1.0.3-1ubuntu1 in cosmic armhf: universe/python/optional/100% -> main python-brotli 1.0.3-1ubuntu1 in cosmic i386: universe/python/optional/100% -> main python-brotli 1.0.3-1ubuntu1 in cosmic ppc64el: universe/python/optional/100% -> main python-brotli 1.0.3-1ubuntu1 in cosmic s390x: universe/python/optional/100% -> main
[Desktop-packages] [Bug 1752578] Re: Evolution 3.27/3.28 transition
Confirming this is being delayed through feature-freeze because of the sheer volume of other transitions and can be applied when sensible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1752578 Title: Evolution 3.27/3.28 transition Status in evolution package in Ubuntu: New Status in evolution-data-server package in Ubuntu: New Status in evolution-ews package in Ubuntu: New Bug description: The Ubuntu Desktop Team would like to update evolution-data-server, evolution, and evolution-ews to 3.27.91 in preparation for evolution 3.28 (expected release March 12). Evolution bumped its sonames so we'll need a transition. Trackers = https://people.canonical.com/~ubuntu-archive/transitions/html/evolution-data-server.html https://release.debian.org/transitions/html/auto-evolution-data- server.html Successfully staged at https://launchpad.net/~jbicha/+archive/ubuntu/tempeds/+packages Justification = This transition was ready two weeks ago, but we wanted to do one major GNOME transition at a time. libgweather transition went smoothly. gnome-desktop3 got entangled with some other incomplete transitions (in particular, mesa/libglvnd). A Qt transition and a kdepim transition the week of 18.04 Feature Freeze made it impossible for those transitions to clear before Feature Freeze. We could have uploaded evolution now to avoid paperwork, but it feels like it would be smoother to be a bit more patient and do this soon after Feature Freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1752578/+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 1724872] Re: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
Hello Seth, or anyone else affected, Accepted nvidia-graphics-drivers-340 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /nvidia-graphics-drivers-340/340.104-0ubuntu0.16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1724872 Title: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 Status in nvidia-graphics-drivers-340 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Committed Bug description: [Impact] Currently the DKMS package fails to install in supported custom kernels that are based on 4.11 or 4.13. That includes the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud kernels as well. [Test Case] Install the DKMS package with the 4.13 hwe-edge kernel from -proposed. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.10 - linux-hwe-edge 4.11 - linux-hwe-edge 4.13 (from xenial-proposed) [Original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20171018_120806_eb45b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20171018_121546_eb45b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1724872/+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 1724872] Re: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
** Also affects: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1724872 Title: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 Status in nvidia-graphics-drivers-340 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-340 source package in Xenial: New Bug description: [Impact] Currently the DKMS package fails to install in supported custom kernels that are based on 4.11 or 4.13. That includes the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud kernels as well. [Test Case] Install the DKMS package with the 4.13 hwe-edge kernel from -proposed. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.10 - linux-hwe-edge 4.11 - linux-hwe-edge 4.13 (from xenial-proposed) [Original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20171018_120806_eb45b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20171018_121546_eb45b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1724872/+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 1725288] Re: [artful] gnome-shell missing dependency on gir1.2-gdm-1.0
Hello Jeremy, or anyone else affected, Accepted gnome-shell into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.26.1-0ubuntu5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-shell (Ubuntu Artful) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-artful -- 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/1725288 Title: [artful] gnome-shell missing dependency on gir1.2-gdm-1.0 Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Artful: Fix Committed Bug description: Impact == A user who tries to use a different display manager than GDM might easily uninstall a package needed by GNOME Shell and therefore will be unable to log in to the default Ubuntu session or to GNOME or to GNOME Classic Test Case = Before applying the update - sudo apt install lightdm (Choose lightdm when asked which display manager to use) sudo apt remove gdm3 gir1.2-gdm-1.0 (This will uninstall ubuntu-desktop.) Reboot Try to log in to Ubuntu A black screen shows and you will get returned to the log in screen The systemd journal shows this error: gnome-shell: JS ERROR: Error: Requiring Gdm, version none: Typelib file for namespace 'Gdm' (any version) not found After applying the update - You won't be able to uninstall gir1.2-gdm-1.0 without uninstalling gnome-shell. You should be able to log in to Ubuntu now from lightdm if gnome-shell and ubuntu-session are installed. Regression Potential None. This simply restores a dependency that was accidentally not restored earlier. The dependency was dropped in https://launchpad.net/ubuntu/+source/gnome-shell/3.24.2-0ubuntu5 but ultimately it ended up being too difficult to run gnome-shell without gir1.2-gdm-1.0 installed so the Ubuntu Desktop Team decided to use GDM instead of LightDM plus the GDM gir by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725288/+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 1725153] Re: Reintroduce headless mode in GNOME Shell
Hello Didier, or anyone else affected, Accepted mutter into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.26.1-2ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mutter (Ubuntu Artful) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-artful ** Changed in: gnome-shell (Ubuntu Artful) Status: New => Fix Committed -- 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/1725153 Title: Reintroduce headless mode in GNOME Shell Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Fix Committed Status in gnome-shell source package in Artful: Fix Committed Status in mutter source package in Artful: Fix Committed Bug description: [Impact] * I day before the 17.10 release, we had to revert some commits in GNOME Shell due to https://bugs.launchpad.net/gnome-shell/+bug/1723577 which was a release blocker (GNOME Shell not displaying anything on multiple config). * Pinging upstream, they debugged it and found the real issue in mutter, and so fixed it, which will enable us to align again with upstream's repo. * This should mostly be a no visible-effect for previously impacted users, but GNOME Shell shouldn't crash anymore in GDM (reverting then to Xorg), triggering apport on logging, and the users can then use Wayland instead of Xorg. [Test Case] * Install both mutter and gnome-shell to their latest version in -proposed * Reboot * Ensure you have an UI in GDM * Log in into your session, check that you have an UI and everything is showing up as expected [Regression Potential] * Impact is a regression in GNOME Shell (showing up your entire UI) and not being able to log in. However, some of us (not impated by the bug) are already running latest version and don't see any issue. I have also asked 3 people being impacted by the bug and fixed by the revert to test upstream commits (prepared a package for them in a PPA), and they are running on it since yesterday, confirming Wayland is available. * The regressions are quite straightfoward to see: either you have an UI in GDM or none. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1725153/+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 1725153] Please test proposed package
Hello Didier, or anyone else affected, Accepted gnome-shell into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.26.1-0ubuntu5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1725153 Title: Reintroduce headless mode in GNOME Shell Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Fix Committed Status in gnome-shell source package in Artful: Fix Committed Status in mutter source package in Artful: Fix Committed Bug description: [Impact] * I day before the 17.10 release, we had to revert some commits in GNOME Shell due to https://bugs.launchpad.net/gnome-shell/+bug/1723577 which was a release blocker (GNOME Shell not displaying anything on multiple config). * Pinging upstream, they debugged it and found the real issue in mutter, and so fixed it, which will enable us to align again with upstream's repo. * This should mostly be a no visible-effect for previously impacted users, but GNOME Shell shouldn't crash anymore in GDM (reverting then to Xorg), triggering apport on logging, and the users can then use Wayland instead of Xorg. [Test Case] * Install both mutter and gnome-shell to their latest version in -proposed * Reboot * Ensure you have an UI in GDM * Log in into your session, check that you have an UI and everything is showing up as expected [Regression Potential] * Impact is a regression in GNOME Shell (showing up your entire UI) and not being able to log in. However, some of us (not impated by the bug) are already running latest version and don't see any issue. I have also asked 3 people being impacted by the bug and fixed by the revert to test upstream commits (prepared a package for them in a PPA), and they are running on it since yesterday, confirming Wayland is available. * The regressions are quite straightfoward to see: either you have an UI in GDM or none. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1725153/+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 1707352] Re: the change from libsane to libsane1 broke many (all?) 3rd party plug-ins for sane
Hello PeterPall, or anyone else affected, Accepted sane-backends into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/sane- backends/1.0.27-1~experimental2ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: sane-backends (Ubuntu Artful) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1707352 Title: the change from libsane to libsane1 broke many (all?) 3rd party plug- ins for sane Status in sane-backends package in Ubuntu: Fix Committed Status in sane-backends source package in Artful: Fix Committed Status in sane-backends package in Debian: New Bug description: Impact == The Debian maintainer renamed libsane to libsane1 "to match with the soname" apparently to fix a Lintian warning. libsane 1.0.25 in zesty includes libsane.so.1.25 libsane1 1.0.27 in artful includes libsane.so.1.27 This appears to be no bigger change than any ordinary new version of the library. The library rename makes it impossible to install any scanner drivers for libsane that are distributed as a .deb unless the driver distributors recompiles against Ubuntu 17.10+. Therefore, adding Provides: libsane seems reasonable here. Test Case = Visit http://support.epson.net/linux/en/iscan_c.html Download the amd64 deb .tar.gz Unzip it. Install the iscan .deb from the core folder. It won't install before this SRU because it Depends: libsane Regression Potential The fix here was proposed to the Debian maintainer in July but there's been virtually zero response on it. In the meantime the workaround that was proposed initially has started to result in automatically uninstalling gtk - which makes the system basically useless. It doesn't seem like adding the Provides will make things any worse for third-party drivers but it has a goodme chance of making things better for some. Original Bug Report === I don't know if that can be prevented in the long run. But both brscan (for my brother scanner) and iscan (for my epson scanners) have been broken by the change from libsane to libsane1. For iscan I have unpackaged the debian package, changed the dependency it contains from libsane to libsane1 and installed the changed package. But even then my epson scanners no more work leaving me without any scanner => Reporting a bug. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental1ubuntu2 Uname: Linux 4.13.0-041300rc2-lowlatency x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sat Jul 29 08:38:15 2017 EcryptfsInUse: Yes SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1707352/+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 1719043] Re: Gnome web urlbar very slow to show typed input
Hello Andrew, or anyone else affected, Accepted gtk+3.0 into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gtk+3.0/3.22.24-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gtk+3.0 (Ubuntu Artful) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1719043 Title: Gnome web urlbar very slow to show typed input Status in GTK+: Confirmed Status in epiphany-browser package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Artful: Fix Committed Status in gtk+3.0 package in Debian: Fix Released Bug description: Impact == It is very difficult to use the address bar in Epiphany on GNOME on Wayland because after a few characters, the address bar field stops redrawing. (This apparently was triggered by mutter 3.26?) Test Case = sudo apt install epiphany-browser Open the Web app Type a URL into the address bar. Type a lng URL. You should see all the characters you type into the address bar. Regression Potential === This is a minimal patch cherry-picked from GTK 3.22 git master (will be part of future GTK+ 3.22.25). I also pushed this patch to Debian unstable. Original Bug Report === First two characters typed in urlbar show immediately, other characters take up to 30 seconds to appear, or url will appear in full once enter key is pressed. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: epiphany-browser 3.26.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 18:42:19 2017 InstallationDate: Installed on 2017-09-22 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1719043/+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 1201528] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie vivid. The bug task representing the vivid nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Vivid) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1201528 Title: [INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in alsa-driver source package in Vivid: Confirmed Status in linux source package in Vivid: Won't Fix Bug description: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita 13188 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=bd987ac2-eb4b-43e7-881b-4cf2b5078e4b InstallationDate: Installed on 2014-05-11 (366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e91bd3a4-787b-404b-9f19-aa6dcbe707b0 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: Tags: vivid vivid vivid vivid Uname: Linux 3.19.0-16-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-11 (61 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: To manage notifications about this bug go to:
[Desktop-packages] [Bug 1590590] Closing unsupported series nomination.
This bug was nominated against a series that is no longer supported, ie yakkety. The bug task representing the yakkety nomination is being closed as Won't Fix. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu Yakkety) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in xserver-xorg-input-synaptics source package in Xenial: New Status in linux source package in Yakkety: Won't Fix Status in xserver-xorg-input-synaptics source package in Yakkety: New Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 16.04 xserver-xorg-input-synaptics version information: xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+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 1677327] Update Released
The verification of the Stable Release Update for nvidia-graphics- drivers-340 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1677327 Title: SRU request: dkms build fails with zesty hwe kernel [error: too few arguments to function ‘NV_GET_USER_PAGES’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Released Bug description: SRU Request: [Impact] The patch for Linux 4.9 in nvidia-340 in Ubuntu 16.04 does not match the one in 17.04. As a result, the module fails to build against the hwe 4.10 kernel. [Test Case] 1) Enable the xenial-proposed repository, and install linux-headers-generic-hwe-16.04-edge, linux-image-generic-hwe-16.04-edge, and nvidia-340. 2) Check that DKMS builds the module, then restart the system, and see if it boots correctly. If unsure, please attach your /var/log/gpu- manager.log and /var/log/Xorg.0.log [Regression Potential] Low, the exact same patch is already available in the package in 17.04. _ ADT test failure against linux-hwe-edge 4.10.0-14.16~16.04.1. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170328_225401_6519b@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170328_230514_6519b@/log.gz We need to backport build fixes for 4.9/4.10 kernels. /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c: In function ‘os_lock_user_pages’: /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:50:65: warning: passing argument 4 of ‘NV_GET_USER_PAGES’ makes integer from pointer without a cast [-Wint-conversion] page_count, write ? FOLL_WRITE : 0, user_pages, NULL); ^ In file included from /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:15:0: /var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:2094:28: note: expected ‘int’ but argument is of type ‘struct page **’ static inline long NV_GET_USER_PAGES(unsigned long start, ^ /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:48:11: error: too few arguments to function ‘NV_GET_USER_PAGES’ ret = NV_GET_USER_PAGES((unsigned long)address, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1677327/+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 1704281] Re: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1704281 Title: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170710_033239_3a664@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170710_08_3a664@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1704281/+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 1704281] Re: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2
** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1704281/+attachment/4914439/+files/make.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1704281 Title: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170710_033239_3a664@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170710_08_3a664@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1704281/+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 1704281] [NEW] nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170710_033239_3a664@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170710_08_3a664@/log.gz ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure kernel-adt-failure-lts-trusty ** Tags added: kernel-adt-failure kernel-adt-failure-lts-trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1704281 Title: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.1 ADT test failure with linux-hwe 4.10.0-27.30~16.04.2 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170710_033239_3a664@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170710_08_3a664@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1704281/+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 1250449] Re: Include the 331 driver in Ubuntu
Precise has now moved into ESM and is not recieving general updates. ** Changed in: nvidia-graphics-drivers-331 (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1250449 Title: Include the 331 driver in Ubuntu Status in nvidia-graphics-drivers-331 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-331 source package in Precise: Won't Fix Status in nvidia-graphics-drivers-331 source package in Saucy: Won't Fix Bug description: As per the title, we should introduce NVIDIA's 331.x driver in 14.04. Here's a list of the source packages we should introduce and of the archive sections they belong to: nvidia-graphics-drivers-331 (section: "restricted") nvidia-graphics-drivers-331-updates (section: "restricted") nvidia-settings-331 (section: "main") nvidia-settings-331-updates (section: "main") Also, please include "nvidia persistenced" (see bug #1246735) Note: the two drivers have transitional packages for nvidia-319 and nvidia-319-updates. The nvidia-settings packages do the same with nvidia-settings-319 and nvidia-settings-319-updates. The packages are waiting for approval in trusty-proposed (NEW) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1250449/+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 1676431] Update Released
The verification of the Stable Release Update for unity-settings-daemon has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1676431 Title: Calculator key doesn't launch the calculator Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity-settings-daemon source package in Zesty: Fix Released Bug description: Impact -- Calculator key doesn't launch the calculator in Zesty This is because gnome-calculator 3.24 renamed its .desktop. Test Case - Run Unity. Install the update. If you have a keyboard with a Calculator key, press that key. Otherwise, open System Settings>Keyboard. Switch to the Shortcuts tab. Click the row that says Launch calculator. Type something else (How about Super+C). Once it's set, press that key combination. In either case, the Calculator should start. Regression Potential This is the same fix applied in gnome-settings-daemon. https://launchpadlibrarian.net/312312021/gnome-settings- daemon_3.24.0-0ubuntu1_3.24.0-0ubuntu2.diff.gz https://git.gnome.org/browse/gnome-settings- daemon/commit/?id=ace15f5dc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1676431/+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 1677327] Re: SRU request: dkms build fails with zesty hwe kernel [error: too few arguments to function ‘NV_GET_USER_PAGES’]
** Tags added: kernel-adt-failure kernel-adt-failure-hwe-edge-4.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1677327 Title: SRU request: dkms build fails with zesty hwe kernel [error: too few arguments to function ‘NV_GET_USER_PAGES’] Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Released Bug description: SRU Request: [Impact] The patch for Linux 4.9 in nvidia-340 in Ubuntu 16.04 does not match the one in 17.04. As a result, the module fails to build against the hwe 4.10 kernel. [Test Case] 1) Enable the xenial-proposed repository, and install linux-headers-generic-hwe-16.04-edge, linux-image-generic-hwe-16.04-edge, and nvidia-340. 2) Check that DKMS builds the module, then restart the system, and see if it boots correctly. If unsure, please attach your /var/log/gpu- manager.log and /var/log/Xorg.0.log [Regression Potential] Low, the exact same patch is already available in the package in 17.04. _ ADT test failure against linux-hwe-edge 4.10.0-14.16~16.04.1. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20170328_225401_6519b@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20170328_230514_6519b@/log.gz We need to backport build fixes for 4.9/4.10 kernels. /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c: In function ‘os_lock_user_pages’: /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:50:65: warning: passing argument 4 of ‘NV_GET_USER_PAGES’ makes integer from pointer without a cast [-Wint-conversion] page_count, write ? FOLL_WRITE : 0, user_pages, NULL); ^ In file included from /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:15:0: /var/lib/dkms/nvidia-340/340.102/build/nv-linux.h:2094:28: note: expected ‘int’ but argument is of type ‘struct page **’ static inline long NV_GET_USER_PAGES(unsigned long start, ^ /var/lib/dkms/nvidia-340/340.102/build/os-mlock.c:48:11: error: too few arguments to function ‘NV_GET_USER_PAGES’ ret = NV_GET_USER_PAGES((unsigned long)address, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1677327/+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 1682238] Please test proposed package
Hello Jeremy, or anyone else affected, Accepted mutter into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.24.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1682238 Title: Update mutter and gnome-shell to 3.24.1 Status in gnome-desktop3 package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: In Progress Status in mutter source package in Zesty: Fix Committed Bug description: Impact -- 3.24.1 is a new bugfix release in the stable 3.24 series. Although mutter and gnome-shell could be handled separately, it makes sense to handle them together since they're so closely tied together. This has several fixes for GNOME Shell 3.24's new Weather feature built-in to the clock menu. There are quite a few other bugfixes too. https://git.gnome.org/browse/gnome-shell/tree/NEWS?h=gnome-3-24 https://git.gnome.org/browse/mutter/tree/NEWS?h=gnome-3-24 https://git.gnome.org/browse/gnome-shell/log?h=gnome-3-24 https://git.gnome.org/browse/mutter/log?h=gnome-3-24 Test Case - In Ubuntu GNOME, install the update then reboot. Log in. Do the same with Ubuntu Budgie (or you can install budgie-desktop on top of Ubuntu GNOME and then log in to Budgie afterwards.) Regression Potential The biggest risk is that something in the update causes Budgie or GNOME Shell to no longer work. If GNOME Shell is broken, it could break gdm which is very bad for Ubuntu GNOME users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1682238/+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 1682238] Re: Update mutter and gnome-shell to 3.24.1
Hello Jeremy, or anyone else affected, Accepted gnome-shell into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/3.24.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Zesty) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1682238 Title: Update mutter and gnome-shell to 3.24.1 Status in gnome-desktop3 package in Ubuntu: In Progress Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: In Progress Status in mutter source package in Zesty: Fix Committed Bug description: Impact -- 3.24.1 is a new bugfix release in the stable 3.24 series. Although mutter and gnome-shell could be handled separately, it makes sense to handle them together since they're so closely tied together. This has several fixes for GNOME Shell 3.24's new Weather feature built-in to the clock menu. There are quite a few other bugfixes too. https://git.gnome.org/browse/gnome-shell/tree/NEWS?h=gnome-3-24 https://git.gnome.org/browse/mutter/tree/NEWS?h=gnome-3-24 https://git.gnome.org/browse/gnome-shell/log?h=gnome-3-24 https://git.gnome.org/browse/mutter/log?h=gnome-3-24 Test Case - In Ubuntu GNOME, install the update then reboot. Log in. Do the same with Ubuntu Budgie (or you can install budgie-desktop on top of Ubuntu GNOME and then log in to Budgie afterwards.) Regression Potential The biggest risk is that something in the update causes Budgie or GNOME Shell to no longer work. If GNOME Shell is broken, it could break gdm which is very bad for Ubuntu GNOME users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1682238/+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 1682236] Re: Update gnome-desktop3 to 3.24.1
Hello Jeremy, or anyone else affected, Accepted gnome-desktop3 into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- desktop3/3.24.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-desktop3 (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1682236 Title: Update gnome-desktop3 to 3.24.1 Status in gnome-desktop3 package in Ubuntu: In Progress Status in gnome-desktop3 source package in Zesty: Fix Committed Bug description: Impact -- Since we do our own translations, the only impact is that some tools use the version reported by this package as the version of GNOME. Since we're updating most of the other GNOME packages to 3.24.1, it's appropriate to do this one too. Test Case - Install gnome-recipes (this version is a very large download; it will be a smaller download in 17.10) Open the Recipes app. In the top bar, click the Recipes app menu and select About. Switch to the System tab. The Desktop should say "GNOME 3.24.1". Regression Potential There shouldn't really be a regression here. Two languages got translation updates but those aren't really used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1682236/+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 1682132] Re: Update gnome-settings-daemon to 3.24.1
Hello Jeremy, or anyone else affected, Accepted gnome-settings-daemon into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gnome-settings-daemon/3.24.1-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-settings-daemon (Ubuntu Zesty) Status: New => Fix Committed ** Tags added: verification-needed -- 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/1682132 Title: Update gnome-settings-daemon to 3.24.1 Status in gnome-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Zesty: Fix Committed Bug description: Impact -- gnome-settings-daemon 3.24.1 is a bugfix release in the stable 3.24 series. https://git.gnome.org/browse/gnome-settings-daemon/log?h=gnome-3-24 https://git.gnome.org/browse/gnome-settings-daemon/tree/NEWS?h=gnome-3-24 https://git.gnome.org/browse/libgnome-volume-control/commit/?id=d52194f https://git.gnome.org/browse/libgnome-volume-control/commit/?id=ce8e488 gnome-settings-daemon itself is used by Ubuntu Budgie and Ubuntu GNOME. The schemas are also used by Ubuntu, Ubuntu Kylin and Ubuntu MATE. And Ubuntu Touch. Test Case - After installing the update, reboot and log into GNOME Regression Potential The changes look like minimal bugfixes. Affected are Bluetooth audio, GNOME's Night Light feature, and the clipboard. Schemas shouldn't be affected in this update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1682132/+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 1657677] Update Released
The verification of the Stable Release Update for opencc has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to opencc in Ubuntu. https://bugs.launchpad.net/bugs/1657677 Title: [SRU]fix versioned Breaks/Replaces Status in opencc package in Ubuntu: Invalid Status in opencc source package in Yakkety: Fix Committed Bug description: [Impact] Previous SRU of opencc to yakkety introduced a bug that the versioned Breaks/Replaces requires a higher version (1.0.4-3, the debian one) than the update version (1.0.4-1ubuntu0.16.10.1), this prevents libopencc-dev from being installed to satisfy build dependencies. [Test Case] Installing libopencc-dev using apt-get, the dependency should be satisfied without problem. [Regression Potential] Changing the dependency version should be safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencc/+bug/1657677/+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 1629849] [NEW] network-manager 1.2.2-0ubuntu0.16.04.1 ADT test failure with linux 4.4.0-41.61
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/network-manager/20161001_130521@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/network-manager/20161001_153354@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/n/network-manager/20160930_222540@/log.gz ** Affects: network-manager (Ubuntu) Importance: Critical Status: New ** Changed in: network-manager (Ubuntu) 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/1629849 Title: network-manager 1.2.2-0ubuntu0.16.04.1 ADT test failure with linux 4.4.0-41.61 Status in network-manager package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/network-manager/20161001_130521@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/network-manager/20161001_153354@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/n/network-manager/20160930_222540@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629849/+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 1592721] Please test proposed package
Hello Mathieu, or anyone else affected, Accepted network-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.2.2-0ubuntu0.16.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1592721 Title: Don't write search domains to resolv.conf in the case of split DNS Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Bug description: [Impact] All VPN users meaning to use split-tunnelling in a situation where leaking DNS data to the internet about what might be behind their VPN is undesirable. [Test case] 1) connect to VPN 2) Use dig to request a name that should be on the VPN 3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only gone through the VPN nameservers (only its request number should have increased by one) 4) Use dig to request a name off-VPN, such as google.com. 5) Verify (kill -USR1 again) that the request has caused the non-VPN nameserver request number to increase, and that the VPN number has not increased. It is easier to verify this when there is as little traffic as possible on the system, to avoid spurious DNS requests which would make it harder to validate the counters. [Regression potential] This change modifies the way in which DNS nameservers and search domains are passed to dnsmasq, as such, if a VPN is configured in a non-standard way and intended to be used to resolve all network requests (which is typically not the case for split-tunnelling) or if the public network is intended to always resolve all requests while the VPN still provides search domains, one might observe incorrect behavior. Possible failure cases would include failure to resolve names correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving to the incorrect values (if the wrong nameserver is used). --- Currently, NM will write all search domains to both any DNS-handling plugins running, and also to resolv.conf / resolvconf; in all cases. The issue is that doing so means that in the split-DNS case on VPNs, you might get a negative response from all nameservers, then a new request by glibc with the search tacked on, to nameservers again, which might cause DNS requests for "private" resources (say, on the VPN) to be sent to external, untrusted resolvers, or for DNS queries not meant for VPN nameservers to be sent through the VPN anyway. This is fixable in the case where we have a caching plugin running (such as dnsmasq). dnsmasq will already know about the search domains and use that to limit queries to the right nameservers when a VPN is running. Writing search domains to resolv.conf is unnecessary in this case. We should still write search domains if no caching gets done, as we then need to expect glibc to send requests as it otherwise would. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+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 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix
Hello Dan, or anyone else affected, Accepted network-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.2.2-0ubuntu0.16.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- 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/1609898 Title: dhclient incorrectly assumes a /64 ipv6 prefix Status in isc-dhcp package in Ubuntu: Fix Committed Status in network-manager package in Ubuntu: Fix Committed Status in isc-dhcp source package in Precise: Fix Released Status in network-manager source package in Precise: Invalid Status in isc-dhcp source package in Trusty: Fix Released Status in network-manager source package in Trusty: Triaged Status in isc-dhcp source package in Xenial: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Committed Status in network-manager source package in Yakkety: Fix Committed Status in isc-dhcp package in Debian: Fix Released Bug description: [Impact] clients who get an ipv6 address from a dhcpv6 server assume the address has a /64 prefix, but that is not necessarily true, and if the subnet is different than /64 those clients will not be able to reach other addresses in that /64 prefix because the other systems are not on-link. This /64 assumption of dhclient effectively breaks the client networking for certain addresses. [Test Case] Set up a server with two interface nics, and one client connected to each of those interfaces. On the server, set up a ipv6 subnet on each interface, with a larger prefix than /64, e.g.: 2001:db8:0:0:1::/96 2001:db8:0:0:2::/96 configure dhcpv6 on the server, to provide ipv6 addresses on each interface. Set the server as the default ipv6 route for the clients. Allow the clients to get dhcpv6 ipv6 addresses from the server. The clients will each get a ipv6 address with a /64 prefix, due to the bug in dhclient. Try to ping (or otherwise communicate) between the clients. Since they have /64 prefixes, they think they are on-link with each other, but they are not, so they can't communicate. After the dhclient bug is fixed, repeat the above setup, and the clients will get /128 prefixes instead, and then will be able to communicate with each other, because they will route the traffic to each other through the server. [Regression Potential] Non-standard (i.e. not /64) subnets served by dhcpv6 currently are broken, this fixes that. However, any ipv6 network configurations that rely on the previous incorrect assumed /64 behavior (as described here: https://tools.ietf.org/html/rfc5942#section-5) in order to allow dhcpv6 clients to communicate with other systems inside the subnet, but do not use RA to also provide clients with the actual prefix len, will break. To clarify: a server that provides clients with dhcpv6 addresses, but does not also provide the prefix len via RA, will change behavior; previously, all clients on the subnet could talk directly to each other, with this update the clients cannot talk to each other directly; all traffic between clients will be routed through the default gateway. Further, if the network does not provide a default gateway - for example a local network that is intended only for traffic between local servers - the clients will not be able to talk to each other at all. Note that such configurations *are* broken configurations, that just happened to work before because of incorrect dhcp client behavior; such configurations must be updated to perform RA to provide the prefix len to clients. See comment 30 for details on how to configure radvd to restore network functionality. [Other Info] This is fixed in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1627641] Please test proposed package
Hello Martin, or anyone else affected, Accepted network-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.2.2-0ubuntu0.16.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1627641 Title: Backport netplan to xenial Status in network-manager package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Committed Bug description: For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more. netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager. PATCHES: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial=6dcdb85 https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=4e9c52b0bb REGRESSION POTENTIAL: netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades. NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work. systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations. TEST PLAN: 1. Run "NetworkManager --print-config" and save the output. 2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work. 3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1. 4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+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 1627641] Re: Backport netplan to xenial
Hello Martin, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.12~16.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: nplan (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1627641 Title: Backport netplan to xenial Status in network-manager package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Committed Bug description: For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more. netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager. PATCHES: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial=6dcdb85 https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=4e9c52b0bb REGRESSION POTENTIAL: netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades. NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work. systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations. TEST PLAN: 1. Run "NetworkManager --print-config" and save the output. 2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work. 3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1. 4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+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 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS
Hello Mathieu, or anyone else affected, Accepted network-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.2.2-0ubuntu0.16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: network-manager (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1592721 Title: Don't write search domains to resolv.conf in the case of split DNS Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Bug description: [Impact] All VPN users meaning to use split-tunnelling in a situation where leaking DNS data to the internet about what might be behind their VPN is undesirable. [Test case] 1) connect to VPN 2) Use dig to request a name that should be on the VPN 3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only gone through the VPN nameservers (only its request number should have increased by one) 4) Use dig to request a name off-VPN, such as google.com. 5) Verify (kill -USR1 again) that the request has caused the non-VPN nameserver request number to increase, and that the VPN number has not increased. It is easier to verify this when there is as little traffic as possible on the system, to avoid spurious DNS requests which would make it harder to validate the counters. [Regression potential] This change modifies the way in which DNS nameservers and search domains are passed to dnsmasq, as such, if a VPN is configured in a non-standard way and intended to be used to resolve all network requests (which is typically not the case for split-tunnelling) or if the public network is intended to always resolve all requests while the VPN still provides search domains, one might observe incorrect behavior. Possible failure cases would include failure to resolve names correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving to the incorrect values (if the wrong nameserver is used). --- Currently, NM will write all search domains to both any DNS-handling plugins running, and also to resolv.conf / resolvconf; in all cases. The issue is that doing so means that in the split-DNS case on VPNs, you might get a negative response from all nameservers, then a new request by glibc with the search tacked on, to nameservers again, which might cause DNS requests for "private" resources (say, on the VPN) to be sent to external, untrusted resolvers, or for DNS queries not meant for VPN nameservers to be sent through the VPN anyway. This is fixable in the case where we have a caching plugin running (such as dnsmasq). dnsmasq will already know about the search domains and use that to limit queries to the right nameservers when a VPN is running. Writing search domains to resolv.conf is unnecessary in this case. We should still write search domains if no caching gets done, as we then need to expect glibc to send requests as it otherwise would. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+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 1627641] Re: Backport netplan to xenial
Hello Martin, or anyone else affected, Accepted network-manager into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/network- manager/1.2.2-0ubuntu0.16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: network-manager (Ubuntu Xenial) Status: In Progress => Fix Committed -- 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/1627641 Title: Backport netplan to xenial Status in network-manager package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in nplan source package in Xenial: Triaged Status in systemd source package in Xenial: Fix Committed Bug description: For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more. netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager. PATCHES: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial=6dcdb85 https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=4e9c52b0bb REGRESSION POTENTIAL: netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades. NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work. systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations. TEST PLAN: 1. Run "NetworkManager --print-config" and save the output. 2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work. 3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1. 4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+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 1627641] Re: Backport netplan to xenial
Hello Martin, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu9 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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/1627641 Title: Backport netplan to xenial Status in network-manager package in Ubuntu: Fix Released Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: In Progress Status in nplan source package in Xenial: Triaged Status in systemd source package in Xenial: Fix Committed Bug description: For snappy (at first at least) we need to provide netplan in xenial, as for the first snappy GA release we must not use any PPAs any more. netplan's NetworkManager backend depends on two patches to read configuration and connections from /run/NetworkManager/. These will need to be backported for full netplan support; but they are not required for snappy as this will use a snapped NM. However, this will need a temporary hack (https://code.launchpad.net/%7Emorphis/netplan/+git/netplan/+merge/306607) until snaps can actually properly support OS components like NetworkManager. PATCHES: https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?h=xenial=6dcdb85 https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu-xenial=4e9c52b0bb REGRESSION POTENTIAL: netplan: The risk for existing installations is practically zero as nplan does not exist in xenial yet and thus will not be pulled in during upgrades. NetworkManager: Nothing in xenial expects/uses /run/NetworkManager/ and as it's an ephemeral tmpfs there is no risk of existing files there. If the patches are broken it could in theory happen that NetworkManager also does not properly read files from /etc/NetworkManager/ any more, so the -proposed package must verify that existing connections still work. systemd: This does change behavior of networkd on restart, but the previous behaviour was arguably buggy. networkd is not being used by default or advertised in Ubuntu 16.04, so this will not affect the vast majority of installations. TEST PLAN: 1. Run "NetworkManager --print-config" and save the output. 2. Install the proposed NetworkManager and confirm that existing connections (from /etc/NetworkManager/system-connections) still work. 3. Run "NetworkManager --print-config" again and verify that the output is the same as in step 1. 4. netplan has a very comprehensive integration test suite run as autopkgtest, which covers NetworkManager (including the /run patches) and network. Confirm that it succeeds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1627641/+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 1626568] Re: rfkill autopkgtests broken with linux 4.8: fake-rfkill.ko: Unknown symbol in module
** Tags added: kernel-4.8 -- 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/1626568 Title: rfkill autopkgtests broken with linux 4.8: fake-rfkill.ko: Unknown symbol in module Status in network-manager package in Ubuntu: In Progress Bug description: The two rfkill tests now fail in yakkety since linux got upgraded to 4.8, like in in https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety/yakkety/i386/n/network-manager/20160922_091844@/log.gz . It still builds fine: $ sudo make -f debian/tests/Makefile fake-rfkill make -C /lib/modules/4.8.0-15-generic/build KBUILD_SRC=/lib/modules/4.8.0-15-generic/build M=/tmp/autopkgtest.zD5lki/build.WwA/real-tree/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.8.0-15-generic' Building modules, stage 2. MODPOST 1 modules But it can't be loaded: $ sudo insmod debian/tests/fake-rfkill.ko insmod: ERROR: could not insert module debian/tests/fake-rfkill.ko: Unknown symbol in module $ dmesg [ 7779.796145] fake_rfkill: Unknown symbol rfkill_unregister (err 0) [ 7779.796153] fake_rfkill: Unknown symbol rfkill_destroy (err 0) [ 7779.796162] fake_rfkill: Unknown symbol rfkill_alloc (err 0) [ 7779.796168] fake_rfkill: Unknown symbol rfkill_register (err 0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1626568/+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 1581076] Re: Xorg segfaults on start-up on Big Endian PPC hardware
Hello Alex, or anyone else affected, Accepted xorg-server into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Tags added: verification-needed -- 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/1581076 Title: Xorg segfaults on start-up on Big Endian PPC hardware Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Committed Bug description: On my Big Endian PowerPC machine, Xorg segfaults when starting. I have been able to confirm that this does not happen when building Xorg from upstream source, and then further confirmed that the source of the segfault appears to be caused by a non-upstreamed, ubuntu specific patch. When building the xorg-server-1.18.3 deb from source, I commented out the following patches from debian/patches/series to try to isolate the source of the crash. With the following patches not-applied, and the resulting .deb package built, the segfault on start does not occur. 08_xfree86_fix_ia64_inx_outx.diff 105_nvidia_autodetect.patch 168_glibc_trace_to_stderr.patch 188_default_primary_to_first_busid.patch 190_cache-xkbcomp_output_for_fast_start_up.patch 191-Xorg-add-an-extra-module-path.patch 232-xf86compatoutput-valgrind.patch no-nv.patch 228_autobind_gpu.patch xf86-inactive-gpuscreen.patch config-add-no-removal.patch xf86-ignore-conflicting-rr-caps.patch fix-detach-gpu.patch disable-rotation-transform-gpuscreens.patch xmir.patch xmir-desktop-file-hint-flag.patch drm_device_keep_trying.patch xi2-resize-touch.patch xmir-fixes.diff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1581076/+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 1586260] Re: System freeze & no display if set External monitor as primary (Performance mode)
Hello Xinxiu, or anyone else affected, Accepted xorg-server into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server (Ubuntu Xenial) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed -- 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/1586260 Title: System freeze & no display if set External monitor as primary (Performance mode) Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-lts-xenial package in Ubuntu: New Status in xorg-server source package in Trusty: Invalid Status in xorg-server-lts-vivid source package in Trusty: Fix Released Status in xorg-server source package in Xenial: Fix Committed Status in xorg-server source package in Yakkety: Fix Released Bug description: [Impact] System freeze & no display if set External monitor as primary (Performance mode) [Test case] 1. Setup Graphic mode to Performance mode 2. Plug External monitor with HDMI 3. Set display mode to External monitor only is pass 4. Set display mode to Extend/ Mirror mode Expected results: External monitor can be set as primary normally Actual results: System freeze & no display if set External monitor as primary (Performance mode) [Regression potential] Unknown right now, upstream review pending. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1586260/+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 1590553] Re: Xmir -rootless: Buttons are randomly unclickable (popups vanish instantly)
Hello Daniel, or anyone else affected, Accepted xorg-server into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- 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/1590553 Title: Xmir -rootless: Buttons are randomly unclickable (popups vanish instantly) Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Committed Bug description: Xmir -rootless: Buttons are randomly unclickable I've noticed this in LibreOffice Impress and Chromium browser. Sometimes when clicking buttons, the button just flickers and does nothing. Sometimes it also involves a popup menu flickering and out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1590553/+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 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work
Hello Albert, or anyone else affected, Accepted xorg-server into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- 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/1591356 Title: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work Status in Canonical System Image: Confirmed Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Triaged Status in libertine package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Status in gtk+3.0 source package in Xenial: New Status in libertine source package in Xenial: New Status in xorg-server source package in Xenial: Fix Committed Status in xorg-server package in Ubuntu RTM: New Bug description: [Impact] Auto key repeating does not work in Libertine X apps which is very frustrating to users. [Test Case] 1. Install xterm in libertine 2. Start xterm from the "Xapps" scope 3. Wait for xterm to appear 4. Press and hold a key See how it only appears once and not multiple times as it should. [Regression Potential] Non observed. Original Description: How to reproduce: * Install xterm in libertine * Start xterm from the "Xapps" scope * Wait for xterm to appear * Press and hold a key * See how it only appears once and not multiple times as it should To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591356/+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 1613708] Re: [regression] Xmir: Some buttons are unclickable after rotating the screen
Hello Victor, or anyone else affected, Accepted xorg-server into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- 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/1613708 Title: [regression] Xmir: Some buttons are unclickable after rotating the screen Status in Canonical System Image: Fix Committed Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Committed Bug description: [Impact] XMir clients do not have their input transform matrix modified properly when the screen dimensions and orientation change (ie. rotation). This shows up primarily on Bq M10 tablets which rotate on startup. [Test Case] Install XMir on a device that supports screen rotation. Connect a client (using Libertine is the easiest way to do this). Attempt to use direct or indirect pointer input on the right side of the screen. The bug is it does nothing. [Regression Potential] This change affects only the XMir server. There is potential that XMir functionality is compromized but mainline x.org functionality is unaffected. This XMir patch update is pulled directly from Ubuntu current development release "Yakkety Yak" where it has been in production for more than 6 weeks without apparent regressions. [Other Info] The patch update also includes bugfixes for bug #1617925, bug #1617932, and bug #1591356. This patch differs from the patch in Ubuntu "Yakkety Yak" to compile with Mir 0.21. The only functional difference is an extra message logged when run against Mir 0.24. -- original bug description follows -- Enviroment: current build number: 169 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en last update: 2016-08-16 10:23:29 version version: 169 version ubuntu: 20160816 version device: 20160809.0 version custom: 20160805--42-20-vivid Product: BQ M10 FHD Steps to reproduce: 1º Open LibreOffice and try to print something 2º Print settings window appear, try to click on Accept/Cancel/Exit etc 3º Buttons on LibreOffice won't respond 1º Open Firefox 2º Mouse-over on search,downloads,bookmarks etc 3º Seems like mouse-over is not focused and is clicking is not responding Current result: Some Xapps buttons are not responding(tested on Firefox and LibreOffice Writer) Expected result: Add info: This is using xmir from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-053/+packages. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1613708/+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 1617932] Re: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension
Hello Daniel, or anyone else affected, Accepted xorg-server into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- 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/1617932 Title: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Committed Bug description: Xmir with glamor is spending 11% of its CPU time in epoxy_has_gl_extension. This only happens on desktop where the default Xmir renderer uses glamor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1617932/+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 1617925] Re: Xmir: Received an unknown 11 event
Hello Daniel, or anyone else affected, Accepted xorg-server into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- 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/1617925 Title: Xmir: Received an unknown 11 event Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Fix Committed Bug description: Xmir says: Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event Received an unknown 11 event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1617925/+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 1619142] Re: [MRE] Update to 1.18.4
Hello Timo, or anyone else affected, Accepted xorg-server into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server-lts-xenial in Ubuntu. https://bugs.launchpad.net/bugs/1619142 Title: [MRE] Update to 1.18.4 Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-lts-xenial package in Ubuntu: Invalid Status in xorg-server source package in Trusty: Invalid Status in xorg-server-lts-xenial source package in Trusty: New Status in xorg-server source package in Xenial: Fix Committed Status in xorg-server-lts-xenial source package in Xenial: Invalid Bug description: Update xserver to new minor release 1.18.4 in order to gain bugfixes from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1619142/+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 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable
What does a manual "modprobe nvidia" (or whatever the failing driver is called) say. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574732 Title: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: New Bug description: I am running Ubuntu 16.04 since at least four months, always with the nvidia proprietary drivers (installed from the repository). I used nvidia-361 for a while with no issues (and i need it for steam gaming). However, an update installed on my machine yesterday breaks the nvidia drivers. I tried purging the driver, rebooting and reinstalling and i tried a newer version for the ubuntu-drivers ppa. Nothing helps: With the nvidia driver installed, i get a low- resolution login screen, but cannot login due to missing 3d acceleration. Running on nouveau works fine. This seems very strange to since everything worked until this afternoon. Yesterday, i was happily playing games on steam, installed some updates and now, my graphics are broken. $ lspci | grep NVIDIA 01:00.0 VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750] (rev a2) 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Apr 25 17:45:12 2016 DistUpgraded: 2016-03-11 21:34:38,175 DEBUG enabling apt cron job DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-18-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750] [10de:1381] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Palit Microsystems Inc. GM107 [GeForce GTX 750] [1569:1381] InstallationDate: Installed on 2016-01-05 (110 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=ed669b2d-c3af-4570-9eb7-2978557208ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to xenial on 2016-03-11 (44 days ago) dmi.bios.date: 05/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: H97 Performance dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd05/18/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97Performance:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Apr 25 17:44:29 2016 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574732/+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 1516007] Re: nvidia-graphics-drivers-*: build failures against kernel 4.3
Fixed in the latest uploads. ** Summary changed: - nvidia-grapics-drivers-*: build failures against kernel 4.3 + nvidia-graphics-drivers-*: build failures against kernel 4.3 ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Fix Released ** Changed in: nvidia-graphics-drivers-340-updates (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1516007 Title: nvidia-graphics-drivers-*: build failures against kernel 4.3 Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340-updates package in Ubuntu: Fix Released Bug description: We are seeing DKMS build failures against the Ubuntu 4.3 kernel: http://people.canonical.com/~kernel/status/adt-matrix/canonical- kernel-team--unstable/xenial-linux-meta.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1516007/+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 1516001] Re: fglrx-installer: build failures against kernel 4.3
Fixed in the latest uploads. ** Changed in: fglrx-installer (Ubuntu) Status: New => Fix Released ** Changed in: fglrx-installer-updates (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1516001 Title: fglrx-installer: build failures against kernel 4.3 Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Bug description: We are seeing DKMS build failures against the Ubuntu 4.3 kernel: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/f /fglrx-installer/20151113_125356@/log.gz Also fglrx-installer-updates: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/f /fglrx-installer-updates/20151113_125319@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1516001/+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 1518958] [NEW] fglrx-installer: dkms build failures with linux-lts-wily
Public bug reported: We are seeing dkms build failures on i386 with linux-lts-wily. ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: New ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Changed in: fglrx-installer (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New -- 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/1518958 Title: fglrx-installer: dkms build failures with linux-lts-wily Status in fglrx-installer package in Ubuntu: New Status in fglrx-installer-updates package in Ubuntu: New Bug description: We are seeing dkms build failures on i386 with linux-lts-wily. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1518958/+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 1516001] Re: fglrx-installer: build failures against kernel 4.3
** Tags added: xenial-4.3-adt-failures -- 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/1516001 Title: fglrx-installer: build failures against kernel 4.3 Status in fglrx-installer package in Ubuntu: New Status in fglrx-installer-updates package in Ubuntu: New Bug description: We are seeing DKMS build failures against the Ubuntu 4.3 kernel: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/f /fglrx-installer/20151113_125356@/log.gz Also fglrx-installer-updates: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/f /fglrx-installer-updates/20151113_125319@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1516001/+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 1516007] Re: nvidia-grapics-drivers-*: build failures against kernel 4.3
** Tags added: xenial-4.3-adt-failures -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1516007 Title: nvidia-grapics-drivers-*: build failures against kernel 4.3 Status in nvidia-graphics-drivers-304 package in Ubuntu: New Status in nvidia-graphics-drivers-304-updates package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in nvidia-graphics-drivers-340-updates package in Ubuntu: New Bug description: We are seeing DKMS build failures against the Ubuntu 4.3 kernel: http://people.canonical.com/~kernel/status/adt-matrix/canonical- kernel-team--unstable/xenial-linux-meta.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1516007/+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 1516007] [NEW] nvidia-grapics-drivers-*: build failures against kernel 4.3
Public bug reported: We are seeing DKMS build failures against the Ubuntu 4.3 kernel: http://people.canonical.com/~kernel/status/adt-matrix/canonical-kernel- team--unstable/xenial-linux-meta.html ** Affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-304-updates (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-340-updates (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304-updates (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340-updates (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-352 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-352-updates (Ubuntu) Importance: Undecided Status: New ** No longer affects: nvidia-graphics-drivers-352 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-352-updates (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1516007 Title: nvidia-grapics-drivers-*: build failures against kernel 4.3 Status in nvidia-graphics-drivers-304 package in Ubuntu: New Status in nvidia-graphics-drivers-304-updates package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in nvidia-graphics-drivers-340-updates package in Ubuntu: New Bug description: We are seeing DKMS build failures against the Ubuntu 4.3 kernel: http://people.canonical.com/~kernel/status/adt-matrix/canonical- kernel-team--unstable/xenial-linux-meta.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1516007/+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 1516001] [NEW] fglrx-installer: build failures against kernel 4.3
Public bug reported: We are seeing DKMS build failures against the Ubuntu 4.3 kernel: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/f/fglrx- installer/20151113_125356@/log.gz Also fglrx-installer-updates: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/f/fglrx- installer-updates/20151113_125319@/log.gz ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Also affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Description changed: We are seeing DKMS build failures against the Ubuntu 4.3 kernel: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/f/fglrx- installer/20151113_125356@/log.gz + + Also fglrx-installer-updates: + + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac + /autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/f/fglrx- + installer-updates/20151113_125319@/log.gz -- 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/1516001 Title: fglrx-installer: build failures against kernel 4.3 Status in fglrx-installer package in Ubuntu: New Status in fglrx-installer-updates package in Ubuntu: New Bug description: We are seeing DKMS build failures against the Ubuntu 4.3 kernel: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/f /fglrx-installer/20151113_125356@/log.gz Also fglrx-installer-updates: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial-canonical-kernel-team-unstable/xenial/amd64/f /fglrx-installer-updates/20151113_125319@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1516001/+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 1486821] [NEW] gstreamer0.10: merge 0.10.36-1.5
Public bug reported: gstreamer0.10: merge 0.10.36-1.5 ** Affects: gstreamer0.10 (Ubuntu) Importance: Medium Assignee: Andy Whitcroft (apw) Status: In Progress ** Changed in: gstreamer0.10 (Ubuntu) Status: New = In Progress ** Changed in: gstreamer0.10 (Ubuntu) Importance: Undecided = Medium ** Changed in: gstreamer0.10 (Ubuntu) Assignee: (unassigned) = Andy Whitcroft (apw) ** Changed in: gstreamer0.10 (Ubuntu) Milestone: None = ubuntu-15.08 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1486821 Title: gstreamer0.10: merge 0.10.36-1.5 Status in gstreamer0.10 package in Ubuntu: In Progress Bug description: gstreamer0.10: merge 0.10.36-1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1486821/+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 1476685] Re: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
The apport hook has failed to run correctly. I suspect there is nothing to be found now, but moving over there. ** Package changed: initramfs-tools (Ubuntu) = apport (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1476685 Title: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: Confirmed Bug description: Most likely a duplicate report, but was just running apt-get upgrade and it returned an exit status 1. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: initramfs-tools 0.103ubuntu4.2 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Tue Jul 21 09:01:08 2015 DpkgHistoryLog: DpkgTerminalLog: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-05-20 (61 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: initramfs-tools Title: package initramfs-tools 0.103ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1476685/+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 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge
** Changed in: linux-lts-quantal (Ubuntu Precise) Status: Invalid = Fix Committed ** Changed in: linux (Ubuntu Precise) Status: Invalid = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in Mesa: Unknown Status in linux package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in linux source package in Precise: Fix Committed Status in linux-lts-quantal source package in Precise: Fix Committed Status in linux-lts-raring source package in Precise: Invalid Status in mesa source package in Precise: Triaged Status in linux source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux source package in Raring: Invalid Status in linux-lts-quantal source package in Raring: Invalid Status in linux package in Debian: New Status in linux package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [81076023] kthread+0x93/0xa0 [26285.658644] [8168a3e4] kernel_thread_helper+0x4/0x10 [26285.658649] [81075f90] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [8168a3e0] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed...
[Desktop-packages] [Bug 465942] Re: Hardware device disappearing from Sound Preferences on ASUS 0x104381b3
** Changed in: linux (Ubuntu Lucid)
Status: Incomplete = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/465942
Title:
Hardware device disappearing from Sound Preferences on ASUS 0x104381b3
Status in alsa-driver package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in alsa-driver source package in Lucid:
New
Status in linux source package in Lucid:
Fix Committed
Status in alsa-driver source package in Maverick:
Won't Fix
Status in linux source package in Maverick:
Invalid
Bug description:
Tried to configure audio using Sound Preferences. The driver
initially showed in the window but then it disappeared. Rebooting is
needed to have it reappear. But it disappears again as soon as I try
to configure it.
I ran the following command *after* the driver had disappeared from
the Sound Prefs window. Evidently, Alsa still knows it's there.
$ aplay -l
List of PLAYBACK Hardware Devices
card 0: VT82xx [HDA VIA VT82xx], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: VT82xx [HDA VIA VT82xx], device 1: AD198x Digital [AD198x Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
As far as I can tell, all the kernel modules are loaded.
Using the 9.10 release - fresh install, no upgrade. Have had no
problems with earlier releases (did not use 8.10 or 9.04).
ProblemType: Bug
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: VT82xx [HDA VIA VT82xx], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp',
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0',
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/seq',
'/dev/snd/timer', '/dev/sequencer', '/dev/sequencer2'] failed with exit code 1:
Card0.Amixer.info:
Card hw:0 'VT82xx'/'HDA VIA VT82xx at 0xcfffc000 irq 17'
Mixer name : 'Analog Devices AD1986A'
Components : 'HDA:11d41986,1043818f,00100500'
Controls : 37
Simple ctrls : 21
CheckboxCommand: alsa_record_playback
CheckboxDescription:
Open the volume control application by right-clicking on the speaker icon in
the panel and selecting Sound Preferences. Select the Input tab and choose
any alternate (non-default) device(s). Select the Output tab and choose any
alternate (non-default) device(s). When you are done, click the Test button,
then speak into the microphone. After a few seconds, your speech will be played
back to you.
Did you hear your speech played back?
CheckboxTest: alsa_record_playback_alternates
Date: Sat Oct 31 15:06:56 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5)
Package: alsa-base 1.0.20+dfsg-1ubuntu5
PackageArchitecture: all
ProcEnviron:
SHELL=/bin/bash
LANG=en_NZ.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: alsa-driver
Tags: checkbox-bug
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
(gnome-settings-daemon:1625): GLib-CRITICAL **: g_propagate_error: assertion
`src != NULL' failed
(gnome-settings-daemon:1625): GLib-CRITICAL **: g_propagate_error: assertion
`src != NULL' failed
(polkit-gnome-authentication-agent-1:1710): GLib-CRITICAL **:
g_once_init_leave: assertion `initialization_value != 0' failed
(nautilus:1681): Eel-CRITICAL **: eel_preferences_get_boolean: assertion
`preferences_is_initialized ()' failed
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: VT82xx [HDA VIA VT82xx], device 0: AD198x Analog [AD198x Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp',
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0',
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1p', '/dev/snd/seq',
'/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1:
Card0.Amixer.info:
Card hw:0 'VT82xx'/'HDA VIA VT82xx at 0xcfffc000 irq 17'
Mixer name : 'Analog Devices AD1986A'
Components : 'HDA:11d41986,1043818f,00100500'
Controls : 37
Simple ctrls : 21
DistroRelease: Ubuntu 10.04
Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
PackageArchitecture: all
ProcEnviron:
LANG=en_NZ.utf8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Tags: lucid
Uname: Linux 2.6.32-21-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 03/25/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5VD2-VM ACPI BIOS Revision 1302
[Desktop-packages] [Bug 583983] Re: Sound capture (microphone) works on LiveCD, but don't work after installation
** Changed in: linux (Ubuntu Lucid) Status: Triaged = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/583983 Title: Sound capture (microphone) works on LiveCD, but don't work after installation Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Invalid Status in alsa-driver source package in Lucid: Fix Committed Status in linux source package in Lucid: Fix Committed Bug description: When LiveCD session sound capture work. Right after installation it doesn't. Ubuntu 10.04_amd64. Notebook Aser Aspire 5110. Workaround. After installation make next: In file /etc/modprobe.d/alsa-base.conf add string: options snd-hda-intel position_fix=1, and restart. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: alsa-base 1.0.22.1+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leo-lucid 1998 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xf840 irq 16' Mixer name : 'Realtek ALC883' Components : 'HDA:10ec0883,1025009f,0012 HDA:14f12bfa,1025009f,0009' Controls : 23 Simple ctrls : 13 Date: Fri May 21 23:58:06 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100224.1) PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=ru_RU.utf8 SHELL=/bin/bash SourcePackage: alsa-driver dmi.bios.date: 08/22/2008 dmi.bios.vendor: Acer dmi.bios.version: V3.13 dmi.board.name: Navarro dmi.board.vendor: Acer dmi.board.version: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5110:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A: dmi.product.name: Aspire 5110 dmi.product.version: V3.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/583983/+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 1434579] Re: Unable to install VirtualBox Guest Service in 15.04
** Changed in: linux (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1434579 Title: Unable to install VirtualBox Guest Service in 15.04 Status in linux package in Ubuntu: Fix Committed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: It is not longer possible to select VirtualBox Guest Service in 15.04. The only options available are: * Continue using a manually install driver * Do not use the device The option 'Using x86 virtualisation solution - guest addition module' is no longer selectable. See the attached screen shot. This is from a fresh install of Ubuntu MATE 15.04 daily (20th March) and no drivers have been manually installed. In light of the Virtualbox issue where new installs on Virtualbox have a resolution of 640x480 (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/) this is going to be a frustration for many users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434579/+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 1434579] Re: Unable to install VirtualBox Guest Service in 15.04
** Changed in: linux (Ubuntu) Milestone: None = ubuntu-15.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1434579 Title: Unable to install VirtualBox Guest Service in 15.04 Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: It is not longer possible to select VirtualBox Guest Service in 15.04. The only options available are: * Continue using a manually install driver * Do not use the device The option 'Using x86 virtualisation solution - guest addition module' is no longer selectable. See the attached screen shot. This is from a fresh install of Ubuntu MATE 15.04 daily (20th March) and no drivers have been manually installed. In light of the Virtualbox issue where new installs on Virtualbox have a resolution of 640x480 (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/) this is going to be a frustration for many users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434579/+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 1434579] Re: Unable to install VirtualBox Guest Service in 15.04
** Changed in: linux (Ubuntu) Status: New = In Progress ** Changed in: linux (Ubuntu) Importance: Undecided = High ** Changed in: linux (Ubuntu) Assignee: (unassigned) = Andy Whitcroft (apw) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1434579 Title: Unable to install VirtualBox Guest Service in 15.04 Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in virtualbox package in Ubuntu: Confirmed Bug description: It is not longer possible to select VirtualBox Guest Service in 15.04. The only options available are: * Continue using a manually install driver * Do not use the device The option 'Using x86 virtualisation solution - guest addition module' is no longer selectable. See the attached screen shot. This is from a fresh install of Ubuntu MATE 15.04 daily (20th March) and no drivers have been manually installed. In light of the Virtualbox issue where new installs on Virtualbox have a resolution of 640x480 (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/) this is going to be a frustration for many users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434579/+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 1429771] [NEW] package gnome-menus 3.10.1-0ubuntu5 failed to install/upgrade: triggers looping, abandoned
Public bug reported: During apt-get dist-upgrade, after reboot, this popped out. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: gnome-menus 3.10.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 Date: Mon Mar 9 09:05:09 2015 DuplicateSignature: package:gnome-menus:3.10.1-0ubuntu5:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2013-06-20 (626 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618) SourcePackage: gnome-menus Title: package gnome-menus 3.10.1-0ubuntu5 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to vivid on 2013-11-10 (483 days ago) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1429771 Title: package gnome-menus 3.10.1-0ubuntu5 failed to install/upgrade: triggers looping, abandoned Status in gnome-menus package in Ubuntu: New Bug description: During apt-get dist-upgrade, after reboot, this popped out. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: gnome-menus 3.10.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 Date: Mon Mar 9 09:05:09 2015 DuplicateSignature: package:gnome-menus:3.10.1-0ubuntu5:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2013-06-20 (626 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618) SourcePackage: gnome-menus Title: package gnome-menus 3.10.1-0ubuntu5 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to vivid on 2013-11-10 (483 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1429771/+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
