[Bug 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel
I don't understand. I currently have nvidia-driver-460 and linux kernel versions 5.8.0-43 to 45 installed (45 is being used). But I have no linux-modules-nvidia-460 packages installed. E.g. I don't have linux- modules-nvidia-460-5.8.0-45-generic and neither for 44 and 43. Is this ok or should I install linux-modules-nvidia-460-5.8.0-XY-generic. If the linux-modules-nvidia-460-5.8.0-XY-generic packages are not necessary for my system then why were they pre-installed in the first place, especially since they caused problems for me when I wanted to downgrade nvidia-driver-450? Please if you can answer my questions here and if you don't regard these as issues then close this bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916971 Title: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1916971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel
Sorry for my late reply. What do you mean by "... in the live session"? Instead I executed that command from my Ubuntu installation (where I observed the bug) and the output is here further below. @Dimitri are you saying that securedboot devices should avoid using the device drivers PPA? Also I'm currently on nvidia-driver-460 but I have no linux-modules-nvidia-460 packages installed. My system seems to work correctly. Is it OK that I don't have the linux-modules-nvidia-460 packages installed? Output of "sudo ubuntu-drivers list": nvidia-driver-418-server, (kernel modules provided by linux-modules-nvidia-418-server-generic-hwe-20.04) nvidia-driver-450-server, (kernel modules provided by linux-modules-nvidia-450-server-generic-hwe-20.04) nvidia-driver-460, (kernel modules provided by linux-modules-nvidia-460-generic-hwe-20.04) nvidia-driver-450, (kernel modules provided by linux-modules-nvidia-450-generic-hwe-20.04) nvidia-driver-390, (kernel modules provided by linux-modules-nvidia-390-generic-hwe-20.04) nvidia-driver-460-server, (kernel modules provided by linux-modules-nvidia-460-server-generic-hwe-20.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916971 Title: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1916971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel
Check apt/history.log and term.log for full history of what I did (starting from fresh install) and install logs. ** Attachment added: "/var/log/apt/term.log" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1916971/+attachment/5467752/+files/term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916971 Title: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1916971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel
** Attachment added: "/var/log/history.log" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1916971/+attachment/5467751/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916971 Title: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1916971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel
In kern.log, look for rows near the search string "API mismatch". They point out the error that occurred during boot. ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1916971/+attachment/5467750/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916971 Title: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1916971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916971] Re: After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel
** Summary changed: - After fresh install, downgrading Nvidia driver doesn't update nvidia modules in kernel + After fresh Ubuntu 20.04 install, downgrading Nvidia driver doesn't update nvidia modules in kernel ** Description changed: SYSTEM: Laptop: ASUS ROG GL552VW - OS: Ubuntu 20.04 + OS: Ubuntu 20.04.2 LTS GRAPHICS: Nvidia Geforce GTX 960m AND Intel HD Graphics Linux kernel version: 5.8.0-44-generic SUMMARY: From a fresh working install of Ubuntu 20.04, I downgraded from nvidia- driver-460 by installing nvidia-driver-440 (which actually is a - transitional package to nvidia-driver-450). After reboot I couldn't - reach login-screen and instead got a black screen. + transitional package to nvidia-driver-450 but I didn't know this). After + reboot I couldn't reach login-screen and instead got a black screen. Problem was that sudo apt-get install nvidia-driver-440 did not insert nvidia modules v450 in kernel since never versions v460 were found. - This was solved by dropping into safe mode and uninstalling linux- - modules-nvidia-460 packages and instead installing linux-modules- - nvidia-450 packages. + This was solved by uninstalling linux-modules-nvidia-460 packages and + instead installing linux-modules-nvidia-450 packages (see WORKAROUND + below for instructions). STEPS TO REPRODUCE: Install Ubuntu 20.04. During installation, allow for the installation of proprietary drivers. Once Ubuntu 20.04 has started, open a terminal and run the following: sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-driver-440 sudo shutdown reboot now PROBLEM: After reboot, you can't reach login screen. Instead you get stuck during bootup. WORKAROUND: Remove the linux-modules-nvidia-460 packages and install the corresponding linux-modules-nvidia-450 packages. In my case I had Linux kernel versions 5.8.0-44-generic and 5.8.0-43-generic installed so I did as follows from recovery mode with network (instead entering recovery mode, you should be able to press CTRL+ALT+F1 from the blank screen after bootup, login with username and password and then running these commands): sudo apt-get autoremove --purge linux-modules-nvidia-460-5.8.0-44-generic linux-modules-nvidia-460-5.8.0-43-generic sudo apt-get install linux-modules-nvidia-450-5.8.0-44-generic linux-modules-nvidia-450-5.8.0-43-generic sudo shutdown reboot now QUESTION: Why was the linux-modules-nvidia-460 packages installed by the Ubuntu installer to begin with? I ask since I later removed the linux-modules- nvidia-450 packages (OBSERVE: 450, not 460) and used the Additional Drivers GUI to update back to nvidia-driver-460. Now linux-modules- nvidia-460 packages are NOT installed but the following still outputs 460: modinfo nvidia | grep -i version LOG: This is a relevant part of /var/log/apt/term.log for when I installed nvidia-driver-440 nvidia.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-modeset.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-modeset.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-drm.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-drm.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-uvm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-44-generic/updates/dkms/ This is a relevant part of /var/log/apt/term.log for when I installed packages linux-modules-nvidia-450-5.8.0-44-generic and linux-modules- nvidia-450-5.8.0-43-generic Building module: cleaning build area... unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j8 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.8.0-43-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/5.8.0-43-generic/build LD=/usr/bin/ld.bfd modules Signing module: - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-modeset.ko - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-uvm.ko - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-drm.ko - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia.ko Secure Boot not enabled on this system. cleaning build area... DKMS: build completed. nvidia.ko: Running module version sanity check. Good news! Module version 450.102.04 for nvidia.ko exactly
[Bug 1916971] Re: After fresh install, downgrading Nvidia driver doesn't update nvidia modules in kernel
** Description changed: SYSTEM: Laptop: ASUS ROG GL552VW OS: Ubuntu 20.04 GRAPHICS: Nvidia Geforce GTX 960m AND Intel HD Graphics Linux kernel version: 5.8.0-44-generic - - SUMMARY: - From a fresh working install of Ubuntu 20.04, I wanted to downgrade from - nvidia-driver-460 by installing nvidia-driver-440 (which actually is a + From a fresh working install of Ubuntu 20.04, I downgraded from nvidia- + driver-460 by installing nvidia-driver-440 (which actually is a transitional package to nvidia-driver-450). After reboot I couldn't reach login-screen and instead got a black screen. Problem was that sudo apt-get install nvidia-driver-440 did not insert nvidia modules v450 in kernel since never versions v460 were found. This was solved by dropping into safe mode and uninstalling linux- modules-nvidia-460 packages and instead installing linux-modules- nvidia-450 packages. - - STEPS TO REPRODUCE: Install Ubuntu 20.04. During installation, allow for the installation of proprietary drivers. Once Ubuntu 20.04 has started, open a terminal and run the following: sudo add-apt-repository ppa:graphics-drivers/ppa - sudo apt-get update + sudo apt-get update sudo apt-get install nvidia-driver-440 sudo shutdown reboot now - - PROBLEM: After reboot, you can't reach login screen. Instead you get stuck during bootup. - - WORKAROUND: Remove the linux-modules-nvidia-460 packages and install the corresponding linux-modules-nvidia-450 packages. In my case I had Linux kernel versions 5.8.0-44-generic and 5.8.0-43-generic installed so I did - as follows from recovery mode with network: + as follows from recovery mode with network (instead entering recovery + mode, you should be able to press CTRL+ALT+F1 from the blank screen + after bootup, login with username and password and then running these + commands): sudo apt-get autoremove --purge linux-modules-nvidia-460-5.8.0-44-generic linux-modules-nvidia-460-5.8.0-43-generic sudo apt-get install linux-modules-nvidia-450-5.8.0-44-generic linux-modules-nvidia-450-5.8.0-43-generic sudo shutdown reboot now - - QUESTION: Why was the linux-modules-nvidia-460 packages installed by the Ubuntu installer to begin with? I ask since I later removed the linux-modules- nvidia-450 packages (OBSERVE: 450, not 460) and used the Additional Drivers GUI to update back to nvidia-driver-460. Now linux-modules- nvidia-460 packages are NOT installed but the following still outputs 460: modinfo nvidia | grep -i version - LOG: This is a relevant part of /var/log/apt/term.log for when I installed nvidia-driver-440 nvidia.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-modeset.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-modeset.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-drm.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-drm.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-uvm.ko: Running module version sanity check. - - Original module -- No original module exists within this kernel - - Installation -- Installing to /lib/modules/5.8.0-44-generic/updates/dkms/ + - Original module + - No original module exists within this kernel + - Installation + - Installing to /lib/modules/5.8.0-44-generic/updates/dkms/ - - - This is a relevant part of /var/log/apt/term.log for when I installed packages linux-modules-nvidia-450-5.8.0-44-generic and linux-modules-nvidia-450-5.8.0-43-generic + This is a relevant part of /var/log/apt/term.log for when I installed + packages linux-modules-nvidia-450-5.8.0-44-generic and linux-modules- + nvidia-450-5.8.0-43-generic Building module: cleaning build area... unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j8 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.8.0-43-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/5.8.0-43-generic/build LD=/usr/bin/ld.bfd modules Signing module: - - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-modeset.ko - - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-uvm.ko - - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-drm.ko - - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia.ko + - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-modeset.ko + - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-uvm.ko + -
[Bug 1916971] Re: After fresh install, downgrading Nvidia driver doesn't update nvidia modules in kernel
I *think* my question in the original post is a relevant cause for this bug and kindly ask you to follow up on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916971 Title: After fresh install, downgrading Nvidia driver doesn't update nvidia modules in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1916971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916971] [NEW] After fresh install, downgrading Nvidia driver doesn't update nvidia modules in kernel
Public bug reported: SYSTEM: Laptop: ASUS ROG GL552VW OS: Ubuntu 20.04 GRAPHICS: Nvidia Geforce GTX 960m AND Intel HD Graphics Linux kernel version: 5.8.0-44-generic SUMMARY: >From a fresh working install of Ubuntu 20.04, I wanted to downgrade from nvidia-driver-460 by installing nvidia-driver-440 (which actually is a transitional package to nvidia-driver-450). After reboot I couldn't reach login-screen and instead got a black screen. Problem was that sudo apt-get install nvidia-driver-440 did not insert nvidia modules v450 in kernel since never versions v460 were found. This was solved by dropping into safe mode and uninstalling linux- modules-nvidia-460 packages and instead installing linux-modules- nvidia-450 packages. STEPS TO REPRODUCE: Install Ubuntu 20.04. During installation, allow for the installation of proprietary drivers. Once Ubuntu 20.04 has started, open a terminal and run the following: sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt-get update sudo apt-get install nvidia-driver-440 sudo shutdown reboot now PROBLEM: After reboot, you can't reach login screen. Instead you get stuck during bootup. WORKAROUND: Remove the linux-modules-nvidia-460 packages and install the corresponding linux-modules-nvidia-450 packages. In my case I had Linux kernel versions 5.8.0-44-generic and 5.8.0-43-generic installed so I did as follows from recovery mode with network: sudo apt-get autoremove --purge linux-modules-nvidia-460-5.8.0-44-generic linux-modules-nvidia-460-5.8.0-43-generic sudo apt-get install linux-modules-nvidia-450-5.8.0-44-generic linux-modules-nvidia-450-5.8.0-43-generic sudo shutdown reboot now QUESTION: Why was the linux-modules-nvidia-460 packages installed by the Ubuntu installer to begin with? I ask since I later removed the linux-modules- nvidia-450 packages (OBSERVE: 450, not 460) and used the Additional Drivers GUI to update back to nvidia-driver-460. Now linux-modules- nvidia-460 packages are NOT installed but the following still outputs 460: modinfo nvidia | grep -i version LOG: This is a relevant part of /var/log/apt/term.log for when I installed nvidia-driver-440 nvidia.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-modeset.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-modeset.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-drm.ko: Running module version sanity check. Error! Module version 450.102.04 for nvidia-drm.ko is not newer than what is already found in kernel 5.8.0-44-generic (460.39). You may override by specifying --force. nvidia-uvm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-44-generic/updates/dkms/ This is a relevant part of /var/log/apt/term.log for when I installed packages linux-modules-nvidia-450-5.8.0-44-generic and linux-modules- nvidia-450-5.8.0-43-generic Building module: cleaning build area... unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j8 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.8.0-43-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/5.8.0-43-generic/build LD=/usr/bin/ld.bfd modules Signing module: - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-modeset.ko - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-uvm.ko - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia-drm.ko - /var/lib/dkms/nvidia/450.102.04/5.8.0-43-generic/x86_64/module/nvidia.ko Secure Boot not enabled on this system. cleaning build area... DKMS: build completed. nvidia.ko: Running module version sanity check. Good news! Module version 450.102.04 for nvidia.ko exactly matches what is already found in kernel 5.8.0-43-generic. DKMS will not replace this module. You may override by specifying --force. nvidia-modeset.ko: Running module version sanity check. Good news! Module version 450.102.04 for nvidia-modeset.ko exactly matches what is already found in kernel 5.8.0-43-generic. DKMS will not replace this module. You may override by specifying --force. nvidia-drm.ko: Running module version sanity check. Good news! Module version 450.102.04 for nvidia-drm.ko exactly matches what is already found in kernel 5.8.0-43-generic. DKMS will not replace this module. You may override by specifying --force. nvidia-uvm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.0-43-generic/updates/dkms/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu
[Bug 1725523] Re: Installing gnome-shell-extensions will make Gnome Classic the default session at login time
** Description changed: + I performed a fresh install of Ubuntu 17.10 (fresh Ubuntu system + partition) but kept my home partition and home folder from Ubuntu Unity + 17.04. I've so far done minimal changes to my system besides from + installing some apps. + If you install gnome-shell-extensions then Gnome Classic will be enabled as a session that the user can choose at login-time. Not only that, but it will also become the session chosen by **default**. When the user logs out and back in its very likely that they miss that Gnome Classic was chosen. When the login is completed the user will be confused because they are presented with a Ubuntu 17.10 that looks ugly and doesn't work correctly. Gnome Classic shouldn't be enabled by installing gnome-shell-extensions, or shouldn't atleast become the session chosen by default upon logging in. What makes this bug serious is that most users, and especially novice ones, won't know what happened (and how easily fixable it is) because the default choice of session is so discrete in the login GUI. Kind regards, Arash ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-release-upgrader-core 1:17.10.7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 01:32:32 2017 InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725523 Title: Installing gnome-shell-extensions will make Gnome Classic the default session at login time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1725523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725536] Re: Ubuntu 17.10 Dock doesn't respect the color choice of the Gnome Shell theme
Claudio, thanks for your guidance. I immediately made the changes with gsettings from the terminal. But I think you wrote wrong key names so I'll write the correct schema and key names in gsettings commands that can be directly executed to change the colors: gsettings set org.gnome.shell.extensions.dash-to-dock custom-theme- running-dots-color "#5294e2" gsettings set org.gnome.shell.extensions.dash-to-dock custom-theme- running-dots-border-color "#5294e2" Also, we aren't stuck with the orange color in the alt+tab panel nor the Dock's window preview because both of these colors were changed for me when I installed the popular Arc Theme (see link in my bug report above). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725536 Title: Ubuntu 17.10 Dock doesn't respect the color choice of the Gnome Shell theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1725536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725523] Re: Installing gnome-shell-extensions will make Gnome Classic the default session at login time
** Description changed: If you install gnome-shell-extensions then Gnome Classic will be enabled as a session that the user can choose at login-time. Not only that, but it will also become the session chosen by **default**. When the user logs out and back in its very likely that they miss that Gnome Classic was chosen. When the login is completed the user will be confused because they are presented with a Ubuntu 17.10 that looks ugly and doesn't work correctly. Gnome Classic shouldn't be enabled by installing gnome-shell-extensions, or shouldn't atleast become the session chosen by default upon logging in. + + What makes this bug serious is that most users, and especially novice + ones, won't know what happened (and how easily fixable it is) because + the default choice of session is so discrete in the login GUI. Kind regards, Arash ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-release-upgrader-core 1:17.10.7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 01:32:32 2017 InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725523 Title: Installing gnome-shell-extensions will make Gnome Classic the default session at login time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1725523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725536] Re: Ubuntu 17.10 Dock doesn't respect the color choice of the Gnome Shell theme
Removed selected package as this bug report has nothing to do with it. ** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu ** Description changed: I performed a fresh install of Ubuntu 17.10 (wiped system partition) but kept my home partition and home folder from Ubuntu Unity 17.04. I've so far done minimal changes to my system besides from installing some apps. The Ubuntu 17.10 Dock uses orange dots to indicate what apps are open and with how many instances. But changing the Gnome Shell theme doesn't change this color even if the theme changes the color orange everywhere - else in the theme. + else in the shell. Take the highly popular Arc theme for instance (https://github.com/horst3180/arc-theme). Installing it will change the orange color that appears in the the alt+tab panel and the Gnome Overview. But the orange color will remain in the Dock, causing a slightly annoying inconsistency. I think the original Gnome Dash to Dock extension respects the Gnome Shell's choice of color (https://micheleg.github.io/dash-to-dock/). Maybe it can be seen there from where the extension reads this crucial color code and then you can do the same in the Dock? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-release-upgrader-core 1:17.10.7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 02:49:07 2017 InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725536 Title: Ubuntu 17.10 Dock doesn't respect the color choice of the Gnome Shell theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1725536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725536] Re: Ubuntu 17.10 Dock doesn't respect the color choice of the Gnome Shell theme
** Description changed: + I performed a fresh install of Ubuntu 17.10 (wiped system partition) but + kept my home partition and home folder from Ubuntu Unity 17.04. I've so + far done minimal changes to my system besides from installing some apps. + The Ubuntu 17.10 Dock uses orange dots to indicate what apps are open and with how many instances. But changing the Gnome Shell theme doesn't change this color even if the theme changes the color orange everywhere else in the theme. Take the highly popular Arc theme for instance (https://github.com/horst3180/arc-theme). Installing it will change the orange color that appears in the the alt+tab panel and the Gnome Overview. But the orange color will remain in the Dock, causing a slightly annoying inconsistency. I think the original Gnome Dash to Dock extension respects the Gnome Shell's choice of color (https://micheleg.github.io/dash-to-dock/). Maybe it can be seen there from where the extension reads this crucial color code and then you can do the same in the Dock? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-release-upgrader-core 1:17.10.7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 02:49:07 2017 InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725536 Title: Ubuntu 17.10 Dock doesn't respect the color choice of the Gnome Shell theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1725536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725536] [NEW] Ubuntu 17.10 Dock doesn't respect the color choice of the Gnome Shell theme
Public bug reported: I performed a fresh install of Ubuntu 17.10 (wiped system partition) but kept my home partition and home folder from Ubuntu Unity 17.04. I've so far done minimal changes to my system besides from installing some apps. The Ubuntu 17.10 Dock uses orange dots to indicate what apps are open and with how many instances. But changing the Gnome Shell theme doesn't change this color even if the theme changes the color orange everywhere else in the theme. Take the highly popular Arc theme for instance (https://github.com/horst3180/arc-theme). Installing it will change the orange color that appears in the the alt+tab panel and the Gnome Overview. But the orange color will remain in the Dock, causing a slightly annoying inconsistency. I think the original Gnome Dash to Dock extension respects the Gnome Shell's choice of color (https://micheleg.github.io/dash-to-dock/). Maybe it can be seen there from where the extension reads this crucial color code and then you can do the same in the Dock? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-release-upgrader-core 1:17.10.7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 02:49:07 2017 InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful dist-upgrade wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725536 Title: Ubuntu 17.10 Dock doesn't respect the color choice of the Gnome Shell theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1725536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725523] Re: Installing gnome-shell-extensions will make Gnome Classic the default session at login time
Removed chosen package since this bug doesn't concern that package ** Package changed: ubuntu-release-upgrader (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725523 Title: Installing gnome-shell-extensions will make Gnome Classic the default session at login time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1725523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725523] [NEW] Installing gnome-shell-extensions will make Gnome Classic the default session at login time
Public bug reported: If you install gnome-shell-extensions then Gnome Classic will be enabled as a session that the user can choose at login-time. Not only that, but it will also become the session chosen by **default**. When the user logs out and back in its very likely that they miss that Gnome Classic was chosen. When the login is completed the user will be confused because they are presented with a Ubuntu 17.10 that looks ugly and doesn't work correctly. Gnome Classic shouldn't be enabled by installing gnome-shell-extensions, or shouldn't atleast become the session chosen by default upon logging in. Kind regards, Arash ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-release-upgrader-core 1:17.10.7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 01:32:32 2017 InstallationDate: Installed on 2017-10-19 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725523 Title: Installing gnome-shell-extensions will make Gnome Classic the default session at login time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1725523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629095] Re: Package makes system fan go on high speed on my laptop ASUS ROG GL552VW even if cpu is idle
** Description changed: - I performed an update of Ubuntu 16.04 LTS by using "sudo apt-get - upgrade". One of the packages that were updated was "ubuntu-drivers- - common", and it was updated from version 1:0.4.17 to 1:0.4.17.2 (note - that my system never had version 1:0.4.17.1). + LAPTOP: ASUS GL552VW + OS: Ubuntu 16.04 LTS + KERNEL: 4.4.0-38-generic + RAM: 8 GB + SWAP: 8 GB + CPU: Intel(R) Core(TM) i7-6700HQ CPU 4 cores @ 2.60GHz + GRAPHICS CARD: Nvidia Geforce GTX 960M + + + I performed an update of Ubuntu 16.04 LTS by using "sudo apt-get upgrade". One of the packages that were updated was "ubuntu-drivers-common", and it was updated from version 1:0.4.17 to 1:0.4.17.2 (note that my system never had version 1:0.4.17.1). After the next reboot my laptop's system fan went constantly on maximum speed, even if the CPU was nearly idle (according to the System Monitor in Ubuntu) and there were no heavy system load. The only thing I did to remedy this problem was to downgrade ubuntu- drivers-common to 1:0.4.17 (pay attention to the version number; I did NOT downgrade to 1:0.4.17.1 because the latter version doesn't exist in Ubuntu's default repositories). After the next reboot the problem was gone and the laptop's system fan functioned as normally. So it's evident that either 1:0.4.17.1 or 1:0.4.17.2 or both (by a short chain of changes) introduced this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629095 Title: Package makes system fan go on high speed on my laptop ASUS ROG GL552VW even if cpu is idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1629095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629095] [NEW] Package makes system fan go on high speed on my laptop ASUS ROG GL552VW even if cpu is idle
Public bug reported: I performed an update of Ubuntu 16.04 LTS by using "sudo apt-get upgrade". One of the packages that were updated was "ubuntu-drivers- common", and it was updated from version 1:0.4.17 to 1:0.4.17.2 (note that my system never had version 1:0.4.17.1). After the next reboot my laptop's system fan went constantly on maximum speed, even if the CPU was nearly idle (according to the System Monitor in Ubuntu) and there were no heavy system load. The only thing I did to remedy this problem was to downgrade ubuntu- drivers-common to 1:0.4.17 (pay attention to the version number; I did NOT downgrade to 1:0.4.17.1 because the latter version doesn't exist in Ubuntu's default repositories). After the next reboot the problem was gone and the laptop's system fan functioned as normally. So it's evident that either 1:0.4.17.1 or 1:0.4.17.2 or both (by a short chain of changes) introduced this problem. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629095 Title: Package makes system fan go on high speed on my laptop ASUS ROG GL552VW even if cpu is idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1629095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
