[Desktop-packages] [Bug 1814359] [NEW] Nvidia Driver 415 and lower prevents startup on 18.10
Public bug reported: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-390/+bug/1752053 Literally this been reported thousands of times and AFTER A YEAR of NO FIX, it is still affecting users! Is this some sort of a joke? I spent over a day re-installing and trying everything again just to result with a constant boot error, and I can't get anywhere near the OS because it is stuck on a purple screen. When the gub comes up it displays some key is wrong error but I don't have encryption enabled, afterwards only the _ is stuck on the screen without flashing. Can't we finally get the graphics drivers some love here from Canonical somehow? This is highly irritating already. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: critical un-fixed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1814359 Title: Nvidia Driver 415 and lower prevents startup on 18.10 Status in gdm3 package in Ubuntu: New Bug description: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-390/+bug/1752053 Literally this been reported thousands of times and AFTER A YEAR of NO FIX, it is still affecting users! Is this some sort of a joke? I spent over a day re-installing and trying everything again just to result with a constant boot error, and I can't get anywhere near the OS because it is stuck on a purple screen. When the gub comes up it displays some key is wrong error but I don't have encryption enabled, afterwards only the _ is stuck on the screen without flashing. Can't we finally get the graphics drivers some love here from Canonical somehow? This is highly irritating already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1814359/+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 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
Unintentionally unassigned Cosmic from Daniel. Please reassign to Daniel. ** Changed in: mutter (Ubuntu Cosmic) Assignee: Daniel van Vugt (vanvugt) => Bryce (bryce-a-carson) ** Changed in: mutter (Ubuntu Cosmic) Assignee: Bryce (bryce-a-carson) => (unassigned) -- 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/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Committed Bug description: [Impact] When zoom is enabled, the top bar and some shell dialogs (wireless network selection, shutdown dialog, etc.) are not displayed properly. (See the attached screenshots.) [Test Case] 1. Enable Zoom in Setting > Universal Access 2. (Optional) Set zoom factor to around 3 (or higher) 3. Look at the top bar. You will notice that all texts and icons are now gone. If you move your cursor to the right of the top bar, and then click on the status menu, you will see that only a portion of the menu is shown. 4. For the shell dialogs, go to the Settings app. In the Wifi section, choose one of the secured network available. You will see that the password dialog is not displayed in its entirety. [Regression Potential] Low. The affected code is only used in rendering shell panels and popup menus at the moment. So any potential regression (like the original bug) would be noticed in those places only, and not beyond. Furthermore, the upstream fix has been tested regularly for 8 months already. [Other Info] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 12:54:24 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-size' b'96' LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+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 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
Verified on Cosmic that mutter version 3.30.2-1~ubuntu.18.10.3 does NOT fix the problem. ** Attachment added: "Proof of installation; proof of bug." https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1767648/+attachment/5235249/+files/Screenshot%20from%202019-02-01%2021-16-19.png -- 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/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Committed Bug description: [Impact] When zoom is enabled, the top bar and some shell dialogs (wireless network selection, shutdown dialog, etc.) are not displayed properly. (See the attached screenshots.) [Test Case] 1. Enable Zoom in Setting > Universal Access 2. (Optional) Set zoom factor to around 3 (or higher) 3. Look at the top bar. You will notice that all texts and icons are now gone. If you move your cursor to the right of the top bar, and then click on the status menu, you will see that only a portion of the menu is shown. 4. For the shell dialogs, go to the Settings app. In the Wifi section, choose one of the secured network available. You will see that the password dialog is not displayed in its entirety. [Regression Potential] Low. The affected code is only used in rendering shell panels and popup menus at the moment. So any potential regression (like the original bug) would be noticed in those places only, and not beyond. Furthermore, the upstream fix has been tested regularly for 8 months already. [Other Info] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 12:54:24 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-size' b'96' LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+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 1581569] Re: Thunderbird & Firefox crash randomly while busy or idle (Xubuntu Xenial)
[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/1581569 Title: Thunderbird & Firefox crash randomly while busy or idle (Xubuntu Xenial) Status in firefox package in Ubuntu: Expired Status in thunderbird package in Ubuntu: Expired Bug description: Since I have been using Thunderbird version 1:38.7.2+build1-0ubuntu0.16.04.1 on Xenial, I can observe it crashing (seemingly) randomly while idle or while busy, resulting in the platform-independent Mozilla crash dialogue window. I don't know if this is related to Xenial or to internal changes at Mozilla. - lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 apt-cache policy thunderbird thunderbird: Installed: 1:38.7.2+build1-0ubuntu0.16.04.1 Candidate: 1:38.7.2+build1-0ubuntu0.16.04.1 Version table: *** 1:38.7.2+build1-0ubuntu0.16.04.1 500 500 http://mirror.lstn.net/ubuntu xenial-updates/main amd64 Packages 500 http://mirror.lstn.net/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1:38.6.0+build1-0ubuntu1 500 500 http://mirror.lstn.net/ubuntu xenial/main amd64 Packages 1:24.4.0+build1-0ubuntu1 500 500 http://cz.archive.ubuntu.com/ubuntu trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: thunderbird 1:38.7.2+build1-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: elkins 1436 F pulseaudio BuildID: 20160426220723 Channel: Unavailable CurrentDesktop: XFCE Date: Fri May 13 09:40:02 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-05-05 (8 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.219 metric 100 IwConfig: enp2s0no wireless extensions. lono wireless extensions. Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-73d462c6-f824-4a34-819a-3c9d82160513 Plugins: IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3ubuntu1)) - /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so (icedtea-8-plugin) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=38.7.2/20160426220723 (In use) RelatedPackageVersions: icedtea-8-plugin 1.6.2-3ubuntu1 RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-73d462c6-f824-4a34-819a-3c9d82160513 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: NM70I-1037U dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/05/2013:svnBIOSTARGroup:pnNM70I-1037U:pvr6.0:rvnBIOSTARGroup:rnNM70I-1037U:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0: dmi.product.name: NM70I-1037U dmi.product.version: 6.0 dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1581569/+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 1581569] Re: Thunderbird & Firefox crash randomly while busy or idle (Xubuntu Xenial)
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (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/1581569 Title: Thunderbird & Firefox crash randomly while busy or idle (Xubuntu Xenial) Status in firefox package in Ubuntu: Expired Status in thunderbird package in Ubuntu: Expired Bug description: Since I have been using Thunderbird version 1:38.7.2+build1-0ubuntu0.16.04.1 on Xenial, I can observe it crashing (seemingly) randomly while idle or while busy, resulting in the platform-independent Mozilla crash dialogue window. I don't know if this is related to Xenial or to internal changes at Mozilla. - lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 apt-cache policy thunderbird thunderbird: Installed: 1:38.7.2+build1-0ubuntu0.16.04.1 Candidate: 1:38.7.2+build1-0ubuntu0.16.04.1 Version table: *** 1:38.7.2+build1-0ubuntu0.16.04.1 500 500 http://mirror.lstn.net/ubuntu xenial-updates/main amd64 Packages 500 http://mirror.lstn.net/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1:38.6.0+build1-0ubuntu1 500 500 http://mirror.lstn.net/ubuntu xenial/main amd64 Packages 1:24.4.0+build1-0ubuntu1 500 500 http://cz.archive.ubuntu.com/ubuntu trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: thunderbird 1:38.7.2+build1-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: elkins 1436 F pulseaudio BuildID: 20160426220723 Channel: Unavailable CurrentDesktop: XFCE Date: Fri May 13 09:40:02 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2016-05-05 (8 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.219 metric 100 IwConfig: enp2s0no wireless extensions. lono wireless extensions. Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-73d462c6-f824-4a34-819a-3c9d82160513 Plugins: IcedTea-Web Plugin (using IcedTea-Web 1.6.2 (1.6.2-3ubuntu1)) - /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so (icedtea-8-plugin) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=38.7.2/20160426220723 (In use) RelatedPackageVersions: icedtea-8-plugin 1.6.2-3ubuntu1 RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-73d462c6-f824-4a34-819a-3c9d82160513 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: NM70I-1037U dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/05/2013:svnBIOSTARGroup:pnNM70I-1037U:pvr6.0:rvnBIOSTARGroup:rnNM70I-1037U:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0: dmi.product.name: NM70I-1037U dmi.product.version: 6.0 dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1581569/+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 1010722] Re: /usr/bin/canberra-gtk-play --id="desktop-login" --description="GNOME Login" Failed to play sound: File or data not found
[Expired for libcanberra (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libcanberra (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1010722 Title: /usr/bin/canberra-gtk-play --id="desktop-login" --description="GNOME Login" Failed to play sound: File or data not found Status in libcanberra package in Ubuntu: Expired Bug description: No StartUp Sound. Command - /usr/bin/canberra-gtk-play --id="desktop-login" --description="GNOME Login" Gives error - Failed to play sound: File or data not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1010722/+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 1588495] Re: package thunderbird-gnome-support 1:38.8.0+build1-0ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1588495 Title: package thunderbird-gnome-support 1:38.8.0+build1-0ubuntu0.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in thunderbird package in Ubuntu: Expired Bug description: fail ProblemType: Package DistroRelease: Ubuntu 16.04 Package: thunderbird-gnome-support 1:38.8.0+build1-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cunorte1610 F pulseaudio /dev/snd/controlC0: cunorte1610 F pulseaudio BuildID: 20160511162223 Channel: Unavailable Date: Thu Jun 2 13:31:12 2016 DuplicateSignature: Processing triggers for libc-bin (2.23-0ubuntu3) ... dpkg: error processing package thunderbird-gnome-support (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-06-02 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 148.202.77.254 dev enp2s0 proto static metric 100 148.202.77.0/24 dev enp2s0 proto kernel scope link src 148.202.77.41 metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 RunningIncompatibleAddons: False SourcePackage: thunderbird Title: package thunderbird-gnome-support 1:38.8.0+build1-0ubuntu0.16.04.1 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) dmi.bios.date: 09/29/2014 dmi.bios.vendor: LENOVO dmi.bios.version: O0IKT14AUS dmi.board.name: CRESCENTBAY dmi.board.vendor: LENOVO dmi.board.version: 31900059 STD 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:bvnLENOVO:bvrO0IKT14AUS:bd09/29/2014:svnLENOVO:pnF0B10045AR:pvrLenovoC50-30:rvnLENOVO:rnCRESCENTBAY:rvr31900059STD:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: F0B10045AR dmi.product.version: Lenovo C50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1588495/+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 1228702] Re: Middle Click Doesn't Add to end of Selection
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1228702 Title: Middle Click Doesn't Add to end of Selection Status in gedit package in Ubuntu: Expired Bug description: When you select a block of text and middle click at either the end or the beginning, it doesn't copy the text to the location that was clicked. Instead, it functions as if it were a primary click (left click). Ubuntu 13.04 Gedit 3.6.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1228702/+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 1242129] Re: Large gray area when file is edited outside gedit
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1242129 Title: Large gray area when file is edited outside gedit Status in gedit package in Ubuntu: Expired Bug description: In Saucy, when a file is opened in gedit, and that file is edited outside gedit, a prompt appears if I want to reload the file or not. This is fine. However, above the prompt, there is a large gray area. If the prompt appears multiple times, the gray area may increase and cover half the window. This did not occur in Raring. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gedit 3.8.3-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sat Oct 19 15:02:28 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-10-19 (364 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: gedit UpgradeStatus: Upgraded to saucy on 2013-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1242129/+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 1786694] Re: calendar applet doesn't connect with google
[Expired for gnome-calendar (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-calendar (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1786694 Title: calendar applet doesn't connect with google Status in gnome-calendar package in Ubuntu: Expired Bug description: If I log in Google Calendar, the applet doesn't synch the events and it is like if I never logged. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Aug 12 14:49:18 2018 InstallationDate: Installed on 2018-04-18 (116 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1786694/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]
[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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] Status in pulseaudio package in Ubuntu: Expired Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 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-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1774143] Re: gnome-calender crashed with SIGSEGV in get_circle_pixbuf_from_color()
[Expired for gnome-calendar (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-calendar (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1774143 Title: gnome-calender crashed with SIGSEGV in get_circle_pixbuf_from_color() Status in gnome-calendar package in Ubuntu: Expired Bug description: I don't know. It just crashed after gnome was unresponsible for a while and I used ALT+F2 and "n" to restart gnome. Then a bunch of crashes occur. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-calendar 3.20.4-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 30 10:09:39 2018 InstallationDate: Installed on 2014-04-18 (1502 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1774143/+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 1708713] Re: thunderbird-locale-de_56.0~b1+build1-0ubuntu0.17.04.3_amd64.deb not working
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1708713 Title: thunderbird-locale-de_56.0~b1+build1-0ubuntu0.17.04.3_amd64.deb not working Status in thunderbird package in Ubuntu: Expired Bug description: TB and language pack worked until update today. status installed thunderbird:amd64 1:56.0~b1+build1-0ubuntu0.17.04.3 status installed thunderbird-locale-de:amd64 1:56.0~b1+build1-0ubuntu0.17.04.3 on Linux 4.10.0-30-generic (x86_64) Ubuntu 17.04 Desktop Environment MATE Thunderbird starts with a blank screen. see picture Thunderbird works as expected after removing thunderbird-locale- de_56.0~b1+build1-0ubuntu0.17.04.3_amd64. After reinstalling the language-pack, same error exists. Bitte warten... Paket installieren: thunderbird-locale-de_56.0~b1+build1-0ubuntu0.17.04.3_amd64.deb Vormals nicht ausgewähltes Paket thunderbird-locale-de wird gewählt. (Lese Datenbank ... 377021 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von .../thunderbird-locale-de_56.0~b1+build1-0ubuntu0.17.04.3_amd64.deb ... Entpacken von thunderbird-locale-de (1:56.0~b1+build1-0ubuntu0.17.04.3) ... thunderbird-locale-de (1:56.0~b1+build1-0ubuntu0.17.04.3) wird eingerichtet ... ENDE DES BEFEHLS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1708713/+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 1771072] Re: GNOME Calendar randomly crashes with segfault when adding and/or removing events
[Expired for gnome-calendar (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-calendar (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1771072 Title: GNOME Calendar randomly crashes with segfault when adding and/or removing events Status in gnome-calendar package in Ubuntu: Expired Bug description: Adding and removing events on "personal" causes GNOME Calendar to randomly crash. Expected behaviour: Don't crash. Actual behaviour: Crashes with segfault. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon May 14 15:55:46 2018 InstallationDate: Installed on 2018-04-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1771072/+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 1806284] Re: Opened Apps don't appear in dock
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- 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/1806284 Title: Opened Apps don't appear in dock Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: As described above. E.g. I've opened GIMP which isn't appearing in the dock (see screenshot). If I click on Activities I can see my opened apps. Maybe the dock crashed because of switching between portrait and landscape mode (see other opened bugreports). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 22:07:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-30 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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-extension-ubuntu-dock/+bug/1806284/+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 1806280] Re: [wayland] Apps button disappeared after switching from portrait to landscape mode
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- 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/1806280 Title: [wayland] Apps button disappeared after switching from portrait to landscape mode Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Expired Bug description: As described above. I first rotated my laptop to work with it in portrait mode. When I switched back to landscape mode, the Gnome Shell button was gone. If I switch back to portrait mode the button is visible again. I will attach a screenshot to better explain what I mean. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 21:45:49 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-30 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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-extension-ubuntu-dock/+bug/1806280/+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 1806278] Re: No multitouch gestures available in Wayland session.
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1806278 Title: No multitouch gestures available in Wayland session. Status in gnome-shell package in Ubuntu: Expired Bug description: As described above. Multitouch-gestures are working if I'm booting into a X session. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 21:33:24 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-30 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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/1806278/+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 1805067] Re: hotkey shift+delete does not work
[Expired for cheese (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cheese (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1805067 Title: hotkey shift+delete does not work Status in cheese package in Ubuntu: Expired Bug description: hotkey shift+delete does not work. OS:Ubuntu 18.04.1 LTS Fail Rate: 2/2 units Fail Frequency: 10/10 times. Fail SKU: all skus. Decription: 1.Hot keys: Ctrl+ 0(Open),Ctrl+ S(Save As),Delete(Move to Trash),Shift+Delete(Delete). All hot keys above cannot work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1805067/+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 1806294] Re: If booted in tent mode screen orientation is wrong
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1806294 Title: If booted in tent mode screen orientation is wrong Status in gnome-shell package in Ubuntu: Expired Bug description: As described above. I've booted my convertible laptop in tent mode. After the login the screen orinetation is getting wrong. Top is on the bottom but the control-orinetation (mouse and touch-screen) is the right one. So if I for example want to open the Gnome Shell I have to click in the bottom left corner, but the button is shown in the top right corner. Even if I turn back the screen in "normal" mode the roientation keeps to be wrong. This bug doesn't appear in a wayland session. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 23:08:18 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-30 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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/1806294/+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 1814238] Re: deja-dup saves passphrase in /tmp
OK... there is at least one sequence that does this. When you: 1. restore files to their original location and 2. some files in the backup are outside your $HOME and 3. you have no deja-dup cache files for the backup location (like on a fresh install) In that case: 1. We write the encryption passphrase and/or network connection password to a file like /tmp/deja-dup-XX so that we can run duplicity as root using pkexec with those settings. (normally we pass those via environment variables, but pkexec strips those) 2. That file is only read/writable for the current user (mode 0600). 3. It is deleted when the restore is finished. So, while not ideal, this doesn't strike me as a critical bug. Still though, we should consider ways to not do that. ** Changed in: deja-dup Importance: Undecided => Medium ** Changed in: deja-dup Status: New => Triaged ** Changed in: deja-dup (Ubuntu) Importance: Critical => Undecided ** Changed in: deja-dup (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1814238 Title: deja-dup saves passphrase in /tmp Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: New Bug description: I have unchecked the "save passphrase" option in deja-dup, but still I have found the file /tmp/deja-dup-HXGLWZ that contains my passphrase in the clear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: deja-dup 37.1-2fakesync1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 10:59:06 2019 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1814238/+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 1814238] Re: deja-dup saves passphrase in /tmp
** Also affects: deja-dup Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1814238 Title: deja-dup saves passphrase in /tmp Status in Déjà Dup: New Status in deja-dup package in Ubuntu: Incomplete Bug description: I have unchecked the "save passphrase" option in deja-dup, but still I have found the file /tmp/deja-dup-HXGLWZ that contains my passphrase in the clear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: deja-dup 37.1-2fakesync1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 10:59:06 2019 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1814238/+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 1671974] Re: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP
I also see the IPv6 requests when a USB device is plugged in. In this case it is a Z-Wave device. I don't have any cannon stuff. I'm running 18.04.1 LTS. -- 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/1671974 Title: CUPS - Excessive Amounts of UDP Multicast Traffic for BJNP Status in cups package in Ubuntu: Confirmed Bug description: It appears that the cups-browsed service as of Xenial (version 1.8.3-2ubuntu3.1) sends an excessive amount of UDP multicast requests for ports 8610 (Canon MFNP) and 8612 (Canon BJNP) under unexpected conditions and regardless of a presence or lack of Canon printer devices on the network. This is manifested by enabling UFW, and observing multicast requests being blocked that are sent from the host machine's network IPv4 or IPv6 address to the multicast address, e.g. [UFW BLOCK] IN=wlp3s0 OUT= MAC= SRC= DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=96642 PROTO=UDP SPT=8612 DPT=8612 LEN=24 IN= OUT=wlan0 SRC=192.168.90.45 DST=192.168.91.255 LEN=44 TOS=0x00 PREC=0x00 TTL=64 ID=7742 DF PROTO=UDP SPT=8612 DPT=8610 LEN=24 Users have observed that the requests can be reproduced when any USB device is plugged/unplugged into the computer, regardless of whether the device has anything to do with printing: https://twitter.com/gertvdijk/status/621790755758178304 https://bugs.kali.org/view.php?id=3094 Just Googling "udp 8612", shows are a large number of results on different websites of people who have observed this behaviour in firewall and traffic logs, and have noticed that it may contribute to network slowdown and latency: https://askubuntu.com/questions/867739/what-is-this-traffic/867786 https://serverfault.com/questions/667376/watchguard-blocking-internal-udp-packets https://jehurst.wordpress.com/2016/01/22/small-victories/ recommends disabling the cups-browsed service to stop these requests: systemctl stop cups-browsed.service systemctl disable cups-browsed.service There are probably two things to address here: 1. Connecting any USB device should not cause these requests unless the device is actually a printer or directly related to printing. 2. Requests independent of connecting USB devices should be rate limited to a degree and/or should be dependent on the actual presence of a Canon printer configured on the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1671974/+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 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
This also happens on my system with RX480 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 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-1ubuntu1 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/linux/+bug/1813701/+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 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 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-1ubuntu1 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/linux/+bug/1813701/+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 550332] Re: [AV200 - Xonar DX] Playback problem - Volume control is very laggy
I no longer have this sound card to evaluate. ** Changed in: alsa-driver (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/550332 Title: [AV200 - Xonar DX] Playback problem - Volume control is very laggy Status in alsa-driver package in Ubuntu: Invalid Bug description: When i change volume the audio stops and takes 5+ seconds to come back. Indicator-sound crashes because of it. I get a message about "waiting for sound system" but sometimes eventually the volume changes. It feels as if there is no DMA with the sound card. Hope you understand what i mean. Tryed the snapshots on the audio ppa: didn't fix ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: alsa-base 1.0.22.1+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-17-generic x86_64 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfe9fc000 irq 17' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 4 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'DX'/'Asus Virtuoso 100 (rev 2) at 0xe800, irq 16' Mixer name : 'AV200' Components : 'CS4398 CS4362A CS5361 AV200' Controls : 16 Simple ctrls : 9 Card2.Amixer.info: Card hw:2 'CinemaTM'/'Microsoft Microsoft® LifeCam Cinema(TM) at usb-:00:1d.7-4, high speed' Mixer name : 'USB Mixer' Components : 'USB045e:075d' Controls : 2 Simple ctrls : 1 Card2.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 56 Mono: Capture 0 [0%] [0.00dB] [on] Date: Sun Mar 28 16:58:19 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1) PackageArchitecture: all ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SelectedCard: 1 DX AV200 - Xonar DX SourcePackage: alsa-driver Symptom: audio Title: [AV200 - Xonar DX] Playback problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/550332/+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 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutt
** Tags added: cosmic -- 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/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Committed Bug description: [ Impact ] Gnome shell crashes on double free Problem is occurring if dual monitor is used. Second monitor is repeatingly blank and activated again. At the bottom it probably contains the upper part of the first monitor. I had the same problem at 18.04 when using gdm3 without wayland during logon. [ Test case ] - Run gnome-shell with multimonitor - No flashing should happen on gdm initialization Also we should monitor crashes in e.u.c [ Regression potential ] Low, the proposed fix is part of the current stable branch upstream and not changed in further revisions. -- ProblemType: CrashDistroRelease: Ubuntu 18.10 Package: gnome-shell 3.29.90-2ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic i686 ApportVersion: 2.20.10-0ubuntu9 Architecture: i386 AssertionMessage: double free or corruption (fasttop) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 21:02:58 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6SourcePackage: gnome-shell StacktraceTop: __libc_signal_restore_set (set=0xbfcd5e9c) at ../sysdeps/unix/sysv/linux/nptl-signals.h:80 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 __GI_abort () at abort.c:79 __libc_message (action=do_abort, fmt=) at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0xb6b437e8 "double free or corruption (fasttop)") at malloc.c:5350 Title: gnome-shell assert failure: double free or corruption (fasttop) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+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 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_text
Reinstalled current libmutter. With dual monitor horizontal aside this problem could not be reproduced because logon-session crashes before showing logon-screen, (caused by bug #1790525). Installed proposed version: apt list libmutter-3-0 Listing... Done libmutter-3-0/cosmic-proposed,now 3.30.2-1~ubuntu18.10.3 i386 [installed] No crash anymore when trying to suspend at logon-screen. Problem is solved by proposed package. No new other problems detected. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Committed Bug description: [ Impact ] Gnome shell crashes on cogl_texture_get_height [ Test case ] No clear reproducer is know for such issue, crashes should be monitored in e.u.c checking that this is not happening anymore for the version in proposed. [ Regression potential ] Low, the proposed fix is part of the current stable branch upstream and not changed in further revisions. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/e5b2dcb04552882a76f1daa6b9f18ba864269d26 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795774/+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 1798597] Re: Backport packages for 18.04.2 HWE stack
kisak: yes, see bug 1811225 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutt
** Tags removed: cosmic verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Committed Bug description: [ Impact ] Gnome shell crashes on double free Problem is occurring if dual monitor is used. Second monitor is repeatingly blank and activated again. At the bottom it probably contains the upper part of the first monitor. I had the same problem at 18.04 when using gdm3 without wayland during logon. [ Test case ] - Run gnome-shell with multimonitor - No flashing should happen on gdm initialization Also we should monitor crashes in e.u.c [ Regression potential ] Low, the proposed fix is part of the current stable branch upstream and not changed in further revisions. -- ProblemType: CrashDistroRelease: Ubuntu 18.10 Package: gnome-shell 3.29.90-2ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic i686 ApportVersion: 2.20.10-0ubuntu9 Architecture: i386 AssertionMessage: double free or corruption (fasttop) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 21:02:58 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6SourcePackage: gnome-shell StacktraceTop: __libc_signal_restore_set (set=0xbfcd5e9c) at ../sysdeps/unix/sysv/linux/nptl-signals.h:80 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 __GI_abort () at abort.c:79 __libc_message (action=do_abort, fmt=) at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0xb6b437e8 "double free or corruption (fasttop)") at malloc.c:5350 Title: gnome-shell assert failure: double free or corruption (fasttop) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+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 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutt
Reinstalled current libmutter. With dual monitor horizontal aside this gives Feb 1 22:26:58 Gert2 gnome-shell[1038]: Failed to allocate texture: Failed to create texture 2d due to size/format constraints Feb 1 22:26:58 Gert2 gnome-shell[1038]: CoglError set over the top of a previous CoglError or uninitialized memory.#012This indicates a bug in someone's code. You must ensure an error is NULL before it's set.#012The overwriting error message was: Sliced texture size of 2560 x 1024 not possible with max waste set to -1 Logon-session crashes before showing logon-screen. Installed proposed version: apt list libmutter-3-0 Listing... Done libmutter-3-0/cosmic-proposed,now 3.30.2-1~ubuntu18.10.3 i386 [installed] Problem is solved by proposed package. No new other problems detected. -- 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/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Committed Bug description: [ Impact ] Gnome shell crashes on double free Problem is occurring if dual monitor is used. Second monitor is repeatingly blank and activated again. At the bottom it probably contains the upper part of the first monitor. I had the same problem at 18.04 when using gdm3 without wayland during logon. [ Test case ] - Run gnome-shell with multimonitor - No flashing should happen on gdm initialization Also we should monitor crashes in e.u.c [ Regression potential ] Low, the proposed fix is part of the current stable branch upstream and not changed in further revisions. -- ProblemType: CrashDistroRelease: Ubuntu 18.10 Package: gnome-shell 3.29.90-2ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic i686 ApportVersion: 2.20.10-0ubuntu9 Architecture: i386 AssertionMessage: double free or corruption (fasttop) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 21:02:58 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6SourcePackage: gnome-shell StacktraceTop: __libc_signal_restore_set (set=0xbfcd5e9c) at ../sysdeps/unix/sysv/linux/nptl-signals.h:80 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 __GI_abort () at abort.c:79 __libc_message (action=do_abort, fmt=) at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0xb6b437e8 "double free or corruption (fasttop)") at malloc.c:5350 Title: gnome-shell assert failure: double free or corruption (fasttop) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1790525/+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 1798597] Re: Backport packages for 18.04.2 HWE stack
Hello Timo, or anyone else affected, Accepted xserver-xorg-video-intel-hwe-18.04 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel- hwe-18.04/2:2.99.917+git20171229-1ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done verification-done-bionic ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, s
[Desktop-packages] [Bug 1506969] Re: Window dimming effect stays after window has gone
Please disregard comment #2 -- 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/1506969 Title: Window dimming effect stays after window has gone Status in mutter package in Ubuntu: New Bug description: I have recently noticed that on Ubuntu GNOME 15.04 with GNOME 3.16 that sometimes if a window pops-up from a program and I go into the Activities Overview, that then if that window closes the dimming effect that it had on the main window behind it stays no matter what you do, unless you manage to open a new pop-up window such as a new dialog box and then close it, that seems to remove the dimming, but otherwise a restart of the application is required. I have noticed this issue with Firefox and VirtualBox, but I am sure that it is not application-specific and has something to do with the window management or something. --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid Package Information: mutter: Installed: 3.16.3-1ubuntu1~vivid1 Candidate: 3.16.3-1ubuntu1~vivid1 Version table: *** 3.16.3-1ubuntu1~vivid1 0 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3.14.4-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1506969/+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 1506969] Re: Window dimming effect stays after window has gone
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016 User no longer uses Launchpad and implied issue not Firefox specific Closing as report unconfirmed and no further comments for over 3 years -- 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/1506969 Title: Window dimming effect stays after window has gone Status in mutter package in Ubuntu: New Bug description: I have recently noticed that on Ubuntu GNOME 15.04 with GNOME 3.16 that sometimes if a window pops-up from a program and I go into the Activities Overview, that then if that window closes the dimming effect that it had on the main window behind it stays no matter what you do, unless you manage to open a new pop-up window such as a new dialog box and then close it, that seems to remove the dimming, but otherwise a restart of the application is required. I have noticed this issue with Firefox and VirtualBox, but I am sure that it is not application-specific and has something to do with the window management or something. --- OS Information: No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.04 Release: 15.04 Codename: vivid Package Information: mutter: Installed: 3.16.3-1ubuntu1~vivid1 Candidate: 3.16.3-1ubuntu1~vivid1 Version table: *** 3.16.3-1ubuntu1~vivid1 0 500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3.14.4-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1506969/+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 1798597] Re: Backport packages for 18.04.2 HWE stack
Good day, just wondering if mesa 18.2.8 was still in the plan? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Released Status in libdrm source package in Bionic: Fix Released Status in llvm-toolchain-7 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in wayland source package in Bionic: Fix Released Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Released Status in xorg-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Released Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Released Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+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 1813506] Re: libreoffice cannot start on live or installed ubuntu budgie 19.04
>From UbuntuForums https://ubuntuforums.org/showthread.php?t=2407348&page=2 "Digging around i've found https://bugs.documentfoundation.org/show_bug.cgi?id=122116#c26"; which suggest a libcpdb removal: purged libcpdb-libs-common1 and cpdb-backend-cups as dependant." I can confirm that purging those two packages allows libreoffice to start. Document Foundation describes this bug https://bugs.documentfoundation.org/show_bug.cgi?id=122116#c26 The end of the bug report says that it is fixed in libreoffice v6.2.0.2. Will disco be getting that version (or later of libreoffice) ? ** Bug watch added: Document Foundation Bugzilla #122116 https://bugs.documentfoundation.org/show_bug.cgi?id=122116 -- 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/1813506 Title: libreoffice cannot start on live or installed ubuntu budgie 19.04 Status in libreoffice package in Ubuntu: Confirmed Bug description: On both the 19.04 daily iso and the installed version of 19.04 UB, libreoffice writer, calc etc cannot start. All you see is a "Document Recovery" window despite that this is the first time the application is started. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice 1:6.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Jan 27 22:08:51 2019 InstallationDate: Installed on 2019-01-21 (6 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190121) 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/1813506/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
I filmed my computer boot up to better show what happens. The right monitor is on the integrated video card (the R7), and doesn't show anything initially. The center and left monitor turn on and mirror each other during boot, and show grub and most of the kernel and systemd messages, then at some point all output is sent to the right monitor. I believe the systemd log says something along the lines of "detecting all video cards" at that point. ** Attachment added: "Computerbootup.webm" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235238/+files/Computerbootup.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: New Status in xserver-xorg-driver-radeonhd: Invalid Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1809044] Re: DVD playback error: unable to play . . . DVD source is required . . .
[SOLVED] Just needed to: $ sudo apt install gstreamer1.0-plugins-bad I'm not sure why this isn't included in the restricted-extras or libdvd-pkg depends? ** Summary changed: - DVD playback error: unable to play . . . DVD source is required . . . + [SOLVED] DVD playback error: unable to play . . . DVD source is required . . . ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Invalid ** Changed in: totem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1809044 Title: [SOLVED] DVD playback error: unable to play . . . DVD source is required . . . Status in gstreamer1.0 package in Ubuntu: Invalid Status in totem package in Ubuntu: Invalid Bug description: Successful installation of libdvd-pkg and dpkg-reconfigure, afterwards, to complete compilation. Inserted known-good DVD and clicked on "Open in Videos" which launched the Totem player. Error msg: "Unable to play the file, DVD source is required, but is not installed." DVD will play normally in VLC player after installation on same machine. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgstreamer1.0-0 1.14.4-1 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 18 15:21:45 2018 InstallationDate: Installed on 2018-11-13 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044/+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 1814342] [NEW] fc-match does not return the correct font
Public bug reported: On Ubuntu 18.10 the command `fc-match monospace:bold` returns DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book" instead of DejaVuSansMono-Bold.ttf: "DejaVu Sans Mono" "Bold" This works correctly on Ubuntu 18.04.1 which is using fontconfig 2.12.6, whereas 18.10 uses 2.13.0. I compiled 2.13.1 from source and just installed libfontconfig.so.1.12.0. This solves the problem. While it does not sound much, this bug also causes Java 8 AWT/Swing font rendering to be uglier than it has to be. Instead of "DejaVu Sans Mono Bold" and emboldened version of "DejaVu Sans Mono" is used which has a different size, which goes counter to the notion of a "monospace" font. ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1814342 Title: fc-match does not return the correct font Status in fontconfig package in Ubuntu: New Bug description: On Ubuntu 18.10 the command `fc-match monospace:bold` returns DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book" instead of DejaVuSansMono-Bold.ttf: "DejaVu Sans Mono" "Bold" This works correctly on Ubuntu 18.04.1 which is using fontconfig 2.12.6, whereas 18.10 uses 2.13.0. I compiled 2.13.1 from source and just installed libfontconfig.so.1.12.0. This solves the problem. While it does not sound much, this bug also causes Java 8 AWT/Swing font rendering to be uglier than it has to be. Instead of "DejaVu Sans Mono Bold" and emboldened version of "DejaVu Sans Mono" is used which has a different size, which goes counter to the notion of a "monospace" font. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1814342/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
** Attachment added: "dmesg log" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235234/+files/dmesg.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: New Status in xserver-xorg-driver-radeonhd: Invalid Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1814341] [NEW] Xbox 360 controller doesn't work in Ubuntu 18.10 anymore
Public bug reported: After upgrading from Ubuntu 18.04 to 18.10, my Xbox 360 controller doesn't work any more. After reloading xpad per modprobe it works again: modprobe -r xpad modprobe xpad There are other users, having the same issue: https://www.reddit.com/r/linux_gaming/comments/9pnvl4/ubuntu_1810_xbox_360_controller/ My system is: Description:Ubuntu 18.10 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- 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/1814341 Title: Xbox 360 controller doesn't work in Ubuntu 18.10 anymore Status in nautilus package in Ubuntu: New Bug description: After upgrading from Ubuntu 18.04 to 18.10, my Xbox 360 controller doesn't work any more. After reloading xpad per modprobe it works again: modprobe -r xpad modprobe xpad There are other users, having the same issue: https://www.reddit.com/r/linux_gaming/comments/9pnvl4/ubuntu_1810_xbox_360_controller/ My system is: Description: Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1814341/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
I've come across this again after upgrading to 18.10 $ xrandr --listproviders Providers: number : 1 Provider 0: id: 0x56 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3 associated providers: 0 name:KAVERI @ pci::00:01.0 $ sudo lspci -nn | grep -E 'VGA|Display' [sudo] password for richard: 00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:1313] 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV770 [Radeon HD 4850] [1002:9442] Only the built-in Radeon R7 is being used ** Changed in: lightdm Status: Invalid => New ** Changed in: lightdm (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in Light Display Manager: New Status in xserver-xorg-driver-radeonhd: Invalid Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1692437/+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 1813506] Re: libreoffice cannot start on live or installed ubuntu budgie 19.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1813506 Title: libreoffice cannot start on live or installed ubuntu budgie 19.04 Status in libreoffice package in Ubuntu: Confirmed Bug description: On both the 19.04 daily iso and the installed version of 19.04 UB, libreoffice writer, calc etc cannot start. All you see is a "Document Recovery" window despite that this is the first time the application is started. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice 1:6.1.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Jan 27 22:08:51 2019 InstallationDate: Installed on 2019-01-21 (6 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190121) 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/1813506/+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 886323] Re: Thumbnail Creation on Digital Camera Slows System and Crashes Nautlilus
Today, 8 years later :), I cannot say something new regarding this bug - I even don't have this camera any more. For me you can close this bug now and try to solve other more important bugs. But I can say that usb read/write is still slow on Ubuntu 18.10 in comparison to win on my current pc, even with a simple usb flash drive. -- 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/886323 Title: Thumbnail Creation on Digital Camera Slows System and Crashes Nautlilus Status in nautilus package in Ubuntu: Incomplete Bug description: The USB 2.0 connection speed on my new Canon S95 camera is not very fast, so when browsing the images directly, Nautilus' thumbnailing process seems to choke the connection. The thumbnailing takes forever, particularly for CR2 files and long .MOV files. During thumbnailing, I cannot copy or view or do anything to these files for several minutes while the thumbnailing is taking place. Sometimes the thumnailing process crashes nautilus. Nautilus should not automatically thumbnail images on these external cameras if the thumbnailing process is going to bog down the camera connection. Nautilus should either: 1) Use a faster thumbnailing process, or 2) Not thumbnail on digital cameras by default. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Nov 4 15:39:16 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: nautilus UpgradeStatus: Upgraded to oneiric on 2011-10-16 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/886323/+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 1687411] Re: If default zoom set to ≠ 100% icons have different sizes
Ok why not. But still "problem" is not totally solved : there are maybe missing size icons in Ubuntu 16.04 / nautilus 3.14.3 -- 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/1687411 Title: If default zoom set to ≠ 100% icons have different sizes Status in nautilus package in Ubuntu: Fix Released Bug description: Hi, In Nautilus 3.14.3 / Ubuntu Unity 16.04.2 If default zoom in Nautilus preferences is not 100%, icons have many sizes or if I manually zoom into a folder [ctrl]+[+]. Screenshots attached. ___ Is this https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1448407 the same problem ? ___ 2017-05-12 Problem happens with Humanity & Ubuntu icon themes ( the default ones ). Problem does not happen with other icon themes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1687411/+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 1814330] [NEW] My adblocker for the Firefox browser was removed in the last update
Public bug reported: The adblocker just disappeared. I am not tech savvy enough to find out why. When I checked my downloads, in the file system, it seems like some of them are missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 65.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lyn1866 F pulseaudio BuildID: 20190128144255 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 12:22:49 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (546 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.4 metric 100 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-f276e77a-a433-4a98-8e56-550590190124 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=65.0/20190128144255 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-f276e77a-a433-4a98-8e56-550590190124 bp-b22f8099-c16b-4b0c-8bbb-79f220181017 bp-d0d17655-e24b-41db-af32-9fa570181002 bp-0aaa6a42-121b-4587-8d37-df3141180328 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2018-08-16 (169 days ago) dmi.bios.date: 04/04/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.29 dmi.board.asset.tag: 2UA1311DPS dmi.board.name: 1494 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA1311DPS dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.29:bd04/04/2016:svnHewlett-Packard:pnHPCompaq8200EliteCMTPC:pvr:rvnHewlett-Packard:rn1494:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 8200 Elite CMT PC dmi.sys.vendor: Hewlett-Packard ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1814330 Title: My adblocker for the Firefox browser was removed in the last update Status in firefox package in Ubuntu: New Bug description: The adblocker just disappeared. I am not tech savvy enough to find out why. When I checked my downloads, in the file system, it seems like some of them are missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 65.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lyn1866 F pulseaudio BuildID: 20190128144255 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 12:22:49 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (546 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.4 metric 100 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-f276e77a-a433-4a98-8e56-550590190124 PrefSources: /usr/lib/firefox/defaults/pref/all-ubuntumate.js prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=65.0/20190128144255 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-f276e77a-a433-4a98-8e56-550590190124 bp-b22f8099-c16b-4b0c-8bbb-79f220181017 bp-d0d17655-e24b-41db-af32-9fa570181002 bp-0aaa6a42-121b-4587-8d37-df3141180328 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2018-08-16 (169 days ago) dmi.bios.
[Desktop-packages] [Bug 699922]
The bug is still here (45.6.0) and it's very annoying. My left monitor is usually in fullscreen mode, so I miss notifications about new mail. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/699922 Title: Thunderbird displays notification on wrong monitor Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird In a multiple monitor setup, Thunderbird displays its notification in the bottom right of the leftmost monitor, rather than the window on which it is currently active. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8 Uname: Linux 2.6.35-24-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Jan 7 16:01:00 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/699922/+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 699922]
...Still here in 60.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/699922 Title: Thunderbird displays notification on wrong monitor Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird In a multiple monitor setup, Thunderbird displays its notification in the bottom right of the leftmost monitor, rather than the window on which it is currently active. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8 Uname: Linux 2.6.35-24-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Jan 7 16:01:00 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/699922/+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 699922]
+1... still here in 60.4... In fact, it may be a corrupted preference or so... My dual-screen configuration has not changed for years but the problem appeared recently, sometimes after the v60 upgrade. It may be connected to the fact that I moved TB to the secondary screen once but since then, I never managed to get the dialogs (not only right-click menu but reply and edit (message) buttons) appearing on the right (main) screen (where TB main window is) after connecting the second screen (without restarting TB). The only workaround I found is to restart TB after disconnecting the screen: then it works fine until I reconnect the second screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/699922 Title: Thunderbird displays notification on wrong monitor Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird In a multiple monitor setup, Thunderbird displays its notification in the bottom right of the leftmost monitor, rather than the window on which it is currently active. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8 Uname: Linux 2.6.35-24-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Jan 7 16:01:00 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/699922/+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 699922]
52.2.1, 7 years guys, 7 years ... The bug is still there -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/699922 Title: Thunderbird displays notification on wrong monitor Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird In a multiple monitor setup, Thunderbird displays its notification in the bottom right of the leftmost monitor, rather than the window on which it is currently active. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8 Uname: Linux 2.6.35-24-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Jan 7 16:01:00 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/699922/+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 1802569] Re: RM openssl1.0 from Ubuntu
** Changed in: ckermit (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp in Ubuntu. https://bugs.launchpad.net/bugs/1802569 Title: RM openssl1.0 from Ubuntu Status in cfengine2 package in Ubuntu: Confirmed Status in ckermit package in Ubuntu: Confirmed Status in conserver package in Ubuntu: Confirmed Status in cqrlog package in Ubuntu: Fix Released Status in freerdp package in Ubuntu: New Status in libpam-ssh package in Ubuntu: New Status in mailavenger package in Ubuntu: Confirmed Status in moonshot-trust-router package in Ubuntu: Confirmed Status in netkit-ftp-ssl package in Ubuntu: Confirmed Status in netty-tcnative-1.1 package in Ubuntu: New Status in openssl1.0 package in Ubuntu: Incomplete Status in osslsigncode package in Ubuntu: New Status in pam-ssh-agent-auth package in Ubuntu: Fix Released Status in pidentd package in Ubuntu: New Status in qpid-proton package in Ubuntu: New Status in radsecproxy package in Ubuntu: New Status in reconserver package in Ubuntu: Confirmed Status in resiprocate package in Ubuntu: New Status in ruby-eventmachine package in Ubuntu: New Status in stunserver package in Ubuntu: New Status in validns package in Ubuntu: New Status in cfengine2 package in Debian: New Status in ckermit package in Debian: Fix Released Status in conserver package in Debian: New Status in cqrlog package in Debian: Fix Released Status in freerdp package in Debian: Fix Released Status in libpam-ssh package in Debian: Fix Released Status in mailavenger package in Debian: Fix Released Status in moonshot-trust-router package in Debian: New Status in netkit-ftp-ssl package in Debian: New Status in netty-tcnative-1.1 package in Debian: Fix Released Status in openssl1.0 package in Debian: New Status in osslsigncode package in Debian: Fix Released Status in pam-ssh-agent-auth package in Debian: Fix Released Status in pidentd package in Debian: New Status in qpid-proton package in Debian: Fix Released Status in radsecproxy package in Debian: Fix Released Status in reconserver package in Debian: New Status in resiprocate package in Debian: Confirmed Status in ruby-eventmachine package in Debian: Fix Released Status in stunserver package in Debian: Confirmed Status in validns package in Debian: Confirmed Bug description: RM openssl1.0 from Ubuntu reconserver has multiple ftbfs issues / bugs. freerdp is superseeded by freerdp2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cfengine2/+bug/1802569/+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 1814174] Re: Xorg crash report after resume
>From that bug report I followed this step: "It works to edit /etc/apport/crashdb.conf and add 'Crash' to the 'problem_types': ['Bug', 'Package', 'Crash'], or to make that change in a separate file and run". So I'll see how that fares. -- 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/1814174 Title: Xorg crash report after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's annoying to have to type the password every time, but since root owns the crash log it's necessary. I've used Lubuntu for years. My prior laptop was a Sager with an AMD card. It had the same sort of issue versions ago. I got in the habit of just clicking it away. I think that the Report Crash fails because the log is owned by root and I don't have rights to it. Perhaps adding myself to the whoopsie group would resolve that (and needing sudo to delete too), so I think I'll try that. It's the only thing about Lubuntu that would be a turn off to new users. It's not a high priority thing, because the system works just fine. But it is a nuisance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-serv
[Desktop-packages] [Bug 684982]
*** Bug 1413147 has been marked as a duplicate of this bug. *** -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
This bug was partly fixed in 52.8 (the session restore was working properly for some time now), but after updating to 63.0.3, it reappeared. The windows are restored at the same position on the same desktop, but the content mixed up (the content from other windows of this session appears instead, hence the logical relationship of windows, positions and content is destroyed). Unfortunately, the workaround of https://bugzilla.mozilla.org/show_bug.cgi?id=372650#c33 doesn't work anymore with this version :-(, and it suffers from new problems as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1510762. Hmm. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
Sorry, but I was wrong with 41.0.2: it managed to restore my ~30 windows for a couple of times now. Whatever was changed between ~40 and 41.0.2 in this area, the result matches my expectations (although it still goes through the recovery manager, but that's a minor issue compared to rearranging a significant portion of the windows on every reboot). -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
Hi Guys, I'm very sorry, but we missed the 10th anniversary of this bug! Just an update: the last couple of versions made the problem worse: while FF remembered the position and size at least (while loosing just the desktop) with versions up to a couple of months ago, since a few versions it mixes up position, size and desktop. (now at 52.1.0) What a pity. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
Well, so maybe this should be a window manager feature, but perhaps FF session restore could make use of the windowmanager's session features to achieve it then rather than attempt to implement sessions, just poorly/broken... I'm now curious which if any apps do have this feature. Konqueror maybe? (May depend on whether you have it in single or multiple process mode.) Just seems to me that if the session is going to attempt to restore window sizes and placements, it should also restore window placement wrt to which virtual desktop. Whether it implements that itself or makes use of window manager session features to do it doesn't matter--which ever way works the best and/or is easiest to implement. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
I have a hacky workaround for Linux users. I threw together a script to deal with this problem some time ago (for a number of programs I was using, but mostly Firefox). It's in a GitHub repository here: https://github.com/zepalmer/script-vdr Since that script expects PIDs, I usually call it from a separate wrapper script for Firefox: #!/bin/bash mode="$1" if [ "$mode" != "load" -a "$mode" != "save" ]; then echo "Valid modes are \"load\" or \"save\"." exit 1 fi ps ax | grep firefox | grep -v grep | egrep -o '^ *[0-9]+' | egrep -o '[0-9]+$' | \ while read pid; do [ -n "$pid" ] && vdr --$mode $pid done I saved the above as "~/bin/vdr-ff". I have keystrokes which run "vdr- ff load" and "vdr-ff save" so I can periodically save my Firefox window positions and then reload them when I have to restart Firefox. In theory, I could put "vdr-ff save" in a user crontab, but I haven't bothered to deal with making sure it doesn't save immediately after Firefox starts. Please note that the script operates by using the X window title. This means that (a) sites with changing titles won't restore properly and (b) some bit of information about your browsing history is stored in "~/.vdr.data". Of course, I'd *much* prefer a proper resolution to this bug, but I haven't the faintest idea how to solve it in a platform-independent manner. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
I'm starting to get a more concrete picture of the problem from a user perspective, and would like to cooperate with somebody from the firefox hacking front, who is willing to solve this problem! I made an interesting observation. It happens, that all windows are restored correctly under certain circumstances. Here's how I can reproduce this at will. Given I want to add a new window with several tabs to my Firefox bouquet. (30-40 windows with maybe 500 tabs). 1) quit or kill Firefox 2) start Firefox all windows will appear on a single desktop (as described in https://bugzilla.mozilla.org/show_bug.cgi?id=372650#c29) 3) push the windows to the correct screens and rearrange their dimensions and order Now I can logoff/reboot without stomach pains, after login, the Firefox "crashed session manager" will appear in a single window. Push restore session, et voilà, all windows with all tabs reappear on the expected locations, and keep the content, too. No mangling. Obviously, Firefox session management cannot handle a heavy working set. I would like to start with examination of the database, where this information is stored, if somebody can point me to it (and give some hints about, how to examine). Notes: I don't care/check the z-order of things (being a fan of shuttering windows, only the window handle bars of most windows will appear). The few, that weren't shuttered, don't overlap with other windows. The "long time no see" message about Firefox restoration notice on every start is bizarre and nagging: no other code burns more cpu cycles on my primary desktop every day - and no, I don't want to throw away my setup which would result in days of work to rearrange! I vote for another option: never show this hint again! z-order -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
FWIW, Gtk+3 >= 3.10 has gdk_x11_window_get_desktop() and gdk_x11_window_move_to_desktop() functions... which, if you ask me, is shortsighted, since it's limited to X11, and won't work in Wayland. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
This really does need sorted. I use about 8 windows across 3 Virtual Desktops (windows 10) with a combined total of anywhere between 60 and 90 tabs. After a while firefox becomes slow and laggy to the point where I need to reboot, when I do, (doesnt matter what way) when I reopen firefox and restore the session EVERYTHING loads up on 1 virtual desktop causing me to have to troll through each window and reassign it to the correct virtual desktop etc. I have noticed people complaining about this issue since like 2013... Surely its about time this was resolved? I cannot even find any add-ons to create this functionality -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
Some news related to 44.0: I've spend a good part of the evening to get 44.0 to behave, but failed. The usual procedure is: killing Firefox, restart places all windows on one desktop, distribute the windows to the correct desktops, resize windows, done. At this point, one can usually leave the desktop session with some confidence, the crashed session restore after a login restores the windows at the correct places with the correct sizes. Up until 43.0.3, this went fine - but no more with 44.0. I tried 3 times, and Firefox 44.0 managed to mangle to arrangement in random ways, more serious than ever before. For the time being, I reverted to 43.0.3, and finally settled my setup again, but I cannot avoid version 44 forever. Please, whatever you did to the session management between 43.0.3 and 44.0, revert it - otherwise more people will stand up and cry. Or, even better, use the opportunity to tackle the problem once again - I already offered my help in this, but nobody seems to care. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
In my experience, on Gnome or KDE every GUI window (not only from Mozilla) opens on whichever virtual desktop is current at the time the window opens. In particular: - if I start a GUI application from a desktop shortcut icon or an xterm then quickly change virtual desktops, the GUI will open on the new virtual desktop; - an alert popup relating to some window on a non-current virtual desktop may appear on the current one if it is "floating" (like our Preferences dialog) and not "tied to its window" (like the SeaMonkey button palette). This happens to me the same way for every GUI, be it Firefox, Vim, LibreOffice, some KDE game, whatever. However: When logging out of X11 with some GUIs still open, then some window managers can restore them to the right virtual desktop at the next X11 login. (KDE window managers can even restore gvim compiled with the Gnome session restore feature built-in.) This of course does not apply to Mozilla apps as long as the preferred closedown method for them is Ctrl+Q or File→Quit rather than letting them be closed forcibly by the window manager. I don't know anything of MacOs with or without X, and I left Windows for good at a time when XP SP2 was state-of-the-art so I'm not going to talk about them. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
A couple of (unclean) restarts of Firefox 41.0.2 later, the results are disappointing. The troublesome behaviour, described in https://bugzilla.mozilla.org/show_bug.cgi?id=372650#c29 returned. There's a general problem in the session management, that will only appear under certain conditions (e.g. crashes), I guess, therefore it is so hard to locate. @Mike Hommey: We're suffering from an issue, that originates from the 17.x/18.x area of Firefox, which is IMHO the most prominent nuisance for _heavy_ (multi desktop) Firefox users over all. This bug, started in 2007, is story telling on its own. Adapting to new technologies, such as Wayland on the other hand, will always suffer from teething troubles. Please don't mix these. My desktop environment is able to restore a couple of apps just fine, where I rely on session management for ages (e.g. okular and dolphin). This Firefox issue points to an internal session management issue, that will need to be solved there. If it gets to be solved there using proven desktop environment interfaces, chances are good to find a proper way to adopt to new technologies like Wayland. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
This bug is over 8 years old. It is extremely aggravating. Is there something I can do to help get some traction on it? I routinely have over 50 windows scattered across specific virtual desktops. *Every time* I close and then restart FF I have to manually move them to where I want them. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
Be assured, that nobody cares about the way, how this feature is implemented, as far as it supports any sane WM. KDE applications don't need to do _anything_ for getting session management working, since its support is implemented in the kapp object already IIRC. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
Is there a fix for OS X? -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
*** Bug 1401143 has been marked as a duplicate of this bug. *** -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
Just confirmed that it still is there in firefox nightly 43.0a1 -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
(In reply to Tim Taubert [:ttaubert] from comment #25) > It probably worked with some window managers, I assume not with all. And I > think you're referring to bug 864107. You meants GNOME's monoculture, sorry the world but is not GNOME. Please areadd support for KDE as well as other window managers like fvwm. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
Remark: A long time ago this had worked perfect with Mozilla. But this major feature (at least for all UNIX/Linux users) had been lost. Question: When will this become a fixed one? Also this feature should be included in the test suite (hopefully there is one) for the Linux part. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
(In reply to Dr. Werner Fink from comment #26) > You meants GNOME's monoculture, sorry the world but is not GNOME. Please > areadd support for KDE as well as other window managers like fvwm. You didn't read my comment. I wasn't referring to any WM in particular, just that it probably worked for some and not for others. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
*** Bug 1165325 has been marked as a duplicate of this bug. *** -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
Every Unix Ffx power user may file this issue earlier or later... Since there'a a difference in behaviour depending on the way, Ffx was quit, here are my two reports: Mine are: https://bugzilla.mozilla.org/show_bug.cgi?id=842170 If Ffx is terminated from the user directly, and started later on, all windows, that were distributed over serveral desktops will appear on the current desktop (one screen, several desktops, KDE4 WM) https://bugzilla.mozilla.org/show_bug.cgi?id=1220675 If Ffx is terminated from the window manager (KDE4 again) due to logout from session, the windows are restored on the correct desktops with the correct dimensions, but the content is mixed up: all tabs of one window appear in another. Interestingly, there was an exception: today all went fine. This might be related to testing https://bugzilla.mozilla.org/show_bug.cgi?id=842170, that I performed yesterday, where I had to distribute the ~30 windows to the correct desktops manually. Since these are pretty distinct differences in behaviour, my humble guess is, these are two bugs at least. And while Ffx isn't that far away from full user satisfaction in this regard, it's not there, yet. This is checked with Version 41.0.2, and applies to many predecessors. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982]
It probably worked with some window managers, I assume not with all. And I think you're referring to bug 864107. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 684982] Re: Firefox windows don't restore on correct workspaces
** Bug watch added: Mozilla Bugzilla #842170 https://bugzilla.mozilla.org/show_bug.cgi?id=842170 ** Bug watch added: Mozilla Bugzilla #1220675 https://bugzilla.mozilla.org/show_bug.cgi?id=1220675 ** Bug watch added: Mozilla Bugzilla #1510762 https://bugzilla.mozilla.org/show_bug.cgi?id=1510762 -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 1814174] Re: Xorg crash report after resume
Output of ls -l total 2320 -rw-r- 1 root whoopsie 2373147 Feb 1 13:35 _usr_lib_xorg_Xorg.0.crash -- 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/1814174 Title: Xorg crash report after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's annoying to have to type the password every time, but since root owns the crash log it's necessary. I've used Lubuntu for years. My prior laptop was a Sager with an AMD card. It had the same sort of issue versions ago. I got in the habit of just clicking it away. I think that the Report Crash fails because the log is owned by root and I don't have rights to it. Perhaps adding myself to the whoopsie group would resolve that (and needing sudo to delete too), so I think I'll try that. It's the only thing about Lubuntu that would be a turn off to new users. It's not a high priority thing, because the system works just fine. But it is a nuisance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad
[Desktop-packages] [Bug 1814174] Re: Xorg crash report after resume
1. I'm not sure what you mean by the ID of the bug. The file is owned by root, group whoopsie 2. The contents of the file whoopsie-id are: ad2a60d37ef07a75f5bb69241962893c2ee51bf68be6d93a3b37992aaf2d45370ac7a5094e472b57985c4979bd5355af775f1d483c51977972fa4f743003d70c 3. didn't do this part -- 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/1814174 Title: Xorg crash report after resume Status in xorg-server package in Ubuntu: Incomplete Bug description: Crash Report when resuming from sleep. Similar to https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586223 This is a Sager NP8278 (Clevo P170SM-A) laptop with an Nvidia GeForce GTX 970M, driver 390.77 The crash log doesn't have much info in it IMO, but I uploaded here http://s000.tinyupload.com/?file_id=09497843963607449328 Output from sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date 4.6.5 11/14/2014 Output from uname -a Linux dksager2linux 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output from cat /etc/*ase DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Output from lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06) 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) 00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) 00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5) 00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) 00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) 00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05) 01:00.0 VGA compatible controller: NVIDIA Corporation GM204M [GeForce GTX 970M] (rev a1) 03:00.0 PCI bridge: Texas Instruments XIO2213A/B/XIO2221 PCI Express to PCI Bridge [Cheetah Express] (rev 01) 04:00.0 FireWire (IEEE 1394): Texas Instruments XIO2213A/B/XIO2221 IEEE-1394b OHCI Controller [Cheetah Express] (rev 01) 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411 PCI Express Card Reader (rev 01) 05:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0a) 06:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) The nuisance inspired me to create a script on the desktop called ClearCrashLog.sh (info I got from a YouTube video) ls /var/crash sudo rm /var/crash/* It's annoying to have to type the password every time, but since root owns the crash log it's necessary. I've used Lubuntu for years. My prior laptop was a Sager with an AMD card. It had the same sort of issue versions ago. I got in the habit of just clicking it away. I think that the Report Crash fails because the log is owned by root and I don't have rights to it. Perhaps adding myself to the whoopsie group would resolve that (and needing sudo to delete too), so I think I'll try that. It's the only thing about Lubuntu that would be a turn off to new users. It's not a high priority thing, because the system works just fine. But it is a nuisance. To manage notifications about this bug
[Desktop-packages] [Bug 856736] Re: problem in rendering of hindi fonts on chrome natty (ubuntu 11.04)
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Chromium since that time. Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012. Do you still see a problem related to the one that you reported using currently supported versions of Chromium and Ubuntu? Please let us know if you do and in which version of Ubuntu otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/856736 Title: problem in rendering of hindi fonts on chrome natty (ubuntu 11.04) Status in chromium-browser package in Ubuntu: Incomplete Bug description: The problem is with respect to browser Chrome (I use Ubuntu 11.04 ) and in certain cases such as heading etc the font is not rendered correctly. https://picasaweb.google.com/mightydreams/HindiFontsProblem Here is the page in problem on Chrome https://picasaweb.google.com/mightydreams/HindiFontsProblem#5655127655183416498 A Correctly rendered page should appear like this https://picasaweb.google.com/mightydreams/HindiFontsProblem#5655127704627761410 the link which I tried is http://in.jagran.yahoo.com/ but this problem is there in many other URLs which I open in chrome, there is no such problem when I am using Firefox on Ubuntu. Upon discussing on Ubuntu users technical support I came to know it is some thing similar to https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/828840 Some one can watch this thread https://lists.ubuntu.com/archives/ubuntu-users/2011-September/251264.html https://lists.ubuntu.com/archives/ubuntu-users/2011-September/251295.html My OS Ubuntu 11.04 64 bit. Problem in Chrome version on it 14.0.835.163 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/856736/+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 1164016] Re: restore type-ahead find
I don't know how long it will take, but in the meantime Ubuntu could ship the patch maintained by the Arch community: https://aur.archlinux.org/cgit/aur.git/tree/nautilus-restore- typeahead.patch?h=nautilus-typeahead It looks like this patch is kept up to date pretty well. There is a similar patch for gtk3 to make the file chooser dialog have type-ahead. It's the best of both worlds, since you can still tap ctrl-f to search. Whilst it would be nice for the Nautilus devs to upstream the patch or for there to be a dialog about what kind of patch they might accept (if any), in the meantime distros can include the patch, there is little downside since the patch is maintained and not bit rotting. Canonical would not be committing themselves to maintaining it by including it. -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1814238] Re: deja-dup saves passphrase in /tmp
Thanks for the report! We should definitely fix this! But I'm having trouble reproducing it. I tried backing up and restoring, didn't see any /tmp files. I also wasn't sure whether you mean the encryption passphrase or the password for a network server. So I did both. Still didn't see any /tmp files. (This was all with 37.1-2fakesync1ubuntu0.1 on Ubuntu 18.04.) Can you explain what the steps are for you to get to the point where we are storing the passphrase in /tmp in plaintext? Also, is the file you see world-readable? (Just trying to get a sense of the severity) ** Changed in: deja-dup (Ubuntu) Importance: Undecided => Critical ** Changed in: deja-dup (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1814238 Title: deja-dup saves passphrase in /tmp Status in deja-dup package in Ubuntu: Incomplete Bug description: I have unchecked the "save passphrase" option in deja-dup, but still I have found the file /tmp/deja-dup-HXGLWZ that contains my passphrase in the clear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: deja-dup 37.1-2fakesync1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 10:59:06 2019 SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1814238/+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 1814140] Re: Folders on `Desktop` cannot be opened when nautilus is launched from `Startup Applications`
Possibly integration problem of Btrfs & LVM
I just check on another laptop (ACER, other is 'Schenker'). It's the
same reproducable bug, that you cannot open folders directly form
desktop when you have nautilus added to 'Startup Applications'.
I may have a clue: These 18.10-installations are on Btrfs and the buggy
18.04 was on LVM file system. In the attached journal you will find the
error in between and at the end when I tried to open a desktop folder:
`Φεβ 01 18:54:55 drstoop-opc nautilus[2041]: can't init metadata tree
/home/drstoop/.local/share/gvfs-metadata/home: open: Permission denied`
gvgs-metadata of these file systems require root permissions. So this
bug may be a integration lack of Btrfs and LVM.
** Attachment added: "journal log of buggy session with ACER-laptop"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1814140/+attachment/5235115/+files/jounral_all_ACER.log
--
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/1814140
Title:
Folders on `Desktop` cannot be opened when nautilus is launched from
`Startup Applications`
Status in nautilus package in Ubuntu:
Incomplete
Bug description:
I experience already with 18.04, and now with the newly installed
18.10, that at some point all folders on the Desktop couldn't be
opened anymore. One needs either open it from a regular nautilus
window, or needs to kill & relaunch nautilus-desktop. I don't
understand why but I finally found the trigger for the bug: It only
occurs when nautilus is launched during boot by `Startup Applications`
(so you have a open file manager window waiting already for you when
you boot). If I remove the nautilus boot-launch from `Startup
Applications` the folders can be opened again directly form the
Desktop.
Please find the `/var/syslog` of Ub18.04 and Ub18.10 which I got right after
trying to open a folder:
```sh
# Ubuntu 18.04 /var/syslog
Jan 16 17:59:51 drstoop-pc kernel: [ 657.870793] [UFW BLOCK] IN=wlp112s0
OUT= MAC=01:00:5e:00:00:01:c4:71:54:33:0a:b0:08:00 SRC=192.168.0.1
DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2
Jan 16 18:00:33 drstoop-pc signal-desktop.desktop[4016]:
{"name":"log","hostname":"drstoop-pc","pid":4016,"level":30,"msg":"Sending a
keepalive message","time":"2019-01-16T16:00:33.885Z","v":0}
Jan 16 18:00:34 drstoop-pc nautilus-deskto[4026]: cannot open folder on
desktop, freedesktop bus not ready
# Ubuntu 18.10 /var/syslog
Jan 31 18:26:40 drstoop-pc systemd[1]: Started Cleanup of Temporary
Directories.
Jan 31 18:26:43 drstoop-pc usbmuxd[1076]: [18:26:43.402][1]
config_get_device_record: failed to read
'/var/lib/lockdown/719aba6e85c2a014e186e582e274284be21acc5c.plist': No such
file or directory
Jan 31 18:26:48 drstoop-pc usbmuxd[1076]: [18:26:48.403][1]
config_get_device_record: failed to read
'/var/lib/lockdown/719aba6e85c2a014e186e582e274284be21acc5c.plist': No such
file or directory
Jan 31 18:26:53 drstoop-pc usbmuxd[1076]: [18:26:53.407][1]
config_get_device_record: failed to read
'/var/lib/lockdown/719aba6e85c2a014e186e582e274284be21acc5c.plist': No such
file or directory
Jan 31 18:26:58 drstoop-pc usbmuxd[1076]: [18:26:58.398][1]
config_get_device_record: failed to read
'/var/lib/lockdown/719aba6e85c2a014e186e582e274284be21acc5c.plist': No such
file or directory
Jan 31 18:27:03 drstoop-pc usbmuxd[1076]: [18:27:03.403][1]
config_get_device_record: failed to read
'/var/lib/lockdown/719aba6e85c2a014e186e582e274284be21acc5c.plist': No such
file or directory
```
Thx & cheers!
Max
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: nautilus 1:3.26.4-0ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 31 18:36:24 2019
GsettingsChanges:
b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
b'org.gnome.nautilus.window-state' b'sidebar-width' b'254'
b'org.gnome.nautilus.window-state' b'geometry' b"'969x364+119+1112'"
InstallationDate: Installed on 2019-01-26 (4 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
(20181017.3)
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1814140/+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 1164016] Re: restore type-ahead find
> In reality, > recursive search is useful, and I want to use it, but it's different to > typeahead Exactly, they are two completely different, unrelated things, and if the Nautilus devs can't understand something as elementary as that, Ubuntu shouldn't be using software developed by those people as the default file explorer. This issue is just one example; nautilus developers have taken quite a few "design decisions" that are - ahem - let's say contrary to common sense, degrading usability rather than improve things. Keeping Nautilus as the file explorer means Ubuntu will have to keep struggling with this sort of things and maintaining patches like this one. Of course, if there's no better alternative out there (I find it hard to believe that such a shitty file manager is the best available, but I don't know, it might be), then it'll have to be this. > I do think things will eventually go back this way > (...) I do think Nautilus can satisfy everyone's preferences here How long do we have to wait for them to recapacitate and revert breaking stuff that had been designed correctly in the first place ages ago? -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1164016] Re: restore type-ahead find
Is there any timeline as to when this stupidity is going to be fixed? This is a very very very basic functionality for any file explorer; something any new application should add. Taking it out of a software that has already had it for years and annoying people who rely on it is simply illogical. -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1674200] Re: Chromium Browser Aw, snap error from Ubuntu-mate 16.04.2 Raspberry Pi 3
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Chromium since that time. Do you still see a problem related to the one that you reported using currently supported versions of Chromium and Ubuntu? Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1674200 Title: Chromium Browser Aw,snap error from Ubuntu-mate 16.04.2 Raspberry Pi 3 Status in chromium-browser package in Ubuntu: Incomplete Bug description: Hi I am using Ubuntu-mate 16.04.2 for the Raspberry Pi 3. And I keep getting Aw,Snap Errors! The browser seems to be not working! Every settings does not seems to work! chromium-browser [3625:3625:0320/114233.992729:ERROR:desktop_window_tree_host_x11.cc(1127)] Not implemented reached in virtual void views::DesktopWindowTreeHostX11::InitModalType(ui::ModalType) [3679:3679:0320/114237.810957:ERROR:sandbox_linux.cc(343)] InitializeSandbox() called with multiple threads in process gpu-process. chromium-browser --type=renderer --enable-pinch --primordial-pipe-token=A3381222F37ED40FAA4CCFD4B415750A --lang=en-US --instant-process --enable-offline-auto-reload --enable-offline-auto-reload-visible-only --ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=24.0.0.221 --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553 --disable-accelerated-video-decode --service-request-channel-token=A3381222F37ED40FAA4CCFD4B415750A --renderer-client-id=4 --v8-natives-passed-by-fd --v8-snapshot-passed-by-fd: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == thread->tid' failed. Received signal 4 723193f6 #0 0x76e03dd2 base::debug::StackTrace::StackTrace() #1 0x76e0410c #2 0x72319270 #3 0x723193f6 abort [end of stack trace] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1674200/+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 1576084] Re: Firefox crashes with raspberry pi 3
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. This bug was reported some time ago and there have been many changes in Ubuntu and Firefox since that time. Does anyone still see a problem related to the one that was reported using currently supported versions of Firefox and Ubuntu? Please let us know if you do and in which version of Ubuntu otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: firefox (Ubuntu) Status: Confirmed => Incomplete -- 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/1576084 Title: Firefox crashes with raspberry pi 3 Status in firefox package in Ubuntu: Incomplete Bug description: apport bug collect for mozilla firefox keeps crashing and having issues with you tube html5 with HDMI hook up to the tv. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 46.0+build5-0ubuntu0.16.04.2 Uname: Linux 4.1.19-v7+ armv7l AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ubuntu 1072 F...m pulseaudio /dev/snd/controlC0: ubuntu 1072 F pulseaudio BrokenPermissions: datareporting/archived/2016-04/1461828388387.ad276ece-7545-4b2d-bae4-2ec24b7d2c84.main.jsonlz4 (0o600, wrong owner) saved-telemetry-pings/ad276ece-7545-4b2d-bae4-2ec24b7d2c84 (0o600, wrong owner) BuildID: 20160425115234 Channel: Unavailable CurrentDesktop: MATE Date: Thu Apr 28 16:13:14 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.160 metric 600 Locales: extensions.sqlite corrupt or missing PciNetwork: PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=46.0/20160425115234 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1576084/+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 1702633] Re: Google chrome cannot start with Raspberry Pi 3 Ubuntu-Mate 16.04.2
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Chromium since that time. Do you still see a problem related to the one that you reported using currently supported versions of Chromium and Ubuntu? Please let us know if you do and in which version of Ubuntu otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1702633 Title: Google chrome cannot start with Raspberry Pi 3 Ubuntu-Mate 16.04.2 Status in chromium-browser package in Ubuntu: Incomplete Bug description: [8278:8278:0706/155805.403422:ERROR:process_singleton_posix.cc(253)] readlink(/tmp/.org.chromium.Chromium.umUEz3/SingletonCookie) failed: Permission denied chromium-browser: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == thread->tid' failed. Received signal 4 722083f6 #0 0x76e13d12 base::debug::StackTrace::StackTrace() #1 0x76e13952 base::debug::StackTrace::StackTrace() #2 0x76e13ffc #3 0x72208270 #4 0x722083f6 abort [end of stack trace] Calling _exit(1). Core file will not be generated. chromium-browser: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == thread->tid' failed. Received signal 4 722083f6 #0 0x76e13d12 base::debug::StackTrace::StackTrace() #1 0x76e13952 base::debug::StackTrace::StackTrace() #2 0x76e13ffc #3 0x72208270 #4 0x722083f6 abort [end of stack trace] Calling _exit(1). Core file will not be generated. Received signal 4 761f8f76 #0 0x76e4cd12 base::debug::StackTrace::StackTrace() #1 0x76e4c952 base::debug::StackTrace::StackTrace() #2 0x76e4cffc #3 0x72241270 [end of stack trace] Calling _exit(1). Core file will not be generated. chromium-browser: pthread_getattr_np.c:71: pthread_getattr_np: Assertion `abs (thread->pid) == thread->tid' failed. Received signal 4 722083f6 #0 0x76e13d12 base::debug::StackTrace::StackTrace() #1 0x76e13952 base::debug::StackTrace::StackTrace() #2 0x76e13ffc #3 0x72208270 #4 0x722083f6 abort [end of stack trace] Calling _exit(1). Core file will not be generated. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: chromium-browser 59.0.3071.109-0ubuntu0.16.04.1289 Uname: Linux 4.9.35-v7+ armv7l ApportVersion: 2.20.1-0ubuntu2.6 Architecture: armhf Date: Thu Jul 6 16:04:23 2017 Desktop-Session: 'None' 'None' 'None' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: Load-Avg-1min: 1.10 Load-Processes-Running-Percent: 0.5% Lspci: Error: command ['lspci', '-mmkv'] failed with exit code 1: pcilib: Cannot open /proc/bus/pci lspci: Cannot find any working access method. Lsusb: Bus 001 Device 005: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 004: ID 046d:c315 Logitech, Inc. Classic Keyboard 200 Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1360 bcm2708_fb.fbheight=768 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.chromium-browser.default: CHROMIUM_FLAGS="--ppapi-flash-path=/usr/lib/PepperFlash/libpepflashplayer.so --ppapi-flash-version=25.0.0.148" modified.conffile..etc.default.chromium-browser: [deleted] mtime.conffile..etc.chromium-browser.default: 2017-06-03T11:44:06.716779 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702633/+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 1575673] Re: Chromium keeps crashing with raspberry pi 3
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Chromium since that time. Do you still see a problem related to the one that you reported using currently supported versions of Chromium and Ubuntu? Please let us know if you do and in which version of Ubuntu otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Incomplete ** Changed in: chromium-browser Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1575673 Title: Chromium keeps crashing with raspberry pi 3 Status in Chromium Browser: Incomplete Status in chromium-browser package in Ubuntu: Incomplete Bug description: I am cuurently using raspberry pi 3 with ubuntu-mate 16.04... Chromium browser keeps crashing. It cannot seems to run or launch. Can you guys please fix this issues To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1575673/+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 1759462] Re: Keyboard shortcuts not operational on 18.04
Nvm, ignore my previous comment. Correct solution is posted here: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1188569 https://code.launchpad.net/~unity7maintainers/+archive/ubuntu/unity7-desktop -- 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/1759462 Title: Keyboard shortcuts not operational on 18.04 Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: After installing 18.04, I noticed that certain keyboard shortcuts no longer function. It appears to be related to the shortcuts that gnome-settings-daemon control as my shortcuts that are provided by my desktop (Budgie) still function. Some examples are: * Media keys for volume up/down/mute * ctrl-alt-t for the terminal. I tried changing the shortcut to test. Same behaviour. I double checked, and it looks like the needed daemon is still running, ``` dustin3337 0.0 0.2 500736 22216 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-keyboard dustin3338 0.0 0.3 943372 25732 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-media-keys dustin3343 0.0 0.0 274908 5844 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-mouse dustin3345 0.0 0.3 519896 25144 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-power dustin3348 0.0 0.1 346004 10212 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-print-notifications dustin3351 0.0 0.0 374684 7952 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-smartcard dustin3355 0.0 0.1 329584 8064 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sound dustin3361 0.0 0.1 449708 9856 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-sharing dustin3367 0.0 0.0 272416 4772 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy dustin3375 0.0 0.0 420028 5804 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-rfkill dustin3383 0.0 0.2 507120 23244 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-wacom dustin3385 0.0 0.3 498040 25040 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-xsettings dustin3387 0.0 0.0 274900 5936 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-a11y-settings dustin3392 0.0 0.2 496016 22044 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-clipboard dustin3395 0.0 0.3 810156 25976 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-color dustin3396 0.0 0.2 471656 21080 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-datetime dustin3400 0.0 0.0 361196 7116 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-housekeeping dustin3433 0.0 0.1 505404 12576 ?Sl 21:03 0:00 /usr/lib/gnome-settings-daemon/gsd-printer dustin9776 0.0 0.0 18188 1032 pts/1S+ 21:19 0:00 grep --color=auto gnome-settings-daemon ``` Reboot does not seem to help. However, occasionally the shortcuts do seem to work - but only very occasionally. Any other info needed? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Mar 27 21:12:18 2018 InstallationDate: Installed on 2018-03-05 (22 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) SourcePackage: gnome-settings-daemon 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/1759462/+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 1769409] Re: Support for global menu
Yes, I discontinued the develop of that extension with base on the repercussion of the Gnome/Gtk developers to drop the support for Gtk- Modules in newly Gtk releases started in GTK-4.0 and upper. For convenience the direct link to the upstream desition is here: https://gitlab.gnome.org/GNOME/gtk/issues/1132 How also Ubuntu is part of Gnome, the desition of not support something is also his own responsibility now and in consequence something that Ubuntu will need to assume, not a third party like me or some one else externally. -- 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/1769409 Title: Support for global menu Status in gnome-shell package in Ubuntu: Won't Fix Bug description: The move to Gnome from Unity was ok except for two major features that got lost and those are global menus and pixel saving when maximized. Are there any chances of official support in future releases? Gnome extension for global menus exists https://github.com/lestcape /Gnome-Global-AppMenu and that may be used as a starting point. The Ubuntu team already did similar move by including the plugin dash-to- dock. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769409/+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 1164016] Re: restore type-ahead find
I don't think it's true that an option is always good. I think software should endeavour to have decent default options, and if multiple use cases can be accommodated without an option, then that is preferable. But you're right, a recursive search with ctrl-f vs typeahaed with simple typing would accomplish what everyone wants without an option. I'm using the 'search in current folder only' setting in order to make the search more like typeahead, but this has the downside that I have to go into the settings to do an actual recursive search. In reality, recursive search is useful, and I want to use it, but it's different to typeahead and it's a shame I have to pick one or the other. Ideally for me would be typing is just going to select things similarly to the old typeahead behaviour, and ctrl-f would do a search, either in the current folder or recursively depending on a checkbox that would ideally be in the main interface next to the search box rather than in the settings menu - since one often wants one or the other, it's not really an all-time preference. I do think things will eventually go back this way. There is currently wasted effort trying to make search meet the requirements of type-ahead, whereas this would be unnecessary if typeahead existed too. Search is becoming a bit of a frankenstein trying to be both, with returning items from the current folder first, and having the search-in-current-folder- only setting being global. It should just be search - features should do one thing each instead of trying to please everyone. I understand that search has been improved a lot in response to complaints about type-ahead being removed, and this shows that the devs are trying to meet people's use cases. But ultimately I think it is misguided and making the search implementation more complex than it otherwise would need to be. They are really are different features. So I know there has been a lot of vitriol over this issue, but I would encourage the nautilus devs to consider that they should become different features once again. Ctrl-f to search will not confuse anybody, type-ahead will not confuse anybody, whereas the current search is trying to be both and so can behave unexpectedly in terms of the order of search results and whether the search is recursive. Presumably this means code complexity too. I also understand that the old type-ahead code was holding back the codebase and so it was desirable to excise it. I imagine new typeahead functionality, working as much as possible within the current codebase and its future directions, would be more amenable to nautilus dev approval than just restoring the old code. For example, we probably don't need the popup box in the bottom right as you type. It should just be type a few characters and have a few-second timeout before forgetting them, just like it is on other platforms such as windows and macos (I think). It seems similar to me to the case or removing nautilus handling the desktop. The code was holding back the codebase, but now we see that a desktop extension for gnome-shell is in development by the main nautilus dev. I do think Nautilus can satisfy everyone's preferences here, and I do think typeahead will eventually be re implemented once tensions die down, especially if the nautilus devs can do it on their terms instead of rejecting a patch that just re-adds code that they don't want to maintain. A good typeahead implementation would even allow Nautilus to remove code that customises how the search works to make it more useful as typeahead - there would no longer be a need for that if typeahead were present in its own right. -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1662765] Re: Crashes stating "illegal instruction" on Rasberry Pi Model B
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Chromium since that time. Do you still see a problem related to the one that you reported using currently supported versions of Chromium and Ubuntu? Please let us know if you do and in which version of Ubuntu otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1662765 Title: Crashes stating "illegal instruction" on Rasberry Pi Model B Status in chromium-browser package in Ubuntu: Incomplete Bug description: When launched from the command line, I simply get "Illegal instruction" after a few seconds. Tried with chromium- browser_47.0.2526.106-0ubuntu0.15.04.1.1192_armhf.deb and chromium- browser_51.0.2704.79-0ubuntu0.14.04.1.1121_armhf.deb. Many thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1662765/+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 1812014] Re: keyboard not responding after suspend after some time
journalctl -b-1 > prevlog.txt ** Attachment added: "prevlog.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+attachment/5235109/+files/prevlog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1115701] Re: GNOME Printer Setup Tool: HP printers discovered by both usb and hp CUPS backends -> Two indistinguishable entries in the list of discovered printers
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1115701 Title: GNOME Printer Setup Tool: HP printers discovered by both usb and hp CUPS backends -> Two indistinguishable entries in the list of discovered printers Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Bug description: I have several HP printers. If I connect one of them via USB and click the "+" button to add a new printer in GNOME's printer setup tool, I get two entries where a user will not see the difference: HP-LaserJet-3390 HP-LaserJet-3390-2 To find out why I got two entries, I added two print queues, one using the first entry, another using the second entry. Then I ran the command lpstat -v and got device for HP-LaserJet-3390: usb://HP/LaserJet%203390?serial=00CNMJP81545 device for HP-LaserJet-3390-2: hp:/usb/HP_LaserJet_3390?serial=00CNMJP81545 So the first comes from the HP LaserJet 3390 discovered via the "usb" CUPS backend and the second from the same printer via the "hp" backend. The preferred backend is the latter, as it is made by HP especially for HP printers. Therefore there should be only one entry, using the "hp" backend. system-config-printer does this correctly, so usingf the D-Bus service of system-config-printer one should be able to join these entries to one using the "hp" backend. Note that this is not a duplicate of bug 1115669. That bug is about making duplicate entries distinguishable, this bug is about making the "hp" backend used with HP printers. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1115701/+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 1115669] Re: GNOME Printer Setup Tool: List of discovered printers should better describe duplicate entries
** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1115669 Title: GNOME Printer Setup Tool: List of discovered printers should better describe duplicate entries Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Triaged Bug description: When adding a printer a list of discovered printers is shown. If there are duplicate entries, for example if the same network printer is discovered with different network protocols (LPD, IPP, ...), these entries are usually grouped into one by using the D-Bus service of system-config-printer. system-config-printer groups entries coming from the network connection of the printer and groups entries coming from the USB connection of the printer, but it does not group network results with USB results, as system-config-printer separates them by a tree view. This means that when one connects one printer by both network and USB one gets two entries, one generated from all appearances under the discovered network printers and one from all appearances under the discovered USB printers (and if theis printer does Bluetooth there would be a third entry). Now the g-c-c printer tool lists these entries as -2 This way the user does not know which is the network printer and which is the USB printer. The results dhould look like (USB) (Network) To reproduce connect a printer with both network and USB (or Bluetooth) input by both network and USB, then try to set it up with the preferred connection type. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1115669/+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 1548312] Re: excessive ram and swap usage
This issue was reported as: https://bugs.chromium.org/p/chromium/issues/detail?id=588707 which was marked as a duplicate of: https://bugs.chromium.org/p/chromium/issues/detail?id=393395 and is showing "Fixed" as of February 2018. No subsequent comments here or upstream so closing as being fixed. ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1548312 Title: excessive ram and swap usage Status in chromium-browser package in Ubuntu: Fix Released Bug description: Chromium Version : 48.0.2564.82 Ubuntu 15.10 (64-bit) URLs (if applicable) : Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: Firefox:better (at point 4 it uses 1.703mb of ram and 0 swap; at point 7: 2.223mb of ram and 0 swap) ver. 44.0.2 IE: What steps will reproduce the problem? 1. Power on pc 2. check ram and swap usage (for me was 755mb/0mb) 3. open Chromium (ram 1.238mb / swap 0mb) 4. open 15 tabs (ram 3.049mb / swap 37mb) 5. open new window (ram 3.126 mb / swap 37mb) 6. open 4 tabs (ram 3.488 / swap 210mb) 7. browse the pages and click on some links (ram 3.329mb / swap 397mb) 8. continue to browse: ram goes up (up to 3.4 gb used ) and a lot of swap (up to 1.4gb) resulting in unstable / non responsive system What is the expected result? uses less ram What happens instead? uses a lot of ram and swap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1548312/+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 1115703] Re: GNOME Printer Setup Tool: "-" button deletes printers without confirmation
** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1115703 Title: GNOME Printer Setup Tool: "-" button deletes printers without confirmation Status in gnome-control-center: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Bug description: If I click the "-" button in the printer setup tool the selected printer gets immediately removed, without any confirmation pop-up. One can easily remove the wrong printer or easily click "-" instead of "+", so it happens easily that one accidentally removes a print queue. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1115703/+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 1038110] Re: Chromium doesn't restart on the correct head in multi-head envs
Hi Barry, Is this still an issue? On my dual screen setup, using Chromium 71 and Ubuntu 18.04, Chromium starts on the display on which it was last closed. Paul White [Ubuntu Bug Squad] ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1038110 Title: Chromium doesn't restart on the correct head in multi-head envs Status in chromium-browser package in Ubuntu: Incomplete Bug description: I have a dual-headed machine. When I gracefully exit Chromium and restart it (e.g. after a reboot), it does not start on the correct screen. I run Chromium on the right screen but it always restarts on the left screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1038110/+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 1284122] Re: unable to change check spelling language in an textarea without refreshing the page
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1284122 Title: unable to change check spelling language in an textarea without refreshing the page Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hello, chromium browser is still unable to change check spelling language in an textarea (via right click) without refreshing the page (which results to losing the data input and is frustrating anyway)... Firefox, to the contrary, does not have problem to change it on-the- fly. But it seems FF uses some different mechanism, because it looks slightly different - see the attachments. There must be a bug somewhere :( ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 32.0.1700.107-0ubuntu0.13.10.1~20140204.972.1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 14:28:11 2014 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2013-10-26 (121 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) MarkForUpload: True SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1284122/+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 1284122] Re: unable to change check spelling language in an textarea without refreshing the page
Confirming issue is still current with Chromium 71 (Ubuntu 18.04) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1284122 Title: unable to change check spelling language in an textarea without refreshing the page Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hello, chromium browser is still unable to change check spelling language in an textarea (via right click) without refreshing the page (which results to losing the data input and is frustrating anyway)... Firefox, to the contrary, does not have problem to change it on-the- fly. But it seems FF uses some different mechanism, because it looks slightly different - see the attachments. There must be a bug somewhere :( ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 32.0.1700.107-0ubuntu0.13.10.1~20140204.972.1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Feb 24 14:28:11 2014 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/usr/share/upstart/xdg:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2013-10-26 (121 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) MarkForUpload: True SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1284122/+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 1792722] Re: Restarting unity-settings-daemon screws up Nautilus settings, needs Nautilus restart
Is the fix available for 16.04? -- 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/1792722 Title: Restarting unity-settings-daemon screws up Nautilus settings, needs Nautilus restart Status in nautilus package in Ubuntu: Fix Released Bug description: UPDATE: see comment 2 From time to time, these two bugs resurface, which were fixed ages ago: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1130722 https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1731985 and also: the font type and/or size in Nautilus changes to a smaller and less readable font. The three things always reappear at once. Then everything goes back to expected; I'm not sure if that's when I get some new updates installed or when I just reboot. It seems to me that all these issues are things that got changed upstream in Nautilus, but patched in Ubuntu because Ubuntu maintainers have some more common sense than the Nautilus developers. I don't know if (a) sometimes someone forgets to apply some patches, and an unpatched version slips into Ubuntu's packages until somebody corrects it, or (b) some configuration gets randomly lost/changed and then restored/changed back on reboot. Either way, it's f***ing annoying. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 15 18:25:09 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1799 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) 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/1792722/+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
