[Desktop-packages] [Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1933828 Title: NTP servers from DHCP are not propagated to timesyncd Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Status in network-manager source package in Focal: New Bug description: Network manager gets NTP servers from DHCP but do not update timesyncd to use it which keeps using ntp.ubuntu.com. This is a problem on private networks which do not have access to public internet. On this type of network the configuration of timesyncd must be updated manually instead of inheriting the conf from the dhcp servers. This can be integrated with a NM dispatcher script such as below: etc/NetworkManager/dispatcher.d/10-update-timesyncd for example: ==8<=8<=8<=8<=8<== #! /usr/bin/bash [ -n "$CONNECTION_UUID" ] || exit INTERFACE=$1 ACTION=$2 case $ACTION in up | dhcp4-change | dhcp6-change) [ -n "$DHCP4_NTP_SERVERS" ] || exit mkdir -p /etc/systemd/timesyncd.conf.d/ cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf [Time] NTP=$DHCP4_NTP_SERVERS RootDistanceMaxSec=15 EOF systemctl restart systemd-timesyncd ;; down) rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf systemctl restart systemd-timesyncd ;; esac ==8<=8<=8<=8<=8<== ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 14:08:52 2021 InstallationDate: Installed on 2020-05-31 (393 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) RebootRequiredPkgs: linux-image-5.11.0-20-generic linux-base SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1933828/+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 1511301] Re: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty.
Failed to upgrade fglrx to 2:15.201-0ubuntu0.14.04.2 Please check full log as attached. dependency problems: update-initramfs: deferring update (trigger activated) dpkg: dependency problems prevent configuration of fglrx: fglrx depends on xorg-video-abi-11 | xorg-video-abi-12 | xorg-video-abi-13 | xorg-video-abi-14 | xorg-video-abi-15 | xorg-video-abi-18 | xorg-video-abi-19; however: Package xorg-video-abi-11 is not installed. Package xorg-video-abi-12 is not installed. Package xorg-video-abi-13 is not installed. Package xorg-video-abi-14 is not installed. Package xorg-video-abi-15 is not installed. Package xserver-xorg-core which provides xorg-video-abi-15 is not configured yet.^M Package xorg-video-abi-18 is not installed. Package xorg-video-abi-19 is not installed. fglrx depends on xserver-xorg-core; however: Package xserver-xorg-core is not configured yet. - Selective upgrading from -proposed $ cat /etc/apt/preferences.d/proposed-updates Package: * Pin: release a=trusty-proposed Pin-Priority: 400 Package: fglrx Pin: release a=trusty-proposed Pin-Priority: 900 Package: fglrx-core Pin: release a=trusty-proposed Pin-Priority: 900 Package: fglrx-amdcccle Pin: release a=trusty-proposed Pin-Priority: 900 Error message: Setting up libgl1-mesa-glx:amd64 (10.1.3-0ubuntu0.6) ...^M update-alternatives: warning: forcing reinstallation of alternative /usr/lib/fglrx/ld.so.conf because link group x86_64-linux-gnu_gl_conf is broken^M ... update-alternatives: error: unable to remove '/etc/ati': Is a directory^M dpkg: error processing package libgl1-mesa-glx:amd64 (--configure):^M subprocess installed post-installation script returned error exit status 2^M ** Attachment added: "log_0222-1.tar" https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1511301/+attachment/4825756/+files/log_0222-1.tar ** Tags removed: verification-needed ** Tags added: verification-failed -- 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/1511301 Title: Failed to upgrade fglrx from 14.502 to 15.200 on Trusty. Status in fglrx-installer package in Ubuntu: Fix Released Status in fglrx-installer-updates package in Ubuntu: Fix Released Status in fglrx-installer source package in Trusty: Fix Committed Status in fglrx-installer-updates source package in Trusty: Fix Committed Bug description: SRU Request: [Impact] Upgrading from the upstream fglrx driver packages to the packages in the Ubuntu repository fails because the /etc/ati directory is a real directory instead of being a link (which was common in the Ubuntu packages). [Test Case] 1. Install the fglrx driver (14.502) in Ubuntu 14.04 generating deb packages from the AMD installer 2. Upgrade the package to the current ubuntu release. 3. Check the apt-get output Expected results: the fglrx module should be updated correctly. Actual results: The update fails as described below. [Regression Potential] Low. The change only affects a migration from a specific release. __ Note that the fglrx 14.502 package name is fglrx_14.502-0ubuntu1_amd64_UB_14.01.deb, which is from AMD's site, not from Ubuntu repository. Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for gconf2 (3.2.6-0ubuntu2) ... Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:22930): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for install-info (5.2.0.dfsg.1-2) ... Processing triggers for shared-mime-info (1.2-0ubuntu3) ... Processing triggers for sgml-base (1.26+nmu4ubuntu1) ... Processing triggers for gnome-icon-theme (3.10.0-0ubuntu2) ... (gtk-update-icon-cache-3.0:23024): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. Processing triggers for doc-base (0.10.5) ... Processing 1 changed doc-base file... Errors were encountered while processing: /var/cache/apt/archives/fglrx_2%3a15.200-0ubuntu0.5_amd64.deb Log ended: 2015-10-22 05:31:11 X-HWE-Bug: Bug #1664810 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1643812] Re: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70].
** Also affects: pulseaudio Importance: Undecided Status: New ** No longer affects: pulseaudio -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1643812 Title: There is no entry in 'Play sound through' list when plug in headset jack [8086:9d70]. Status in HWE Next: New Status in pulseaudio package in Ubuntu: New Status in pulseaudio source package in Trusty: New Bug description: 1. Install 14.04.5 image on P50s 2. Login system 3. $ sudo apt-get update 4. $ apt-get dist-upgrade sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa-lts-xenial 5. Reboot the system 6. Login system 7. Open Sound setting window 8. Plug headset jack, unplug headset jack. The kernel is 4.4.0-47, and the pulseaudio is 1:4.0-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1643812/+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 1630156] Re: No password needed to Log in after cancel the password and then reset again
** Also affects: lightdm Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** No longer affects: oem-priority/precise ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority/trusty Importance: Undecided => High ** Changed in: oem-priority Importance: High => Critical ** Changed in: oem-priority/trusty Importance: High => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1630156 Title: No password needed to Log in after cancel the password and then reset again Status in Light Display Manager: New Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in lightdm package in Ubuntu: New Bug description: OS: 14.04 trusty 1. Go to path "System Setting --> User Accounts--> Unlock" to unlock system setting. 2. Click "Password --> Action --> Log in without password -->Change to clear Log in password. 3. Reboot and log to desktop without password. 4. Then do the similar action "Set a password now" as the same way to set Log in password. 5. Reboot but still no password needed at Log in interface. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1630156/+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 1455533] Re: Dell systems showing DIAGS in Nautilus bar
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** No longer affects: oem-priority/trusty ** Changed in: oem-priority Importance: Undecided = Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1455533 Title: Dell systems showing DIAGS in Nautilus bar Status in OEM Priority Project: New Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Trusty: In Progress Bug description: [Impact] * Dell factory installed Linux systems are showing the partition DIAGS in the Nautilus bar * Also, Dell systems configured as a dual boot with Windows and Ubuntu 14.04.x show the same behavior. * This has been fixed in udisks2 upstream release 2.1.5 * This partition is not supposed to be accessible easily to users in any OS. [Test Case] * Create a FAT32 partition called diags and verify that it doesn't show up in the Nautilus bar after a reboot. [Regression Potential] * Regression potential is that anyone who is using this partition to store data won't be able to easily access it anymore To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1455533/+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 861171] Re: Shutdown from greeter does nothing when multiple accounts open
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/861171 Title: Shutdown from greeter does nothing when multiple accounts open Status in The Session Menu: Triaged Status in LightDM GTK+ Greeter: Triaged Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in Unity Greeter: Triaged Status in “gnome-session” package in Ubuntu: Confirmed Status in “indicator-session” package in Ubuntu: Triaged Status in “policykit” package in Ubuntu: Confirmed Status in “unity-greeter” package in Ubuntu: Triaged Bug description: Selecting shutdown from the greeter does nothing when multiple accounts are open. This is because the lightdm user (which the greeter runs as) does not have permission to shutdown while sessions are open. Inside a normal session this would just return you to the login screen. The solution is either for the indicator to say not allowed or to run a PolicyKit frontend in the greeter than can get the required permissions to perform the shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/861171/+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 889278] Re: Screen is locked again after unsuspend and successful authentication
Lower the OEM Priority importance to Medium as this is not critical to our customer. ** Changed in: oem-priority Importance: Critical = Medium -- 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/889278 Title: Screen is locked again after unsuspend and successful authentication Status in OEM Priority Project: In Progress Status in OEM Priority Project oneiric series: New Status in OEM Priority Project precise series: New Status in “gnome-screensaver” package in Ubuntu: Incomplete Status in “gnome-settings-daemon” package in Ubuntu: Incomplete Bug description: After unsuspending and successful authentication, the screen is locked again a few seconds later without any possibility to prevent this. This occurs only if the machine is suspended automatically after a certain inactive time, however not if it is initiated by the user. The bug occurs reproducibly in Ubuntu 11.10. --- ApportVersion: 1.23-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 11.10 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) Package: gnome-screensaver 3.2.0-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Tags: oneiric running-unity Uname: Linux 3.0.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/889278/+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 889278] Re: Screen is locked again after unsuspend and successful authentication
** Also affects: gnome-settings-daemon Importance: Undecided Status: New ** No longer affects: gnome-settings-daemon ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/889278 Title: Screen is locked again after unsuspend and successful authentication Status in OEM Priority Project: New Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: After unsuspending and successful authentication, the screen is locked again a few seconds later without any possibility to prevent this. This occurs only if the machine is suspended automatically after a certain inactive time, however not if it is initiated by the user. The bug occurs reproducibly in Ubuntu 11.10. --- ApportVersion: 1.23-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 11.10 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) Package: gnome-screensaver 3.2.0-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Tags: oneiric running-unity Uname: Linux 3.0.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/889278/+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 838539] Re: Help button does not work for startup applications help
** Also affects: gnome-session Importance: Undecided Status: New ** Project changed: gnome-session = oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/838539 Title: Help button does not work for startup applications help Status in OEM Priority Project: New Status in “gnome-session” package in Ubuntu: Triaged Bug description: Just opens help and says this: Document Not Found The URI ‘ghelp:user-guide?gosstartsession-2#gosstartsession-2’ does not point to a valid page. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-session-bin 3.1.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CasperVersion: 1.280 Date: Thu Sep 1 02:15:06 2011 ExecutablePath: /usr/bin/gnome-session-properties LiveMediaBuild: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110831) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/838539/+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
