[Desktop-packages] [Bug 1970060] [NEW] Firefox Snap Element Desktop URL Handler not working
Public bug reported: Summary: The Firefox snap version seems to be unable to open application URIs. Steps to reproduce the issue: - Have Element Desktop installed https://element.io/get-started - Go to https://matrix.to/#/#element-dev:matrix.org - Select Element Desktop - Click Continue Expected: - Element opens the room What happens: - Can only select „System Handler“ - Confirming to use „System Handler“ does nothing OS version: Ubuntu 22.04 LTS Snap version: 99.0.1-1 Workaround: Remove the snap version; install from Mozilla PPA ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1970060 Title: Firefox Snap Element Desktop URL Handler not working Status in firefox package in Ubuntu: New Bug description: Summary: The Firefox snap version seems to be unable to open application URIs. Steps to reproduce the issue: - Have Element Desktop installed https://element.io/get-started - Go to https://matrix.to/#/#element-dev:matrix.org - Select Element Desktop - Click Continue Expected: - Element opens the room What happens: - Can only select „System Handler“ - Confirming to use „System Handler“ does nothing OS version: Ubuntu 22.04 LTS Snap version: 99.0.1-1 Workaround: Remove the snap version; install from Mozilla PPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1970060/+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 1846944] Re: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta
I also found out that there has been a pull request in the package https://github.com/ubuntu/gnome-shell-extension- appindicator/pull/231/files trying to fix this. That didn't work. Related GitHub issue: https://github.com/ubuntu/gnome-shell-extension- appindicator/issues/235 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1846944 Title: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: When running the Nextcloud Client (flatpak or PPA) in Eoan Beta, its app indicator icon is never displayed in the notification area. Other apps sch as Steam and Skype have their indicator icons displayed fine. Output from the command line when running the flatpak produces the following error: Qt: Session management error: None of the authentication protocols specified are supported I can duplicate this issue 100% of the time. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-appindicator 30-1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 13:35:44 2019 InstallationDate: Installed on 2019-09-23 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1846944/+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 1846944] Re: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta
Same problem here running Ubuntu 20.04.1. > I think this is a Wayland related issue. I am using X.org. The workaround mentioned by Xianglong Kong does not work :/ I am using the Nextcloud client, too but it already is in the startup applications list. TopIcons Plus works for me. ** Bug watch added: github.com/ubuntu/gnome-shell-extension-appindicator/issues #235 https://github.com/ubuntu/gnome-shell-extension-appindicator/issues/235 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1846944 Title: Nextcloud client app indicator icon not visible in 19.10 Eoan Beta Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: When running the Nextcloud Client (flatpak or PPA) in Eoan Beta, its app indicator icon is never displayed in the notification area. Other apps sch as Steam and Skype have their indicator icons displayed fine. Output from the command line when running the flatpak produces the following error: Qt: Session management error: None of the authentication protocols specified are supported I can duplicate this issue 100% of the time. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-appindicator 30-1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 13:35:44 2019 InstallationDate: Installed on 2019-09-23 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to eoan on 2019-09-27 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1846944/+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 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
Present on current 20.04 dev release with vanilla GNOME. While this bug doesn't affect any functionality is shows me every day a broken UI. That reduces the fun using Ubuntu / snaps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-extra in Ubuntu. https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+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 1848011] Re: Samba share connection only works once
> [Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] Then let me write a comment. This issue is still valid. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1848011 Title: Samba share connection only works once Status in nautilus package in Ubuntu: Expired Bug description: Summary === I'm only able to connect to a samba share once. Steps to reproduce === * Open a samba network share via Nautilus. * Enter credentials, check "forget immediately" * Share mounted * Disconnect (or wait some time) * Try to open the same share again Expected behaviour === * Credentials pop-up * Enter credentials * Share mounted Actual behaviour === * Mouse pointer turns into spinner * After some minutes the credentials dialogue appears * I enter the correct credentials * Mouse pointer turns into spinner * ... Additional info === lsb_release Description: Ubuntu 19.04 Release: 19.04 kernel 5.0.0-31-generic ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 14:15:43 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'158' b'org.gnome.nautilus.window-state' b'initial-size' b'(963, 662)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2018-11-10 (337 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-18 (179 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1848011/+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 1735981] Re: Huawei ME936 mobile broadband can't connect
Works with Philipp Hufnagl's workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1735981 Title: Huawei ME936 mobile broadband can't connect Status in modemmanager package in Ubuntu: Confirmed Bug description: Hi, I have an Acer Travelmate P648 with a Huawei ME936 internal USB mobile broadband card, and can't connect. This didn't work in 17.04, and still does not work in 17.10. The USB device is successfully connected, ModemManager gets as far as "Simple connect state (8/8): All done" During the setup ModemManager complains with "Couldn't find associated cdc-wdm port for 'net/wwp0s20f0u9c2'" DHCP tries to get a configuration, but " dhcp4 (wwp0s20f0u9c2): request timed out". IP6 is set to "automatically" in the network settings for this configuration. and finally connection fails with "device (ttyUSB0): state change: ip-config -> failed (reason 'ip-config-unavailable', internal state 'managed')" I checked that there are enough credits left in my account with the provider. Any ideas what else to check ? Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: modemmanager 1.6.8-1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 11:27:49 2017 InstallationDate: Installed on 2017-04-24 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: modemmanager UpgradeStatus: Upgraded to artful on 2017-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735981/+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 1848011] Re: Samba share connection only works once
Thanks for the fast response. > Could you get a 'journalctl -b 0' log after getting the issue? When the connection fails these lines show up: Okt 14 16:18:11 mweimann systemd-resolved[1165]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Okt 14 16:18:11 mweimann systemd-resolved[1165]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Okt 14 16:18:11 mweimann systemd-resolved[1165]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. > When you say 'disconnect' do you mean you software unmount it? or turn off the server/disconect the cable? Here I mean clicking the unmount button for the network connection in nautilus. > do you get the same issue using gio mount? I hope I did it right (anonymized paths / user name): gio mount smb://username@server.intern/share mountpoint After a while it asks me for "Password required for share". Then I have to enter domain and password. After another while it asks the same question again. Same journal output as above occurs: Okt 14 16:28:55 mweimann systemd-resolved[1165]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Okt 14 16:28:55 mweimann systemd-resolved[1165]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Okt 14 16:28:55 mweimann systemd-resolved[1165]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1848011 Title: Samba share connection only works once Status in nautilus package in Ubuntu: Incomplete Bug description: Summary === I'm only able to connect to a samba share once. Steps to reproduce === * Open a samba network share via Nautilus. * Enter credentials, check "forget immediately" * Share mounted * Disconnect (or wait some time) * Try to open the same share again Expected behaviour === * Credentials pop-up * Enter credentials * Share mounted Actual behaviour === * Mouse pointer turns into spinner * After some minutes the credentials dialogue appears * I enter the correct credentials * Mouse pointer turns into spinner * ... Additional info === lsb_release Description: Ubuntu 19.04 Release: 19.04 kernel 5.0.0-31-generic ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 14:15:43 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'158' b'org.gnome.nautilus.window-state' b'initial-size' b'(963, 662)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2018-11-10 (337 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-18 (179 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1848011/+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 1848011] [NEW] Samba share connection only works once
Public bug reported: Summary === I'm only able to connect to a samba share once. Steps to reproduce === * Open a samba network share via Nautilus. * Enter credentials, check "forget immediately" * Share mounted * Disconnect (or wait some time) * Try to open the same share again Expected behaviour === * Credentials pop-up * Enter credentials * Share mounted Actual behaviour === * Mouse pointer turns into spinner * After some minutes the credentials dialogue appears * I enter the correct credentials * Mouse pointer turns into spinner * ... Additional info === lsb_release Description:Ubuntu 19.04 Release:19.04 kernel 5.0.0-31-generic ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 14:15:43 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'158' b'org.gnome.nautilus.window-state' b'initial-size' b'(963, 662)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2018-11-10 (337 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-18 (179 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1848011 Title: Samba share connection only works once Status in nautilus package in Ubuntu: New Bug description: Summary === I'm only able to connect to a samba share once. Steps to reproduce === * Open a samba network share via Nautilus. * Enter credentials, check "forget immediately" * Share mounted * Disconnect (or wait some time) * Try to open the same share again Expected behaviour === * Credentials pop-up * Enter credentials * Share mounted Actual behaviour === * Mouse pointer turns into spinner * After some minutes the credentials dialogue appears * I enter the correct credentials * Mouse pointer turns into spinner * ... Additional info === lsb_release Description: Ubuntu 19.04 Release: 19.04 kernel 5.0.0-31-generic ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 14:15:43 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'158' b'org.gnome.nautilus.window-state' b'initial-size' b'(963, 662)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2018-11-10 (337 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-18 (179 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1848011/+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 1848011] Re: Samba share connection only works once
If I can provide any further info to solve this issue please let me know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1848011 Title: Samba share connection only works once Status in nautilus package in Ubuntu: New Bug description: Summary === I'm only able to connect to a samba share once. Steps to reproduce === * Open a samba network share via Nautilus. * Enter credentials, check "forget immediately" * Share mounted * Disconnect (or wait some time) * Try to open the same share again Expected behaviour === * Credentials pop-up * Enter credentials * Share mounted Actual behaviour === * Mouse pointer turns into spinner * After some minutes the credentials dialogue appears * I enter the correct credentials * Mouse pointer turns into spinner * ... Additional info === lsb_release Description: Ubuntu 19.04 Release: 19.04 kernel 5.0.0-31-generic ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 14:15:43 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'158' b'org.gnome.nautilus.window-state' b'initial-size' b'(963, 662)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2018-11-10 (337 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-18 (179 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1848011/+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 1334329] Re: Sound input settings not saved
I also have kind of that problem on Ubuntu 18.10. I don't want to have sound. So I mute every device. After a re boot the sound is turned back on again. It's a laptop in a dock. The system detects multiple sound devices. Internal speakers and dock output. -- 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/1334329 Title: Sound input settings not saved Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: When attempting to set my preferred sound input device, simply leaving sound preferences and going back to sound preferences, and selecting input, causes the default SPDIF to be selected again, and not the internal microphone I preferred. I made a video to demonstrate what I mean by this here: http://youtu.be/9Q9EQvLl_rA 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center I really don't know. It's just the sound preferences. 3) What you expected to happen For my selected sound input to be saved. 4) What happened instead Keeps defaulting to the top sound input ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: brandon 23953 F pulseaudio /dev/snd/controlC0: brandon 23953 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 25 11:20:14 2014 InstallationDate: Installed on 2014-04-26 (60 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Caicos HDMI Audio [Radeon HD 6400 Series] - HDA ATI HDMI Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: None of the above Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/12 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP81.88Z.0047.B27.1201241646 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-94245A3940C91C80 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro8,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-94245A3940C91C80 dmi.modalias: dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80: dmi.product.name: MacBookPro8,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1334329/+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 1765363] Re: prime-select intel is not powering off the nvidia card
This still happens after the 18.04.2 update. My card is a MX150. I have to power off the card by bbswitch every time I boot my laptop. -- 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/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I observed the same behaviour as Adrian S.. Selecting Intel keeps the Nvidia card powered and the fan spinning. Installing and using bbswitch manually works. I can't make it working powering off the card at boot time :( Therefore I have to do it manually every time I boot my notebook. MX150, Ubuntu 18.04.2 -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 209513] Re: After upgrade, "Update standard folders to current language" threatens to rename your home folder
See my post above. This happens since I removed the unused (I thought) "Desktop" directory in my home. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/209513 Title: After upgrade, "Update standard folders to current language" threatens to rename your home folder Status in xdg-user-dirs package in Ubuntu: Confirmed Bug description: Occurs during: * Ubuntu Gutsy upgrade to Hardy beta * Ubuntu 8.04.1 routine updates * Ubuntu 8.04.1 upgrade to Intrepid beta After upgrading, this dialog appears: Update standard folders to current language? You have logged in in a new language. You can automatically update the names of some standard folders in your home folder to match this language. The update would change the following folders: Current folder name: New folder name: /home/jamie /home/jamie/Videos Note that existing content will not be moved. WTF? (My home directory _is_ /home/jamie). What is this trying to do? Will it rename my home directory? Or is it just updating default directory where Nautilus searches? Or where downloaded files are saved?? (There's no Help button, btw.) The only sane thing is to say "No, thanks" (i.e. "Keep old names"). Perhaps that's the wrong answer, but the dialog text isn't clear about what this change does, so I'd be foolish to say yes. Either (1) this shouldn't appear and show those paths, it's a bug, or (2) this dialog is correct, but the text should be better at saying that it's safe and merely changes default paths of no great consequence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/209513/+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 209513] Re: After upgrade, "Update standard folders to current language" threatens to rename your home folder
As of today Ubuntu also asks me to rename my home :/ ** Attachment added: "home_rename.png" https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/209513/+attachment/5218073/+files/home_rename.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/209513 Title: After upgrade, "Update standard folders to current language" threatens to rename your home folder Status in xdg-user-dirs package in Ubuntu: Confirmed Bug description: Occurs during: * Ubuntu Gutsy upgrade to Hardy beta * Ubuntu 8.04.1 routine updates * Ubuntu 8.04.1 upgrade to Intrepid beta After upgrading, this dialog appears: Update standard folders to current language? You have logged in in a new language. You can automatically update the names of some standard folders in your home folder to match this language. The update would change the following folders: Current folder name: New folder name: /home/jamie /home/jamie/Videos Note that existing content will not be moved. WTF? (My home directory _is_ /home/jamie). What is this trying to do? Will it rename my home directory? Or is it just updating default directory where Nautilus searches? Or where downloaded files are saved?? (There's no Help button, btw.) The only sane thing is to say "No, thanks" (i.e. "Keep old names"). Perhaps that's the wrong answer, but the dialog text isn't clear about what this change does, so I'd be foolish to say yes. Either (1) this shouldn't appear and show those paths, it's a bug, or (2) this dialog is correct, but the text should be better at saying that it's safe and merely changes default paths of no great consequence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/209513/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
For me the power management isn't working, too. The fan is always running and my notebook is getting hot. I'm using Ubuntu 18.04 and installed the default nvidia driver 390. My machine is an ASUS UX331UN with an nvidia mx150. Currently my workaround is to install bbswitch and turn the nvidia graphics on/off with that by hand :/ -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
** Attachment added: "My gpu-manager log file" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5211042/+files/gpu-manager.log -- 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/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1798999] Re: firefox windows are black in Ubuntu 18.10
@Chronon thanks for your reply. My report has been closed as duplicate: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1799483 :( -- 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/1798999 Title: firefox windows are black in Ubuntu 18.10 Status in firefox package in Ubuntu: Fix Released Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 18.10 Release:18.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center firefox: Installed: 63.0+build1-0ubuntu1 Candidate: 63.0+build1-0ubuntu1 Version table: *** 63.0+build1-0ubuntu1 500 500 http://ubuntu.osuosl.org/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Normal web browsing experience 4) What happened instead Graphical elements are black. After upgrading to 18.10, firefox graphical elements (window contents, context menus) are black. The only exception is a small rectangle in the upper left corner. Right-clicking within the window creates a context menu, which I am able to verify by observing a new black rectangle of the correct width that can be made to occlude the task bar by initiating it at a suitable starting position. If I launch firefox from a terminal then I get messages like the following: code [GFX1-]: Failed to lock new back buffer. [Parent 25238, Main Thread] WARNING: failed to open shm: Permission denied: file /build/firefox-MtV3KQ/firefox-63.0+build1/ipc/chromium/src/base/shared_memory_posix.cc, line 129 /code This occurs regardless of which desktop environment I use. Other browsers are working fine. I'm guessing the problem is related to the reported problem accessing shm. However, for the sake of completeness, I am using an AMD gpu with standard driver: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [1002:6810] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798999/+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 1798999] Re: firefox windows are black in Ubuntu 18.10
For me Firefox still doesn't work. I'm getting version 63.0+build2-0ubuntu0.18.10.2 . My Firefox windows aren't black, they're white. -- 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/1798999 Title: firefox windows are black in Ubuntu 18.10 Status in firefox package in Ubuntu: Fix Released Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 18.10 Release:18.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center firefox: Installed: 63.0+build1-0ubuntu1 Candidate: 63.0+build1-0ubuntu1 Version table: *** 63.0+build1-0ubuntu1 500 500 http://ubuntu.osuosl.org/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Normal web browsing experience 4) What happened instead Graphical elements are black. After upgrading to 18.10, firefox graphical elements (window contents, context menus) are black. The only exception is a small rectangle in the upper left corner. Right-clicking within the window creates a context menu, which I am able to verify by observing a new black rectangle of the correct width that can be made to occlude the task bar by initiating it at a suitable starting position. If I launch firefox from a terminal then I get messages like the following: code [GFX1-]: Failed to lock new back buffer. [Parent 25238, Main Thread] WARNING: failed to open shm: Permission denied: file /build/firefox-MtV3KQ/firefox-63.0+build1/ipc/chromium/src/base/shared_memory_posix.cc, line 129 /code This occurs regardless of which desktop environment I use. Other browsers are working fine. I'm guessing the problem is related to the reported problem accessing shm. However, for the sake of completeness, I am using an AMD gpu with standard driver: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [1002:6810] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798999/+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 1798999] Re: firefox windows are black in Ubuntu 18.10
The suggested command sudo apparmor_parser -R /etc/apparmor.d/usr.bin.firefox doesn't work for me :/ The profile is already disabled but Firefox still doesn't work. I get many errors like: Unable to init server: Could not connect: Connection refu###!!! [Parent][MessageChannel] Error: (msgtype=0x3B,name=PContent::Msg_InitRendering) Channel error: cannot send/recvsed (/usr/lib/firefox/firefox:7325): Gtk-WARNING **: 09:24:47.539: cannot open display: :1 [Parent 7238, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /build/firefox-MtV3KQ/firefox-63.0+build1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 729 -- 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/1798999 Title: firefox windows are black in Ubuntu 18.10 Status in firefox package in Ubuntu: Confirmed Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 18.10 Release:18.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center firefox: Installed: 63.0+build1-0ubuntu1 Candidate: 63.0+build1-0ubuntu1 Version table: *** 63.0+build1-0ubuntu1 500 500 http://ubuntu.osuosl.org/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Normal web browsing experience 4) What happened instead Graphical elements are black. After upgrading to 18.10, firefox graphical elements (window contents, context menus) are black. The only exception is a small rectangle in the upper left corner. Right-clicking within the window creates a context menu, which I am able to verify by observing a new black rectangle of the correct width that can be made to occlude the task bar by initiating it at a suitable starting position. If I launch firefox from a terminal then I get messages like the following: code [GFX1-]: Failed to lock new back buffer. [Parent 25238, Main Thread] WARNING: failed to open shm: Permission denied: file /build/firefox-MtV3KQ/firefox-63.0+build1/ipc/chromium/src/base/shared_memory_posix.cc, line 129 /code This occurs regardless of which desktop environment I use. Other browsers are working fine. I'm guessing the problem is related to the reported problem accessing shm. However, for the sake of completeness, I am using an AMD gpu with standard driver: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [1002:6810] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798999/+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 1798999] Re: firefox windows are black in Ubuntu 18.10
For me the issue also appeared for a none updated version of 18.10 (installing 18.10 directly). -- 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/1798999 Title: firefox windows are black in Ubuntu 18.10 Status in firefox package in Ubuntu: Confirmed Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 18.10 Release:18.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center firefox: Installed: 63.0+build1-0ubuntu1 Candidate: 63.0+build1-0ubuntu1 Version table: *** 63.0+build1-0ubuntu1 500 500 http://ubuntu.osuosl.org/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Normal web browsing experience 4) What happened instead Graphical elements are black. After upgrading to 18.10, firefox graphical elements (window contents, context menus) are black. The only exception is a small rectangle in the upper left corner. Right-clicking within the window creates a context menu, which I am able to verify by observing a new black rectangle of the correct width that can be made to occlude the task bar by initiating it at a suitable starting position. If I launch firefox from a terminal then I get messages like the following: code [GFX1-]: Failed to lock new back buffer. [Parent 25238, Main Thread] WARNING: failed to open shm: Permission denied: file /build/firefox-MtV3KQ/firefox-63.0+build1/ipc/chromium/src/base/shared_memory_posix.cc, line 129 /code This occurs regardless of which desktop environment I use. Other browsers are working fine. I'm guessing the problem is related to the reported problem accessing shm. However, for the sake of completeness, I am using an AMD gpu with standard driver: 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT / Trinidad XT [Radeon R7 370 / R9 270X/370X] [1002:6810] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798999/+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 1799483] [NEW] Firefox blank screen; doesn't work
Public bug reported: The repository version of Firefox only shows a white screen for me. When starting in console it shows some errors: Gtk-WARNING **: 16:36:55.427: cannot open display: :1 [Parent 25961, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /build/firefox-MtV3KQ/firefox-63.0+build1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 729 ###!!! [Parent][MessageChannel] Error: (msgtype=0x3B,name=PContent::Msg_InitRendering) Channel error: cannot send/recv I'm using the Ubuntu desktop with Xorg (not Wayland). Things I already tried out: * starting in safe mode * setting the DISPLAY variable Using the snap version works. But I need the repo version... ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 63.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mweimann 1871 F pulseaudio /dev/snd/controlC1: mweimann 1871 F pulseaudio BuildID: 20181016102217 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 16:36:07 2018 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-18 (4 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IpRoute: default via 172.29.6.1 dev enp0s31f6 proto dhcp metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 172.29.6.0/23 dev enp0s31f6 proto kernel scope link src 172.29.6.148 metric 100 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=63.0/20181016102217 Profile1 - LastVersion=Safe Mode/Safe Mode (Out of date) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET37W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L50007GE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET37W(1.12):bd03/14/2018:svnLENOVO:pn20L50007GE:pvrThinkPadT480:rvnLENOVO:rn20L50007GE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L50007GE dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1799483 Title: Firefox blank screen; doesn't work Status in firefox package in Ubuntu: New Bug description: The repository version of Firefox only shows a white screen for me. When starting in console it shows some errors: Gtk-WARNING **: 16:36:55.427: cannot open display: :1 [Parent 25961, Gecko_IOThread] WARNING: pipe error: Broken pipe: file /build/firefox-MtV3KQ/firefox-63.0+build1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 729 ###!!! [Parent][MessageChannel] Error: (msgtype=0x3B,name=PContent::Msg_InitRendering) Channel error: cannot send/recv I'm using the Ubuntu desktop with Xorg (not Wayland). Things I already tried out: * starting in safe mode * setting the DISPLAY variable Using the snap version works. But I need the repo version... ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: firefox 63.0+build1-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mweimann 1871 F pulseaudio /dev/snd/controlC1: mweimann 1871 F pulseaudio BuildID: 20181016102217 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 16:36:07 2018 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions:
[Desktop-packages] [Bug 1797749] [NEW] Drag and drop from File Roller to Nautilus not working
Public bug reported: This started to appear after updating to 18.10. Steps to reproduce: * open any archive with File Roller * open any location in Nautilus * drag a file or directory from File Roller to Nautilus Expected: * selected files/directories are extracted to the drop location Actually happens: * nothing ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu6 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: Sun Oct 14 10:26:22 2018 InstallationDate: Installed on 2017-12-20 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) 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-04-20T17:55:23.166649 usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1797749 Title: Drag and drop from File Roller to Nautilus not working Status in nautilus package in Ubuntu: New Bug description: This started to appear after updating to 18.10. Steps to reproduce: * open any archive with File Roller * open any location in Nautilus * drag a file or directory from File Roller to Nautilus Expected: * selected files/directories are extracted to the drop location Actually happens: * nothing ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu6 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: Sun Oct 14 10:26:22 2018 InstallationDate: Installed on 2017-12-20 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) 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-04-20T17:55:23.166649 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1797749/+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 264691] Re: Please add NM option for connecting to L2TP IPSEC VPN
Still no support in 16.04 and I didn't find a solution using a PPA or things like this :/ -- 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/264691 Title: Please add NM option for connecting to L2TP IPSEC VPN Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Status in network-manager package in Debian: Invalid Bug description: Binary package hint: network-manager Missing feature: You cannot connect to a (Microsoft) L2TP IPSEC VPN with Network Manager. The server I want to connect to expects a login / password and a PSK. When you do a connection in XP you can see the following details on a connection: Device name: L2TP Server type: PPP Authentication: MS CHAP v2 IPSEC Encryption: IPSEC ESP 3DES Compression: MPPC To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/264691/+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 1439440] Re: Laptop does not go to sleep when closing lid with external monitor connected
For me this bug appeared after updating to 16.04. (intel graphics HD 520). -- 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/1439440 Title: Laptop does not go to sleep when closing lid with external monitor connected Status in xorg package in Ubuntu: Confirmed Bug description: Using Dell Inspiron 15 3521 with Intel HD 4000 and an external monitor on HDMI output, in 15.04 beta 2: when closing the lid of the laptop, the laptop does not go to sleep (suspend to ram) as expected, but instead stays on, with the external monitor still on. I excepted that the laptop goes to sleep and the external monitor was blanked and turned off. This was the behavior on 14.10 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 2 01:17:27 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-10-generic, x86_64: installed virtualbox, 4.3.26, 3.19.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0597] InstallationDate: Installed on 2015-04-01 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) MachineType: Dell Inc. Inspiron 3521 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic.efi.signed root=UUID=cxxx---- ro quiet splash SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0X dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd10/25/2013:svnDellInc.:pnInspiron3521:pvrA12:rvnDellInc.:rn06XXX:rvrA02:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron 3521 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Thu Apr 2 00:14:49 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 939 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1439440/+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 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
I can more or less reliable reproduce the problem when plugging in/off an external display. Rebooting helps. I don't have any other integration problems. Just the font changes to the thin one. Is there any data I can provide helping to investigate this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1506704 Title: Thin font, nautilus doesn't integrate with Unity. Status in nautilus package in Ubuntu: Confirmed Bug description: It happens frequently (around 1/2 of the time) that when I boot the computer, font lines are only one pixel thick. This concerns watch in the sys-tray, all item in the menu of all applications, as well as all fonts in Nautilus. When this happens. Nautilus doesn't display menu in the Unity menu bar, but displays an additional button showing three horizontal lines for bringing up the menu. This problem has been with me for years, although sometimes disappears for months at a time when I run sudo apt-get update. This time it re- emerged after upgrading to 15.10 beta (Wily). It happens usually on power-up, and disappears after system restart. (To appear again on the next power-up). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu12 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 16 04:53:31 2015 GsettingsChanges: InstallationDate: Installed on 2015-10-08 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1506704/+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 1506704] Re: Thin font, nautilus doesn't integrate with Unity.
Can confirm this on the latest 15.10. It disappears when I reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1506704 Title: Thin font, nautilus doesn't integrate with Unity. Status in nautilus package in Ubuntu: Confirmed Bug description: It happens frequently (around 1/2 of the time) that when I boot the computer, font lines are only one pixel thick. This concerns watch in the sys-tray, all item in the menu of all applications, as well as all fonts in Nautilus. When this happens. Nautilus doesn't display menu in the Unity menu bar, but displays an additional button showing three horizontal lines for bringing up the menu. This problem has been with me for years, although sometimes disappears for months at a time when I run sudo apt-get update. This time it re- emerged after upgrading to 15.10 beta (Wily). It happens usually on power-up, and disappears after system restart. (To appear again on the next power-up). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu12 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 16 04:53:31 2015 GsettingsChanges: InstallationDate: Installed on 2015-10-08 (7 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1506704/+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 1296114] Re: [desktop] Bluetooth is always enabled after reboot even if it was disabled
This still happens on 15.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rfkill in Ubuntu. https://bugs.launchpad.net/bugs/1296114 Title: [desktop] Bluetooth is always enabled after reboot even if it was disabled Status in Bluetooth Menu: Invalid Status in indicator-bluetooth package in Ubuntu: Invalid Status in rfkill package in Ubuntu: Incomplete Status in urfkill package in Ubuntu: Triaged Bug description: If bluetooth was disabled using the switcher in the bluetooth indicator, after reboot it becomes enabled. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-bluetooth 0.0.6+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 22 22:34:52 2014 InstallationDate: Installed on 2014-01-27 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: indicator-bluetooth UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-bluetooth.log: (bluetooth-wizard:2251): Gtk-DEBUG: Connecting to session manager To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+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 1239310] Re: Session type select badge is missing
The bug doesn't appear anymore after updating to 14.04. ** Changed in: unity-greeter (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1239310 Title: Session type select badge is missing Status in “unity-greeter” package in Ubuntu: Invalid Bug description: I've installed gnome-session-fallback as an alternative to unity. After starting ubuntu the ubuntu-badge beside the username/password field is missing. If i switch the user (up and down key) the icon is present and I'm able to select another session type. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-greeter 13.10.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 13 12:04:37 2013 MarkForUpload: True SourcePackage: unity-greeter UpgradeStatus: Upgraded to saucy on 2013-09-28 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1239310/+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 1239310] [NEW] Session type select badge is missing
Public bug reported: I've installed gnome-session-fallback as an alternative to unity. After starting ubuntu the ubuntu-badge beside the username/password field is missing. If i switch the user (up and down key) the icon is present and I'm able to select another session type. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-greeter 13.10.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 13 12:04:37 2013 MarkForUpload: True SourcePackage: unity-greeter UpgradeStatus: Upgraded to saucy on 2013-09-28 (14 days ago) ** Affects: unity-greeter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1239310 Title: Session type select badge is missing Status in “unity-greeter” package in Ubuntu: New Bug description: I've installed gnome-session-fallback as an alternative to unity. After starting ubuntu the ubuntu-badge beside the username/password field is missing. If i switch the user (up and down key) the icon is present and I'm able to select another session type. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-greeter 13.10.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sun Oct 13 12:04:37 2013 MarkForUpload: True SourcePackage: unity-greeter UpgradeStatus: Upgraded to saucy on 2013-09-28 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1239310/+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 452049] Re: Gnome Places contains filesystems mounted via bind
Since the update to Ubuntu 12.10 beta this bug affects me. Under 12.04 the behavior was as expected: bind mounted directories were not shown as devices. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/452049 Title: Gnome Places contains filesystems mounted via bind Status in The G Library - GLib: Confirmed Status in Nautilus: New Status in “glib2.0” package in Ubuntu: Confirmed Bug description: Binary package hint: nautilus What happens: 1. mount a folder a to point b with the -bind option in /etc/fstab, for example: /media/data /home/username/MyDocuments none bind,user=username,group=username 0 0 2. reboot and then open nautilus 3. nautilus will show the new mount point in the places sidebar but it will give you an error if you click on the mount point: Unable to mount MyDocuments mount: according to mtab, /media/data is already mounted on /home/username/MyDocuments mount failed What should happen: 1. nautilus should not show these binded folders since they are well accessible through the filesystem 2. if the mounted folder (e.g. /mount/data) is a block device then it will appear in the places sidebar anyway and thus it is not necessary to show the mount point again 3. if the mounted folder is a normal folder from an existing file system then its accessible both from the original location and the newly binded location, thus the is no need to show it in places again 4. this is quite annoying Additional Information: This bug persists in Lucid ProblemType: Bug Architecture: amd64 Date: Thu Oct 15 12:04:11 2009 DistroRelease: Ubuntu 10.04 Package: nautilus 2.30 To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/452049/+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
