[Desktop-packages] [Bug 1838485] Re: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
[Expired for policykit-1 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: policykit-1 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1838485 Title: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in policykit-1 package in Ubuntu: Expired Bug description: I don't have Window. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: policykit-1 0.105-14.1ubuntu0.5 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Tue Jul 30 11:19:23 2019 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2019-07-27 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: policykit-1 Title: package policykit-1 0.105-14.1ubuntu0.5 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1838485/+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 379015] Re: Asterisk showing new messages is not shown at topmost level
Launchpad has imported 6 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1472463. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-06-30T16:06:14+00:00 Gfmozillabug wrote: Created attachment 8989004 thunderbird-folder_unread_indicator.odg Thunderbird 52.8.0 64-bit Folders and Message Lists Ubuntu Linux 18.04 Enhancement Request - Summary: Thunderbird enhancement suggestion by Christoph Jungling at UbuntuBugs #379015: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/379015 When you have a directory tree/hierarchy of mail subfolders, give the top of the directory tree an indicator of how many unread messages are in any of the subfolders. See attached drawing with the suggested location of the new indicator (the "(239)" in red beside label of the top of the folder tree). Also, for each folder containing sub-folders with new emails should indicate the summarized number of unread mails in its underlying folder hierarchy. Similar to closed Mozilla Bug #235956 which is listed as closed/fixed but that feature doesn’t appear to be present in current version. Thanks (on behalf of Christoph) G Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/379015/comments/16 On 2018-09-30T18:57:25+00:00 Wls220spring wrote: Created attachment 9013166 msgcount.png That attachment appears to show what I have when I enable the Menu bar and enable View > Layout > Folder Pane Columns. That adds a Total column to the Folder Pane. The user may have to adjust column width. It is in Thunderbird 52.x.x and 60.0. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/379015/comments/19 On 2018-09-30T19:07:57+00:00 Gfmozillabug wrote: Wow, that's great, Walt! I will email the user right away and get back to you as to their response. Thanks! :) G Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/379015/comments/20 On 2018-09-30T19:42:43+00:00 Gfmozillabug wrote: Hi again Walt, Based on your picture, in the Diane folder, is there one unread email and 72 total emails (71 of them are already read)? Do you have any folders that have subfolders that have unread emails in those subfolders? In your picture, would that be "Verison" folder that has the "heart" symbol and the number 1? That's what I also get on my Ubuntu 18.04, TB 52.9.1. The user is in a different language (German, I think) - does that make a difference? And he does not get the number with the "heart" symbol beside the top folder of a collapsed set of subfolders. See attached original screen print from user ( I will attach it next). Thanks G Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/379015/comments/21 On 2018-09-30T19:45:53+00:00 Gfmozillabug wrote: Created attachment 9013172 User Original screen print - missing unread count beside top folders.png User's original screen print of subfolders, showing no count of unread messages beside top folder Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/379015/comments/22 On 2019-09-28T08:45:54+00:00 Unicorn-consulting wrote: (In reply to g from comment #4) > User's original screen print of subfolders, showing no count of unread > messages beside top folder The top folders children are visible, so it gets no visible counts. If the folder is collapsed then counts are made visible Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/379015/comments/24 ** Changed in: thunderbird Status: Unknown => New ** Changed in: thunderbird Importance: Unknown => Medium -- 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/379015 Title: Asterisk showing new messages is not shown at topmost level Status in Mozilla Thunderbird: New Status in thunderbird package in Ubuntu: Confirmed Bug description: Binary package hint: thunderbird I use filters to put new received and sent mails (the latter with support of "Send Filter 1.0") into folders. If the destination folder is somewhat deeper in the folder hierarchy this folder alone shows the asterisk and the number in braces indicating that new messages have arrived. Well, if the folder structure is collapsed, the highest visible folder indicates unread mails by beeing
[Desktop-packages] [Bug 1514474] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: tex-common (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1514474 Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in tex-common package in Ubuntu: Fix Released Bug description: dist-upgrade from wily to xenial ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tex-common 6.04 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu4 Architecture: amd64 Date: Mon Nov 9 09:56:09 2015 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2011-07-12 (1580 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.3ubuntu1 apt 1.0.10.2ubuntu1 SourcePackage: tex-common Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2011-12-23 (1416 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1514474/+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 1844422] Re: WPA3-SAE support
above automated response is correct - it's three backported commits. There should be more before it's done though, so consider this "something to test things out". The network-manager UI does not yet have SAE / WPA3 personal support in this backport, and doesn't look like that's available upstream yet - at least not in the network-manager git. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1844422] Re: WPA3-SAE support
The attachment "Backport of upstream support" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1760068] Re: Wrong resolution at unlock screen
ls /usr/lib/x86_64-linux-gnu/nvidia* tells "No such file or directory" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1760068 Title: Wrong resolution at unlock screen Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: After coming out of suspend - the unlock screen is at 640x480 resolution. Expect to see unlock screen at 1920x1080 resolution. Using nvidia-340. Previously tested using nouveau driver where resolution at unlock screen was correct. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 11:31:20 2018 InstallationDate: Installed on 2017-09-02 (209 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+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 1845810] Re: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor
> I'm using a manually reinstalled Ubuntu Bionic Actually it looks like I upgraded up to it from Artful. -- 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/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in alsa-driver package in Ubuntu: New Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR: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/alsa-driver/+bug/1845810/+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 1845810] [NEW] [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor
Public bug reported: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic 4.15.0-60.67 BAD: linux-image-4.15.0-62-generic 4.15.0-62.69 BAD: linux-image-4.15.0-64-generic 4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers and not the headset as required. I have tried messing with alsamixer but haven't found anything to explain or reduce the noise. Switching to a previous kernel fixes the problem immediately with no settings change required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robie 2126 F pulseaudio robie 3648 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 23:51:05 2019 InstallationDate: Installed on 2017-05-11 (870 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago) dmi.bios.date: 03/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.11.0 dmi.board.name: 00GCYR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic regression-update -- 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/1845810 Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor Status in alsa-driver package in Ubuntu: New Bug description: Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise in my headphones has increased to unreasonable levels. In linux- image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise was present but at a bearable level, which I had always assumed was a hardware design issue. Now, with the increased noise floor, the headphone socket is essentially unusable. This is a regression in a stable release (Bionic). The problem consistently reproduces as follows: OK: linux-image-4.15.0-58-generic 4.15.0-58.64 BAD: linux-image-4.15.0-60-generic4.15.0-60.67 BAD: linux-image-4.15.0-62-generic4.15.0-62.69 BAD: linux-image-4.15.0-64-generic4.15.0-64.73 Steps to reproduce: Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything is on defaults. 1. Boot with no headphones connected 2. Log in 3. Plug the headphones in Expected: normal noise level Actual: very high noise level. Playback does work correctly but the SnR is terrible. The "Select Audio Device" prompt appears, but the noise problem is present before I make a selection. If I select Headphones or Headset (I'm using a headset) then the noise remains after a brief (~0.5s) interruption. If I select Microphone then the noise goes, but then the audio comes through the speakers
[Desktop-packages] [Bug 1724876] Re: libreoffice soffice.bin using 100% cpu
Here's another screenshot showing the *massive* difference in total CPU load that I made simply by calling `pkill soffice.bin`! ** Attachment added: "HUGE total CPU drop after calling `pkill soffice.bin`" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876/+attachment/5292391/+files/Selection_016_edit.png -- 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/1724876 Title: libreoffice soffice.bin using 100% cpu Status in libreoffice package in Ubuntu: Confirmed Bug description: With literally every action in libreoffice Calc, CPU usage goes to 100% due to soffice.bin, and stays on 100% for minutes. To the extend that libreoffice calc is UNUSABLE for anything that has to do with spreadsheets. As far as I am concerned, this is a critical bug because it makes the program unusable, and often even the complete computer due to the high cpu load. - 'Every action' includes typing as much as one single letter in a cell. Or opening the file. - the file I am working on is only 1.1Mb in size - the same file used to open fine in previous versions of libreoffice. what I've tried so far - without any improvement in speed: - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per object (no solution) - automatic calculation has been turned off (no solution) - libreoffice-gnome and libreoffice-gtk have been removed (no solution) - purged and reinstalled libreoffice. (no solution) - created new user profile - also no resolve System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD. Libreoffice: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876/+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 1845809] [NEW] Yaru dark is not completely dark after upgrade 19.04 to 19.10
Public bug reported: Yaru-dark worked fine until upgraded from 19.04 to 19.10. Now some dropdown menus are always light (see the screenshot). Tried to change it to light/default and back - did not help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: yaru-theme-gnome-shell 19.10.3 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 29 00:31:56 2019 Dependencies: InstallationDate: Installed on 2018-11-13 (319 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "sshot.png" https://bugs.launchpad.net/bugs/1845809/+attachment/5292392/+files/sshot.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1845809 Title: Yaru dark is not completely dark after upgrade 19.04 to 19.10 Status in yaru-theme package in Ubuntu: New Bug description: Yaru-dark worked fine until upgraded from 19.04 to 19.10. Now some dropdown menus are always light (see the screenshot). Tried to change it to light/default and back - did not help. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: yaru-theme-gnome-shell 19.10.3 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 29 00:31:56 2019 Dependencies: InstallationDate: Installed on 2018-11-13 (319 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1845809/+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 1724876] Re: libreoffice soffice.bin using 100% cpu
FYI these are the tweaks I've made to my Ubuntu 18 installation, in case any of them triggered or shed light on the LibreOffice issue: https://electricrcaircraftguy.github.io/20190919-post_ubuntu_18_todos.html. -- 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/1724876 Title: libreoffice soffice.bin using 100% cpu Status in libreoffice package in Ubuntu: Confirmed Bug description: With literally every action in libreoffice Calc, CPU usage goes to 100% due to soffice.bin, and stays on 100% for minutes. To the extend that libreoffice calc is UNUSABLE for anything that has to do with spreadsheets. As far as I am concerned, this is a critical bug because it makes the program unusable, and often even the complete computer due to the high cpu load. - 'Every action' includes typing as much as one single letter in a cell. Or opening the file. - the file I am working on is only 1.1Mb in size - the same file used to open fine in previous versions of libreoffice. what I've tried so far - without any improvement in speed: - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per object (no solution) - automatic calculation has been turned off (no solution) - libreoffice-gnome and libreoffice-gtk have been removed (no solution) - purged and reinstalled libreoffice. (no solution) - created new user profile - also no resolve System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD. Libreoffice: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876/+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 1021375] Re: Nautilus says the USB stick is read only when it is not
I know I'm not running the latest LTS, but 16.04, yet I tried Etienne's advice (because it seems to make perfect sense), but fsck wasn't allowed to fix a FAT-mismatch: sudo fsck.vfat /dev/sdf1 fsck.fat 3.0.28 (2015-05-16) FATs differ but appear to be intact. Use which FAT ? 1) Use first FAT 2) Use second FAT ? 1 Perform changes ? (y/n) y /dev/sdf1: 25 files, 445911/487648 clusters Writing 1950600 bytes at 2243584 failed: Operation not permitted Seems like the readonly even applies to "sudo fsck". Permissions of the block device are: brw-rw 1 root disk 8, 81 Sep 28 23:04 /dev/sdf1 As it seems that this issue is still open, I hope that maybe someone might find this information useful for debugging. Thanks for any hints! -- 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/1021375 Title: Nautilus says the USB stick is read only when it is not Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in thunar package in Ubuntu: Confirmed Bug description: First time I use an USB drive since I updated to 12.04 and I found a really annoying bug on Nautilus. Nautilus claims that the destination drive is read-only when in fact it is not. How to reproduce: 1. Connect a USB stick drive to your competer. 2. The USB will appear in the desktop. 3. Open two Nautilus windows one in your home folder, other in the USB stick drive. 4. Select any file from your home folder (small enough to fit the free space in the USB drive) 5. Drag the file and drop it in the USB drive window. -- Nautilus will say that it cannot copy the file because the destination is read ony -- If you try the copy the same file with the terminal you will see that the file is copied without problem, other programs like gedit or LibreOffice can write in the usb stick drive just fine. It is not a problem with the USB stick, as shown here: [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd [ 6232.426378] scsi8 : usb-storage 2-1:1.0 [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP PQ: 0 ANSI: 0 CCS [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0 [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 GB/1.86 GiB) [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.210138] sdb: sdb1 [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk The permisions on the removable drive are set correctly: sergio@shana:/media$ ls -lah total 12K drwxr-xr-x 3 root root 4,0K jul 5 10:20 . drwxr-xr-x 23 root root 4,0K jul 3 11:01 .. drwx-- 5 sergio sergio 4,0K dic 31 1969 DESIGNPLUS There is enough free space in the drive: sergio@shana:/media/DESIGNPLUS$ df -h S.ficheros Tamaño Usado Disp Uso% Montado en /dev/sda2 50G 5,5G 42G 12% / udev 1,5G 4,0K 1,5G 1% /dev tmpfs579M 872K 579M 1% /run none 5,0M 0 5,0M 0% /run/lock none 1,5G 1,1M 1,5G 1% /run/shm /dev/sda1497M 113M 360M 24% /boot /dev/sda5245G 111G 122G 48% /home /dev/sdb11,9G 681M 1,2G 36% /media/DESIGNPLUS A file can be copied to the USB stick using the cp command for example. sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS sergio@shana:~/Trash$ cd /media/DESIGNPLUS sergio@shana:/media/DESIGNPLUS$ ls -lah total 204K drwx-- 5 sergio sergio 4,0K jul 5 10:38 . drwxr-xr-x 3 root root 4,0K jul 5 10:20 .. -rw-r--r-- 1 sergio sergio 117K jul 5 10:14 ._Screen Shot 2012-06-30 at 8.50.37 AM.png -rw-r--r-- 1 sergio sergio 55K jun 30 08:51 Screen Shot 2012-06-30 at 8.50.37 AM.png drwx-- 4 sergio sergio 4,0K jul 5 10:05 .Spotlight-V100 drwx-- 2 sergio sergio 4,0K jul 5 10:05 .Trashes -rw-r--r-- 1 sergio sergio 4,0K jul 5 10:05 ._.Trashes -rw-r--r-- 1 sergio sergio 73 jul 5 10:38 wireless.txt But nautilus just dennies to copy the file claming that the destination is read only, when it is not. I tested it with two different USB sticks in two different computers running Ubuntu 12.04 and the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1021375/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1724876] Re: libreoffice soffice.bin using 100% cpu
Note: I'm running Ubuntu 18.04 with this LibreOffice: Version: 6.3.1.2 Build ID: b79626edf0065ac373bd1df5c28bd630b4424273 CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded Here's a screenshot of my System Monitor, attached. Notice soffice.bin is really sucking up my system hard with 24% total CPU usage, which is ~100% of one core since I only have 4 cores! It doesn't make any sense. ** Attachment added: "Selection_015.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876/+attachment/5292390/+files/Selection_015.png -- 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/1724876 Title: libreoffice soffice.bin using 100% cpu Status in libreoffice package in Ubuntu: Confirmed Bug description: With literally every action in libreoffice Calc, CPU usage goes to 100% due to soffice.bin, and stays on 100% for minutes. To the extend that libreoffice calc is UNUSABLE for anything that has to do with spreadsheets. As far as I am concerned, this is a critical bug because it makes the program unusable, and often even the complete computer due to the high cpu load. - 'Every action' includes typing as much as one single letter in a cell. Or opening the file. - the file I am working on is only 1.1Mb in size - the same file used to open fine in previous versions of libreoffice. what I've tried so far - without any improvement in speed: - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per object (no solution) - automatic calculation has been turned off (no solution) - libreoffice-gnome and libreoffice-gtk have been removed (no solution) - purged and reinstalled libreoffice. (no solution) - created new user profile - also no resolve System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD. Libreoffice: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876/+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 1724876] Re: libreoffice soffice.bin using 100% cpu
Exact same as TLRobb notes just above: 100% usage of one cpu core for an extended period (hours?)--no idea what it's doing, but on a slow computer with few cores it's really rendering my computer nearly unusable just to have LibreOffice open in the background with a document minimized while I do something else on the computer. Please work on this bug. It's making LibreOffice really affect my computer negatively. -- 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/1724876 Title: libreoffice soffice.bin using 100% cpu Status in libreoffice package in Ubuntu: Confirmed Bug description: With literally every action in libreoffice Calc, CPU usage goes to 100% due to soffice.bin, and stays on 100% for minutes. To the extend that libreoffice calc is UNUSABLE for anything that has to do with spreadsheets. As far as I am concerned, this is a critical bug because it makes the program unusable, and often even the complete computer due to the high cpu load. - 'Every action' includes typing as much as one single letter in a cell. Or opening the file. - the file I am working on is only 1.1Mb in size - the same file used to open fine in previous versions of libreoffice. what I've tried so far - without any improvement in speed: - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per object (no solution) - automatic calculation has been turned off (no solution) - libreoffice-gnome and libreoffice-gtk have been removed (no solution) - purged and reinstalled libreoffice. (no solution) - created new user profile - also no resolve System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD. Libreoffice: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876/+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 1844422] Re: WPA3-SAE support
On one side this fixes SAE / WPA3 personal support on the other, you still can't edit or update WPA3 connections in the GUI components. If you use nmtui or try connecting to WPA3 though, it works. (I've tested this) Consider upstream to be "nearing complete" I've been working on WPA3 support on some AP series so I very much can test this. Up until now I've been using manual settings on a custom compile of wpa_supplicant (etc). Attached is the backported patches (from networkmanager master, they're not even in any tags yet) I'm going to keep an eye on networkmanager development and follow this report. However I'd class support as "not yet ready". ** Patch added: "Backport of upstream support" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+attachment/5292389/+files/nm-sae-backport.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1792167] Re: Display size detected incorrectly
Bug still present. In my multi-display setup a 40" display is reported as a 7" in Ubuntu. -- 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/1792167 Title: Display size detected incorrectly Status in mutter package in Ubuntu: Expired Status in qtbase-opensource-src package in Ubuntu: Expired Bug description: My external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls! It seems like many users have the same problem (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable Qt auto scaling. I think the solution should be to fix the size detection instead. It seems not related to the display server, compositor or window manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on Wayland). Further, it seems not related to graphics driver, since I personally use the open source driver with my internal Intel card, whereas someone else uses a proprietary Nvidia driver (https://askubuntu.com/q/1066879/206608). If it is in the wrong category, please move it / add the corresponding packages. If you need any further information to tackle the problem, just tell me! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-09-05 (372 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: qtbase-opensource-src PackageArchitecture: amd64 Tags: bionic Uname: Linux 4.18.7-041807-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo vboxusers video voice _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+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 1845802] [NEW] Smeared top panel and hint tips on Plank and browser icon
Public bug reported: It would take more than one snapshot, but this all happens on Dell external monitor: 1. Top panel has blurred/smeared icons. 2. Hint tips on browser icons are also smeared. 3. Plank tips are smeared or blurry on some icons. Screenshot after exiting full screen (could not restore to full) and top panel was set to autohide and would not budge. https://justpaste.it/7rqzp Otherwise, everything is okay on laptop monitor itself. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sat Sep 28 13:23:08 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2019-09-28 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) MachineType: Hewlett-Packard HP EliteBook 8460p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=64852f66-77ef-4b0f-b326-aec23cfe7db3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2017 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.asset.tag: CNU148133S dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: LQ168AW#ABA dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1845802 Title: Smeared top panel and hint tips on Plank and browser icon Status in xorg package in Ubuntu: New Bug description: It would take more than one snapshot, but this all happens on Dell external monitor: 1. Top panel has blurred/smeared icons. 2. Hint tips on browser icons are also smeared. 3. Plank tips are smeared or blurry on some icons. Screenshot after exiting full screen (could not restore to full) and top panel was set to autohide and would not budge. https://justpaste.it/7rqzp Otherwise, everything is okay on laptop monitor itself. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sat Sep 28 13:23:08 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2019-09-28 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) MachineType: Hewlett-Packard HP EliteBook 8460p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=64852f66-77ef-4b0f-b326-aec23cfe7db3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2017 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.65 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.asset.tag: CNU148133S dmi.chassis.type: 10 dmi.chassis.vendor:
[Desktop-packages] [Bug 1844422] Re: WPA3-SAE support
** Summary changed: - WPA3-support + WPA3-SAE support -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-SAE support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1844422] Re: WPA3-support
** Description changed: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 + + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi- networks using WPA3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1845801] [NEW] Trying to log in just takes me back to the login screen. Killing gnome-session-binary fixes it.
Public bug reported: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash eoan ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: Trying to log in just takes me back to the login screen. Killing gnome-session-binary fixes it. Status in xorg package in Ubuntu: New Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
[Desktop-packages] [Bug 1844422] Re: WPA3-support
Indeed. 19.04 shipped with wpasupplicant 2.6, which had no support at all for WPA3, although network-manager 1.16 already started to support it. With 19.10 shipping wpasupplicant 2.9 and network-manager 1.20, there's just no excuse. I have WPA2+WPA3 mixed-mode deployed on my home network and all my connections are downgraded to WPA2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1844422] Re: WPA3-support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844422 Title: WPA3-support Status in network-manager package in Ubuntu: Confirmed Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844422/+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 1845797] Re: Microphone not detected Lenovo Yoga S940
** Tags added: disco ** Tags added: eoa ** Tags removed: eoa ** Tags added: eoan -- 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/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1845797/+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 1748429] Re: [snap] Libreoffice uses the adwaita gtk theme
Awesome, thanks for confirming :) ** Changed in: libreoffice (Ubuntu) Status: Incomplete => Fix Released -- 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/1748429 Title: [snap] Libreoffice uses the adwaita gtk theme Status in libreoffice package in Ubuntu: Fix Released Bug description: Ubuntu 17.10 Installed the snap via https://forum.snapcraft.io/t/call-for-testing-libreoffice-6-0-0/3917 sudo snap install libreoffice --candidate Libreoffice 6 snap uses adwaita gtk Libreoffice 6 snap uses a hard path to the icon instead of the freedesktop spec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748429/+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 1845797] [NEW] Microphone not detected Lenovo Yoga S940
Public bug reported: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2019-09-28 18-25-03.png" https://bugs.launchpad.net/bugs/1845797/+attachment/5292290/+files/Screenshot%20from%202019-09-28%2018-25-03.png -- 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/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1845797/+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 1845795] [NEW] authentication window got stuck over other windows
Public bug reported: The "Authentication required" screen appeared while I was changing software repository settings, but it is stuck there: 1. I can click "cancel" but there is no effect 2. The window is now always on top of any other window, despite the original Software Repository Settings windows has been closed (actually, terminated manually) As you can see in the screenshot, The Firefox windows has focus now as I am typing in the address bar, but still the "dead" authentication window is on top. Using Ubuntu 19.10 on a Yoga Lenovo S940, upgraded from 19.04 ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "Screenshot from 2019-09-28 18-16-35.png" https://bugs.launchpad.net/bugs/1845795/+attachment/5292289/+files/Screenshot%20from%202019-09-28%2018-16-35.png ** Description changed: The "Authentication required" screen appeared while I was changing software repository settings, but it is stuck there: 1. I can click "cancel" but there is no effect 2. The window is now always on top of any other window, despite the original Software Repository Settings windows has been closed (actually, terminated manually) As you can see in the screenshot, The Firefox windows has focus now as I am typing in the address bar, but still the "dead" authentication window is on top. + + Using Ubuntu 19.10 on a Yoga Lenovo S940, upgraded from 19.04 ** Package changed: pulseaudio (Ubuntu) => ubuntu -- 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/1845795 Title: authentication window got stuck over other windows Status in Ubuntu: New Bug description: The "Authentication required" screen appeared while I was changing software repository settings, but it is stuck there: 1. I can click "cancel" but there is no effect 2. The window is now always on top of any other window, despite the original Software Repository Settings windows has been closed (actually, terminated manually) As you can see in the screenshot, The Firefox windows has focus now as I am typing in the address bar, but still the "dead" authentication window is on top. Using Ubuntu 19.10 on a Yoga Lenovo S940, upgraded from 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1845795/+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 1768752] Re: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also i
*** This bug is a duplicate of bug 1617564 *** https://bugs.launchpad.net/bugs/1617564 ** This bug has been marked a duplicate of bug 1617564 [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1768752 Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package account- plugin-facebook 0.12+16.04.20160126-0ubuntu1 Status in account-plugins package in Ubuntu: New Status in kaccounts-providers package in Ubuntu: New Bug description: apart from kde config telepathy accounts package install error, I even cant update ubuntu base as i try every time the results is broken file. then it asks me to report the bug. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Sun Apr 29 07:05:33 2018 DuplicateSignature: package:kaccounts-providers:(not installed) Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2018-04-26 (6 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1768752/+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 1845792] Re: gnome-shell crashed with SIGSEGV in meta_get_window_actors()
*** This bug is a duplicate of bug 1845136 *** https://bugs.launchpad.net/bugs/1845136 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1845136, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1845792/+attachment/5292259/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1845792/+attachment/5292261/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1845792/+attachment/5292266/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1845792/+attachment/5292267/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1845792/+attachment/5292268/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1845792/+attachment/5292271/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1845792/+attachment/5292272/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1845136 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1845792 Title: gnome-shell crashed with SIGSEGV in meta_get_window_actors() Status in gnome-shell package in Ubuntu: New Bug description: Several gnome-shell crashes ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:31:52 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-09-28 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_get_window_actors () from /lib/x86_64-linux-gnu/libmutter-5.so.0 shell_global_get_window_actors () from /usr/lib/gnome-shell/libgnome-shell.so ffi_call_unix64 () from /lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /lib/x86_64-linux-gnu/libffi.so.6 ?? () from /lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in meta_get_window_actors() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845792/+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 1748429] Re: [snap] Libreoffice uses the adwaita gtk theme
Hi there! No this is no longer happening on new LO snap installations :) -- 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/1748429 Title: [snap] Libreoffice uses the adwaita gtk theme Status in libreoffice package in Ubuntu: Incomplete Bug description: Ubuntu 17.10 Installed the snap via https://forum.snapcraft.io/t/call-for-testing-libreoffice-6-0-0/3917 sudo snap install libreoffice --candidate Libreoffice 6 snap uses adwaita gtk Libreoffice 6 snap uses a hard path to the icon instead of the freedesktop spec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748429/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set
I'm wondering why this has not been fixed after such a long time. It can at
least be improved easily.
If the Adwaita theme works (which it does in may case, too), then it is (at
least partly) a theme issue.
In fact, some defaults seem to be missing in the Ambiance and Radiance themes:
By setting a default for the text background color in the following
file, most problems (gnome-calculator, gedit) are resolved for me:
/usr/share/themes/Ambiance/gtk-3.20/gtk.css:
textview text {
background-color: white; }
@import url("gtk-main.css");
However:
* Some problems remain., e.g. emacs scrollbar background color broken, too.
The following solves that partly, too, but not completely:
scrollbar {
background-color: white; }
* If you change such system files, they will get reset with some later system
updates.
(dpkg-divert can help to prevent such resetting/updating of files)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1760818
Title:
gedit and gnome-calculator transparency/graphics corruption issue when
GTK_IM_MODULE=xim is set
Status in gtk+3.0 package in Ubuntu:
Confirmed
Status in im-config package in Ubuntu:
Confirmed
Bug description:
In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator
suffer from a graphics issue where parts of their windows hold parts
of wallpaper or other windows' contents as background.
See attached screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180328-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 3 09:12:31 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1760818/+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 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
Why the f*** has nothing been done on this for over a year? > Could someone having the issue record a screencast showing the bug? Do you need a screencast because you are too lazy to read my description of the issue which is in my original report and perfectly describes what happens, or because you genuinely doubt that I might be making this up? Or is my english really so bad that my description of the issue isn't clear enough? I think you can literally picture it in your head by reading it, but of course I'm biased because I wrote it myself and I've seen the issue. Yet I find it really difficult to believe that anyone familiar with Nautilus, even without having ever observed the issue, would have any difficulty in understanding what I describe. By the way, now I found out that my Trash folder (in home/.local/share/Trash) was about 140 GB. There's obviously something wrong with that. I certainly haven't deleted 100 GB (nor even anywhere near one GB) in the last few months, and I assume the trash is supposed to get emptied automatically from time to time. Now I did "empty Trash" from nautilus and during the whole time it took, it kept flickering just as described in the issue report as it usually happens when deleting folders with "many" files in them. -- 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/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. 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: Thu Sep 13 19:24:36 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 (1797 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/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
Same issue for me. Nvidia is not powered off in intel mode. Cause massive battery drain, powertop shows value between 30-40 W. Ubuntu 18.04.3, gdm3 MSI GS65 Stealth, Nvidia GTX 1070 MaxQ nvidia-prime version 0.8.8.2 Its strange that nvidia powering off in intel mode worked before on 18.04. Then I used nvidia mode for two months. Now I want to switch back to intel mode but its not working anymore. Unfortunately I don't know which update caused this, because I used nvidia mode for some time. Does this issue already have some official solution, or I have to use bbswitch? The manual bbswitch solution works for me, but I don't like it. Some notes: I tried to install nvidia driver 390, nvidia driver 430 and nvidia driver 435 from ppa and also from repository. Nvidia is not powering off in intel mode with any of them. When system booted in intel mode the /sys/kernel/debug/vgaswitcheroo directory doens't even exist... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845783] Re: Xwayland crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1843987 *** https://bugs.launchpad.net/bugs/1843987 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1843987, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1845783/+attachment/5292214/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1845783/+attachment/5292217/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1845783/+attachment/5292225/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1845783/+attachment/5292227/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1845783/+attachment/5292228/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1845783/+attachment/5292229/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1845783/+attachment/5292230/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1843987 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1845783 Title: Xwayland crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: New Bug description: The problem seems to have occurred whilst browsing though the Gnome Settings. The last page I opened was 'Power'. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20190820-0ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Sep 28 14:08:01 2019 DistUpgraded: 2019-09-27 23:57:07,895 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:082a] InstallationDate: Installed on 2019-09-23 (5 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9360 ProcCmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth /run/user/123/.mutter-Xwaylandauth.UJRB8Z -listen 4 -listen 5 -displayfd 6 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=8871f847-02c3-4658-891c-d58f0eafa0d5 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () InitOutput () ?? () Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to eoan on 2019-09-27 (0 days ago) UserGroups: dmi.bios.date: 05/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.12.0 dmi.board.name: 0TPN17 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0TPN17:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 082A dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1845783/+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 1760068] Re: Wrong resolution at unlock screen
Okay.For nvidia-435.21 I fixed it with: Section "Files" ModulePath "/usr/lib/x86_64-linux-gnu/nvidia/xorg" ModulePath "/usr/lib/xorg/modules" EndSection Light-locker displays the correct resolution now. //this is insane. They need to patch this on the light-locker side soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1760068 Title: Wrong resolution at unlock screen Status in light-locker package in Ubuntu: Invalid Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: After coming out of suspend - the unlock screen is at 640x480 resolution. Expect to see unlock screen at 1920x1080 resolution. Using nvidia-340. Previously tested using nouveau driver where resolution at unlock screen was correct. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-locker 1.8.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 30 11:31:20 2018 InstallationDate: Installed on 2017-09-02 (209 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+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 1845198] Re: GNOME Shell seemingly locked up at login
I had this issue in VM consistently when loggin in with Xorg. No problems with Wayland. Tried the patch from above ppa and it appears to have solved problem. Will do physical install on laptop to verify -- 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/1845198 Title: GNOME Shell seemingly locked up at login Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Eoan: In Progress Bug description: In 19.10, and also running the X PPA from http://ppa.launchpad.net/canonical-x/x-staging/ubuntu When I logged in (after having attached a Bluetooth speaker in order to test if it was being reconnected correctly) GNOME Shell isn't responding to mouse or keyboard input. The clock continues to tell the right time, and the mouse moves around the screen and is repainted correctly. Most recent output from gdb here: https://paste.ubuntu.com/p/pSshP8V2SZ/ Older output here: https://paste.ubuntu.com/p/rPY2VDj6tX/ Journal here: https://paste.ubuntu.com/p/GZcWsQdRhd/ To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1845198/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish
On 2019-09-28 11:27, Jaroslav Hron wrote:
> I can report that the new packages in bionic-proposed work without
> any problem.
> Scanner- canon LiDE 200 on ubuntu 18.04.
So then we have a bionic verification at last. :) Thanks, @Jaroslav!
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1731459
Title:
genesys_gl847 scanners produce a black band in scanned images on
Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish
Status in sane-backends:
Fix Released
Status in sane-backends package in Ubuntu:
Fix Released
Status in sane-backends source package in Bionic:
Fix Committed
Status in sane-backends source package in Disco:
Fix Released
Status in sane-backends package in Debian:
Confirmed
Bug description:
[Impact]
When using a Genesys GL847 scanner, the documents get disfigured by a
discolored bar. The proposed uploads should fix the issue. They are
available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends
[Test case]
1. Install the libsane (libsane1 in bionic), libsane-common
and sane-utils packages from {bionic,disco]-proposed.
2. Use an affected device to scan, and find that the issue is
no longer present.
[Regression risk]
Upstream commit, focused bug fix => low regression risk
[Original description]
On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
black band on scanned image. The scanner is Canon CanoScan LIDE100.
Libsane version is 1.0.27-1~experimental2ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+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 1845775] [NEW] Xorg freeze
Public bug reported: Reproduced on VmWare virtual machine. Ubuntu" Desktop session worked after fresh install of Eoan 19.10 beta install + fresh update. Added Italian language and set it system-wide Restarted Ubuntu Logging with "Ubuntu": session starts but mouse & keyboard do not respond --> have to hard reset the machine. Logging with "Ubuntu Wayland": session starts and properly work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 03:34:25 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2019-09-28 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=fb519e2f-a6b3-4c97-a72c-ffbaec2246bb ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan freeze ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1845775 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Reproduced on VmWare virtual machine. Ubuntu" Desktop session worked after fresh install of Eoan 19.10 beta install + fresh update. Added Italian language and set it system-wide Restarted Ubuntu Logging with "Ubuntu": session starts but mouse & keyboard do not respond --> have to hard reset the machine. Logging with "Ubuntu Wayland": session starts and properly work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 03:34:25 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2019-09-28 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic
[Desktop-packages] [Bug 1748429] Re: [snap] Libreoffice uses the adwaita gtk theme
** Changed in: libreoffice (Ubuntu) Status: Confirmed => Incomplete -- 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/1748429 Title: [snap] Libreoffice uses the adwaita gtk theme Status in libreoffice package in Ubuntu: Incomplete Bug description: Ubuntu 17.10 Installed the snap via https://forum.snapcraft.io/t/call-for-testing-libreoffice-6-0-0/3917 sudo snap install libreoffice --candidate Libreoffice 6 snap uses adwaita gtk Libreoffice 6 snap uses a hard path to the icon instead of the freedesktop spec To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748429/+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 1772512] Re: Unable to install i386 and amd64 arch at the same time
hi guys, on ubuntu bionic 18.04 amd64 I still can't install libsdl2-dev:i386 and libsdl2-dev:amd64 because of that libxkbcommon- dev:i386 and libxkbcommon-dev:amd64 can't coexist. Is there any progress so far? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1772512 Title: Unable to install i386 and amd64 arch at the same time Status in libxkbcommon package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Committed Bug description: [Impact] libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the package isn't properly multi-archified in bionic [Test case] apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64 should succeed [Regression potential] not really -- Not sure if this is intended, but it's not possible to install two architectures of the libxkbcommon-dev at the same time. On Ubuntu 16.04 and 18.04 apt-get says that they are in conflict. The package is a dependency for libegl1-mesa-dev, which I need to have installed in 64 and 32-bit variants. Please see the example output below: $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04 LTS Release: 18.04 Codename: bionic $ sudo apt-get install libxkbcommon-dev:* Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be installed libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish
I can report that the new packages in bionic-proposed work without any problem.
Scanner- canon LiDE 200 on ubuntu 18.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1731459
Title:
genesys_gl847 scanners produce a black band in scanned images on
Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish
Status in sane-backends:
Fix Released
Status in sane-backends package in Ubuntu:
Fix Released
Status in sane-backends source package in Bionic:
Fix Committed
Status in sane-backends source package in Disco:
Fix Released
Status in sane-backends package in Debian:
Confirmed
Bug description:
[Impact]
When using a Genesys GL847 scanner, the documents get disfigured by a
discolored bar. The proposed uploads should fix the issue. They are
available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends
[Test case]
1. Install the libsane (libsane1 in bionic), libsane-common
and sane-utils packages from {bionic,disco]-proposed.
2. Use an affected device to scan, and find that the issue is
no longer present.
[Regression risk]
Upstream commit, focused bug fix => low regression risk
[Original description]
On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
black band on scanned image. The scanner is Canon CanoScan LIDE100.
Libsane version is 1.0.27-1~experimental2ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1811946] Re: black stripe in scans using canon lide 200 usb scanner
*** This bug is a duplicate of bug 1731459 *** https://bugs.launchpad.net/bugs/1731459 I can report that the new packages in bionic-proposed work without any problem. Scanner- canon LiDE 200 on ubuntu 18.04. On 28/09/2019 03:15, Gunnar Hjalmarsson wrote: > *** This bug is a duplicate of bug 1731459 *** > https://bugs.launchpad.net/bugs/1731459 > > There are updated packages in bionic-proposed which may fix this issue; > please see bug #1731459. What remains is that somebody who has an > affected device tests those packages and confirms that the updated > packages address the issue. > > So @Jaroslav, it would be great if you could verify the packages in > bionic-proposed (see the test case in the description on the other bug). > > Marking this bug a duplicate. > > ** This bug has been marked a duplicate of bug 1731459 > genesys_gl847 scanners produce a black band in scanned images on Ubuntu > 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1811946 Title: black stripe in scans using canon lide 200 usb scanner Status in sane-backends package in Ubuntu: Confirmed Bug description: thick vertical black stripe in the middle scans using canon lide 200 usb scanner lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 apt-cache policy libsane1 libsane1: Installed: 1.0.27-1~experimental3ubuntu2 Candidate: 1.0.27-1~experimental3ubuntu2 Version table: *** 1.0.27-1~experimental3ubuntu2 500 500 http://ftp.cvut.cz/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsane1 1.0.27-1~experimental3ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 16 09:16:04 2019 InstallationDate: Installed on 2019-01-14 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: sane-backends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1811946/+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 1834495] Re: Calendar name is not persistent after log out (it changes back to default name)
** Description changed: Steps to reproduce the bug: - 1. Add a Google or a Nextcloud account in gnome-calendar (or gnome-online-accounts) + 1. Add a Google or a Nextcloud account in gnome-calendar 2. Activate the calendar component in the account - 3. Open gnome-calendar and go to Calendar Settings (either from the "Manage your calendars" button in the app or from the app menu in the top bar of gnome-shell) - 4. Choose a Google or a Nextcloud calendar, which was already setup from step 1 + 3. Open gnome-calendar and go to Calendar Settings + 4. Choose a Google or a Nextcloud calendar 5. Change the calendar name 6. Go back, close the app and open it again 7. The new name is still there 8. Log out and log back in 9. Check the calendar name 10. It's back to the default name The new calendar name should always be persistent and does not change to the default name. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 27 16:45:18 2019 InstallationDate: Installed on 2018-11-29 (209 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-calendar UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1834495 Title: Calendar name is not persistent after log out (it changes back to default name) Status in gnome-calendar package in Ubuntu: New Bug description: Steps to reproduce the bug: 1. Add a Google or a Nextcloud account in gnome-calendar 2. Activate the calendar component in the account 3. Open gnome-calendar and go to Calendar Settings 4. Choose a Google or a Nextcloud calendar 5. Change the calendar name 6. Go back, close the app and open it again 7. The new name is still there 8. Log out and log back in 9. Check the calendar name 10. It's back to the default name The new calendar name should always be persistent and does not change to the default name. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calendar 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 27 16:45:18 2019 InstallationDate: Installed on 2018-11-29 (209 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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/1834495/+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 1845599] Re: eoan regression: ImportError: librsync.so.1: cannot open shared object file: No such file or directory
Indeed. When I thought that I switched to distro-provided package a few years back, I forgot to update the path in my cron script. Sorry for the confusion. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1845599 Title: eoan regression: ImportError: librsync.so.1: cannot open shared object file: No such file or directory Status in duplicity package in Ubuntu: Invalid Bug description: After yesterday's upgrade, librsync2 is 2.0.2-1, it's shared object name is /usr/lib/x86_64-linux-gnu/librsync.so.2 but duplicity's _librsync.so wants librsync.so.1: etc/cron.daily/dbackup: Traceback (most recent call last): File "/usr/local/bin/duplicity", line 47, in from duplicity import collections File "/usr/local/lib/python2.7/dist-packages/duplicity/collections.py", line 32, in from duplicity import path File "/usr/local/lib/python2.7/dist-packages/duplicity/path.py", line 44, in from duplicity import librsync File "/usr/local/lib/python2.7/dist-packages/duplicity/librsync.py", line 30, in from . import _librsync ImportError: librsync.so.1: cannot open shared object file: No such file or directory Does the package need to be rebuilt, perhaps? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: duplicity 0.8.04-2 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Fri Sep 27 09:00:31 2019 SourcePackage: duplicity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1845599/+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 1837321] Re: Update to 2.7
** Changed in: iio-sensor-proxy (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1837321 Title: Update to 2.7 Status in iio-sensor-proxy package in Ubuntu: Fix Released Bug description: https://github.com/hadess/iio-sensor-proxy/blob/master/NEWS 2.7 --- This release fixes broken sensor readings on multiple platforms due to a compiler optimisation. 2.6 --- This release adds support for mount matrices coming from the kernel itself, checking those more thoroughly for validity. On devices with multiple accelerometers, the ones in the base are now ignored. Support for sensors with uncommon formats was already enhanced (or fixed depending on the device). A couple of possible crashes and memory leaks were also fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1837321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11
thanks for the feedback On Thu, Sep 26, 2019, 09:55 daniel primo stuart <1609...@bugs.launchpad.net> wrote: > Kernel needs this patch for maxim98090 to work on cyan and some baytrail > chromebooks: > > https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f > > As it didn't make to 5.3 on time, would be nice if it were backported by > ubuntu devs > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1803810). > https://bugs.launchpad.net/bugs/1609750 > > Title: > Audio not working on Acer Chromebook R11 > > Status in linux: > Confirmed > Status in linux package in Ubuntu: > In Progress > Status in pulseaudio package in Ubuntu: > Invalid > > Bug description: > Audio is not working at all on Acer Chromebook R11 (codename CYAN). > It's a Intel Braswell platform. snd_hda_intel messages seem normal, > but Pulseaudio does not detect sound hardware. > > ProblemType: Bug > DistroRelease: Ubuntu 16.10 > Package: pulseaudio 1:9.0-1.1ubuntu1 > ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 > Uname: Linux 4.4.0-33-generic x86_64 > ApportVersion: 2.20.3-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > Date: Thu Aug 4 14:12:03 2016 > InstallationDate: Installed on 2016-07-22 (13 days ago) > InstallationMedia: > > 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: No upgrade log present (probably fresh install) > dmi.bios.date: 05/20/2016 > dmi.bios.vendor: coreboot > dmi.chassis.type: 3 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: > dmi.product.name: Cyan > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > --- > ApportVersion: 2.20.3-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', > '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', > '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer'] failed with exit code 1: > CurrentDesktop: Unity > DistroRelease: Ubuntu 16.10 > HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 > InstallationDate: Installed on 2016-07-22 (13 days ago) > InstallationMedia: > > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 8087:0a2a Intel Corp. >Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: GOOGLE Cyan > Package: linux-image-4.4.0-33-generic 4.4.0-33.52 > PackageArchitecture: amd64 > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic > root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 > ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 > PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No > PulseAudio daemon running, or not running as session daemon. > RelatedPackageVersions: >linux-restricted-modules-4.4.0-33-generic N/A >linux-backports-modules-4.4.0-33-generic N/A >linux-firmware1.159 > Tags: yakkety > Uname: Linux 4.4.0-33-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 05/20/2016 > dmi.bios.vendor: coreboot > dmi.chassis.type: 3 > dmi.chassis.vendor: GOOGLE > dmi.modalias: > dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: > dmi.product.name: Cyan > dmi.product.version: 1.0 > dmi.sys.vendor: GOOGLE > > To manage notifications about this bug go to: > https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions > -- 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/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2
[Desktop-packages] [Bug 1813173] Re: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() when using the GPaste extension
Bug #1775971 is for updating gpaste to 3.28.3 in Bionic, which fixes two crashes, one with emptying history and one with image support. -- 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/1813173 Title: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() when using the GPaste extension Status in gnome-shell package in Ubuntu: Confirmed Status in gpaste package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/ced4a4eb6e94763756d8b463a6135c31dd711619 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 24 16:34:05 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-04-29 (999 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x7fa4603b6021 : mov(%rbx),%rdi PC (0x7fa4603b6021) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: clutter_container_get_child_meta () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 () at /usr/lib/libgjs.so.0 () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in clutter_container_get_child_meta() UpgradeStatus: Upgraded to bionic on 2018-08-04 (173 days ago) UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813173/+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 1845772] Re: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1845772 Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: This error pops-up every time I start the computer. Since the update to eoan, this pop-up appears, however, I didn't trust that it worked on disco either, as I have a hardware light indicating wether I'm using or not my GPU, and even though I had the option "Nvidia on demand", my GPU was still being used every time, so I think there's something wrong with the driver itself, ad it's not controlling the use of the GPU. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-430 430.50-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Fri Sep 27 17:27:03 2019 ErrorMessage: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-09-07 (20 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-430 Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845772/+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 1845772] [NEW] package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit stat
Public bug reported: This error pops-up every time I start the computer. Since the update to eoan, this pop-up appears, however, I didn't trust that it worked on disco either, as I have a hardware light indicating wether I'm using or not my GPU, and even though I had the option "Nvidia on demand", my GPU was still being used every time, so I think there's something wrong with the driver itself, ad it's not controlling the use of the GPU. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-430 430.50-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Fri Sep 27 17:27:03 2019 ErrorMessage: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-09-07 (20 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-430 Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-27 (0 days ago) ** Affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1845772 Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-430 package in Ubuntu: New Bug description: This error pops-up every time I start the computer. Since the update to eoan, this pop-up appears, however, I didn't trust that it worked on disco either, as I have a hardware light indicating wether I'm using or not my GPU, and even though I had the option "Nvidia on demand", my GPU was still being used every time, so I think there's something wrong with the driver itself, ad it's not controlling the use of the GPU. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-430 430.50-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Fri Sep 27 17:27:03 2019 ErrorMessage: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-09-07 (20 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-430 Title: package nvidia-dkms-430 430.50-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1845772/+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
