[Desktop-packages] [Bug 1800101] Re: gnome-shell uses 100% CPU
Can you please try uninstalling the Nvidia driver (for a moment), reboot, and if the default 'nouveau' driver works for you then please let us know if that also avoids the 100% CPU problem? I am wondering if the problem is unique to the Nvidia driver. -- 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/1800101 Title: gnome-shell uses 100% CPU Status in gnome-shell package in Ubuntu: Incomplete Bug description: For no obvious reason gnome-shell starts to use 100% CPU. This is a standard install of Ubuntu 18.04 with no special extensions installed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 26 10:03:02 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-08-15 (71 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1800101/+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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Workaround for 18.10 is to change the Dash to Dock setting "Customize opacity - Tune the dash background opacity" to "Fixed". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+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 1800333] Re: Ubuntu dock not working properly
Workaround is to change the Dash to Dock setting "Customize opacity - Tune the dash background opacity" to "Fixed". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1800333 Title: Ubuntu dock not working properly Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Ubuntu 18.10 Linux mbpr13b 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Upgrade from Ubuntu 18.04, all updates applied Ubuntu dock has several issues (some reported elsewhere) a) dock does not allow to relocate on screen (does not honour gsetting dock-position) b) dock does not react to hotkeys (even though are set in gsettings) c) dock does not hide on lock screen (https://www.queryxchange.com/q/3_1085426/desktop-is-visible-is-visible-after-suspend/) d) dock does allow application launch, termination and some commands when machine in locked e) dock appears after resume from RAM f) dash button does not react on first mouse click when applications are open g) dock changes size if applications are open and a dot indicates the fact here are the Gnome settings: gsettings list-recursively org.gnome.shell.extensions.dash-to-dock org.gnome.shell.extensions.dash-to-dock click-action 'previews' org.gnome.shell.extensions.dash-to-dock preferred-monitor -1 org.gnome.shell.extensions.dash-to-dock force-straight-corner false org.gnome.shell.extensions.dash-to-dock show-show-apps-button true org.gnome.shell.extensions.dash-to-dock show-windows-preview true org.gnome.shell.extensions.dash-to-dock animation-time 0.20001 org.gnome.shell.extensions.dash-to-dock scroll-action 'switch-workspace' org.gnome.shell.extensions.dash-to-dock height-fraction 0.90002 org.gnome.shell.extensions.dash-to-dock activate-single-window true org.gnome.shell.extensions.dash-to-dock running-indicator-dominant-color false org.gnome.shell.extensions.dash-to-dock custom-theme-customize-running-dots true org.gnome.shell.extensions.dash-to-dock minimize-shift true org.gnome.shell.extensions.dash-to-dock show-apps-at-top true org.gnome.shell.extensions.dash-to-dock pressure-threshold 100.0 org.gnome.shell.extensions.dash-to-dock show-delay 0.25 org.gnome.shell.extensions.dash-to-dock icon-size-fixed true org.gnome.shell.extensions.dash-to-dock intellihide-mode 'ALL_WINDOWS' org.gnome.shell.extensions.dash-to-dock customize-alphas false org.gnome.shell.extensions.dash-to-dock apply-custom-theme false org.gnome.shell.extensions.dash-to-dock hot-keys true org.gnome.shell.extensions.dash-to-dock extend-height true org.gnome.shell.extensions.dash-to-dock background-color '#ff' org.gnome.shell.extensions.dash-to-dock shortcut-timeout 2.0 org.gnome.shell.extensions.dash-to-dock transparency-mode 'ADAPTIVE' org.gnome.shell.extensions.dash-to-dock multi-monitor false org.gnome.shell.extensions.dash-to-dock shortcut-text 'q' org.gnome.shell.extensions.dash-to-dock isolate-workspaces false org.gnome.shell.extensions.dash-to-dock max-alpha 0.80004 org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock hide-delay 0.20001 org.gnome.shell.extensions.dash-to-dock show-favorites true org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-color '#e95420' org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-width 0 org.gnome.shell.extensions.dash-to-dock app-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock app-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock isolate-monitors false org.gnome.shell.extensions.dash-to-dock app-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock custom-theme-shrink true org.gnome.shell.extensions.dash-to-dock app-hotkey-7 ['7'] org.gnome.shell.extensions.dash-to-dock autohide true
[Desktop-packages] [Bug 1799430] Re: Icon dock visible on lock screen
Workaround is to change the Dash to Dock setting "Customize opacity - Tune the dash background opacity" to "Fixed". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1799430 Title: Icon dock visible on lock screen Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When locking the machine with alt-L the icon dock is still visible. After Login, the dock does not get adjusted to the top menu. In rare cases, the dock does not respond any more. This requires a reboot of the machine ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 12:59:27 2018 InstallationDate: Installed on 2018-04-30 (176 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+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 1799293] Re: gnome session: Must ask twice to lock the screen
Workaround is to change the Dash to Dock setting "Customize opacity - Tune the dash background opacity" to "Fixed". -- 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/1799293 Title: gnome session: Must ask twice to lock the screen Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Bug description: 1) Ubuntu 18.10 (new install) 2) gdm3 3.30.1-1ubuntu5 Preconditions The session's user has auto-login enabled (i.e. the system starts and the user is not prompted for a password but directly presented with the desktop) 3) What should happen: Unlocked desktop is showing. Lock screen is invoked (via WIN+L or via top right corner menu) and the lock screen is engaged (that is, lock screen clock shade drops down and screen fades to dark). Pressing ENTER brings back the lock screen and the password is prompted. 4) What happens: First Win + L lets the system in a half locked state in which the contents of the desktop are seen although no interaction is possible. A second Win + L correctly invokes the lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799293/+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 1801264] Re: Wifi drops out 1-30 minutes after boot on Ubuntu 18.10
Please reproduce the problem, do a hard reset and then run this command: journalctl -b-1 > prev_boot.txt and send us the resulting file prev_boot.txt ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1801264 Title: Wifi drops out 1-30 minutes after boot on Ubuntu 18.10 Status in network-manager package in Ubuntu: Incomplete Bug description: I will boot, Wifi connects fine, and then the wifi drops out and no connection can be made until a restart. When I try to reconnect it "Connection Failed: Activation of network connection failed". The Wifi works fine on phone and on Fedora 29. Network Manager 1.12.4 Expected: Wifi stays connected Happened: Wifi drops out after 1-30 minutes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 13:38:42 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-02 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.42.129 dev enp0s20f0u2 proto dhcp metric 100 169.254.0.0/16 dev enp0s20f0u2 scope link metric 1000 192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.66 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s20f0u2 ethernet connected /org/freedesktop/NetworkManager/Devices/3 Wired connection 1 a79e5d9a-26c0-34c5-a20d-5a371d0eafd6 /org/freedesktop/NetworkManager/ActiveConnection/9 wlp1s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1801264/+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 773931] Re: Embeded videos do not work in facebook / daily motion. Youtube works fine!
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/773931 Title: Embeded videos do not work in facebook / daily motion. Youtube works fine! Status in firefox package in Ubuntu: Expired Bug description: Binary package hint: firefox Embeded videos do not work in facebook / daily motion. Youtube works fine! No sound control on youtube through the keyboard keys ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 4.0+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 NonfreeKernelModules: wl Architecture: amd64 Date: Sat Apr 30 12:11:14 2011 ExecutablePath: /usr/lib/firefox-4.0/firefox-bin FirefoxPackages: firefox 4.0+nobinonly-0ubuntu3 flashplugin-installer 10.2.159.1ubuntu1 adobe-flashplugin N/A icedtea-plugin N/A InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) XsessionErrors: (knotify4:1421): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed (firefox-bin:1876): GLib-CRITICAL **: g_hash_table_insert_internal: assertion `hash_table != NULL' failed (npviewer.bin:1930): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so (npviewer.bin:1930): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so (npviewer.bin:1930): GdkPixbuf-WARNING **: Error loading XPM image loader: Unable to load image-loading module: /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so: /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-xpm.so: wrong ELF class: ELFCLASS64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/773931/+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 799337] Re: Firefox does not display PDF using plugin
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/799337 Title: Firefox does not display PDF using plugin Status in firefox package in Ubuntu: Expired Bug description: Setting: vanilla Natty installation, Firefox 4 and the Adobe PDF plugin from Adobe Reader 9. Instead of trigerring the PDF plugin and displaying the PDF within the browser, a dialog appears asking how to handle the file. To reproduce go to http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.110.6657=1 If you click the PDF button unter "cached", the PDF is not loaded within the browser. If you however click, for example the second link under "Downloads" everything works as should. This seems to be a problem with several journal sites. behaviour is the same when using mozplugger + evince instead of the Adobe PDF plugin, or using the Adobe Reader 8 plugin. It seems to be related to how Firefox 4 handles file downloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/799337/+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 788996] Re: Firefox stops accepting characters while typing
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/788996 Title: Firefox stops accepting characters while typing Status in firefox package in Ubuntu: Expired Bug description: Binary package hint: firefox When I fill an input field in a web form, Firefox stops accepting further keystrokes after a couple of characters. The same happens in the URL address line. I have to re-click on the input field with the mouse, and then I can continue typing. While this seems to mean that the input field has lost focus, the cursor is still there. It doesn't happen with Textarea field, only with one-line input fields. I use Natty + Unity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/788996/+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 588236] Re: Firefox loses memory of user/pass + history
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/588236 Title: Firefox loses memory of user/pass + history Status in firefox package in Ubuntu: Expired Bug description: Binary package hint: firefox The version of Ubunu that is affected with this is Ubuntu 10.04 both 32-bit and 64-bits in Sweden as far as I know. The version of Firefox is 3.6.3... After a while Firefox loses it's memory of the user/pass that is saved and even the history, and to solve the problem you need to close firefox and re-start it. Even in safe mode it occurs but not as fast as in normal mode... In normal mode all settings clear out after about 10-15 minutes! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/588236/+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 840989] Re: Firefox is becoming slower and hanging periodically
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/840989 Title: Firefox is becoming slower and hanging periodically Status in firefox package in Ubuntu: Expired Bug description: while loading some web pages especially www.latesttricks.in, softpedia.com and many more sites. Please look after this problem and try to find the solution for this . I'm having same issue with firefox on windows based computer also ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 6.0.1+build1+nobinonly-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic i686 Architecture: i386 Date: Sun Sep 4 18:23:59 2011 FirefoxPackages: firefox 6.0.1+build1+nobinonly-0ubuntu0.11.04.1 flashplugin-installer N/A adobe-flashplugin 10.3.183.7-0natty1 icedtea-plugin N/A InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/840989/+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 1790416] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all (ALC3246)
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1790416 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all (ALC3246) Status in alsa-driver package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: O notebook travou,e posteriormente fui reproduzir áudio é simplesmente não reproduz, aparece como esta tocando, mas não sai som, nem nos alto-falantes interno nem fones-de-auvidos. nesse intermédio no painel de controle apareceu "saída fictícia". Atualmente esta aparecendo os alto falantes e de HDMI, mas continua a não toca nada. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: hallison 2403 F...m pulseaudio /dev/snd/controlC0: hallison 2403 F pulseaudio CurrentDesktop: Unity Date: Sun Sep 2 18:11:19 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-18 (472 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: hallison 2403 F...m pulseaudio /dev/snd/controlC0: hallison 2403 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0P1MTV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd02/03/2017:svnDellInc.:pnInspiron5566:pvr:rvnDellInc.:rn0P1MTV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5566 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1790416/+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 1790218] Re: Black screen after login
[Expired for nvidia-graphics-drivers-340 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: Incomplete => Expired -- 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/1790218 Title: Black screen after login Status in nvidia-graphics-drivers-340 package in Ubuntu: Expired Bug description: Fresh ubuntu 18.04 Enabled the nvidia driver Black screen after login ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.106 Tue Jan 9 15:10:23 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Fri Aug 31 22:47:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-33-generic, x86_64: installed nvidia-340, 340.106, 4.15.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell GT216GLM [Quadro FX 880M] [1028:040c] InstallationDate: Installed on 2018-08-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Precision M4500 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=50dd2a99-b522-484b-8c75-de09106c92b7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0RRH3K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/05/2013:svnDellInc.:pnPrecisionM4500:pvr0001:rvnDellInc.:rn0RRH3K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4500 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1790218/+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 1790416] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all (ALC3246)
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1790416 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all (ALC3246) Status in alsa-driver package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: O notebook travou,e posteriormente fui reproduzir áudio é simplesmente não reproduz, aparece como esta tocando, mas não sai som, nem nos alto-falantes interno nem fones-de-auvidos. nesse intermédio no painel de controle apareceu "saída fictícia". Atualmente esta aparecendo os alto falantes e de HDMI, mas continua a não toca nada. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: hallison 2403 F...m pulseaudio /dev/snd/controlC0: hallison 2403 F pulseaudio CurrentDesktop: Unity Date: Sun Sep 2 18:11:19 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-18 (472 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: hallison 2403 F...m pulseaudio /dev/snd/controlC0: hallison 2403 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0P1MTV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd02/03/2017:svnDellInc.:pnInspiron5566:pvr:rvnDellInc.:rn0P1MTV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5566 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1790416/+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 1801264] [NEW] Wifi drops out 1-30 minutes after boot on Ubuntu 18.10
Public bug reported: I will boot, Wifi connects fine, and then the wifi drops out and no connection can be made until a restart. When I try to reconnect it "Connection Failed: Activation of network connection failed". The Wifi works fine on phone and on Fedora 29. Network Manager 1.12.4 Expected: Wifi stays connected Happened: Wifi drops out after 1-30 minutes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 13:38:42 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-02 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.42.129 dev enp0s20f0u2 proto dhcp metric 100 169.254.0.0/16 dev enp0s20f0u2 scope link metric 1000 192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.66 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s20f0u2 ethernet connected/org/freedesktop/NetworkManager/Devices/3 Wired connection 1 a79e5d9a-26c0-34c5-a20d-5a371d0eafd6 /org/freedesktop/NetworkManager/ActiveConnection/9 wlp1s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session -- 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/1801264 Title: Wifi drops out 1-30 minutes after boot on Ubuntu 18.10 Status in network-manager package in Ubuntu: New Bug description: I will boot, Wifi connects fine, and then the wifi drops out and no connection can be made until a restart. When I try to reconnect it "Connection Failed: Activation of network connection failed". The Wifi works fine on phone and on Fedora 29. Network Manager 1.12.4 Expected: Wifi stays connected Happened: Wifi drops out after 1-30 minutes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 2 13:38:42 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-02 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.42.129 dev enp0s20f0u2 proto dhcp metric 100 169.254.0.0/16 dev enp0s20f0u2 scope link metric 1000 192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.66 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH enp0s20f0u2 ethernet connected /org/freedesktop/NetworkManager/Devices/3 Wired connection 1 a79e5d9a-26c0-34c5-a20d-5a371d0eafd6 /org/freedesktop/NetworkManager/ActiveConnection/9 wlp1s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/2 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled
[Desktop-packages] [Bug 563265] Re: package nvidia-* failed to install/upgrade: nvidia-current kernel module failed to build / make[2]: *** No rule to make target `modules'. Stop.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/563265 Title: package nvidia-* failed to install/upgrade: nvidia-current kernel module failed to build / make[2]: *** No rule to make target `modules'. Stop. Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After getting the latest updates in lucid, including the 2.6.32-20 kernel, and rebooting the machine, X only started in low graphics mode. After I started to investigate it seemed like the nvidia kernel module failed to build. I tried to reinstall nvidia-current (apt-get autoremove nvidia-current, apt-get install nvidia-current) but it failed with the following message. root@thor:~# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up nvidia-current (195.36.15-0ubuntu2) ... Removing old nvidia-current-195.36.15 DKMS files... -- Deleting module version: 195.36.15 completely from the DKMS tree. -- Done. Loading new nvidia-current-195.36.15 DKMS files... Building for 2.6.32-19-generic and 2.6.32-20-generic Building for architecture x86_64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. Building initial module for 2.6.32-20-generic Error! Bad return status for module build on kernel: 2.6.32-20-generic (x86_64) Consult the make.log in the build directory /var/lib/dkms/nvidia-current/195.36.15/build/ for more information. dpkg: error processing nvidia-current (--configure): subprocess installed post-installation script returned error exit status 10 Processing triggers for python-gmenu ... Rebuilding /usr/share/applications/desktop.en_US.utf8.cache... Processing triggers for python-support ... Errors were encountered while processing: nvidia-current E: Sub-process /usr/bin/dpkg returned an error code (1) The make.log contains the following information root@thor:~# cat /var/lib/dkms/nvidia-current/195.36.15/build/make.log DKMS make.log for nvidia-current-195.36.15 for kernel 2.6.32-20-generic (x86_64) Wed Apr 14 20:34:45 EEST 2010 NVIDIA: calling KBUILD... make[2]: *** No rule to make target `modules'. Stop. NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [module] Error 1 make: *** [module] Error 2 If I try to activate the nvidia drivers using jockey-gtk or jockey- text, I get the following error root@thor:~# jockey-text -e xorg:nvidia_current Searching for available drivers... SystemError: installArchives() failed Meanwhile, the proprietary nvidia drivers continue to happily work in 2.6.32-19 kernel. Only building the module for 2.6.32-20 seems to fail. Thank you for your help. Please let me know if I can give you any more relevant debugging information. This machine was upgraded from 9.04 to 10.04, for all that it matters. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.15-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 Architecture: amd64 CurrentDmesg: [ 22.352714] ppdev: user-space parallel port driver [ 31.65] eth0: no IPv6 routers present [ 35.870840] UDF-fs: Partition marked readonly; forcing readonly mount [ 35.899382] UDF-fs INFO UDF: Mounting volume 'CIVCOMPLETEEU', timestamp 2007/09/22 01:42 (10b4) Date: Wed Apr 14 21:07:06 2010 DkmsStatus: nvidia-current, 195.36.15: added ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: System manufacturer P5Q PackageVersion: 195.36.15-0ubuntu2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=2846018c-2e2a-4803-8a02-ad3c18f7c317 ro quiet splash SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 195.36.15-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build XorgConf: dmi.bios.date: 08/20/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1306 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q dmi.board.vendor: ASUSTeK Computer INC.
[Desktop-packages] [Bug 563265] Re: package nvidia-* failed to install/upgrade: nvidia-current kernel module failed to build / make[2]: *** No rule to make target `modules'. Stop.
** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-367 in Ubuntu. https://bugs.launchpad.net/bugs/563265 Title: package nvidia-* failed to install/upgrade: nvidia-current kernel module failed to build / make[2]: *** No rule to make target `modules'. Stop. Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in nvidia-graphics-drivers-331 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-367 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After getting the latest updates in lucid, including the 2.6.32-20 kernel, and rebooting the machine, X only started in low graphics mode. After I started to investigate it seemed like the nvidia kernel module failed to build. I tried to reinstall nvidia-current (apt-get autoremove nvidia-current, apt-get install nvidia-current) but it failed with the following message. root@thor:~# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0B of additional disk space will be used. Setting up nvidia-current (195.36.15-0ubuntu2) ... Removing old nvidia-current-195.36.15 DKMS files... -- Deleting module version: 195.36.15 completely from the DKMS tree. -- Done. Loading new nvidia-current-195.36.15 DKMS files... Building for 2.6.32-19-generic and 2.6.32-20-generic Building for architecture x86_64 Module build for the currently running kernel was skipped since the kernel source for this kernel does not seem to be installed. Building initial module for 2.6.32-20-generic Error! Bad return status for module build on kernel: 2.6.32-20-generic (x86_64) Consult the make.log in the build directory /var/lib/dkms/nvidia-current/195.36.15/build/ for more information. dpkg: error processing nvidia-current (--configure): subprocess installed post-installation script returned error exit status 10 Processing triggers for python-gmenu ... Rebuilding /usr/share/applications/desktop.en_US.utf8.cache... Processing triggers for python-support ... Errors were encountered while processing: nvidia-current E: Sub-process /usr/bin/dpkg returned an error code (1) The make.log contains the following information root@thor:~# cat /var/lib/dkms/nvidia-current/195.36.15/build/make.log DKMS make.log for nvidia-current-195.36.15 for kernel 2.6.32-20-generic (x86_64) Wed Apr 14 20:34:45 EEST 2010 NVIDIA: calling KBUILD... make[2]: *** No rule to make target `modules'. Stop. NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [module] Error 1 make: *** [module] Error 2 If I try to activate the nvidia drivers using jockey-gtk or jockey- text, I get the following error root@thor:~# jockey-text -e xorg:nvidia_current Searching for available drivers... SystemError: installArchives() failed Meanwhile, the proprietary nvidia drivers continue to happily work in 2.6.32-19 kernel. Only building the module for 2.6.32-20 seems to fail. Thank you for your help. Please let me know if I can give you any more relevant debugging information. This machine was upgraded from 9.04 to 10.04, for all that it matters. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: nvidia-current 195.36.15-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 Architecture: amd64 CurrentDmesg: [ 22.352714] ppdev: user-space parallel port driver [ 31.65] eth0: no IPv6 routers present [ 35.870840] UDF-fs: Partition marked readonly; forcing readonly mount [ 35.899382] UDF-fs INFO UDF: Mounting volume 'CIVCOMPLETEEU', timestamp 2007/09/22 01:42 (10b4) Date: Wed Apr 14 21:07:06 2010 DkmsStatus: nvidia-current, 195.36.15: added ErrorMessage: nvidia-current kernel module failed to build InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MachineType: System manufacturer P5Q PackageVersion: 195.36.15-0ubuntu2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic root=UUID=2846018c-2e2a-4803-8a02-ad3c18f7c317 ro quiet splash SourcePackage: nvidia-graphics-drivers Title: package nvidia-current 195.36.15-0ubuntu2 failed to install/upgrade: nvidia-current kernel module failed to build XorgConf: dmi.bios.date: 08/20/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1306 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag:
[Desktop-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
1. Can you please confirm where you are looking when you say "it no longer shows any of the audio output devices"? Are you looking in Settings > Sound > Output ? 2. Can you please try booting Ubuntu from USB: http://releases.ubuntu.com/18.10/ and tell us if the problem still occurs in the live USB session? -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1801181] Re: Pixelized display
Can you please provide a photo of the "Pixelized display"? ** Tags added: radeon ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1801181 Title: Pixelized display Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Artefakty upgrading to 18.04 lts three iż a problem without display. I have no duch problem on 16.04 lts --- CurrentDmesg.txt: [ 29.779035] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid [ 29.779082] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! [ 30.612745] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid [ 30.612804] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Nov 1 22:51:23 2018 DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115] Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] InstallationDate: Installed on 2015-03-10 (1332 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 2087A37 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=76e45c9b-b94c-414a-9c7f-cfbbafb58a1a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-11-01 (0 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2087A37 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2087A37:pvrThinkPadT500:rvnLENOVO:rn2087A37:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T500 dmi.product.name: 2087A37 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 1 20:57:30 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801181/+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 1800899] Re: Line out and headphones audio output keep swithing causing crackles in sound
Thanks. It sounds like there is a bad connection in the port on the back panel. That would explain both crackling and flickering settings. The flickering would be Ubuntu quickly detecting spurious insertion/removal or connection/disconnection of the headphones. So this sounds like a hardware problem with that port. ** Package changed: alsa-driver (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Invalid -- 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/1800899 Title: Line out and headphones audio output keep swithing causing crackles in sound Status in Ubuntu: Invalid Bug description: There is an audio crackle every few seconds when I use headphones. Under the sound tab in settings the "Line Out-Built-in Audio" device flickers at the exact moment there is a crackle. By opening the pavucontrol audio manager I can see the "Built-in Audio Analog Stereo" output device port keeps switching to "Headphones (unplugged)" from "Line Out(plugged in)" for an instance. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: george10877 F pulseaudio /dev/snd/controlC2: george10877 F pulseaudio /dev/snd/controlC0: george10877 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 31 20:21:09 2018 InstallationDate: Installed on 2018-10-09 (21 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulseAudioLog: Οκτ 31 18:49:55 LinuxPC dbus-daemon[775]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.38' (uid=1000 pid=1298 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") Οκτ 31 18:49:58 LinuxPC dbus-daemon[775]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.44' (uid=1000 pid=1298 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") Οκτ 31 19:49:44 LinuxPC dbus-daemon[775]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.211' (uid=1000 pid=10877 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [To be filled by O.E.M., Realtek ALC887-VD, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170-HD3P-CF 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: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd11/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3P-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1800899/+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 1801110] Re: gnome-shell crashes ending session upon DP monitor switch-away
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1801110 Title: gnome-shell crashes ending session upon DP monitor switch-away Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have a DisplayPort switching arrangement consisting of a 4way DP switch that switches 2, daisy-chained DP monitors. Many times, but not always, when switching the displays away from this host, gnome-shell crashes. Later, switching back, I'm presented with the gdm login screen, previous session is gone. journal trace. Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142617.735610:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142617.828123:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142617.829899:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142617.844313:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! Oct 31 14:26:19 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142619.936305:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=0.999619 s, l Oct 31 14:26:20 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142620.866151:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00119 s, la Oct 31 14:26:21 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142621.876094:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00083 s, la Oct 31 14:26:22 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142622.866910:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00015 s, la Oct 31 14:26:23 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142623.866649:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=0.999805 s, l Oct 31 14:26:24 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142624.866857:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00075 s, la Oct 31 14:26:25 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142625.867939:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00054 s, la Oct 31 14:26:26 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142626.867620:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=0.999784 s, l Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Backtrace: Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 0: /usr/bin/Xwayland (OsLookupColor+0x139) [0x561135c42c39] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fd818e74e1f] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 2: /usr/bin/Xwayland (present_extension_init+0xce6) [0x561135bab416] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 3: /usr/bin/Xwayland (glamor_egl_fd_from_pixmap+0x390) [0x561135aed380] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 4: /usr/bin/Xwayland (glamor_egl_fd_from_pixmap+0x533) [0x561135aed6f3] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 5: /usr/bin/Xwayland (TimerSet+0x180) [0x561135c3c4b0] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 6: /usr/bin/Xwayland (TimerSet+0x1f8) [0x561135c3c578] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 7: /usr/bin/Xwayland (WaitForSomething+0x277)
[Desktop-packages] [Bug 1801202] Re: Xorg freeze
Unfortunately your harddisk is failing, which is a hardware error.
Consider replacing the harddisk with a new one and then reinstall Ubuntu
:(
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/1801202
Title:
Xorg freeze
Status in linux package in Ubuntu:
Invalid
Status in xorg-server package in Ubuntu:
Invalid
Bug description:
The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs or folders open.
---
CurrentDmesg.txt:
[ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0
[ 5465.753954] ata1.00: irq_stat 0x4008
[ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED
[ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma
131072 in
res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409
(media error)
[ 5465.753973] ata1.00: status: { DRDY ERR }
[ 5465.753976] ata1.00: error: { UNC }
[ 5466.031887] ata1.00: configured for UDMA/133
[ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current]
[ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error -
auto reallocate failed
[ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01
00 00
[ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120
[ 5466.031994] ata1: EH complete
---
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e]
(rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b]
Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b]
InstallationDate: Installed on 2018-10-04 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: LENOVO 80QQ
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN63WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Nano 5B6
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 100-15IBD
dmi.modalias:
dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
dmi.product.family: IDEAPAD
dmi.product.name: 80QQ
dmi.product.version: Lenovo ideapad 100-15IBD
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801202/+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 1800333] Re: Ubuntu dock not working properly
Also c) sounds like bug 1769383. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1800333 Title: Ubuntu dock not working properly Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Ubuntu 18.10 Linux mbpr13b 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Upgrade from Ubuntu 18.04, all updates applied Ubuntu dock has several issues (some reported elsewhere) a) dock does not allow to relocate on screen (does not honour gsetting dock-position) b) dock does not react to hotkeys (even though are set in gsettings) c) dock does not hide on lock screen (https://www.queryxchange.com/q/3_1085426/desktop-is-visible-is-visible-after-suspend/) d) dock does allow application launch, termination and some commands when machine in locked e) dock appears after resume from RAM f) dash button does not react on first mouse click when applications are open g) dock changes size if applications are open and a dot indicates the fact here are the Gnome settings: gsettings list-recursively org.gnome.shell.extensions.dash-to-dock org.gnome.shell.extensions.dash-to-dock click-action 'previews' org.gnome.shell.extensions.dash-to-dock preferred-monitor -1 org.gnome.shell.extensions.dash-to-dock force-straight-corner false org.gnome.shell.extensions.dash-to-dock show-show-apps-button true org.gnome.shell.extensions.dash-to-dock show-windows-preview true org.gnome.shell.extensions.dash-to-dock animation-time 0.20001 org.gnome.shell.extensions.dash-to-dock scroll-action 'switch-workspace' org.gnome.shell.extensions.dash-to-dock height-fraction 0.90002 org.gnome.shell.extensions.dash-to-dock activate-single-window true org.gnome.shell.extensions.dash-to-dock running-indicator-dominant-color false org.gnome.shell.extensions.dash-to-dock custom-theme-customize-running-dots true org.gnome.shell.extensions.dash-to-dock minimize-shift true org.gnome.shell.extensions.dash-to-dock show-apps-at-top true org.gnome.shell.extensions.dash-to-dock pressure-threshold 100.0 org.gnome.shell.extensions.dash-to-dock show-delay 0.25 org.gnome.shell.extensions.dash-to-dock icon-size-fixed true org.gnome.shell.extensions.dash-to-dock intellihide-mode 'ALL_WINDOWS' org.gnome.shell.extensions.dash-to-dock customize-alphas false org.gnome.shell.extensions.dash-to-dock apply-custom-theme false org.gnome.shell.extensions.dash-to-dock hot-keys true org.gnome.shell.extensions.dash-to-dock extend-height true org.gnome.shell.extensions.dash-to-dock background-color '#ff' org.gnome.shell.extensions.dash-to-dock shortcut-timeout 2.0 org.gnome.shell.extensions.dash-to-dock transparency-mode 'ADAPTIVE' org.gnome.shell.extensions.dash-to-dock multi-monitor false org.gnome.shell.extensions.dash-to-dock shortcut-text 'q' org.gnome.shell.extensions.dash-to-dock isolate-workspaces false org.gnome.shell.extensions.dash-to-dock max-alpha 0.80004 org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock hide-delay 0.20001 org.gnome.shell.extensions.dash-to-dock show-favorites true org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-color '#e95420' org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-width 0 org.gnome.shell.extensions.dash-to-dock app-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock app-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock isolate-monitors false org.gnome.shell.extensions.dash-to-dock app-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock custom-theme-shrink true org.gnome.shell.extensions.dash-to-dock app-hotkey-7 ['7'] org.gnome.shell.extensions.dash-to-dock autohide true org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-7 ['7'] org.gnome.shell.extensions.dash-to-dock
[Desktop-packages] [Bug 1800333] Re: Ubuntu dock not working properly
e) is bug 1769383 For the remaining issues, please log each as a separate bug. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1800333 Title: Ubuntu dock not working properly Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Ubuntu 18.10 Linux mbpr13b 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Upgrade from Ubuntu 18.04, all updates applied Ubuntu dock has several issues (some reported elsewhere) a) dock does not allow to relocate on screen (does not honour gsetting dock-position) b) dock does not react to hotkeys (even though are set in gsettings) c) dock does not hide on lock screen (https://www.queryxchange.com/q/3_1085426/desktop-is-visible-is-visible-after-suspend/) d) dock does allow application launch, termination and some commands when machine in locked e) dock appears after resume from RAM f) dash button does not react on first mouse click when applications are open g) dock changes size if applications are open and a dot indicates the fact here are the Gnome settings: gsettings list-recursively org.gnome.shell.extensions.dash-to-dock org.gnome.shell.extensions.dash-to-dock click-action 'previews' org.gnome.shell.extensions.dash-to-dock preferred-monitor -1 org.gnome.shell.extensions.dash-to-dock force-straight-corner false org.gnome.shell.extensions.dash-to-dock show-show-apps-button true org.gnome.shell.extensions.dash-to-dock show-windows-preview true org.gnome.shell.extensions.dash-to-dock animation-time 0.20001 org.gnome.shell.extensions.dash-to-dock scroll-action 'switch-workspace' org.gnome.shell.extensions.dash-to-dock height-fraction 0.90002 org.gnome.shell.extensions.dash-to-dock activate-single-window true org.gnome.shell.extensions.dash-to-dock running-indicator-dominant-color false org.gnome.shell.extensions.dash-to-dock custom-theme-customize-running-dots true org.gnome.shell.extensions.dash-to-dock minimize-shift true org.gnome.shell.extensions.dash-to-dock show-apps-at-top true org.gnome.shell.extensions.dash-to-dock pressure-threshold 100.0 org.gnome.shell.extensions.dash-to-dock show-delay 0.25 org.gnome.shell.extensions.dash-to-dock icon-size-fixed true org.gnome.shell.extensions.dash-to-dock intellihide-mode 'ALL_WINDOWS' org.gnome.shell.extensions.dash-to-dock customize-alphas false org.gnome.shell.extensions.dash-to-dock apply-custom-theme false org.gnome.shell.extensions.dash-to-dock hot-keys true org.gnome.shell.extensions.dash-to-dock extend-height true org.gnome.shell.extensions.dash-to-dock background-color '#ff' org.gnome.shell.extensions.dash-to-dock shortcut-timeout 2.0 org.gnome.shell.extensions.dash-to-dock transparency-mode 'ADAPTIVE' org.gnome.shell.extensions.dash-to-dock multi-monitor false org.gnome.shell.extensions.dash-to-dock shortcut-text 'q' org.gnome.shell.extensions.dash-to-dock isolate-workspaces false org.gnome.shell.extensions.dash-to-dock max-alpha 0.80004 org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock hide-delay 0.20001 org.gnome.shell.extensions.dash-to-dock show-favorites true org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-color '#e95420' org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-width 0 org.gnome.shell.extensions.dash-to-dock app-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock app-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock isolate-monitors false org.gnome.shell.extensions.dash-to-dock app-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock custom-theme-shrink true org.gnome.shell.extensions.dash-to-dock app-hotkey-7 ['7']
[Desktop-packages] [Bug 1800555] Re: Computer slow. Error reports appear.
** Tags added: radeon -- 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/1800555 Title: Computer slow. Error reports appear. Status in xorg-server package in Ubuntu: New Bug description: Computer slow. Error reports appear. Says system is running on low graphics sometimes. Makes me log in most of the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Stopped WPA supplicant. [[0;32m OK [0m] Started Show Plymouth Boot Screen. Starting Hold until boot process finishes up... 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 Oct 29 17:37:27 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1] InstallationDate: Installed on 2016-09-11 (778 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard p6710f ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.07 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: 4CE0480TV4 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6710f dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 29 17:32:25 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 8 inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 9 inputLogitech USB Optical Mouse MOUSE, id 10 xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800555/+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 1800308] Re: return from lock is extremely slow
*** This bug is a duplicate of bug 1774188 *** https://bugs.launchpad.net/bugs/1774188 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1774188, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1774188 Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) -- 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/1800308 Title: return from lock is extremely slow Status in gnome-shell package in Ubuntu: Triaged Bug description: System Details -Computer- Processor : Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz Memory: 16329MB (7787MB used) Machine Type : Laptop Operating System : Ubuntu 18.10 -Display- Resolution: 1920x1080 pixels OpenGL Renderer : (Unknown) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HDA Intel HDMI Audio Adapter : HDA-Intel - HDA Intel PCH -Input Devices- Lid Switch Power Button Sleep Button Power Button AT Translated Set 2 keyboard Video Bus AlpsPS/2 ALPS DualPoint Stick AlpsPS/2 ALPS DualPoint TouchPad Dell WMI hotkeys Laptop_Integrated_Webcam_HD: In HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 HDA Intel PCH Dock Mic HDA Intel PCH Dock Line Out HDA Intel PCH Front Headphone -SCSI Disks- ATA Origin Inception Whenever the system locks after closing the laptop lid for a period of time and I try to resurrect the screen is frozen not on the lock screen but on the desktop. Eventually this transitions to the laock screen but still freezes. I can move the mouse the entire time. Eventually after a period of time I can access the password screen and all is normal but total duration can be 2 minutes or more. In 18.04 I did not have this issue. I have marked it as a security vulnerability as if I close my lid and sensitive data was visible on screen opening the lid will show this instead of the lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800308/+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 1801205] [NEW] Can't mount veracrypt volumes
Public bug reported: Using mount from nautilus (open with) or right from Gnome Disk, the file in question is "mounted" as a loop device. Therefore, no opening of that container nor questions about how to open the file. This is Ubuntu 18.10 from 18.04. Already tried 18.10 on a VM (Live session) and Gnome on Xorg & Wayland. Also tryed Tail in order to see the Veracrypt property working. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-disk-utility 3.30.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Nov 1 18:35:17 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-08 (146 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to cosmic on 2018-10-30 (2 days ago) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic gnome-session main-features third-party-packages ubuntu-session wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1801205 Title: Can't mount veracrypt volumes Status in gnome-disk-utility package in Ubuntu: New Bug description: Using mount from nautilus (open with) or right from Gnome Disk, the file in question is "mounted" as a loop device. Therefore, no opening of that container nor questions about how to open the file. This is Ubuntu 18.10 from 18.04. Already tried 18.10 on a VM (Live session) and Gnome on Xorg & Wayland. Also tryed Tail in order to see the Veracrypt property working. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-disk-utility 3.30.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Nov 1 18:35:17 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-08 (146 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to cosmic on 2018-10-30 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1801205/+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 1801202] Re: Xorg freeze
It seems to have problems with your hard drive.
--
Cristian Aravena Romero (caravena)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
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/1801202
Title:
Xorg freeze
Status in linux package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
New
Bug description:
The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs or folders open.
---
CurrentDmesg.txt:
[ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0
[ 5465.753954] ata1.00: irq_stat 0x4008
[ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED
[ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma
131072 in
res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409
(media error)
[ 5465.753973] ata1.00: status: { DRDY ERR }
[ 5465.753976] ata1.00: error: { UNC }
[ 5466.031887] ata1.00: configured for UDMA/133
[ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current]
[ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error -
auto reallocate failed
[ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01
00 00
[ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120
[ 5466.031994] ata1: EH complete
---
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e]
(rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b]
Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b]
InstallationDate: Installed on 2018-10-04 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: LENOVO 80QQ
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN63WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Nano 5B6
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 100-15IBD
dmi.modalias:
dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
dmi.product.family: IDEAPAD
dmi.product.name: 80QQ
dmi.product.version: Lenovo ideapad 100-15IBD
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801202/+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 1801202] Status changed to Confirmed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1801202
Title:
Xorg freeze
Status in linux package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
New
Bug description:
The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs or folders open.
---
CurrentDmesg.txt:
[ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0
[ 5465.753954] ata1.00: irq_stat 0x4008
[ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED
[ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma
131072 in
res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409
(media error)
[ 5465.753973] ata1.00: status: { DRDY ERR }
[ 5465.753976] ata1.00: error: { UNC }
[ 5466.031887] ata1.00: configured for UDMA/133
[ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current]
[ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error -
auto reallocate failed
[ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01
00 00
[ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120
[ 5466.031994] ata1: EH complete
---
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e]
(rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b]
Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b]
InstallationDate: Installed on 2018-10-04 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: LENOVO 80QQ
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN63WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Nano 5B6
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 100-15IBD
dmi.modalias:
dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
dmi.product.family: IDEAPAD
dmi.product.name: 80QQ
dmi.product.version: Lenovo ideapad 100-15IBD
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801202/+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 1801202] Re: Xorg freeze
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".
Thanks in advance.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Description changed:
The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs or folders open.
+
+ ---
+
+ CurrentDmesg.txt:
+ [ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0
+ [ 5465.753954] ata1.00: irq_stat 0x4008
+ [ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED
+ [ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma
131072 in
+ res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409
(media error)
+ [ 5465.753973] ata1.00: status: { DRDY ERR }
+ [ 5465.753976] ata1.00: error: { UNC }
+ [ 5466.031887] ata1.00: configured for UDMA/133
+ [ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
+ [ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current]
+ [ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error -
auto reallocate failed
+ [ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01
00 00
+ [ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120
+ [ 5466.031994] ata1: EH complete
+
+ ---
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e]
(rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b]
Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b]
InstallationDate: Installed on 2018-10-04 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
MachineType: LENOVO 80QQ
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN63WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Nano 5B6
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 100-15IBD
dmi.modalias:
dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
dmi.product.family: IDEAPAD
dmi.product.name: 80QQ
dmi.product.version: Lenovo ideapad 100-15IBD
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
--
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/1801202
Title:
Xorg freeze
Status in linux package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
New
Bug description:
The
[Desktop-packages] [Bug 1801202] [NEW] Xorg freeze
Public bug reported:
The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs or folders open.
---
CurrentDmesg.txt:
[ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0
[ 5465.753954] ata1.00: irq_stat 0x4008
[ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED
[ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma
131072 in
res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409
(media error)
[ 5465.753973] ata1.00: status: { DRDY ERR }
[ 5465.753976] ata1.00: error: { UNC }
[ 5466.031887] ata1.00: configured for UDMA/133
[ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current]
[ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error -
auto reallocate failed
[ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01 00
00
[ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120
[ 5466.031994] ata1: EH complete
---
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev
09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b]
Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b]
InstallationDate: Installed on 2018-10-04 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 80QQ
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN63WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Nano 5B6
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 100-15IBD
dmi.modalias:
dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
dmi.product.family: IDEAPAD
dmi.product.name: 80QQ
dmi.product.version: Lenovo ideapad 100-15IBD
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic freeze ubuntu
** Description changed:
The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs open.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
- nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
- nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
+ nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
+ nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:
-
+
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
- Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e]
(rev 09) (prog-if 00
[Desktop-packages] [Bug 1801181] Re: Pixelized display
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- 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/1801181 Title: Pixelized display Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: New Bug description: Artefakty upgrading to 18.04 lts three iż a problem without display. I have no duch problem on 16.04 lts --- CurrentDmesg.txt: [ 29.779035] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid [ 29.779082] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! [ 30.612745] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid [ 30.612804] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! -- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Nov 1 22:51:23 2018 DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115] Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] InstallationDate: Installed on 2015-03-10 (1332 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 2087A37 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=76e45c9b-b94c-414a-9c7f-cfbbafb58a1a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-11-01 (0 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2087A37 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2087A37:pvrThinkPadT500:rvnLENOVO:rn2087A37:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T500 dmi.product.name: 2087A37 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 1 20:57:30 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801181/+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 1769480] Re: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes
Is there any chance to reactivate that topic? I have the same issue on a fresh Lubuntu 18.10 installation on my Sony Vaio Notebook. After 5 minutes the tray icon (nm-tray) only shows the current wifi connection (which still works), no others anymore. -- 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/1769480 Title: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: how to reproduce: dd the iso to an usb drive and boot from it. List all wifi devices in live-mode and connect to one of it. Use the web for some minutes. Open up the wifi on the top right again and list the available networks - it dont show any others any more. Just the one you are connected to. How to overcome the bug: put the computer into airplane mode and go away from airplane mode again. Or: disconnect the usb wifi device and connect it again. Does this bug exist also on installed 18.04 and updated to last (apt update, apt upgrade, apt dist-upgrade)? Yes What wifi device is been used: ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' usbcore: registered new interface driver rt2800usb ... ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin' ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36 uname -a Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769480/+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 1800963] Re: Changing Primary DIsplay Flips Which Display Has The Dock
This behavior is also encountered when using the nouveau display driver on a fresh install that hasn't had nvidia drivers installed. -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
[Desktop-packages] [Bug 1793918] Re: Add/reintroduce setting to enable suspend on lid-close with external monitors attached
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-desktop (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1793918 Title: Add/reintroduce setting to enable suspend on lid-close with external monitors attached Status in gnome-desktop package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-tweaks package in Ubuntu: Confirmed Bug description: With Ubuntu 18.04 my laptop does not suspend when lid is closed while external monitors are attached. This might be a good behavior for many users but I want to have my laptop suspend again when I close it. Some time ago there was an option in gsettings scheme org.gnome .settings-daemon.plugins.power named lid-close-suspend-with-external- monitor (introduced in https://bugzilla.gnome.org/show_bug.cgi?id=657201). This settings seems to have no effect anymore and seems to be removed in the current scheme (repatched in ubuntu's version only). This is realy anoying because at the moment the laptop does not suspend at all with lid-close action because the nvidia driver discover the internal built-in display under DP-4. That makes gnome think that there is an external monitor connected. Is this a bug in nvidia driver or a problem of gnome-desktop's gnome-rr which thinks that only monitors with "LVDS|Lvds|LCD|eDP|DSI" in it's name could be an internal display? However this might be another bug. I want to suspend with realy external monitors attached anyhow because I always use my laptop as second/third monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1793918/+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 1801172] Re: Network Manager fails to require VPN
Please reproduce the problem, do a hard reset and then run this command: journalctl -b-1 > prev_boot.txt and send us the resulting file prev_boot.txt ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1801172 Title: Network Manager fails to require VPN Status in network-manager package in Ubuntu: Incomplete Bug description: In Network Manager you can require that the local network requires a particular VPN connection. This works without issue, when networking is enabled, VPN connects automatically. But should there be any service interruption, Network Manager will reconnect using the local network and then exposing the real IP address. This issue only started to occur in 18.04 using GNome desktop environment. This was not an issue in 16.04 using GNome or Unity. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 16:16:08 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.7.1 dev enp0s3 proto dhcp metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 192.168.7.0/24 dev enp0s3 proto kernel scope link src 192.168.7.143 metric 100 IwConfig: enp0s3no wireless extensions. lono wireless extensions. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 f6168b50-a792-36c3-8c34-cae535a9f95f ethernet 1541106764 Thu 01 Nov 2018 04:12:44 PM CDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s3 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s3 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 f6168b50-a792-36c3-8c34-cae535a9f95f /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1801172/+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 1801172] Re: Network Manager fails to require VPN
Your system is updated/upgrade? -- Cristian Aravena Romero (caravena) -- 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/1801172 Title: Network Manager fails to require VPN Status in network-manager package in Ubuntu: Incomplete Bug description: In Network Manager you can require that the local network requires a particular VPN connection. This works without issue, when networking is enabled, VPN connects automatically. But should there be any service interruption, Network Manager will reconnect using the local network and then exposing the real IP address. This issue only started to occur in 18.04 using GNome desktop environment. This was not an issue in 16.04 using GNome or Unity. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 16:16:08 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.7.1 dev enp0s3 proto dhcp metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 192.168.7.0/24 dev enp0s3 proto kernel scope link src 192.168.7.143 metric 100 IwConfig: enp0s3no wireless extensions. lono wireless extensions. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 f6168b50-a792-36c3-8c34-cae535a9f95f ethernet 1541106764 Thu 01 Nov 2018 04:12:44 PM CDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes enp0s3 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s3 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 f6168b50-a792-36c3-8c34-cae535a9f95f /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1801172/+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 1793918] Re: Add/reintroduce setting to enable suspend on lid-close with external monitors attached
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1793918 Title: Add/reintroduce setting to enable suspend on lid-close with external monitors attached Status in gnome-desktop package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-tweaks package in Ubuntu: Confirmed Bug description: With Ubuntu 18.04 my laptop does not suspend when lid is closed while external monitors are attached. This might be a good behavior for many users but I want to have my laptop suspend again when I close it. Some time ago there was an option in gsettings scheme org.gnome .settings-daemon.plugins.power named lid-close-suspend-with-external- monitor (introduced in https://bugzilla.gnome.org/show_bug.cgi?id=657201). This settings seems to have no effect anymore and seems to be removed in the current scheme (repatched in ubuntu's version only). This is realy anoying because at the moment the laptop does not suspend at all with lid-close action because the nvidia driver discover the internal built-in display under DP-4. That makes gnome think that there is an external monitor connected. Is this a bug in nvidia driver or a problem of gnome-desktop's gnome-rr which thinks that only monitors with "LVDS|Lvds|LCD|eDP|DSI" in it's name could be an internal display? However this might be another bug. I want to suspend with realy external monitors attached anyhow because I always use my laptop as second/third monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1793918/+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 1793918] Re: Add/reintroduce setting to enable suspend on lid-close with external monitors attached
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-tweaks (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1793918 Title: Add/reintroduce setting to enable suspend on lid-close with external monitors attached Status in gnome-desktop package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-tweaks package in Ubuntu: Confirmed Bug description: With Ubuntu 18.04 my laptop does not suspend when lid is closed while external monitors are attached. This might be a good behavior for many users but I want to have my laptop suspend again when I close it. Some time ago there was an option in gsettings scheme org.gnome .settings-daemon.plugins.power named lid-close-suspend-with-external- monitor (introduced in https://bugzilla.gnome.org/show_bug.cgi?id=657201). This settings seems to have no effect anymore and seems to be removed in the current scheme (repatched in ubuntu's version only). This is realy anoying because at the moment the laptop does not suspend at all with lid-close action because the nvidia driver discover the internal built-in display under DP-4. That makes gnome think that there is an external monitor connected. Is this a bug in nvidia driver or a problem of gnome-desktop's gnome-rr which thinks that only monitors with "LVDS|Lvds|LCD|eDP|DSI" in it's name could be an internal display? However this might be another bug. I want to suspend with realy external monitors attached anyhow because I always use my laptop as second/third monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1793918/+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 1801103] Re: Kubuntu driver manager fails to install nvidia-prime on hybrid systems and that makes system unusable for unexperienced users
It's not needed for everyone, just for laptops with hybrid nvidia graphics. With current behavior some perfectly reasonable user actions render system unusable without CLI knowledge. IMO it's exactly driver managers' problem and it should not just install a package but make sure drivers are correctly installed for this system. -- 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/1801103 Title: Kubuntu driver manager fails to install nvidia-prime on hybrid systems and that makes system unusable for unexperienced users Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Ignoring the fact that only nvidia-340 drivers were suggested when 390 is available, with a completely fresh install after using Kubuntu driver manager system does not show GUI on the next boot because NVIDIA drivers cannot work without nvidia-prime on hybrid systems. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: kubuntu-driver-manager 15.10ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 1 16:44:54 2018 InstallationDate: Installed on 2018-11-01 (0 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: kubuntu-driver-manager 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-340/+bug/1801103/+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 1801181] Re: Pixelized display
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19 ** Description changed: Artefakty upgrading to 18.04 lts three iż a problem without display. I have no duch problem on 16.04 lts + + --- + + CurrentDmesg.txt: + [ 29.779035] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid + [ 29.779082] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! + [ 30.612745] radeon :01:00.0: r600_check_texture_resource:1566 tex pitch (1680, 0x40, 1) invalid + [ 30.612804] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream ! + + -- + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Nov 1 22:51:23 2018 DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: - bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed - bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed + bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed + bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: - Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115] - Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) -Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] + Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115] + Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) + Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] InstallationDate: Installed on 2015-03-10 (1332 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 2087A37 PccardctlIdent: - Socket 0: -no product info available + Socket 0: + no product info available PccardctlStatus: - Socket 0: -no card + Socket 0: + no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=76e45c9b-b94c-414a-9c7f-cfbbafb58a1a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-11-01 (0 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2087A37 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2087A37:pvrThinkPadT500:rvnLENOVO:rn2087A37:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T500 dmi.product.name: 2087A37 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 1 20:57:30 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 ** Also affects: linux (Ubuntu) Importance: Undecided
[Desktop-packages] [Bug 1801181] [NEW] Pixelized display
Public bug reported: Artefakty upgrading to 18.04 lts three iż a problem without display. I have no duch problem on 16.04 lts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Nov 1 22:51:23 2018 DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115] Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] InstallationDate: Installed on 2015-03-10 (1332 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 2087A37 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=76e45c9b-b94c-414a-9c7f-cfbbafb58a1a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-11-01 (0 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6FET93WW (3.23 ) dmi.board.name: 2087A37 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2087A37:pvrThinkPadT500:rvnLENOVO:rn2087A37:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T500 dmi.product.name: 2087A37 dmi.product.version: ThinkPad T500 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 1 20:57:30 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1801181 Title: Pixelized display Status in xorg package in Ubuntu: New Bug description: Artefakty upgrading to 18.04 lts three iż a problem without display. I have no duch problem on 16.04 lts ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Thu Nov 1 22:51:23 2018 DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:2115] Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] [1002:9591] (prog-if 00 [VGA controller]) Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116] InstallationDate: Installed on 2015-03-10 (1332 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: LENOVO 2087A37 PccardctlIdent: Socket 0: no product info available PccardctlStatus:
[Desktop-packages] [Bug 1801054] Re: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: tentando escribir «/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», que tamén está no paquete nvidia-34
*** This bug is a duplicate of bug 1791542 *** https://bugs.launchpad.net/bugs/1791542 ** This bug has been marked a duplicate of bug 1791542 package libglvnd-dev 1.0.0-2ubuntu2.1 failed to upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so', which is also in package nvidia-340 340.107-0ubuntu0~gpu18.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1801054 Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: tentando escribir «/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», que tamén está no paquete nvidia-340 340.106-0ubuntu3 Status in libglvnd package in Ubuntu: New Bug description: Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic x86_64 4.15.0-34-generic ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglvnd-dev 1.0.0-2ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: libgles1:amd64: Install libglvnd-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Nov 1 11:33:35 2018 DpkgHistoryLog: Start-Date: 2018-11-01 11:33:34 Commandline: apt-get install -f Requested-By: manuel (1000) Install: libgles1:amd64 (1.0.0-2ubuntu2.2, automatic) Upgrade: libglvnd-dev:amd64 (1.0.0-2ubuntu2.1, 1.0.0-2ubuntu2.2) ErrorMessage: tentando escribir «/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», que tamén está no paquete nvidia-340 340.106-0ubuntu3 InstallationDate: Installed on 2018-05-03 (181 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libglvnd Title: package libglvnd-dev 1.0.0-2ubuntu2.1 failed to install/upgrade: tentando escribir «/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so», que tamén está no paquete nvidia-340 340.106-0ubuntu3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1801054/+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 1801172] [NEW] Network Manager fails to require VPN
Public bug reported: In Network Manager you can require that the local network requires a particular VPN connection. This works without issue, when networking is enabled, VPN connects automatically. But should there be any service interruption, Network Manager will reconnect using the local network and then exposing the real IP address. This issue only started to occur in 18.04 using GNome desktop environment. This was not an issue in 16.04 using GNome or Unity. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 16:16:08 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.7.1 dev enp0s3 proto dhcp metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 192.168.7.0/24 dev enp0s3 proto kernel scope link src 192.168.7.143 metric 100 IwConfig: enp0s3no wireless extensions. lono wireless extensions. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 f6168b50-a792-36c3-8c34-cae535a9f95f ethernet 1541106764 Thu 01 Nov 2018 04:12:44 PM CDT yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 yes enp0s3 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s3 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 f6168b50-a792-36c3-8c34-cae535a9f95f /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1801172 Title: Network Manager fails to require VPN Status in network-manager package in Ubuntu: New Bug description: In Network Manager you can require that the local network requires a particular VPN connection. This works without issue, when networking is enabled, VPN connects automatically. But should there be any service interruption, Network Manager will reconnect using the local network and then exposing the real IP address. This issue only started to occur in 18.04 using GNome desktop environment. This was not an issue in 16.04 using GNome or Unity. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 16:16:08 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.7.1 dev enp0s3 proto dhcp metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 192.168.7.0/24 dev enp0s3 proto kernel scope link src 192.168.7.143 metric 100 IwConfig: enp0s3no wireless extensions. lono wireless extensions. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE
[Desktop-packages] [Bug 1800426] Re: gnome-screensaver only locks the screen a moment after resuming from standby
*** This bug is a duplicate of bug 1532508 *** https://bugs.launchpad.net/bugs/1532508 Ok, then it's not gnome-screensaver. Gnome uses the shell to do screen locking. Thanks. ** Information type changed from Private Security to Public Security ** This bug has been marked a duplicate of bug 1532508 Screen contents revealed briefly on resume, before even unlocking -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1800426 Title: gnome-screensaver only locks the screen a moment after resuming from standby Status in gnome-screensaver package in Ubuntu: New Bug description: If I lock my screen by pressing my system's "suspend" button and walk away anyone can get and photograph a glimpse of my unlocked screen just by pressing any key: - the system wakes up and shows the contents of the theoretically-locked screen - keyboard input is activated allowing - if one is quick - to enter and execute a command. - the screen is locked. Alas! too late. For Android and the iPhone more harmless ways to get glympses of the unlocked system were treated as security scandals by heise.de and golem.de (IT-centered german press services) => reporting this as a security bug. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-screensaver 3.6.1-8ubuntu3 Uname: Linux 4.18.1-041801-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Mon Oct 29 07:54:36 2018 SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1800426/+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 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
Can confirm that louBurnard's method mentioned in comment #96 also worked for me with Ubuntu 18.04 and the Epson Perfection V500. Thanks also to staedtler-przyborski for his tip in #36. -- 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/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Confirmed Bug description: Many scanners can no more be used since sane has changed something: The 3rd-party plug-in the vendor provides as .deb package will still install. But the scanner is no more recognized. Scanners that are affected are(besides others): - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Brother MFC-8510DN - Epson Perfection V33 It is to note that the probability that the scanner manufacturers fix things others broke is below 100%. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental2ubuntu2 Uname: Linux 4.14.0-041400rc5-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 Date: Fri Oct 27 12:35:52 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/1728012/+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 1801161] [NEW] soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Public bug reported: Using LibreOffice Calc I was editing a filter on a pivot table and all LibreOffice windows hung. What appeared in /var/log/syslog was: Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Unknown sequence number while processing queue Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Aborting, sorry about that. Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Nov 1 13:32:27 santiago gnome-shell[8288]: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice-calc 1:6.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 13:39:03 2018 InstallationDate: Installed on 2018-10-29 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1801161 Title: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Status in libreoffice package in Ubuntu: New Bug description: Using LibreOffice Calc I was editing a filter on a pivot table and all LibreOffice windows hung. What appeared in /var/log/syslog was: Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Unknown sequence number while processing queue Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: [xcb] Aborting, sorry about that. Nov 1 13:31:57 santiago org.gnome.Shell.desktop[8288]: soffice.bin: ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Nov 1 13:32:27 santiago gnome-shell[8288]: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice-calc 1:6.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 13:39:03 2018 InstallationDate: Installed on 2018-10-29 (3 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161/+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 1801098] Re: gnome-software does not exit a search
*** This bug is a duplicate of bug 1801097 *** https://bugs.launchpad.net/bugs/1801097 ** This bug has been marked a duplicate of bug 1801097 gnome-software does not exit a search -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1801098 Title: gnome-software does not exit a search Status in gnome-software package in Ubuntu: New Bug description: I (accidentally) started Rhythmbox for the firt time ever at this laptop. It started, and a pop-up came asking if I wanted to install additional needed codecs (title line says "Available software for MPEG-4 ACC decoder", so I guess this was the search argument. I accepted, and gnome-software opened with a search result for GSTreamer codecs. I installed two of them, life is good, closed (Alt-F4) gnome-software. Then I decided to install some other package via GS as well. Opened (again) it, and... I am shown a search result for GStreamer codecs. I cannot exit this search. (via the "<" at the left of the title line). I can only close the thing. End result: gnome-software is now, for all practical purposes, unavailable. Hence, the bug. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-software 3.30.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 1 09:15:18 2018 ExecutablePath: /usr/bin/gnome-software InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu7 SourcePackage: gnome-software UpgradeStatus: Upgraded to cosmic on 2018-07-07 (116 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-03-07T18:07:32.794203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1801098/+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 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster
Coming back from Pop!_OS 18.10 (Based on Ubuntu 18.10, 4.18.0-10-generic) Still haven't tried with Audacity, but gnome-sound-recorded and Telegram Desktop have been fixed in my case. All I did this time was setting default-sample-rate = 48000 on /etc/pulse/daemon.conf and restarting (Probably restarting pulseaudio is enough). before this, trying to send an audio recording through Telegram would end in an "muted" audio. Now it's working perfectly. You can try with arecord arecord -f cd -d 10 test.wav -> For recording aplay test.wav -> For playing (Probably gonna end up in noise) arecord -f cd -d 10 -r 48000 test-mic.wav -> recording with the 48000 sample rate should provide good results PD: Remember to increase a bit the mic volume from the sound settings -- 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/1764965 Title: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster Status in sound-2.6 (alsa-kernel): New Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recording applications (audacity, arecord, gnome-sound-recorder) record extremely slowly (at what seems to be 0,1x speed), which means that at playback the sound is played at a very high pitch and much faster than the original. To help you understand the issue, I've attached an archive containing two files recorded at the same time, one with arecord -f cd and the other with a stand-alone Olympus recorder. A video of Audacity's behavior when trying to record is also available: https://youtu.be/Fe20eQNvZVA Look at the seconds hand of the xclock and how much it is moving before Audacity is done recording one second of audio. Things I've already tried: * Purging and reinstalling Audacity * Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki * Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 audacity as suggested on AskUbuntu * Reinstalling Ubuntu on a new hard disk * Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 daily and Xubuntu 17.10.1, 18.04) The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard. The problem can be reproduced as follows: * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've tested with) * Install audacity via the terminal * Start recording, microphone is connected to the rear microphone jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacopo 2417 F pulseaudio /dev/snd/controlC0: jacopo 2417 F pulseaudio CurrentDesktop: Unity Date: Wed Apr 18 09:35:50 2018 InstallationDate: Installed on 2018-03-03 (45 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_Type: None of the above Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1764965/+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 1716654] Re: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound
I'm getting the same on ALC892 -- 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/1716654 Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Have checked under windows (same computer in dual-boot & same headset), and the sound is crystal clear, so 99% sure this is not a hardware problem. Motherboard is ASUS Crosshair Hero 6. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: paul 2587 F pulseaudio /dev/snd/controlC0: paul 2587 F pulseaudio /dev/snd/controlC1: paul 2587 F pulseaudio /dev/snd/controlC2: paul 2587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 11:48:05 2017 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic successful Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
ahhh well like I said that crash dump was from after uninstalling the jack packages. things are still broken without jack installed. no sound in any app. -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+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 1801148] [NEW] package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it bef
Public bug reported: Unable to open skype ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 Uname: Linux 4.4.0-94-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: gir1.2-unity-5.0: Configure upower: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Nov 1 13:11:35 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.29 SourcePackage: libunity Title: package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libunity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1801148 Title: package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libunity package in Ubuntu: New Bug description: Unable to open skype ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83 Uname: Linux 4.4.0-94-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: gir1.2-unity-5.0: Configure upower: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Nov 1 13:11:35 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.29 SourcePackage: libunity Title: package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1801148/+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 1800333] Re: Ubuntu dock not working properly
@Marc re d) I have a terminal on my dock. I can open this terminal from the lock screen I do have sudo rights on my account I can enter commands that are kept in the buffer I can press ENTER to get the command executed I just leave it up to your judgement if this is a security issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1800333 Title: Ubuntu dock not working properly Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 18.10 Linux mbpr13b 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Upgrade from Ubuntu 18.04, all updates applied Ubuntu dock has several issues (some reported elsewhere) a) dock does not allow to relocate on screen (does not honour gsetting dock-position) b) dock does not react to hotkeys (even though are set in gsettings) c) dock does not hide on lock screen (https://www.queryxchange.com/q/3_1085426/desktop-is-visible-is-visible-after-suspend/) d) dock does allow application launch, termination and some commands when machine in locked e) dock appears after resume from RAM f) dash button does not react on first mouse click when applications are open g) dock changes size if applications are open and a dot indicates the fact here are the Gnome settings: gsettings list-recursively org.gnome.shell.extensions.dash-to-dock org.gnome.shell.extensions.dash-to-dock click-action 'previews' org.gnome.shell.extensions.dash-to-dock preferred-monitor -1 org.gnome.shell.extensions.dash-to-dock force-straight-corner false org.gnome.shell.extensions.dash-to-dock show-show-apps-button true org.gnome.shell.extensions.dash-to-dock show-windows-preview true org.gnome.shell.extensions.dash-to-dock animation-time 0.20001 org.gnome.shell.extensions.dash-to-dock scroll-action 'switch-workspace' org.gnome.shell.extensions.dash-to-dock height-fraction 0.90002 org.gnome.shell.extensions.dash-to-dock activate-single-window true org.gnome.shell.extensions.dash-to-dock running-indicator-dominant-color false org.gnome.shell.extensions.dash-to-dock custom-theme-customize-running-dots true org.gnome.shell.extensions.dash-to-dock minimize-shift true org.gnome.shell.extensions.dash-to-dock show-apps-at-top true org.gnome.shell.extensions.dash-to-dock pressure-threshold 100.0 org.gnome.shell.extensions.dash-to-dock show-delay 0.25 org.gnome.shell.extensions.dash-to-dock icon-size-fixed true org.gnome.shell.extensions.dash-to-dock intellihide-mode 'ALL_WINDOWS' org.gnome.shell.extensions.dash-to-dock customize-alphas false org.gnome.shell.extensions.dash-to-dock apply-custom-theme false org.gnome.shell.extensions.dash-to-dock hot-keys true org.gnome.shell.extensions.dash-to-dock extend-height true org.gnome.shell.extensions.dash-to-dock background-color '#ff' org.gnome.shell.extensions.dash-to-dock shortcut-timeout 2.0 org.gnome.shell.extensions.dash-to-dock transparency-mode 'ADAPTIVE' org.gnome.shell.extensions.dash-to-dock multi-monitor false org.gnome.shell.extensions.dash-to-dock shortcut-text 'q' org.gnome.shell.extensions.dash-to-dock isolate-workspaces false org.gnome.shell.extensions.dash-to-dock max-alpha 0.80004 org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock hide-delay 0.20001 org.gnome.shell.extensions.dash-to-dock show-favorites true org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-color '#e95420' org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-width 0 org.gnome.shell.extensions.dash-to-dock app-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock app-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock isolate-monitors false org.gnome.shell.extensions.dash-to-dock app-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock
[Desktop-packages] [Bug 1280300] Re: Desktop contents displayed on resume, before lock screen is shown
I'd imagine a workaround could be to have a hook for suspend write to the framebuffer, but I failed at getting this working when I tried today (put a script in /usr/lib/systemd/system-sleep to invoke eog in fullscreen). Regarding the comment above about this being fixed in "certified" laptops, this doesn't seem to be 100% correct. See this on a Dell XPS 9350, and this machine was available in a "Developer edition" running Ubuntu. Still see this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1280300 Title: Desktop contents displayed on resume, before lock screen is shown Status in gnome-screensaver package in Ubuntu: Invalid Bug description: I am running 14.04. When I resume from sleep, the contents of my desktop (including any open windows, emails, etc) are displayed onscreen briefly before the unlock screen is shown. This potentially allows an attacker to view the contents of a locked screen. To reproduce: 1) Suspend a machine, e.g. by closing the lid 2) Resume the machine Expected results: Upon resume, the first thing shown onscreen is the screensaver unlock screen. Actual results: Upon resume, the first thing shown onscreen is the set of open windows that were displayed before the machine was put to sleep. After a second or two, the unlock screen is drawn and you have to enter a password to unlock the machine. This is reproducible on my system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 14 09:05:50 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2013-12-02 (73 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-02-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1280300/+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 1801140] Re: Strange screen behaviour with tearing
Forgot to say that playing on the external monitor seem different even with the same tearing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1801140 Title: Strange screen behaviour with tearing Status in nvidia-prime package in Ubuntu: New Bug description: It's a known issue the amount of screen tearing when using the Optimus NVIDIA card, and with PRIME sync this is partially fixed, but the games are unplayable due to the input lag. But I'm figuring out another issue that I'm not sure about what the cause can be. I'm getting solid fps in games, but they feel choppy and different from Windows even with the same fps, tested in a lot of games, I don't know if that has something to do with the screen tearing but they look like false fps drops or a screen refresh rate issue, I'm 100% sure that they are not fps drops, the fps are stable, so that's why I think it could be extreme screen tearing or refresh rate, this is very annoying when you play games. Screen tearing is obviously occurring also in Windows, but in there it doesn't feel choppy as when playing on Linux. Same games on my non-prime desktop, with the same NVIDIA driver feel a lot different. NVIDIA driver 410 (from graphics-drivers repo) Kubuntu 18.10 with compositing disabled Tested games: Steam half life 2, Lutris DXVK Overwatch and Heroes of the storm NVIDIA GTX 960m on Dell XPS 15 9550 i5 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1801140/+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 1801140] [NEW] Strange screen behaviour with tearing
Public bug reported: It's a known issue the amount of screen tearing when using the Optimus NVIDIA card, and with PRIME sync this is partially fixed, but the games are unplayable due to the input lag. But I'm figuring out another issue that I'm not sure about what the cause can be. I'm getting solid fps in games, but they feel choppy and different from Windows even with the same fps, tested in a lot of games, I don't know if that has something to do with the screen tearing but they look like false fps drops or a screen refresh rate issue, I'm 100% sure that they are not fps drops, the fps are stable, so that's why I think it could be extreme screen tearing or refresh rate, this is very annoying when you play games. Screen tearing is obviously occurring also in Windows, but in there it doesn't feel choppy as when playing on Linux. Same games on my non-prime desktop, with the same NVIDIA driver feel a lot different. NVIDIA driver 410 (from graphics-drivers repo) Kubuntu 18.10 with compositing disabled Tested games: Steam half life 2, Lutris DXVK Overwatch and Heroes of the storm NVIDIA GTX 960m on Dell XPS 15 9550 i5 version ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1801140 Title: Strange screen behaviour with tearing Status in nvidia-prime package in Ubuntu: New Bug description: It's a known issue the amount of screen tearing when using the Optimus NVIDIA card, and with PRIME sync this is partially fixed, but the games are unplayable due to the input lag. But I'm figuring out another issue that I'm not sure about what the cause can be. I'm getting solid fps in games, but they feel choppy and different from Windows even with the same fps, tested in a lot of games, I don't know if that has something to do with the screen tearing but they look like false fps drops or a screen refresh rate issue, I'm 100% sure that they are not fps drops, the fps are stable, so that's why I think it could be extreme screen tearing or refresh rate, this is very annoying when you play games. Screen tearing is obviously occurring also in Windows, but in there it doesn't feel choppy as when playing on Linux. Same games on my non-prime desktop, with the same NVIDIA driver feel a lot different. NVIDIA driver 410 (from graphics-drivers repo) Kubuntu 18.10 with compositing disabled Tested games: Steam half life 2, Lutris DXVK Overwatch and Heroes of the storm NVIDIA GTX 960m on Dell XPS 15 9550 i5 version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1801140/+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 1799293] Re: gnome session: Must ask twice to lock the screen
This bug is not specific to Ubuntu, I found out today that I have exactly the same problem on my other desktop running Fedora 29 with GNOME 3.30.1. I have the following extensions installed on it: - (K)StatusNotifierItem/AppIndicator Support - Dash to dock - No topleft hot corner - Background logo -- 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/1799293 Title: gnome session: Must ask twice to lock the screen Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Bug description: 1) Ubuntu 18.10 (new install) 2) gdm3 3.30.1-1ubuntu5 Preconditions The session's user has auto-login enabled (i.e. the system starts and the user is not prompted for a password but directly presented with the desktop) 3) What should happen: Unlocked desktop is showing. Lock screen is invoked (via WIN+L or via top right corner menu) and the lock screen is engaged (that is, lock screen clock shade drops down and screen fades to dark). Pressing ENTER brings back the lock screen and the password is prompted. 4) What happens: First Win + L lets the system in a half locked state in which the contents of the desktop are seen although no interaction is possible. A second Win + L correctly invokes the lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799293/+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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
This happened to me when using Ubuntu Cosmic Cuttlefish with htop and tilix installed beyond the clean install. I was able to open the applications that are available in the dock and noticed the bar resizing when hovering over it. Later multiple graphical bugs started to happen and in the next boot Xorg was failing to start. Rebooting again solved the login issues. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+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 1792843] Re: GDM lock screen will not accept credentials and then loses keyboard?
I can work around by using ctrl-alt-f1 to change to the user switcher and re-authenticatie into the session that way. -- 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/1792843 Title: GDM lock screen will not accept credentials and then loses keyboard? Status in gnome-shell package in Ubuntu: New Bug description: So yesterday I got the prompt to upgrade my 16LTS system to 18. This caused a number of issues, but the most frustrating issue out of many has to be this one. After a period of inactivity, the lock screen kicks in. When I then try to log in, using the correct password, I get a spinner for about 10 seconds, the "Authentication error". After a couple of seconds "Authentication error" goes away but now it seems no keys are registering at all in the password field. I say "it seems" because I see no "*"s as I type, but I do see occasional prompts of "Authentication error" coming back, but I haven't pinpointed the circumstances - certainly not triggered by hitting ENTER, sometimes backspace? Not sure if it has anything to do with the keys. After this all I can do is log in over ssh and reboot; I'm basically locked out on the console. If I wait a while the keyboard does seem to come back but the problem is still there - my password is not accepted and then the keyboard again seems to do nothing for a while. This happens whether I have a USB keyboard connected or whether I am running Synergy and using a virtual keyboard. Mouse continues to work fine. Release and kernel: Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-34-generic x86_64) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-09-16 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792843/+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 1792843] Re: GDM lock screen will not accept credentials and then loses keyboard?
This also happens to me on bionic on a dell xps 9370 (intel video) -- 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/1792843 Title: GDM lock screen will not accept credentials and then loses keyboard? Status in gnome-shell package in Ubuntu: New Bug description: So yesterday I got the prompt to upgrade my 16LTS system to 18. This caused a number of issues, but the most frustrating issue out of many has to be this one. After a period of inactivity, the lock screen kicks in. When I then try to log in, using the correct password, I get a spinner for about 10 seconds, the "Authentication error". After a couple of seconds "Authentication error" goes away but now it seems no keys are registering at all in the password field. I say "it seems" because I see no "*"s as I type, but I do see occasional prompts of "Authentication error" coming back, but I haven't pinpointed the circumstances - certainly not triggered by hitting ENTER, sometimes backspace? Not sure if it has anything to do with the keys. After this all I can do is log in over ssh and reboot; I'm basically locked out on the console. If I wait a while the keyboard does seem to come back but the problem is still there - my password is not accepted and then the keyboard again seems to do nothing for a while. This happens whether I have a USB keyboard connected or whether I am running Synergy and using a virtual keyboard. Mouse continues to work fine. Release and kernel: Ubuntu 18.04.1 LTS (GNU/Linux 4.15.0-34-generic x86_64) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-09-16 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1792843/+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 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
@grzesiekC, on my side, I quite frequently do the same (connecting / reconnecting), I will try to pay attention, to see if it's correlated. -- 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/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:68 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:67 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:71 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device is a touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:72 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is disabled. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver cannot change properties on a disabled device Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:65 Aug 8 10:44:55 Leggiero
[Desktop-packages] [Bug 1799631] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1799631 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: I can't not install Nvidia driver for my Nvidia gt 730 ddr5. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Oct 23 07:31:25 2018 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 InstallationDate: Installed on 2018-10-19 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 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-340/+bug/1799631/+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 1800555] Re: Computer slow. Error reports appear.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- 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/1800555 Title: Computer slow. Error reports appear. Status in xorg-server package in Ubuntu: New Bug description: Computer slow. Error reports appear. Says system is running on low graphics sometimes. Makes me log in most of the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Stopped WPA supplicant. [[0;32m OK [0m] Started Show Plymouth Boot Screen. Starting Hold until boot process finishes up... 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 Oct 29 17:37:27 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1] InstallationDate: Installed on 2016-09-11 (778 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard p6710f ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.07 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: 4CE0480TV4 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6710f dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 29 17:32:25 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 8 inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 9 inputLogitech USB Optical Mouse MOUSE, id 10 xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800555/+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 1800333] Re: Ubuntu dock not working properly
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Package changed: systemd (Ubuntu) => gnome-shell-extension-ubuntu- dock (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1800333 Title: Ubuntu dock not working properly Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 18.10 Linux mbpr13b 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Upgrade from Ubuntu 18.04, all updates applied Ubuntu dock has several issues (some reported elsewhere) a) dock does not allow to relocate on screen (does not honour gsetting dock-position) b) dock does not react to hotkeys (even though are set in gsettings) c) dock does not hide on lock screen (https://www.queryxchange.com/q/3_1085426/desktop-is-visible-is-visible-after-suspend/) d) dock does allow application launch, termination and some commands when machine in locked e) dock appears after resume from RAM f) dash button does not react on first mouse click when applications are open g) dock changes size if applications are open and a dot indicates the fact here are the Gnome settings: gsettings list-recursively org.gnome.shell.extensions.dash-to-dock org.gnome.shell.extensions.dash-to-dock click-action 'previews' org.gnome.shell.extensions.dash-to-dock preferred-monitor -1 org.gnome.shell.extensions.dash-to-dock force-straight-corner false org.gnome.shell.extensions.dash-to-dock show-show-apps-button true org.gnome.shell.extensions.dash-to-dock show-windows-preview true org.gnome.shell.extensions.dash-to-dock animation-time 0.20001 org.gnome.shell.extensions.dash-to-dock scroll-action 'switch-workspace' org.gnome.shell.extensions.dash-to-dock height-fraction 0.90002 org.gnome.shell.extensions.dash-to-dock activate-single-window true org.gnome.shell.extensions.dash-to-dock running-indicator-dominant-color false org.gnome.shell.extensions.dash-to-dock custom-theme-customize-running-dots true org.gnome.shell.extensions.dash-to-dock minimize-shift true org.gnome.shell.extensions.dash-to-dock show-apps-at-top true org.gnome.shell.extensions.dash-to-dock pressure-threshold 100.0 org.gnome.shell.extensions.dash-to-dock show-delay 0.25 org.gnome.shell.extensions.dash-to-dock icon-size-fixed true org.gnome.shell.extensions.dash-to-dock intellihide-mode 'ALL_WINDOWS' org.gnome.shell.extensions.dash-to-dock customize-alphas false org.gnome.shell.extensions.dash-to-dock apply-custom-theme false org.gnome.shell.extensions.dash-to-dock hot-keys true org.gnome.shell.extensions.dash-to-dock extend-height true org.gnome.shell.extensions.dash-to-dock background-color '#ff' org.gnome.shell.extensions.dash-to-dock shortcut-timeout 2.0 org.gnome.shell.extensions.dash-to-dock transparency-mode 'ADAPTIVE' org.gnome.shell.extensions.dash-to-dock multi-monitor false org.gnome.shell.extensions.dash-to-dock shortcut-text 'q' org.gnome.shell.extensions.dash-to-dock isolate-workspaces false org.gnome.shell.extensions.dash-to-dock max-alpha 0.80004 org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock hide-delay 0.20001 org.gnome.shell.extensions.dash-to-dock show-favorites true org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-color '#e95420' org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-width 0 org.gnome.shell.extensions.dash-to-dock app-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock app-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock isolate-monitors false org.gnome.shell.extensions.dash-to-dock app-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-hotkey-5 ['5']
[Desktop-packages] [Bug 1800308] Re: return from lock is extremely slow
** Package changed: ubuntu => gnome-shell (Ubuntu) ** Information type changed from Private Security to Public Security ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- 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/1800308 Title: return from lock is extremely slow Status in gnome-shell package in Ubuntu: Triaged Bug description: System Details -Computer- Processor : Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz Memory: 16329MB (7787MB used) Machine Type : Laptop Operating System : Ubuntu 18.10 -Display- Resolution: 1920x1080 pixels OpenGL Renderer : (Unknown) X11 Vendor: The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HDA Intel HDMI Audio Adapter : HDA-Intel - HDA Intel PCH -Input Devices- Lid Switch Power Button Sleep Button Power Button AT Translated Set 2 keyboard Video Bus AlpsPS/2 ALPS DualPoint Stick AlpsPS/2 ALPS DualPoint TouchPad Dell WMI hotkeys Laptop_Integrated_Webcam_HD: In HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 HDA Intel PCH Dock Mic HDA Intel PCH Dock Line Out HDA Intel PCH Front Headphone -SCSI Disks- ATA Origin Inception Whenever the system locks after closing the laptop lid for a period of time and I try to resurrect the screen is frozen not on the lock screen but on the desktop. Eventually this transitions to the laock screen but still freezes. I can move the mouse the entire time. Eventually after a period of time I can access the password screen and all is normal but total duration can be 2 minutes or more. In 18.04 I did not have this issue. I have marked it as a security vulnerability as if I close my lid and sensitive data was visible on screen opening the lid will show this instead of the lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800308/+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 1800320] Re: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-k
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1800320 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Sun Oct 28 00:14:27 2018 ErrorMessage: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 InstallationDate: Installed on 2018-10-27 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.6 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 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-340/+bug/1800320/+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 1800555] Re: Computer slow. Error reports appear.
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1800555 Title: Computer slow. Error reports appear. Status in xorg package in Ubuntu: New Bug description: Computer slow. Error reports appear. Says system is running on low graphics sometimes. Makes me log in most of the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Stopped WPA supplicant. [[0;32m OK [0m] Started Show Plymouth Boot Screen. Starting Hold until boot process finishes up... 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 Oct 29 17:37:27 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1] InstallationDate: Installed on 2016-09-11 (778 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard p6710f ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.07 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: 4CE0480TV4 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6710f dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 29 17:32:25 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 8 inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 9 inputLogitech USB Optical Mouse MOUSE, id 10 xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1800555/+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 1801028] Re: Virus bug on ubuntu 16.4 32bits
Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. Please visit https://answers.launchpad.net/ubuntu/+addquestion ** Information type changed from Private Security to Public ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1801028 Title: Virus bug on ubuntu 16.4 32bits Status in xorg package in Ubuntu: Invalid Bug description: Hello.Sorry but I'm French I'll do my best to explain. The Bug I'm reporting happened from a mail that I opened, I mean a kind of virus. It blow up my picture back screen and fix sometime the image in a way that I can't move it out. I'm trying actually to fight against it but I don't know enough to win.So I need help anyway. thank you. Oliver ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Nov 1 09:31:25 2018 DistUpgraded: 2017-10-22 20:28:39,732 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] G94 [GeForce 9600 GT] [1462:1270] InstallationDate: Installed on 2016-04-18 (926 days ago) InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) MachineType: Dell Inc. Vostro 410 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=011baf0e-1274-4ca0-9f7e-2929ae27e3fc ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-10-22 (374 days ago) dmi.bios.date: 06/20/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.3 dmi.board.name: 0J584C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.3:bd06/20/2008:svnDellInc.:pnVostro410:pvr:rvnDellInc.:rn0J584C:rvrA00:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Vostro 410 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Nov 1 09:26:52 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard KEYBOARD, id 8 inputUSB Optical MouseMOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1801028/+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 1800333] [NEW] Ubuntu dock not working properly
You have been subscribed to a public bug: Ubuntu 18.10 Linux mbpr13b 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Upgrade from Ubuntu 18.04, all updates applied Ubuntu dock has several issues (some reported elsewhere) a) dock does not allow to relocate on screen (does not honour gsetting dock-position) b) dock does not react to hotkeys (even though are set in gsettings) c) dock does not hide on lock screen (https://www.queryxchange.com/q/3_1085426/desktop-is-visible-is-visible-after-suspend/) d) dock does allow application launch, termination and some commands when machine in locked e) dock appears after resume from RAM f) dash button does not react on first mouse click when applications are open g) dock changes size if applications are open and a dot indicates the fact here are the Gnome settings: gsettings list-recursively org.gnome.shell.extensions.dash-to-dock org.gnome.shell.extensions.dash-to-dock click-action 'previews' org.gnome.shell.extensions.dash-to-dock preferred-monitor -1 org.gnome.shell.extensions.dash-to-dock force-straight-corner false org.gnome.shell.extensions.dash-to-dock show-show-apps-button true org.gnome.shell.extensions.dash-to-dock show-windows-preview true org.gnome.shell.extensions.dash-to-dock animation-time 0.20001 org.gnome.shell.extensions.dash-to-dock scroll-action 'switch-workspace' org.gnome.shell.extensions.dash-to-dock height-fraction 0.90002 org.gnome.shell.extensions.dash-to-dock activate-single-window true org.gnome.shell.extensions.dash-to-dock running-indicator-dominant-color false org.gnome.shell.extensions.dash-to-dock custom-theme-customize-running-dots true org.gnome.shell.extensions.dash-to-dock minimize-shift true org.gnome.shell.extensions.dash-to-dock show-apps-at-top true org.gnome.shell.extensions.dash-to-dock pressure-threshold 100.0 org.gnome.shell.extensions.dash-to-dock show-delay 0.25 org.gnome.shell.extensions.dash-to-dock icon-size-fixed true org.gnome.shell.extensions.dash-to-dock intellihide-mode 'ALL_WINDOWS' org.gnome.shell.extensions.dash-to-dock customize-alphas false org.gnome.shell.extensions.dash-to-dock apply-custom-theme false org.gnome.shell.extensions.dash-to-dock hot-keys true org.gnome.shell.extensions.dash-to-dock extend-height true org.gnome.shell.extensions.dash-to-dock background-color '#ff' org.gnome.shell.extensions.dash-to-dock shortcut-timeout 2.0 org.gnome.shell.extensions.dash-to-dock transparency-mode 'ADAPTIVE' org.gnome.shell.extensions.dash-to-dock multi-monitor false org.gnome.shell.extensions.dash-to-dock shortcut-text 'q' org.gnome.shell.extensions.dash-to-dock isolate-workspaces false org.gnome.shell.extensions.dash-to-dock max-alpha 0.80004 org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock hide-delay 0.20001 org.gnome.shell.extensions.dash-to-dock show-favorites true org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-color '#e95420' org.gnome.shell.extensions.dash-to-dock custom-theme-running-dots-border-width 0 org.gnome.shell.extensions.dash-to-dock app-hotkey-10 ['0'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock app-hotkey-1 ['1'] org.gnome.shell.extensions.dash-to-dock app-hotkey-2 ['2'] org.gnome.shell.extensions.dash-to-dock isolate-monitors false org.gnome.shell.extensions.dash-to-dock app-hotkey-4 ['4'] org.gnome.shell.extensions.dash-to-dock app-hotkey-5 ['5'] org.gnome.shell.extensions.dash-to-dock app-hotkey-6 ['6'] org.gnome.shell.extensions.dash-to-dock app-hotkey-3 ['3'] org.gnome.shell.extensions.dash-to-dock app-hotkey-8 ['8'] org.gnome.shell.extensions.dash-to-dock app-hotkey-9 ['9'] org.gnome.shell.extensions.dash-to-dock custom-theme-shrink true org.gnome.shell.extensions.dash-to-dock app-hotkey-7 ['7'] org.gnome.shell.extensions.dash-to-dock autohide true org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-7 ['7'] org.gnome.shell.extensions.dash-to-dock hotkeys-show-dock true org.gnome.shell.extensions.dash-to-dock autohide-in-fullscreen false org.gnome.shell.extensions.dash-to-dock dash-max-icon-size 22 org.gnome.shell.extensions.dash-to-dock background-opacity 0.80004 org.gnome.shell.extensions.dash-to-dock running-indicator-style 'DOTS' org.gnome.shell.extensions.dash-to-dock dock-position 'LEFT' org.gnome.shell.extensions.dash-to-dock middle-click-action 'launch'
[Desktop-packages] [Bug 1800963] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207898/+files/XorgLog.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
Re: [Desktop-packages] [Bug 856776] Re: Cannot declare itself as another username with CUPS server
*laughs* Indeed, I do not need this anymore. I've had time to graduate university (where CUPS was useful), move homes a bunch of times, change OSes, among other things. Have a good triage! On Thu, Nov 1, 2018 at 11:06 AM gf <856...@bugs.launchpad.net> wrote: > Hello Jonathan, > Thank you for submitting this feature/enhancement request for the cups > package. You made this request quite some time ago and Ubuntu has been > updated since then. > > Do you think this feature/enhancement is still needed or can we close > this bug report? > > Thank you again for helping make Ubuntu better. > G > [Ubuntu Bug Squad volunteer triager] > > ** Changed in: cups (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/856776 > > Title: > Cannot declare itself as another username with CUPS server > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/common-print-dialog-gtk/+bug/856776/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/856776 Title: Cannot declare itself as another username with CUPS server Status in Common Print Dialog: New Status in cups package in Ubuntu: Incomplete Bug description: Originally posted on http://askubuntu.com/questions/61095/use- different-username-on-cups-remote-printing : > I'm using CUPS to print on an enterprise network. The job gets submitted fine, but I need to submit it as another username. Now I'm `jon` but I need to send it as say `jonallard`. > > On the command line, one could print as such > > lp -U jonallard -d printer1 file.ext > > How do I customize the *username* part when using the GUI printing dialogs and the Printing system settings? > > It is possible that it isn't, in fact, possible to add this username to the Ubuntu print config. If so, where should I ask for an improvement?" Martin Owens -doctormo-@AskUbuntu suggested I add the username in the IPP URI directly. The printer address dialog won't let me do that. Is this a bug or is there some hidden place to put this username or should it be improved? ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: system-config-printer-gnome 1.3.1+20110222-0ubuntu16.3 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CupsErrorLog: Date: Thu Sep 22 16:17:38 2011 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) InterpreterPath: /usr/bin/python2.7 Lpstat: device for uprint-mono: ipp://cups.ncs.mcgill.ca:631/printers/mcgill_mono MachineType: LENOVO 427637U PackageArchitecture: all Papersize: letter PpdFiles: uprint-mono: Generic PCL Laser Printer ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=264a98b8-d582-4814-bb46-81adf856e638 ro splash vga=795 quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET44WW (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 427637U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET44WW(1.24):bd05/13/2011:svnLENOVO:pn427637U:pvrThinkPadW520:rvnLENOVO:rn427637U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 427637U dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/common-print-dialog-gtk/+bug/856776/+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 1796499] Re: Keyboard calculator button not working
seb128 I don't understand what that means, but I am certain a solution is being worked on. I think the importance should be higher. As Flatron commented in the askubuntu question, "How could they possible break the Calculator ? Of all things that may be broken this one should always work on any OS, no matter what... Imagine being a new person to (Ubuntu) Linux and finding that your calculator simply does not work with no error". -- 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/1796499 Title: Keyboard calculator button not working Status in gnome-settings-daemon package in Ubuntu: In Progress Bug description: The calculator app doesn't open when the calculator button on the keyboard is pressed. I'm using a Logitech K520 keyboard. I found this: https://askubuntu.com/questions/1031673/cannot-open-calculator-app- from-keyboard-calculator-button An out-of-the-box solution would be nice though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 18:17:47 2018 InstallationDate: Installed on 2018-09-29 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1796499/+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 1800963] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207897/+files/UdevDb.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Desktop-packages] [Bug 1800963] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207901/+files/xdpyinfo.txt ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Confirmed -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
[Desktop-packages] [Bug 1800963] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207899/+files/Xrandr.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Desktop-packages] [Bug 1800963] Re: Changing Primary DIsplay Flips Which Display Has The Dock
Could I try the 'nouveau' driver? To see if the same thing happens. -- Cristian Aravena Romero (caravena) ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
[Desktop-packages] [Bug 1800963] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207893/+files/ProcCpuinfo.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Desktop-packages] [Bug 1800963] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207890/+files/Lsusb.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Desktop-packages] [Bug 1800963] Re: Changing Primary DIsplay Flips Which Display Has The Dock
apport information ** Tags added: ubuntu ** Description changed: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True + --- + ProblemType: Bug + .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' + .proc.driver.nvidia.registry: Binary: "" + .proc.driver.nvidia.version: + NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 + GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) + ApportVersion: 2.20.9-0ubuntu7.4 + Architecture: amd64 + BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' + CompositorRunning: None + CurrentDesktop: ubuntu:GNOME + DistUpgraded: Fresh install + DistroCodename: bionic + DistroRelease: Ubuntu 18.04 + DistroVariant: ubuntu + DkmsStatus: + nvidia, 390.77, 4.15.0-29-generic, x86_64: installed + nvidia, 390.77, 4.15.0-38-generic, x86_64: installed + ExtraDebuggingInterest: Yes + GraphicsCard: + Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] + NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) +Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] + InstallationDate: Installed on 2018-10-31 (1 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + MachineType: ASUS All Series + NonfreeKernelModules: nvidia_modeset nvidia + Package: xorg-server (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 + Tags: bionic ubuntu + Uname: Linux 4.15.0-38-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 08/18/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 2103 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: Z87-PRO + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.family: ASUS MB + dmi.product.name: All Series + dmi.product.version: System Version + dmi.sys.vendor: ASUS + version.compiz: compiz N/A + version.libdrm2: libdrm2 2.4.91-2 + version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 + version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 + version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A + version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Attachment added: ".proc.driver.nvidia.params.txt"
[Desktop-packages] [Bug 1800963] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207887/+files/CurrentDmesg.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Desktop-packages] [Bug 1800963] nvidia-settings.txt
apport information ** Attachment added: "nvidia-settings.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207900/+files/nvidia-settings.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-*
[Desktop-packages] [Bug 1800963] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207891/+files/MonitorsUser.xml.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers:
[Desktop-packages] [Bug 1800963] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207895/+files/ProcInterrupts.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-*
[Desktop-packages] [Bug 1800963] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207888/+files/DpkgLog.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Desktop-packages] [Bug 1800963] NvidiaBugReportLog.txt
apport information ** Attachment added: "NvidiaBugReportLog.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207892/+files/NvidiaBugReportLog.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers:
[Desktop-packages] [Bug 1800963] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207894/+files/ProcCpuinfoMinimal.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers:
[Desktop-packages] [Bug 1800963] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207889/+files/Lspci.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Desktop-packages] [Bug 1800963] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1800963/+attachment/5207896/+files/ProcModules.txt -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.77 Tue Jul 10 18:28:52 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: nvidia, 390.77, 4.15.0-29-generic, x86_64: installed nvidia, 390.77, 4.15.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] NVIDIA Corporation GK104 [GeForce GTX 760] [10de:1187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK104 [GeForce GTX 760] [1043:8472] InstallationDate: Installed on 2018-10-31 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUS All Series NonfreeKernelModules: nvidia_modeset nvidia Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=f29793fe-db23-4afe-a808-426f9bc10fda ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 08/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
[Desktop-packages] [Bug 1801110] [NEW] gnome-shell crashes ending session upon DP monitor switch-away
Public bug reported: I have a DisplayPort switching arrangement consisting of a 4way DP switch that switches 2, daisy-chained DP monitors. Many times, but not always, when switching the displays away from this host, gnome-shell crashes. Later, switching back, I'm presented with the gdm login screen, previous session is gone. journal trace. Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142617.735610:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142617.828123:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142617.829899:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! Oct 31 14:26:17 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142617.844313:ERROR:gl_surface_presentation_helper.cc(237)] GetVSyncParametersIfAvailable() failed! Oct 31 14:26:19 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142619.936305:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=0.999619 s, l Oct 31 14:26:20 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142620.866151:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00119 s, la Oct 31 14:26:21 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142621.876094:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00083 s, la Oct 31 14:26:22 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142622.866910:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00015 s, la Oct 31 14:26:23 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142623.866649:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=0.999805 s, l Oct 31 14:26:24 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142624.866857:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00075 s, la Oct 31 14:26:25 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142625.867939:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=1.00054 s, la Oct 31 14:26:26 u24b6-skull org.gnome.Shell.desktop[16220]: [16887:16887:1031/142626.867620:ERROR:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=0.999784 s, l Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Backtrace: Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 0: /usr/bin/Xwayland (OsLookupColor+0x139) [0x561135c42c39] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7fd818e74e1f] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 2: /usr/bin/Xwayland (present_extension_init+0xce6) [0x561135bab416] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 3: /usr/bin/Xwayland (glamor_egl_fd_from_pixmap+0x390) [0x561135aed380] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 4: /usr/bin/Xwayland (glamor_egl_fd_from_pixmap+0x533) [0x561135aed6f3] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 5: /usr/bin/Xwayland (TimerSet+0x180) [0x561135c3c4b0] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 6: /usr/bin/Xwayland (TimerSet+0x1f8) [0x561135c3c578] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 7: /usr/bin/Xwayland (WaitForSomething+0x277) [0x561135c3c657] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 8: /usr/bin/Xwayland (SendErrorToClient+0x10c) [0x561135c0c95c] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 9: /usr/bin/Xwayland (InitFonts+0x3b6) [0x561135c10b36] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7fd818c9c09b] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) 11: /usr/bin/Xwayland (_start+0x2a) [0x561135ae21ea] Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Segmentation fault at address 0x0 Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: Fatal server error: Oct 31 14:26:27 u24b6-skull org.gnome.Shell.desktop[16220]: (EE) Caught signal 11 (Segmentation fault). Server aborting ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1801110 Title: gnome-shell crashes ending session upon DP
[Desktop-packages] [Bug 1801103] [NEW] Kubuntu driver manager fails to install nvidia-prime on hybrid systems and that makes system unusable for unexperienced users
You have been subscribed to a public bug: Ignoring the fact that only nvidia-340 drivers were suggested when 390 is available, with a completely fresh install after using Kubuntu driver manager system does not show GUI on the next boot because NVIDIA drivers cannot work without nvidia-prime on hybrid systems. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: kubuntu-driver-manager 15.10ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 1 16:44:54 2018 InstallationDate: Installed on 2018-11-01 (0 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: kubuntu-driver-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- Kubuntu driver manager fails to install nvidia-prime on hybrid systems and that makes system unusable for unexperienced users https://bugs.launchpad.net/bugs/1801103 You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. -- 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 1778332] Re: Apparmor Permission Denied (apparmor="DENIED")
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1778332 Title: Apparmor Permission Denied (apparmor="DENIED") Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: I try to launch the system monitor but nothing show up. journalctl -f Result: Jun 23 19:04:24 laptop-hostname audit[8109]: AVC apparmor="DENIED" operation="capable" profile="snap-update-ns.gnome-system-monitor" pid=8109 comm="3" capability=6 capname="setgid" Jun 23 19:04:24 laptop-hostname kernel: audit: type=1400 audit(1529751864.744:47): apparmor="DENIED" operation="capable" profile="snap-update-ns.gnome-system-monitor" pid=8109 comm="3" capability=6 capname="setgid" Jun 23 19:04:24 laptop-hostname gnome-system-monitor_gnome-system-monitor.desktop[8097]: cannot update snap namespace: cannot drop supplementary groups: operation not permitted Jun 23 19:04:24 laptop-hostname gnome-system-monitor_gnome-system-monitor.desktop[8097]: snap-update-ns failed with code 1: File exists Jun 23 19:04:28 laptop-hostname pkexec[8128]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) /var/log/syslog Result: Jun 23 19:03:17 laptop-hostname kernel: [ 433.266715] audit: type=1400 audit(1529751797.796:42): apparmor="DENIED" operation="mount" info="failed srcname match" error=-13 profile="snap-update-ns.gnome-system-monitor" name="/snap/gnome-system-monitor/45/gnome-platform/" pid=7471 comm="3" srcname="/snap/gnome-3-26-1604/64/" flags="rw, bind" Jun 23 19:03:17 laptop-hostname gnome-system-monitor_gnome-system-monitor.desktop[7456]: 2018/06/23 19:03:17.799121 main.go:192: cannot change mount namespace of snap "gnome-system-monitor" according to change mount (/snap/gnome-3-26-1604/64 /snap/gnome-system-monitor/45/gnome-platform none bind,ro 0 0): permission denied Jun 23 19:03:17 laptop-hostname gnome-system-monitor_gnome-system-monitor.desktop[7456]: 2018/06/23 19:03:17.833637 main.go:192: cannot change mount namespace of snap "gnome-system-monitor" according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): permission denied Jun 23 19:03:17 laptop-hostname kernel: [ 433.301209] audit: type=1400 audit(1529751797.828:43): apparmor="DENIED" operation="mount" info="failed srcname match" error=-13 profile="snap-update-ns.gnome-system-monitor" name="/usr/local/share/fonts/" pid=7471 comm="3" flags="ro, remount, bind" Jun 23 19:03:17 laptop-hostname gnome-system-monitor_gnome-system-monitor.desktop[7456]: 2018/06/23 19:03:17.835300 main.go:192: cannot change mount namespace of snap "gnome-system-monitor" according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): permission denied Jun 23 19:03:17 laptop-hostname gnome-system-monitor_gnome-system-monitor.desktop[7456]: 2018/06/23 19:03:17.838094 main.go:192: cannot change mount namespace of snap "gnome-system-monitor" according to change mount (/var/lib/snapd/hostfs/var/cache/fontconfig /var/cache/fontconfig none bind,ro 0 0): permission denied Jun 23 19:03:17 laptop-hostname kernel: [ 433.302850] audit: type=1400 audit(1529751797.832:44): apparmor="DENIED" operation="mount" info="failed srcname match" error=-13 profile="snap-update-ns.gnome-system-monitor" name="/usr/share/fonts/" pid=7471 comm="3" flags="ro, remount, bind" Jun 23 19:03:17 laptop-hostname kernel: [ 433.305652] audit: type=1400 audit(1529751797.832:45): apparmor="DENIED" operation="mount" info="failed srcname match" error=-13 profile="snap-update-ns.gnome-system-monitor" name="/var/cache/fontconfig/" pid=7471 comm="3" flags="ro, remount, bind" Jun 23 19:03:17 laptop-hostname kernel: [ 433.336540] audit: type=1400 audit(1529751797.864:46): apparmor="DENIED" operation="capable" profile="snap-update-ns.gnome-system-monitor" pid=7478 comm="3" capability=6 capname="setgid" Jun 23 19:03:17 laptop-hostname gnome-system-monitor_gnome-system-monitor.desktop[7456]: cannot update snap namespace: cannot drop supplementary groups: operation not permitted Jun 23 19:03:17 laptop-hostname gnome-system-monitor_gnome-system-monitor.desktop[7456]: snap-update-ns failed with code 1 Jun 23 19:03:18 laptop-hostname PackageKit: resolve transaction /260_bebcecdc from uid 1000 finished with success after 610ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1778332/+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 1801103] Re: Kubuntu driver manager fails to install nvidia-prime on hybrid systems and that makes system unusable for unexperienced users
The driver manager simply installs the nvidia driver/meta package for the compatible selected driver. If prime should be a dependency of that, then is really an issue with that package. ** Package changed: kubuntu-driver-manager (Ubuntu) => nvidia-graphics- drivers-340 (Ubuntu) -- 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/1801103 Title: Kubuntu driver manager fails to install nvidia-prime on hybrid systems and that makes system unusable for unexperienced users Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Ignoring the fact that only nvidia-340 drivers were suggested when 390 is available, with a completely fresh install after using Kubuntu driver manager system does not show GUI on the next boot because NVIDIA drivers cannot work without nvidia-prime on hybrid systems. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: kubuntu-driver-manager 15.10ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 1 16:44:54 2018 InstallationDate: Installed on 2018-11-01 (0 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: kubuntu-driver-manager 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-340/+bug/1801103/+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 1800785] Re: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess new libgs9-common package pre-installation script gab den Fehler-Ausgang
Great, closing this bug. Thanks! ** Changed in: ghostscript (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1800785 Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess new libgs9-common package pre- installation script gab den Fehler-Ausgangsstatus 1 zurück Status in ghostscript package in Ubuntu: Invalid Bug description: ? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: ghostscript-x:amd64: Install ghostscript:amd64: Install libgs9:amd64: Install libgs9-common:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 31 09:19:21 2018 ErrorMessage: Unterprozess new libgs9-common package pre-installation script gab den Fehler-Ausgangsstatus 1 zurück InstallationDate: Installed on 2018-01-29 (274 days ago) InstallationMedia: budgie-remix 16.04.3 "Budgie-remix" - Release amd64 (20170804) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ghostscript Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess new libgs9-common package pre-installation script gab den Fehler-Ausgangsstatus 1 zurück UpgradeStatus: Upgraded to bionic on 2018-10-25 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1800785/+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 1800963] Re: Changing Primary DIsplay Flips Which Display Has The Dock
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect -p xorg-server 1800963 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1800963 Title: Changing Primary DIsplay Flips Which Display Has The Dock Status in gnome-control-center package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: On a fresh install from at least Ubuntu 17.04 up to 18.10, when I change Settings->Dock->Show on to a specific monitor on a dual monitor setup, this setting gets flipped if I change the primary display in Settings->Devices->Displays->Primary Display. For Example I have Monitor A and Monitor B After a fresh install Monitor A is primary with title bar, clock, etc. and the dock. If I change the dock to Show on Monitor B it moves as desired. But when I change Primary Display to Monitor B also, the dock immediately goes to Monitor A again. When I check the Show on setting it still displays Monitor B but it's actually on Monitor A. Selecting Monitor A will move the dock to Monitor B. Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-10-31 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1800963/+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
Re: [Desktop-packages] [Bug 1800785] Re: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess new libgs9-common package pre-installation script gab den Fehler-Aus
Thank you very much for your help. Yes, I tried to fix the problem with my printer and it works, but only one day. I am very pleased, that I can update again and my printers works too. On 31.10.18 12:15, Marc Deslauriers wrote: > Here's the error log: > > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/ps_gray.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/ps_cmyk.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/gray_to_k.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/default_gray.icc' not owned by > package 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/lab.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/srgb.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/default_cmyk.icc' not owned by > package 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/ps_rgb.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/sgray.icc' not owned by package > 'libgs9-common:all' > dpkg-maintscript-helper: error: file > '/usr/share/ghostscript/9.25/iccprofiles/default_rgb.icc' not owned by > package 'libgs9-common:all' > > Did you manually copy files into the > /usr/share/ghostscript/9.25/iccprofiles directory to try and fix an > upgrade issue? > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1800785 Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess new libgs9-common package pre- installation script gab den Fehler-Ausgangsstatus 1 zurück Status in ghostscript package in Ubuntu: Incomplete Bug description: ? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 AptOrdering: ghostscript-x:amd64: Install ghostscript:amd64: Install libgs9:amd64: Install libgs9-common:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Oct 31 09:19:21 2018 ErrorMessage: Unterprozess new libgs9-common package pre-installation script gab den Fehler-Ausgangsstatus 1 zurück InstallationDate: Installed on 2018-01-29 (274 days ago) InstallationMedia: budgie-remix 16.04.3 "Budgie-remix" - Release amd64 (20170804) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ghostscript Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: Unterprozess new libgs9-common package pre-installation script gab den Fehler-Ausgangsstatus 1 zurück UpgradeStatus: Upgraded to bionic on 2018-10-25 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1800785/+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 1795760] Re: Xwayland crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1745799 *** https://bugs.launchpad.net/bugs/1745799 As stated above this bug report is not a duplicate and contains working code to solve the bug. Using this code doesn ot give any risk to the main stream of the code, it only handles an exception. I thought it might be a pleasure to get a solution for a problem. PLease do something with it. -- 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/1795760 Title: Xwayland crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: New Bug description: This bug contains a crash related to bug 1795089. Local code is used for libmutter, to solve bug 1790525 and to display buffersizes at module setup_spans at cogl/cogl/cogl-texture-2d-sliced.c and at module allocate_from_bitmap at cogl/cogl/driver/gl/cogl-texture-2d-gl.c . Dual monitor is used without a monitors.xml files usable by gdm3 with wayland. After logging in using ubuntu with wayland both screens are shown, but crash after a short time without user doing anything. At syslog we see the displayed buffersizes which are too large before the crash: Oct 2 23:57:42 Gert2 gnome-shell[2636]: GK_allocate_from_bitmap 2560 1024 Oct 2 23:57:42 Gert2 gnome-shell[2636]: GK_cogl_set_error Failed to create texture 2d due to size/format constraints Oct 2 23:57:42 Gert2 gnome-shell[2636]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xwayland 2:1.20.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic i686 ApportVersion: 2.20.10-0ubuntu11 Architecture: i386 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 2 23:57:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [1028:01c2] Subsystem: Dell Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [1028:01c2] MachineType: Dell Inc. Latitude D620 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4ccc6cca-be3d-4471-9677-1012a53ebfd7 ro splash quiet vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () _start () Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/11/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0TD761 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd04/11/2006:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0TD761:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D620 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1795760/+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 322210] Re: [needs-packaging] PPD for Dymo LabelWriter 400 not complete
Hello Ben, Thank you for submitting this feature/enhancement request for the hplip package. You made this request quite some time ago and Ubuntu has been updated since then. Do you think this feature/enhancement is still needed or can we close this bug report? Thank you again for helping make Ubuntu better. G [Ubuntu Bug Squad volunteer triager] ** Changed in: cups (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/322210 Title: [needs-packaging] PPD for Dymo LabelWriter 400 not complete Status in cups package in Ubuntu: Incomplete Bug description: Binary package hint: cups Release: 8.10 Cups package version: 1.3.9-2ubuntu6.1 I installed Dymo LabelWriter 400 with the Multi-Purpose labels 11354. I chose the only available driver: Dymo Label Printer, 1.3 Problem: I could not set the correct label size as the Multi-Purpose labels are missing from the ppd-file. The result is that I get printouts which do not fit the labels. Solution: I downloaded the driver from the manufacturer and extracted the lines for the Multi-Purpose labels from their ppd-file. drivers page: https://global.dymo.com/enUS/RNW/RNW.html?pg=std_adp.php_faqid=101 driver file: http://www.dymo.com/media/Software/dymo-cups-drivers-1.0.3.tar.gz What should be done is that the ppd-file in cups should be updated with all the labels in the manufacturers ppd. Depending on their license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/322210/+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 343801] Re: cupsd.conf defaults need to allow reprint of jobs
Sorry, I meant: ".. with the *cups* package." ** Changed in: cups (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/343801 Title: cupsd.conf defaults need to allow reprint of jobs Status in CUPS: New Status in cups package in Ubuntu: Incomplete Status in system-config-printer package in Ubuntu: Fix Released Bug description: Binary package hint: cups if you see the screen shots in this thread http://ubuntuforums.org/showthread.php?t=820916 you will see what im talking about i think it would be much nicer if /etc/cups/cupsd.conf contained these 2 lines by default # preserve last 50 print jobs PreserveJobFiles Yes MaxJobs 50 you can make max jobs higher but the "PreserveJobFiles Yes" is important as it allows users to reprint jobs that fail due to various reasons. its handy and other distros are using this as a default option To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/343801/+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 322210] Re: [needs-packaging] PPD for Dymo LabelWriter 400 not complete
Sorry, I meant: ".. with the *cups* package." :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/322210 Title: [needs-packaging] PPD for Dymo LabelWriter 400 not complete Status in cups package in Ubuntu: Incomplete Bug description: Binary package hint: cups Release: 8.10 Cups package version: 1.3.9-2ubuntu6.1 I installed Dymo LabelWriter 400 with the Multi-Purpose labels 11354. I chose the only available driver: Dymo Label Printer, 1.3 Problem: I could not set the correct label size as the Multi-Purpose labels are missing from the ppd-file. The result is that I get printouts which do not fit the labels. Solution: I downloaded the driver from the manufacturer and extracted the lines for the Multi-Purpose labels from their ppd-file. drivers page: https://global.dymo.com/enUS/RNW/RNW.html?pg=std_adp.php_faqid=101 driver file: http://www.dymo.com/media/Software/dymo-cups-drivers-1.0.3.tar.gz What should be done is that the ppd-file in cups should be updated with all the labels in the manufacturers ppd. Depending on their license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/322210/+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 856776] Re: Cannot declare itself as another username with CUPS server
Hello Jonathan, Thank you for submitting this feature/enhancement request for the cups package. You made this request quite some time ago and Ubuntu has been updated since then. Do you think this feature/enhancement is still needed or can we close this bug report? Thank you again for helping make Ubuntu better. G [Ubuntu Bug Squad volunteer triager] ** Changed in: cups (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/856776 Title: Cannot declare itself as another username with CUPS server Status in Common Print Dialog: New Status in cups package in Ubuntu: Incomplete Bug description: Originally posted on http://askubuntu.com/questions/61095/use- different-username-on-cups-remote-printing : > I'm using CUPS to print on an enterprise network. The job gets submitted fine, but I need to submit it as another username. Now I'm `jon` but I need to send it as say `jonallard`. > > On the command line, one could print as such > > lp -U jonallard -d printer1 file.ext > > How do I customize the *username* part when using the GUI printing dialogs and the Printing system settings? > > It is possible that it isn't, in fact, possible to add this username to the Ubuntu print config. If so, where should I ask for an improvement?" Martin Owens -doctormo-@AskUbuntu suggested I add the username in the IPP URI directly. The printer address dialog won't let me do that. Is this a bug or is there some hidden place to put this username or should it be improved? ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: system-config-printer-gnome 1.3.1+20110222-0ubuntu16.3 ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CupsErrorLog: Date: Thu Sep 22 16:17:38 2011 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) InterpreterPath: /usr/bin/python2.7 Lpstat: device for uprint-mono: ipp://cups.ncs.mcgill.ca:631/printers/mcgill_mono MachineType: LENOVO 427637U PackageArchitecture: all Papersize: letter PpdFiles: uprint-mono: Generic PCL Laser Printer ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic root=UUID=264a98b8-d582-4814-bb46-81adf856e638 ro splash vga=795 quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8BET44WW (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 427637U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8BET44WW(1.24):bd05/13/2011:svnLENOVO:pn427637U:pvrThinkPadW520:rvnLENOVO:rn427637U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 427637U dmi.product.version: ThinkPad W520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/common-print-dialog-gtk/+bug/856776/+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
