[Desktop-packages] [Bug 1856317] Re: [SRU] 3.34.2
This bug was fixed in the package gnome-desktop3 - 3.34.2-2ubuntu1~19.10.1 --- gnome-desktop3 (3.34.2-2ubuntu1~19.10.1) eoan; urgency=medium * Backport for SRU from focal to eoan (LP: #1856317) * Update branch references to ubuntu/eoan gnome-desktop3 (3.34.2-2ubuntu1) focal; urgency=medium * Merge with Debian. Remaining changes: - Add 04_compute_average_color.patch: Compute the avergage color in gnome-desktop itself, not in unity to fix some races (LP #963140) - Add tweak_color_computation.patch, Patch from Gord, no patch header, no bug link. - Add git_revert_draw_background.patch - Add ubuntu_language_list_from_SUPPORTED.patch, Add API to get list of available languages from SUPPORTED file. To be used by gnome 3.8 region panel language installation. - Add gnomebg_hidpi_image.patch, gnome_bg_create_surface: always honor device scale, that fixes the wallpaper rendering in HiDPI config under ubiquity - debian/control.in: Build-Depend on language-pack-gnome-he for build tests - debian/libgnome-desktop-3-18.symbols: + Add symbols included in Ubuntu patches - Update Vcs fields and debian/gbp.conf for Ubuntu - Call dh_translations in the build so we get a translation template generated for langpacks gnome-desktop3 (3.34.2-2) unstable; urgency=medium * debian/control.in: Add libsystemd-dev to the dependencies of the libgnome-desktop-3-dev package as well gnome-desktop3 (3.34.2-1) unstable; urgency=medium * New upstream release * Add libsystemd-dev to the build-dependencies, this is used by the helper to create transient systemd scopes * debain/control.in: Bump Standards-Version to 4.4.1 (no further changes) * d/p/seccomp-is-not-supported-ATM-on-riscv64-architecture-blac.patch: seccomp is ATM not available on riscv64, let's blacklist it for now gnome-desktop3 (3.34.1-2) unstable; urgency=medium * debian/control.in: Do not make libgnome-desktop-3-dev depend against libudev-dev on non-linux architectures, this is not needed * debian/control.in: Do not (build-)depend against libseccomp-dev on riscv64, seccomp is not supported on this architecture ATM * debian/control.in: Add at-spi2-core to the build-dependencies, this seems to be needed for the tests on hurd-i386, that should fix the FTBFS -- Iain Lane Fri, 13 Dec 2019 13:32:51 + ** Changed in: gnome-desktop3 (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1856317 Title: [SRU] 3.34.2 Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Eoan: Fix Released Bug description: [ Description ] Update to 3.34.2, which is going to be required by gnome-shell. == Version 3.34.2 == - Add helper to create transient systemd scopes - Translation updates [ QA ] This is uploaded under the GNOME MRE: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This is solely to add new API. Test that the desktop continues to work. Maybe try the thumbnailer in Nautilus, and the background panel in Settings. [ Regression potential ] Not as a result of this SRU itself, *but* when gnome-shell / gnome- settings-daemon are uploaded then *they* could regress if this update is buggy. They should probably be released all together. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1856317/+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 1856317] Update Released
The verification of the Stable Release Update for gnome-desktop3 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1856317 Title: [SRU] 3.34.2 Status in gnome-desktop3 package in Ubuntu: Fix Released Status in gnome-desktop3 source package in Eoan: Fix Committed Bug description: [ Description ] Update to 3.34.2, which is going to be required by gnome-shell. == Version 3.34.2 == - Add helper to create transient systemd scopes - Translation updates [ QA ] This is uploaded under the GNOME MRE: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This is solely to add new API. Test that the desktop continues to work. Maybe try the thumbnailer in Nautilus, and the background panel in Settings. [ Regression potential ] Not as a result of this SRU itself, *but* when gnome-shell / gnome- settings-daemon are uploaded then *they* could regress if this update is buggy. They should probably be released all together. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1856317/+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 1694373] Re: Gnome Shell app list scrolls too quickly with mouse wheel
Hmm that upstream status is wrong, or linked to the wrong bug. It's definitely NOT fixed with the latest master code yet. -- 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/1694373 Title: Gnome Shell app list scrolls too quickly with mouse wheel Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://bugzilla.gnome.org/show_bug.cgi?id=707973 --- Gnome Shell app list scrolls too quickly with mouse wheel. It seems to scroll one page per wheel tick, which is way too much. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Tue May 30 14:08:46 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'command-history' b"['ls', 'xterm', 'caribou', 'cariboukkk', 'cariboujj']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'chromium-browser.desktop', 'gnome-control-center.desktop', 'org.gnome.Terminal.desktop', 'rhythmbox.desktop', 'yelp.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (27 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1694373/+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. Power consumption ~10W higher than normal on intel mode. Linux Mint 19.3 Cinnamon Dell 7577 NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] Kernel: 5.0.0-37-generic Can anyone help me turn of dGpu... -- 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 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** Description changed: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] - Low, The first part of the patch is a workaround for a bug elsewhere - which is reporting things in the wrong order. The second part is a fix - for a case that wasn't being handled correctly. + Low. - - Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages + Package in this PPA: + https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Fix Released Bug description: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] Low. Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+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 1859398] Re: Extracting .rar creates multi-GB file which fills up harddrive
** Description changed: 1) Ubuntu 19.10 2) Archive Manager 3.32.2-1 - 3) Display a message if .rar is unsupported. + 3) Display a message if .rar is unsupported or display a message to install p7zip which can extract .rar files. 4) Selecting the ProtectionId.690.December.2017.rar file and then right clicking "Extract Here", Archive Manager creates a multi-GB file named file_id.dz which fills up the harddrive. I was able to successfully extract the ProtectionId.690.December.2017.rar file with 7zip via WINE. https://protectionid.net/ https://web.archive.org/web/20181229235034/https://pid.wiretarget.com/?f=ProtectionId.690.December.2017.rar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1859398 Title: Extracting .rar creates multi-GB file which fills up harddrive Status in file-roller package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Archive Manager 3.32.2-1 3) Display a message if .rar is unsupported or display a message to install p7zip which can extract .rar files. 4) Selecting the ProtectionId.690.December.2017.rar file and then right clicking "Extract Here", Archive Manager creates a multi-GB file named file_id.dz which fills up the harddrive. I was able to successfully extract the ProtectionId.690.December.2017.rar file with 7zip via WINE. https://protectionid.net/ https://web.archive.org/web/20181229235034/https://pid.wiretarget.com/?f=ProtectionId.690.December.2017.rar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1859398/+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 1859398] [NEW] Extracting .rar creates multi-GB file which fills up harddrive
Public bug reported: 1) Ubuntu 19.10 2) Archive Manager 3.32.2-1 3) Display a message if .rar is unsupported. 4) Selecting the ProtectionId.690.December.2017.rar file and then right clicking "Extract Here", Archive Manager creates a multi-GB file named file_id.dz which fills up the harddrive. I was able to successfully extract the ProtectionId.690.December.2017.rar file with 7zip via WINE. https://protectionid.net/ https://web.archive.org/web/20181229235034/https://pid.wiretarget.com/?f=ProtectionId.690.December.2017.rar ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1859398 Title: Extracting .rar creates multi-GB file which fills up harddrive Status in file-roller package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Archive Manager 3.32.2-1 3) Display a message if .rar is unsupported. 4) Selecting the ProtectionId.690.December.2017.rar file and then right clicking "Extract Here", Archive Manager creates a multi-GB file named file_id.dz which fills up the harddrive. I was able to successfully extract the ProtectionId.690.December.2017.rar file with 7zip via WINE. https://protectionid.net/ https://web.archive.org/web/20181229235034/https://pid.wiretarget.com/?f=ProtectionId.690.December.2017.rar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1859398/+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 1859390] Re: Blurred texts, icons and character typed on login screen after logout
** Package changed: ubuntu => lightdm (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1859390 Title: Blurred texts, icons and character typed on login screen after logout Status in lightdm package in Ubuntu: New Bug description: I login to my account normally. But, when I click on "switch user" from app indicator, the clock in login screen will be completely blurred, impossible even to perceive it is a clock/time, except if I wait one minute so that the last number will update and it will show correctly (only the last number). If I press enter or click-up, I see the login form with the same problem: I can see that there are two users but they are completely indistinguishable and blurred. If I click on it, I can type my password but still blurred, even the chars I type are blurred. The app indicator icons are blurred too, but when I put the cursor over them, instantly they are fixed. PS: I have two enabled monitors and two users, but the second user is not logged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 13 00:13:45 2020 InstallationDate: Installed on 2019-12-31 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1859390/+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 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** Description changed: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] + + Low, The first part of the patch is a workaround for a bug elsewhere + which is reporting things in the wrong order. The second part is a fix + for a case that wasn't being handled correctly. Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Fix Released Bug description: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] Low, The first part of the patch is a workaround for a bug elsewhere which is reporting things in the wrong order. The second part is a fix for a case that wasn't being handled correctly. Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+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 1859260] Re: Cant go back to primary monitor when app indicator menu is open
Hmm, maybe?... Can you reproduce the issue with any other Gnome Shell popovers? -- 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/1859260 Title: Cant go back to primary monitor when app indicator menu is open Status in gnome-shell package in Ubuntu: New Bug description: This bugs happens if you: 1. Open app indicator menu (top right); 2. Move your cursor to the right monitor; Now you can't go back. The only way is pressing ESC to close app indicator menu so that you can go back to the first monitor. This only happens when ubuntu-dock autohide is on. Maybe it can be useful: https://github.com/micheleg/dash-to- dock/issues/743 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 00:01:41 2020 InstallationDate: Installed on 2019-12-31 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859260/+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 1859390] [NEW] Blurred texts, icons and character typed on login screen after logout
You have been subscribed to a public bug: I login to my account normally. But, when I click on "switch user" from app indicator, the clock in login screen will be completely blurred, impossible even to perceive it is a clock/time, except if I wait one minute so that the last number will update and it will show correctly (only the last number). If I press enter or click-up, I see the login form with the same problem: I can see that there are two users but they are completely indistinguishable and blurred. If I click on it, I can type my password but still blurred, even the chars I type are blurred. The app indicator icons are blurred too, but when I put the cursor over them, instantly they are fixed. PS: I have two enabled monitors and two users, but the second user is not logged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 13 00:13:45 2020 InstallationDate: Installed on 2019-12-31 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Blurred texts, icons and character typed on login screen after logout https://bugs.launchpad.net/bugs/1859390 You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859339] Re: Freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1859339 Title: Freeze Status in Ubuntu: Incomplete Bug description: Freeze screen, keyboard block, mouse smile, activity in court frozen regularly. only possibility to restart in force. it also restarts itself regularly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jan 12 17:30:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7c51] InstallationDate: Installed on 2020-01-06 (6 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Micro-Star International Co., Ltd. MS-7C51 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=64715203-5a05-42f8-93df-f2967370ca5d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M-A PRO (MS-7C51) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd09/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320M-APRO(MS-7C51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C51 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1859339/+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 1859326] Re: When I logut and try to log in, the password field is hidden
When the problem happens, try Ctrl+Alt+F1 or Ctrl+Alt+F2 -- 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/1859326 Title: When I logut and try to log in, the password field is hidden Status in gnome-shell package in Ubuntu: New Bug description: Hello, I have upgraded from Ubuntu 19.04 to Ubuntu 19.10. Now, When I logout, the lock-screen background is shown on the screen, usaully i used to press any button, then the lock-screen moves up, and the user login form appears, but now the login form never appears, only the lock-screen taking all of the screen, and I have to enter the password without seeing the form and press Enter to log in, I can't even see which user is selected. Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:0a: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 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 14:24:27 2020 DistUpgraded: 2020-01-12 13:15:58,832 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 5.0.0-38-generic, x86_64: installed nvidia, 430.50, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2166] Subsystem: Hewlett-Packard Company GK208M [GeForce GT 740M] [103c:2166] InstallationDate: Installed on 2019-05-02 (255 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=0335c8fd-b7c3-4fc4-bf52-2a78bfe22f38 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2020-01-12 (0 days ago) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.40 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08971030410610100:rvnHewlett-Packard:rn2166:rvr29.40:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.sku: F1E53EA#ABV dmi.product.version: 08971030410610100 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.2.1-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+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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/gnome-shell/+bug/1859326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1859353] Re: software-properties-gtk not working
** Tags added: eoan ** Package changed: gnome-shell (Ubuntu) => software-properties (Ubuntu) -- 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/1859353 Title: software-properties-gtk not working Status in software-properties package in Ubuntu: New Bug description: Additional Drivers /Software & Update not working Hello, I am running :- Description: Ubuntu 19.10 Release: 19.10 software-properties-gtk: Installed: 0.98.5 Candidate: 0.98.5 Version table: *** 0.98.5 500 500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status I am trying to run Additional Drivers /Software & Update . But it opened once and froze and never opened again. When I try running the command:- $ sudo software-properties-gtk Did a remove and reinstall of the same, but did not work. It returns:- ERROR:dbus.proxies:Introspect error on :1.2559:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 175, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 147, in __call__ **keywords) File "/usr/lib/python3/dist-packages/dbus/connection.py", line 653, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.2559 was not provided by any .service files Also, the syslog says:- name='com.ubuntu.SoftwareProperties' requested by ':1.2455' (uid=1000 pid=2267 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " label="unconfined") (using servicehelper) Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Unable to init server: Could not connect: Connection refused Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Unable to init server: Could not connect: Connection refused Jan 12 11:58:55 gillZ dbus-daemon[2192]: [system] Successfully activated service 'com.ubuntu.SoftwareProperties' Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Traceback (most recent call last): Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File "/usr/lib/software-properties/software-properties-dbus", line 68, in Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: server = SoftwarePropertiesDBus(bus, datadir=datadir) Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File "/lib/python3/dist-packages/softwareproperties/dbus/SoftwarePropertiesDBus.py", line 66, in __init__ Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: self._livepatch_service = LivepatchService() Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File "/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line 93, in __init__ Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: self._session = requests_unixsocket.Session() Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: NameError: name 'requests_unixsocket' is not defined Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: ERROR:dbus.proxies:Introspect error on :1.2457:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: Traceback (most recent call last): Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File "/usr/bin/software-properties-gtk", line 100, in Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 175, in __init__ Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: self.backend.Reload(); Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: return self._proxy_method(*args, **keywords) Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 147, in __call__ Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: **keywords) Jan 12 11:58:55 gillZ
[Desktop-packages] [Bug 1859260] Re: Cant go back to primary monitor when app indicator menu is open
Ok vanvugt, thank you. I thought it was related because disabling "autohide" the problem goes away. -- 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/1859260 Title: Cant go back to primary monitor when app indicator menu is open Status in gnome-shell package in Ubuntu: New Bug description: This bugs happens if you: 1. Open app indicator menu (top right); 2. Move your cursor to the right monitor; Now you can't go back. The only way is pressing ESC to close app indicator menu so that you can go back to the first monitor. This only happens when ubuntu-dock autohide is on. Maybe it can be useful: https://github.com/micheleg/dash-to- dock/issues/743 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 00:01:41 2020 InstallationDate: Installed on 2019-12-31 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859260/+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 1859326] Re: When I logut and try to log in, the password field is hidden
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- 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/1859326 Title: When I logut and try to log in, the password field is hidden Status in gnome-shell package in Ubuntu: New Bug description: Hello, I have upgraded from Ubuntu 19.04 to Ubuntu 19.10. Now, When I logout, the lock-screen background is shown on the screen, usaully i used to press any button, then the lock-screen moves up, and the user login form appears, but now the login form never appears, only the lock-screen taking all of the screen, and I have to enter the password without seeing the form and press Enter to log in, I can't even see which user is selected. Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:0a: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 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 14:24:27 2020 DistUpgraded: 2020-01-12 13:15:58,832 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 5.0.0-38-generic, x86_64: installed nvidia, 430.50, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2166] Subsystem: Hewlett-Packard Company GK208M [GeForce GT 740M] [103c:2166] InstallationDate: Installed on 2019-05-02 (255 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=0335c8fd-b7c3-4fc4-bf52-2a78bfe22f38 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2020-01-12 (0 days ago) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.40 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08971030410610100:rvnHewlett-Packard:rn2166:rvr29.40:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.sku: F1E53EA#ABV dmi.product.version: 08971030410610100 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.2.1-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+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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/gnome-shell/+bug/1859326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1859260] Re: Cant go back to primary monitor when app indicator menu is open
The indicator menu is not related to the 'ubuntu-dock' extension so I'll move this... ** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => gnome- shell (Ubuntu) ** Tags added: multimonitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1859260 Title: Cant go back to primary monitor when app indicator menu is open Status in gnome-shell package in Ubuntu: New Bug description: This bugs happens if you: 1. Open app indicator menu (top right); 2. Move your cursor to the right monitor; Now you can't go back. The only way is pressing ESC to close app indicator menu so that you can go back to the first monitor. This only happens when ubuntu-dock autohide is on. Maybe it can be useful: https://github.com/micheleg/dash-to- dock/issues/743 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 11 00:01:41 2020 InstallationDate: Installed on 2019-12-31 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859260/+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 1837392] Re: "unable to find firefox.desktop" when clicking "Show Details" on the Firefox menu (top)
This may be useful, and a bit obvious: /usr/share/applications/firefox.desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1837392 Title: "unable to find firefox.desktop" when clicking "Show Details" on the Firefox menu (top) Status in gnome-software package in Ubuntu: Confirmed Bug description: When a user tries to open the menu that is on the top, next to Activities button, and clicks "Show Details", it opens GNOME Software, but stays on the loading bar for a while then it says "Unable to find firefox.desktop". However, if I opened GNOME Software to search for Firefox, there are two entries for Firefox, one from Ubuntu repo, one from Snap. I know that Firefox existed on GNOME Software, but it seems weird that it won't be able to search for "firefox.desktop." ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu8 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 22 14:59:54 2019 InstallationDate: Installed on 2019-07-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1837392/+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 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state()
It looks like some JavaScript is doing painting here... #8 0x7fa5318efa05 in meta_wayland_surface_role_commit (pending=0x555e42fcde50, surface_role=) at ../src/wayland/meta-wayland-surface.h:45 No locals. #9 meta_wayland_surface_apply_pending_state (surface=0x555e458b8540, pending=0x555e42fcde50) at ../src/wayland/meta-wayland-surface.c:802 had_damage = 1 __func__ = "meta_wayland_surface_apply_pending_state" #10 0x7fa53093a81e in ffi_call_unix64 () at ../src/x86/unix64.S:76 No locals. #11 0x7fa53093a1ef in ffi_call (cif=cif@entry=0x7ffde18c88f0, fn=, rvalue=, rvalue@entry=0x0, avalue=avalue@entry=0x7ffde18c89c0) at ../src/x86/ffi64.c:525 So that sounds like a buggy extension more than a Gnome Shell issue. You also have a few extensions installed: 'user-th...@gnome-shell-extensions.gcampax.github.com' 'impatie...@gfxmonk.net' 'no...@maestroschan.fr' 'bingwallpa...@ineffable-gmail.com' 'dayni...@maze-n.github.com' Please try UNINSTALLING those. I suspect BingWallpaper the most since it would do rendering, and it shows up in your system log with errors too. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1859259 Title: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2 --- This has begun happening in the last few days; I was unable to create a bug for the last crash because I had some outdated packages installed. This crash occurred as I started Firefox Nightly on my machine with a fairly large session being restored. GNOME logged me out as the windows were being spawned by session restored. My Firefox is being started in pure Wayland mode -- MOZ_ENABLE_WAYLAND=1 I am using "Basic" compositing (not WebRender) in this session. Happy to provide any other details. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 10 20:22:13 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-01-05 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax PC (0x7fa5318821db) ok source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859259/+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 1859388] Re: /usr/bin/gnome-shell:11:meta_surface_actor_get_texture:meta_wayland_actor_surface_real_sync_actor_state:meta_wayland_subsurface_sync_actor_state:meta_wayland_actor
*** This bug is a duplicate of bug 1859259 *** https://bugs.launchpad.net/bugs/1859259 ** This bug has been marked a duplicate of bug 1859259 gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() -- 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/1859388 Title: /usr/bin/gnome- shell:11:meta_surface_actor_get_texture:meta_wayland_actor_surface_real_sync_actor_state:meta_wayland_subsurface_sync_actor_state:meta_wayland_actor_surface_sync_actor_state:meta_wayland_actor_surface_real_sync_actor_state Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859388/+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 1859259] Re: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state()
Tracking in https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2 ** Summary changed: - gnome-shell crashed with SIGSEGV + gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() ** Information type changed from Private to Public ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Description changed: + https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2 + + --- + This has begun happening in the last few days; I was unable to create a bug for the last crash because I had some outdated packages installed. This crash occurred as I started Firefox Nightly on my machine with a fairly large session being restored. GNOME logged me out as the windows were being spawned by session restored. My Firefox is being started in pure Wayland mode -- MOZ_ENABLE_WAYLAND=1 I am using "Basic" compositing (not WebRender) in this session. Happy to provide any other details. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 10 20:22:13 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-01-05 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: - Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax - PC (0x7fa5318821db) ok - source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA region (needed readable region)! - destination "%rax" ok + Segfault happened at: 0x7fa5318821db:mov(%rdi,%rax,1),%rax + PC (0x7fa5318821db) ok + source "(%rdi,%rax,1)" (0xfcb0) not located in a known VMA region (needed readable region)! + destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 - ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 - ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 - ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 - ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 + ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 + ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 + ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 + ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 + ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Tags added: eoan ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium -- 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/1859259 Title: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2 --- This has begun happening in the last few days; I was unable to create a bug for the last crash because I had some outdated packages installed. This crash occurred as I started Firefox Nightly on my machine with a fairly large session being restored. GNOME logged me out as the windows were being spawned by session restored. My Firefox is being started in pure Wayland mode -- MOZ_ENABLE_WAYLAND=1 I am using "Basic" compositing (not WebRender) in this session. Happy to provide any other details. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 10 20:22:13 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-01-05 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR=
[Desktop-packages] [Bug 1859388] [NEW] /usr/bin/gnome-shell:11:meta_surface_actor_get_texture:meta_wayland_actor_surface_real_sync_actor_state:meta_wayland_subsurface_sync_actor_state:meta_wayland_act
*** This bug is a duplicate of bug 1859259 *** https://bugs.launchpad.net/bugs/1859259 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: eoan focal -- 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/1859388 Title: /usr/bin/gnome- shell:11:meta_surface_actor_get_texture:meta_wayland_actor_surface_real_sync_actor_state:meta_wayland_subsurface_sync_actor_state:meta_wayland_actor_surface_sync_actor_state:meta_wayland_actor_surface_real_sync_actor_state Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.34.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859388/+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 1859173] Re: display
Can you please provide a screenshot of the problem? ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1859173 Title: display Status in gnome-shell package in Ubuntu: Incomplete Bug description: i comandi e la barra superiore sbordano, non riesco a visualizzarli ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 13:12:16 2020 DistUpgraded: 2020-01-10 07:57:08,409 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio «./xorg_fix_proprietary.py» non riuscita (File o directory non esistente) (8)) DistroCodename: disco DistroVariant: ubuntu GraphicsCard: VIA Technologies, Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro] [1106:3108] (rev 01) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. K8M800/K8N800/K8N800A [S3 UniChrome Pro] [1043:8129] InstallationDate: Installed on 2020-01-08 (2 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic root=UUID=943bdf0d-bfd4-4e4d-b427-5c0ac904be90 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2020-01-10 (0 days ago) dmi.bios.date: 09/12/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0203 dmi.board.name: K8V-MX dmi.board.vendor: ASUSTeK Computer Inc. dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 6 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0203:bd09/12/2005:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerInc.:rnK8V-MX:rvr:cvnChassisManufacture:ct6:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 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/gnome-shell/+bug/1859173/+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 1859071] Re: Secondary monitor unpredictable behavior at boot
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1859071 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: disco ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1859071 Title: Secondary monitor unpredictable behavior at boot Status in xorg-server package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy gdm3 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy lightdm lightdm: Installed: 1.30.0-0ubuntu1 Candidate: 1.30.0-0ubuntu1 Version table: *** 1.30.0-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) I have a 3rd gen Intel laptop with only Ubuntu 19.10 installed, and a monitor attached via DisplayPort. The monitor has a native resolution of 2560x1080. When I power on my laptop, it is seemingly random whether one of the three following situations occurs. 1. Displays at the proper native resolution of 2560x1080, 2. Displays at 1600x1200 but not let me select a higher resolution in display settings, or 3. The display will fail to connect and stay blank (when I enter display settings it will be on "Single Monitor" mode, but from there I can enable Join Displays and set it to its native resolution). Please note I selected "I don't know" instead of gdm3 or lightdm since i've been having this issue since before installing/switching to lightdm. Please let me know what additional information I can provide at this time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1859071/+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 1853357] Re: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland
** Tags added: displaylink -- 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/1853357 Title: display (whole computer?) hangs when I attempt to use DisplayLink with Wayland Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: In Progress Bug description: [ Impact ] I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu DisplayLink is working under Xorg, but when I try to use it under Wayland my whole display hangs and I can't even switch to a different VT with Ctrl-Alt-F3 so I think maybe the whole computer is hung? Not certain. [ Test case ] - Install DisplayLink drivers - Start GNOME Shell in wayland mode - Connect to a display-link dock - Expect the shell to work properly and be visible in the external device [ Regression potential ] Wayland session won't work even for standard drm devices I am using the DisplayLink driver for Ubuntu provided at https://www.displaylink.com/downloads/ubuntu, which I think is the only way to get DisplayLink fully working under Ubuntu? That is, DisplayLink didn't work when I installed the evdi-dkms and libevdi0 Ubuntu packages, and I couldn't find any other packages that might be relevant (did I miss something?) so as far as I can tell the only way to get everything that's needed is from displaylink.com. I'm reporting this issue while logged in under Xorg because I can't report it when logged in with my DisplayLink monitors plugged in under Wayland, for obvious reasons. :-/ ProblemType: BugDistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 14:08:21 2019 InstallationDate: Installed on 2019-09-12 (69 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-20 (61 days ago) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853357/+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 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome
Norbert, I can't tell for sure if that crash is the same as this one because it's missing line number debug info. Please turn your crash file (and future ones) into a new bug by running: ubuntu-bug YOURFILE.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1796437 Title: X11 crashed when attempting to open Budgie and MATE Welcome Status in ubuntu-mate-meta package in Ubuntu: New Status in ubuntu-mate-welcome package in Ubuntu: New Status in xorg-server package in Ubuntu: Won't Fix Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg 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 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1796437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1511244] Re: Mouse pointer flickers at using DisplayLink
Ubuntu 14.04 reached end of standard support in April 2019 so if you still experience any problems then please open a fresh new bug by running: ubuntu-bug xorg-server ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- 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/1511244 Title: Mouse pointer flickers at using DisplayLink Status in xorg package in Ubuntu: Won't Fix Bug description: I have a three screen setup, the built-in laptop screen, a monitor connected directly into the laptop via DisplayPort, and a monitor connected via a USB DisplayLink Adapter. What happens is that when a monitor is connected via the USB DisplayLink Adapter, the mouse icon flickers only on the laptop screen and monitor connected via DisplayPort (not on the monitor connected via USB DisplayLink Adapter). However, this is also reproducible if I either deactivate the built-in laptop screen, or disconnect the DisplayPort connected monitor. WORKAROUND: Disconnect the USB DisplayLink Adapter for the computer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu Oct 29 08:29:50 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:503c] InstallationDate: Installed on 2015-09-25 (33 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: LENOVO 20DT0003GE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic root=UUID=500f2ef6-7426-42ec-9fe2-88e9bcea ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JDET50WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJDET50WW(1.12):bd03/25/2015:svnLENOVO:pn20DT0003GE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DT0003GE dmi.product.version: ThinkPad L450 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Oct 29 07:45:59 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9782 vendor ENC xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1511244/+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 1766230] Re: Strange window matching behaviour between Slack and Chrome
** Tags added: bionic -- 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/1766230 Title: Strange window matching behaviour between Slack and Chrome Status in gnome-shell package in Ubuntu: Confirmed Bug description: There seems to be a window matching bug between the Slack snap and Chrome. If you open a URL from within Slack without Chrome open, then the launcher shows the extra pip next to Slack and doesn't add a Chrome icon to the launcher. If you open Chrome first, then things work as expected. Steps to reproduce 1. Install Slack snap and Chrome deb. 2. Join a Slack channel and open a hyperlink. Notice the extra pip next to Slack in the launcher. 3. Close Chrome and reopen it. 4. Open a URL from Slack again and notice the Chrome icon get added to the launcher. I'm not sure if this is an Ubuntu Dock or GNOME Shell issue. EDIT: Spoke to didrocks, he says that matching is done by Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1766230/+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 1768734] Re: Restoring edge tiled windows on Wayland shrinks them
** Tags added: bionic -- 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/1768734 Title: Restoring edge tiled windows on Wayland shrinks them Status in Mutter: New Status in mutter package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 18.04 with a vanilla GNOME session under Wayland (the issue presents with the default Ubuntu session too). I've encountered this issue with applications that use Client-Side window decorations, which is most of the GNOME applications. Windows with borders drawn through the window manager do not have this issue. Steps to reproduce: 1. Open an application that uses client-side decorations, e.g. gnome-terminal. 2. Edge tile the window by snapping the window to the left or right screen edge via dragging or Super+left/right keyboard shortcut. 3. Unsnap the window to restore it to its non-tiled state. Expected behaviour: The position and dimensions of the window after undoing the edge tiling should be restored to exactly what it was prior to tiling. Observed behaviour: Every time the window is unsnapped from the edge, its size gets smaller. Repeating it over and over will lead to it eventually shrinking to the minimum possible size. I've found this issue only with client-side decorated windows, and only while restoring from split view / edge tiling. Restoring from a normal maximized state is ok. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1768734/+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 1768734] Re: Restoring edge tiled windows on Wayland shrinks them
The mutter MR https://gitlab.gnome.org/GNOME/mutter/merge_requests/801 should fix that issue. -- 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/1768734 Title: Restoring edge tiled windows on Wayland shrinks them Status in Mutter: New Status in mutter package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 18.04 with a vanilla GNOME session under Wayland (the issue presents with the default Ubuntu session too). I've encountered this issue with applications that use Client-Side window decorations, which is most of the GNOME applications. Windows with borders drawn through the window manager do not have this issue. Steps to reproduce: 1. Open an application that uses client-side decorations, e.g. gnome-terminal. 2. Edge tile the window by snapping the window to the left or right screen edge via dragging or Super+left/right keyboard shortcut. 3. Unsnap the window to restore it to its non-tiled state. Expected behaviour: The position and dimensions of the window after undoing the edge tiling should be restored to exactly what it was prior to tiling. Observed behaviour: Every time the window is unsnapped from the edge, its size gets smaller. Repeating it over and over will lead to it eventually shrinking to the minimum possible size. I've found this issue only with client-side decorated windows, and only while restoring from split view / edge tiling. Restoring from a normal maximized state is ok. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1768734/+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 1859376] Re: Problems with updates
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community- support/709. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: xorg (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/xorg/+question/687946 -- 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/1859376 Title: Problems with updates Status in xorg package in Ubuntu: Invalid Bug description: When you want to install the updates, the manager says that the packages are broken and that you try again. I did it and it didn't work, so I tried to update through the terminal and it didn't work either. I would like to receive help with this problem. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jan 12 18:55:35 2020 DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0742] InstallationDate: Installed on 2018-07-02 (559 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2c17 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer V5-131 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic root=UUID=a61bcc7e-d9c3-4e26-9abd-45c28eb06478 ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-13 (395 days ago) dmi.bios.date: 03/22/2013 dmi.bios.vendor: Acer dmi.bios.version: V2.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.17 dmi.modalias: dmi:bvnAcer:bvrV2.17:bd03/22/2013:svnAcer:pnV5-131:pvrV2.17:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.17: dmi.product.family: Type1Family dmi.product.name: V5-131 dmi.product.version: V2.17 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jan 3 21:00:06 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1859376/+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 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
I can't test the latest packages fully because I'm running eoan but I did install the packages from focal and it didn't work, while I'm home- built binaries from mid october do work, so maybe some regressed? The usbmuxd upgrade is fine, but libimobiledevice/libusbmuxd is what breaks it. I can't disentangle those two because the so version changed. I also tried installing focal in a VM - the pass through behaviour is not perfect, but the problems were the same. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1859375] [NEW] External subtitles do not work with LG Smart TV
Public bug reported: External subtitles do not work with LG Smart TV miniDLNA supports srt files so you don't have to implement something else, but... Ubuntu 19.10 has built-in DLNA/UPnP AV services offered by rygel package. It can be easily enabled via System Settings utility. It would be great to solve this problem because users would not have to install other software. ** Affects: rygel Importance: Unknown Status: Unknown ** Affects: rygel (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/rygel/issues #84 https://gitlab.gnome.org/GNOME/rygel/issues/84 ** Also affects: rygel via https://gitlab.gnome.org/GNOME/rygel/issues/84 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rygel in Ubuntu. https://bugs.launchpad.net/bugs/1859375 Title: External subtitles do not work with LG Smart TV Status in Rygel: Unknown Status in rygel package in Ubuntu: New Bug description: External subtitles do not work with LG Smart TV miniDLNA supports srt files so you don't have to implement something else, but... Ubuntu 19.10 has built-in DLNA/UPnP AV services offered by rygel package. It can be easily enabled via System Settings utility. It would be great to solve this problem because users would not have to install other software. To manage notifications about this bug go to: https://bugs.launchpad.net/rygel/+bug/1859375/+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 1859376] [NEW] Problems with updates
Public bug reported: When you want to install the updates, the manager says that the packages are broken and that you try again. I did it and it didn't work, so I tried to update through the terminal and it didn't work either. I would like to receive help with this problem. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jan 12 18:55:35 2020 DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0742] InstallationDate: Installed on 2018-07-02 (559 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2c17 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer V5-131 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic root=UUID=a61bcc7e-d9c3-4e26-9abd-45c28eb06478 ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-13 (395 days ago) dmi.bios.date: 03/22/2013 dmi.bios.vendor: Acer dmi.bios.version: V2.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Mimic dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.17 dmi.modalias: dmi:bvnAcer:bvrV2.17:bd03/22/2013:svnAcer:pnV5-131:pvrV2.17:rvnAcer:rnMimic:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.17: dmi.product.family: Type1Family dmi.product.name: V5-131 dmi.product.version: V2.17 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Jan 3 21:00:06 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1859376 Title: Problems with updates Status in xorg package in Ubuntu: New Bug description: When you want to install the updates, the manager says that the packages are broken and that you try again. I did it and it didn't work, so I tried to update through the terminal and it didn't work either. I would like to receive help with this problem. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jan 12 18:55:35 2020 DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0742] InstallationDate: Installed on 2018-07-02 (559 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2c17 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer
[Desktop-packages] [Bug 1859372] [NEW] duckduckgo icon in firefox (canonical and apt packages)is low res
Public bug reported: duckduckgo icon in firefox (canonical and apt packages) is low res and blurry ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 72.0.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20200107212822 CurrentDesktop: KDE Date: Sun Jan 12 17:23:17 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:727 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-10-19 (85 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=72.0.1/20200107212822 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1859372 Title: duckduckgo icon in firefox (canonical and apt packages)is low res Status in firefox package in Ubuntu: New Bug description: duckduckgo icon in firefox (canonical and apt packages) is low res and blurry ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: firefox 72.0.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BuildID: 20200107212822 CurrentDesktop: KDE Date: Sun Jan 12 17:23:17 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:727 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2019-10-19 (85 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=72.0.1/20200107212822 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859372/+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 1859369] [NEW] Gnome Cheese Overwrites gsettings
Public bug reported: I cannot get cheese to use my external USB webcam. cheese: 3.28.0-1ubuntu1 OS: 18.04.3 LTS on x86_64 gnome: 3.28.2 After plugging in the webcam, a new device appears at /dev/video2. Before running cheese, I set the camera setting as follows: $ gsettings set org.gnome.Cheese camera '/dev/video2' I then confirm the settings are correct: $ gsettings list-recursively org.gnome.Cheese org.gnome.Cheese countdown-duration 3 org.gnome.Cheese flash true org.gnome.Cheese photo-y-resolution 480 org.gnome.Cheese countdown true org.gnome.Cheese brightness 0.0 org.gnome.Cheese saturation 1.0 org.gnome.Cheese video-y-resolution 480 org.gnome.Cheese camera '/dev/video2' org.gnome.Cheese burst-repeat 4 org.gnome.Cheese photo-x-resolution 640 org.gnome.Cheese contrast 1.0 org.gnome.Cheese photo-path '' org.gnome.Cheese selected-effect 'identity' org.gnome.Cheese video-x-resolution 640 org.gnome.Cheese burst-delay 1000 org.gnome.Cheese hue 0.0 org.gnome.Cheese video-path '' I then run the Cheese app, open the Preferences menu and find that the Device field is greyed out and shows just one choice: "BisonCam, NB Pro: BisonCam, NB" I then run gsettings again: $ gsettings list-recursively org.gnome.Cheese org.gnome.Cheese countdown-duration 3 org.gnome.Cheese flash true org.gnome.Cheese photo-y-resolution 480 org.gnome.Cheese countdown true org.gnome.Cheese brightness 0.0 org.gnome.Cheese saturation 1.0 org.gnome.Cheese video-y-resolution 480 org.gnome.Cheese camera 'BisonCam, NB Pro: BisonCam, NB' org.gnome.Cheese burst-repeat 4 org.gnome.Cheese photo-x-resolution 640 org.gnome.Cheese contrast 1.0 org.gnome.Cheese photo-path '' org.gnome.Cheese selected-effect 'identity' org.gnome.Cheese video-x-resolution 640 org.gnome.Cheese burst-delay 1000 org.gnome.Cheese hue 0.0 org.gnome.Cheese video-path '' So, cheese seems to overwrite the gconf settings. I can't figure out how to get cheese to use my USB webcam! Additional info: $ sudo lsusb -v -s 003:036 Bus 003 Device 036: ID 0ac8:0302 Z-Star Microelectronics Corp. ZC0302 Webcam Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0ac8 Z-Star Microelectronics Corp. idProduct 0x0302 ZC0302 Webcam bcdDevice1.00 iManufacturer 1 V Micro. Corp. iProduct2 PC Camera iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 336 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 160mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x 1x 0 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes1 Transfer TypeIsochronous Synch Type None Usage Type Data wMaxPacketSize 0x0080 1x 128 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes3 Transfer
[Desktop-packages] [Bug 1859368] [NEW] size/transferred should be transferred/size in "network" tab
Public bug reported: 1) Ubuntu 19.10 2) Firefox 71 3) Transferred data should be displayed to the left of the total size. 4) Transferred data is displayed in the incorrect position. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1859368 Title: size/transferred should be transferred/size in "network" tab Status in firefox package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Firefox 71 3) Transferred data should be displayed to the left of the total size. 4) Transferred data is displayed in the incorrect position. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859368/+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 1859365] [NEW] Display "Downloading xx/xxKB" on the right bottom of Firefox.
Public bug reported: 1) Ubuntu 19.10 2) Firefox 71 3) When a webpage loads, "Transferring data from mozilla.org..." is displayed on the left bottom of Firefox. Could you display "Downloading xx/xxKB" on the right bottom of Firefox? 4) Message was not displayed. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1859365 Title: Display "Downloading xx/xxKB" on the right bottom of Firefox. Status in firefox package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Firefox 71 3) When a webpage loads, "Transferring data from mozilla.org..." is displayed on the left bottom of Firefox. Could you display "Downloading xx/xxKB" on the right bottom of Firefox? 4) Message was not displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1859365/+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 1858294] Re: Ubuntu 19.10 Razer Core X Saphire RX 580 - hot-plug freeze; kernel oops on boot
Appears to work with updated Ubuntu 18.04. I'll keep the 19.10 partition around for a little while in case I can provide further information. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1858294 Title: Ubuntu 19.10 Razer Core X Saphire RX 580 - hot-plug freeze; kernel oops on boot Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Hardware (verified working with Windows 10) - Lenovo X1 Carbon Gen 7 - Razer Core X with Saphire RX 580 - lspci-vvnn.log Software - New install of Ubuntu 19.10 - uname-a.log - version.log - mesa and amdgpu software from eoan repo Symptoms when hot connected - Doesn't work - Eventially freezes (mouse and clock frozen) - dmesg.0.before-hot-plug.txt - dmesg.1.not-yet-frozen-after-hot-plug.txt - dmesg.2.frozen-after-hot-plug.txt - Xorg.0.log - regdump_good.txt - regdump_broke.txt - on `sudo reboot`, GPu attached displays show shutdown banner (this is the only time they display anything) Symptoms when connected at startup - Crash - dmesg.3.kernel-oops-reboot-while-attached.jpg - Reported bug through GUI after reboot, I think this identifies it: ``` rhew@x1:/var/crash$ sudo cat _usr_bin_gnome-shell.124.uploaded 6be3909c-2f27-11ea-a76d-fa163ee63de6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1858294/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
** Bug watch removed: Xfce Bugzilla #16335 https://bugzilla.xfce.org/show_bug.cgi?id=16335 -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1859354] [NEW] xprinter xp-c2008 not to join ubuntu
Public bug reported: xprinter xp-c2008 not to join ubuntu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.7 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 13 01:25:55 2020 InstallationDate: Installed on 2019-09-20 (114 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lpstat: device for Follow-Me: smb://printservice.utwente.nl/Follow-Me MachineType: Dell Inc. Inspiron 3558 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Follow-Me.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Follow-Me.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=ddb1a77a-b195-4fb6-945f-df8dd841be84 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0G1TDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/20/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.product.sku: 06B0 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1859354 Title: xprinter xp-c2008 not to join ubuntu Status in cups package in Ubuntu: New Bug description: xprinter xp-c2008 not to join ubuntu ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.7 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 13 01:25:55 2020 InstallationDate: Installed on 2019-09-20 (114 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lpstat: device for Follow-Me: smb://printservice.utwente.nl/Follow-Me MachineType: Dell Inc. Inspiron 3558 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Follow-Me.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Follow-Me.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=ddb1a77a-b195-4fb6-945f-df8dd841be84 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0G1TDD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd01/20/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0G1TDD:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3558 dmi.product.sku: 06B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1859354/+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 1859353] [NEW] software-properties-gtk not working
Public bug reported: Additional Drivers /Software & Update not working Hello, I am running :- Description: Ubuntu 19.10 Release: 19.10 software-properties-gtk: Installed: 0.98.5 Candidate: 0.98.5 Version table: *** 0.98.5 500 500 http://ca.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status I am trying to run Additional Drivers /Software & Update . But it opened once and froze and never opened again. When I try running the command:- $ sudo software-properties-gtk Did a remove and reinstall of the same, but did not work. It returns:- ERROR:dbus.proxies:Introspect error on :1.2559:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Traceback (most recent call last): File "/usr/bin/software-properties-gtk", line 100, in app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 175, in __init__ self.backend.Reload(); File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 147, in __call__ **keywords) File "/usr/lib/python3/dist-packages/dbus/connection.py", line 653, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.2559 was not provided by any .service files Also, the syslog says:- name='com.ubuntu.SoftwareProperties' requested by ':1.2455' (uid=1000 pid=2267 comm="/usr/bin/python3 /usr/bin/software-properties-gtk " label="unconfined") (using servicehelper) Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Unable to init server: Could not connect: Connection refused Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Unable to init server: Could not connect: Connection refused Jan 12 11:58:55 gillZ dbus-daemon[2192]: [system] Successfully activated service 'com.ubuntu.SoftwareProperties' Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: Traceback (most recent call last): Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File "/usr/lib/software-properties/software-properties-dbus", line 68, in Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: server = SoftwarePropertiesDBus(bus, datadir=datadir) Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File "/lib/python3/dist-packages/softwareproperties/dbus/SoftwarePropertiesDBus.py", line 66, in __init__ Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: self._livepatch_service = LivepatchService() Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: File "/lib/python3/dist-packages/softwareproperties/LivepatchService.py", line 93, in __init__ Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: self._session = requests_unixsocket.Session() Jan 12 11:58:55 gillZ com.ubuntu.SoftwareProperties[2192]: NameError: name 'requests_unixsocket' is not defined Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: ERROR:dbus.proxies:Introspect error on :1.2457:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: Traceback (most recent call last): Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File "/usr/bin/software-properties-gtk", line 100, in Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, file=file) Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File "/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py", line 175, in __init__ Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: self.backend.Reload(); Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__ Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: return self._proxy_method(*args, **keywords) Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 147, in __call__ Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: **keywords) Jan 12 11:58:55 gillZ software-properties-drivers.desktop[3536]: File "/usr/lib/python3/dist-packages/dbus/connection.py", line 653, in call_blocking ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1859353 Title: software-properties-gtk not working Status in gnome-shell package in Ubuntu: New Bug
[Desktop-packages] [Bug 1511244] Re: Mouse pointer flickers at using DisplayLink
** Changed in: xorg (Ubuntu) Status: Expired => Confirmed -- 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/1511244 Title: Mouse pointer flickers at using DisplayLink Status in xorg package in Ubuntu: Confirmed Bug description: I have a three screen setup, the built-in laptop screen, a monitor connected directly into the laptop via DisplayPort, and a monitor connected via a USB DisplayLink Adapter. What happens is that when a monitor is connected via the USB DisplayLink Adapter, the mouse icon flickers only on the laptop screen and monitor connected via DisplayPort (not on the monitor connected via USB DisplayLink Adapter). However, this is also reproducible if I either deactivate the built-in laptop screen, or disconnect the DisplayPort connected monitor. WORKAROUND: Disconnect the USB DisplayLink Adapter for the computer. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Thu Oct 29 08:29:50 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:503c] InstallationDate: Installed on 2015-09-25 (33 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: LENOVO 20DT0003GE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-31-generic root=UUID=500f2ef6-7426-42ec-9fe2-88e9bcea ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JDET50WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: Intel powered classmate PC dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJDET50WW(1.12):bd03/25/2015:svnLENOVO:pn20DT0003GE:pvrThinkPadL450:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DT0003GE dmi.product.version: ThinkPad L450 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Oct 29 07:45:59 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9782 vendor ENC xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1511244/+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 1859347] Re: cups-browsed crashed with SIGSEGV in unlink_chunk()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1859347 Title: cups-browsed crashed with SIGSEGV in unlink_chunk() Status in cups-filters package in Ubuntu: New Bug description: I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.26.1-1 Uname: Linux 5.4.10-050410-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CupsErrorLog: Date: Sun Jan 12 14:39:42 2020 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2018-12-02 (405 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for Samsung-CLX-8640-8650: lpd://10.39.106.2/lp MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx Papersize: letter PpdFiles: Samsung-CLX-8640-8650: Samsung CLX-8640 8650 Series PS ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.10-050410-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f5c60543ad1 : cmp 0x18(%rax),%rdi PC (0x7f5c60543ad1) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: cups-filters StacktraceTop: unlink_chunk (p=p@entry=0x561be25b4fc0, av=0x7f5c60695b80 ) at malloc.c:1459 _int_malloc (av=av@entry=0x7f5c60695b80 , bytes=bytes@entry=184) at malloc.c:4041 __libc_calloc (n=, elem_size=) at malloc.c:3428 () at /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_message_loader_queue_messages () at /lib/x86_64-linux-gnu/libdbus-1.so.3 Title: cups-browsed crashed with SIGSEGV in unlink_chunk() UpgradeStatus: Upgraded to focal on 2018-12-02 (405 days ago) UserGroups: dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1859347/+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 1859339] [NEW] Freeze
Public bug reported: Freeze screen, keyboard block, mouse smile, activity in court frozen regularly. only possibility to restart in force. it also restarts itself regularly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jan 12 17:30:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7c51] InstallationDate: Installed on 2020-01-06 (6 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Micro-Star International Co., Ltd. MS-7C51 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=64715203-5a05-42f8-93df-f2967370ca5d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M-A PRO (MS-7C51) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd09/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320M-APRO(MS-7C51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C51 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1859339 Title: Freeze Status in xorg package in Ubuntu: New Bug description: Freeze screen, keyboard block, mouse smile, activity in court frozen regularly. only possibility to restart in force. it also restarts itself regularly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Jan 12 17:30:29 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7c51] InstallationDate: Installed on 2020-01-06 (6 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Micro-Star International Co., Ltd. MS-7C51 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=64715203-5a05-42f8-93df-f2967370ca5d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M-A PRO (MS-7C51) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd09/03/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C51:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320M-APRO(MS-7C51):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M.
[Desktop-packages] [Bug 1858860] Re: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive
Done https://github.com/storaged-project/udisks/issues/723 ** Bug watch added: github.com/storaged-project/udisks/issues #723 https://github.com/storaged-project/udisks/issues/723 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1858860 Title: Gnome Disk Utility Issues incorrect command when ejecting a SATA Harddisk or Solid State Drive Status in gnome-disk-utility package in Ubuntu: New Bug description: Use case: As a user of hot swap-able SATA disks using a Harddrive Riser over eSATA. I need a safe, easy and convenient way to remove the hot swap-able SATA disk without rebooting and without having to go to the command line. When attempting to eject an harddisk or a solid state disk using the eject button in "Gnome Disk Utility" it issues the 'eject' command which results in an IOCTL error. The correct commands the eject button in the GUI should issue to eject a SATA HDD or SSD are: # where X is the drive letter of the drive being worked with # -Y Put drive to sleep sudo hdparm -Y /dev/sdX # remove the device from the kernel sudo sh -c 'echo 1 > /sys/block/sdX/device/delete' Please see the screen shots for the error. This should be an easy fix (20 minutes) for someone who is good a programmer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-disk-utility 3.28.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 8 21:07:32 2020 InstallationDate: Installed on 2018-11-11 (423 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1858860/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I have the same issue on a HP Spectre Folio 13 with Xubuntu 18.04. Internal microphone does not work. Headset microphone is detected when connected through a usb-c hub. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1844445] Re: gnome-session-binary crashed with SIGSEGV in tcache_thread_shutdown()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/185 Title: gnome-session-binary crashed with SIGSEGV in tcache_thread_shutdown() Status in gnome-session package in Ubuntu: Confirmed Bug description: I saw this crash shortly after boot. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-session-bin 3.33.92-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-lowlatency 5.3.0-rc8 Uname: Linux 5.3.0-10-lowlatency x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Sep 17 12:56:57 2019 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-session/gnome-session-binary InstallationDate: Installed on 2016-02-19 (1306 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: /usr/lib/gnome-session/gnome-session-binary --debug --systemd-service --session=gnome SegvAnalysis: Segfault happened at: 0x7effd96109e8 <__malloc_arena_thread_freeres+88>: mov0x0(%r13),%rax PC (0x7effd96109e8) ok source "0x0(%r13)" (0x7eff0002) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-session StacktraceTop: tcache_thread_shutdown () at malloc.c:2963 __malloc_arena_thread_freeres () at arena.c:949 __libc_thread_freeres () at thread-freeres.c:38 start_thread (arg=) at pthread_create.c:493 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: gnome-session-binary crashed with SIGSEGV in tcache_thread_shutdown() UpgradeStatus: Upgraded to eoan on 2019-06-23 (86 days ago) UserGroups: adm audio bumblebee cdrom dip docker libvirt libvirtd lpadmin lxd mock plugdev sambashare sbuild sudo wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/185/+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 118988] Re: No way to disable trash in nautilus
The http://www.theitcommunity.com/wiki/ link I posted above no longer works … a step-by-step tutorial on how to (completely) disable Gnome's Trash can now be found on my Github page: http://htmlpreview.github.io/?https://github.com/Cordic77/libgio- disable-trash/blob/master/Globally%20disable%20GNOME%27s%20Trash%20in %20Debian-based%20distributions.htm -- 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/118988 Title: No way to disable trash in nautilus Status in Nautilus: Won't Fix Status in nautilus package in Ubuntu: Triaged Bug description: This is a similar 'bug' to #12893 but what I think there should be is a check-box in the nautilus configuration that just says 'Disable the trash and delete files immediately' I realize you can shift delete, but there should be a way to just disable the trash all together. You can do this in both windows and OSX so there is no reason it shouldn't be possible in Linux. I believe the ideal situation would be the nautilus configuration as it is now with two additional check-boxes: 1. Disable the trash and delete files immediately. 2. Disable the trash for removable media and delete files immediately. Option two check-box would get greyed out when option 1 was checked. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/118988/+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 1859326] [NEW] When I logut and try to log in, the password field is hidden
Public bug reported: Hello, I have upgraded from Ubuntu 19.04 to Ubuntu 19.10. Now, When I logout, the lock-screen background is shown on the screen, usaully i used to press any button, then the lock-screen moves up, and the user login form appears, but now the login form never appears, only the lock-screen taking all of the screen, and I have to enter the password without seeing the form and press Enter to log in, I can't even see which user is selected. Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:0a: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 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 14:24:27 2020 DistUpgraded: 2020-01-12 13:15:58,832 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 430.50, 5.0.0-38-generic, x86_64: installed nvidia, 430.50, 5.3.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:2166] Subsystem: Hewlett-Packard Company GK208M [GeForce GT 740M] [103c:2166] InstallationDate: Installed on 2019-05-02 (255 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=0335c8fd-b7c3-4fc4-bf52-2a78bfe22f38 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2020-01-12 (0 days ago) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.40 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.23:bd09/26/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08971030410610100:rvnHewlett-Packard:rn2166:rvr29.40:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.sku: F1E53EA#ABV dmi.product.version: 08971030410610100 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.2.1-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+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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 third-party-packages 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/1859326 Title: When I logut and try to log in, the password field is hidden Status in xorg package in Ubuntu: New Bug description: Hello, I have upgraded from Ubuntu 19.04 to Ubuntu 19.10. Now, When I logout, the lock-screen background is shown on the screen, usaully i used to press any button, then the lock-screen moves up, and the user login form appears, but now the login form never appears, only the lock-screen taking all of the
[Desktop-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
iPhone 7, latest software update iOS 13.3 (17C54), seems to fix this. I could successfully transfer files TO the phone using ubuntu 18.04.3 LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Incomplete Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1859325] Re: Column selection in LibreOffice Calc is very slow with GTK3
By the way, the slowness is much worse in LibreOffice version 6.2 and
above. In the ubuntu build version (which is version 6.0.7), the
slowness is not too bad, but still significant as compared to non-gtk3
mode.
--
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/1859325
Title:
Column selection in LibreOffice Calc is very slow with GTK3
Status in libreoffice package in Ubuntu:
New
Bug description:
Column selection in a Calc spreadsheet is very slow under gtk3.
Steps to Reproduce:
1. Open the attached ODS file with LibreOffice Calc in gtk3 mode.
("Help > About LibreOffice" should show "VCL: gtk3". If not, "export
SAL_USE_VCLPLUGIN=gtk3" and start libreoffice from terminal)
2. Try to select the entire columns A:G.
--> The selection is very slow.
3. Open the ODS file in "gen" mode, then select columns A:G.
("export SAL_USE_VCLPLUGIN=gen" and start libreoffice from terminal)
--> The selection is fast.
This bug was initially reported on the LibreOffice bugzilla, but it is
suspected to be specific to Ubuntu 18.04 and gtk3, so I raise this issue here.
https://bugs.documentfoundation.org/show_bug.cgi?id=129915
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 12 18:52:45 2020
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2019-12-14 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1859325/+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 1859325] [NEW] Column selection in LibreOffice Calc is very slow with GTK3
Public bug reported:
Column selection in a Calc spreadsheet is very slow under gtk3.
Steps to Reproduce:
1. Open the attached ODS file with LibreOffice Calc in gtk3 mode.
("Help > About LibreOffice" should show "VCL: gtk3". If not, "export
SAL_USE_VCLPLUGIN=gtk3" and start libreoffice from terminal)
2. Try to select the entire columns A:G.
--> The selection is very slow.
3. Open the ODS file in "gen" mode, then select columns A:G.
("export SAL_USE_VCLPLUGIN=gen" and start libreoffice from terminal)
--> The selection is fast.
This bug was initially reported on the LibreOffice bugzilla, but it is
suspected to be specific to Ubuntu 18.04 and gtk3, so I raise this issue here.
https://bugs.documentfoundation.org/show_bug.cgi?id=129915
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 12 18:52:45 2020
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2019-12-14 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
** Attachment added: "Test ods file."
https://bugs.launchpad.net/bugs/1859325/+attachment/5319399/+files/selection.ods
--
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/1859325
Title:
Column selection in LibreOffice Calc is very slow with GTK3
Status in libreoffice package in Ubuntu:
New
Bug description:
Column selection in a Calc spreadsheet is very slow under gtk3.
Steps to Reproduce:
1. Open the attached ODS file with LibreOffice Calc in gtk3 mode.
("Help > About LibreOffice" should show "VCL: gtk3". If not, "export
SAL_USE_VCLPLUGIN=gtk3" and start libreoffice from terminal)
2. Try to select the entire columns A:G.
--> The selection is very slow.
3. Open the ODS file in "gen" mode, then select columns A:G.
("export SAL_USE_VCLPLUGIN=gen" and start libreoffice from terminal)
--> The selection is fast.
This bug was initially reported on the LibreOffice bugzilla, but it is
suspected to be specific to Ubuntu 18.04 and gtk3, so I raise this issue here.
https://bugs.documentfoundation.org/show_bug.cgi?id=129915
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice-core 1:6.0.7-0ubuntu0.18.04.10
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 12 18:52:45 2020
ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
InstallationDate: Installed on 2019-12-14 (28 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1859325/+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 1859320] [NEW] Multiple sign-in options in menu of Ubuntu Software
Public bug reported: Why does Ubuntu Software have (effectively) two sign in / sign out options for the same thing? Steps to reproduce * Install 20.04 (or indeed 19.10, not tested on previous releases) * Launch Ubuntu Software Expected behaviour * Option to sign in to Snap Store should exist * Option to sign in to Ubuntu One should not exist Actual behaviour * Options for signing into Ubuntu One and Snap Store are present ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.30.6-2ubuntu11 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 10:29:11 2020 InstallationDate: Installed on 2020-01-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu11 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-01-12 10-28-59.png" https://bugs.launchpad.net/bugs/1859320/+attachment/5319371/+files/Screenshot%20from%202020-01-12%2010-28-59.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1859320 Title: Multiple sign-in options in menu of Ubuntu Software Status in gnome-software package in Ubuntu: New Bug description: Why does Ubuntu Software have (effectively) two sign in / sign out options for the same thing? Steps to reproduce * Install 20.04 (or indeed 19.10, not tested on previous releases) * Launch Ubuntu Software Expected behaviour * Option to sign in to Snap Store should exist * Option to sign in to Ubuntu One should not exist Actual behaviour * Options for signing into Ubuntu One and Snap Store are present ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.30.6-2ubuntu11 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 10:29:11 2020 InstallationDate: Installed on 2020-01-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu11 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1859320/+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 1859319] [NEW] widget factory slighty too wide for common 1366x768 display
Public bug reported: I'm using a ThinkPad X220 to test the Ubuntu default theme. It has a wildly common 1366x768 display panel. At the time of writing, around 25% of installs have such a resolution - https://ubuntu.com/desktop/statistics The default non-hiding 48px launcher, and width of the widget factory, means that it's impossible to get the entire application on screen at once. There appears to be some space which could be saved by shrinking horizontally a couple of components on each page. Steps to reproduce * Install Ubuntu 20.04. * Set system resolution to 1366x768 * Install gtk3-examples * Alt-f2, gtk3-widget-factory Expected outcome * Entire widget factory should fit on the screen Actual outcome * The widget factory window is off the right hand side of the screen Workaround Set the launcher to auto hide, to make room. I don't consider this suitable, because part of the point of gtk widget factory is to test the theme, the experience, the out of the box install. Being unable to actually get the window on the screen seems a flawed set of tests. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gtk-3-examples 3.24.13-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 10:13:41 2020 InstallationDate: Installed on 2020-01-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-01-12 10-20-48.png" https://bugs.launchpad.net/bugs/1859319/+attachment/5319366/+files/Screenshot%20from%202020-01-12%2010-20-48.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1859319 Title: widget factory slighty too wide for common 1366x768 display Status in gtk+3.0 package in Ubuntu: New Bug description: I'm using a ThinkPad X220 to test the Ubuntu default theme. It has a wildly common 1366x768 display panel. At the time of writing, around 25% of installs have such a resolution - https://ubuntu.com/desktop/statistics The default non-hiding 48px launcher, and width of the widget factory, means that it's impossible to get the entire application on screen at once. There appears to be some space which could be saved by shrinking horizontally a couple of components on each page. Steps to reproduce * Install Ubuntu 20.04. * Set system resolution to 1366x768 * Install gtk3-examples * Alt-f2, gtk3-widget-factory Expected outcome * Entire widget factory should fit on the screen Actual outcome * The widget factory window is off the right hand side of the screen Workaround Set the launcher to auto hide, to make room. I don't consider this suitable, because part of the point of gtk widget factory is to test the theme, the experience, the out of the box install. Being unable to actually get the window on the screen seems a flawed set of tests. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gtk-3-examples 3.24.13-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 12 10:13:41 2020 InstallationDate: Installed on 2020-01-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1859319/+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 1851674] Re: All deb packages as being listed as "Proprietary" when opened in gnome-software
Doesn't appear to have been looked at yet, but still a longstanding issue ** Changed in: gnome-software (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1851674 Title: All deb packages as being listed as "Proprietary" when opened in gnome-software Status in gnome-software package in Ubuntu: New Bug description: It seems all open-source packages, including for example the official package for lshw (https://packages.ubuntu.com/disco/lshw) seem to be listed as "Proprietary" in gnome-software/Ubuntu Software. This seems to happen in Ubuntu 18.04 and newer, with official and 3rd party packages (like those from virtualbox.org). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1851674/+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 1849859] Re: smb printing fails
Despite really a lot of updates (samba, cups) the "held for authentication" problem persists! I hope, it's comming soon a solution. This is very disappointing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+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
