[Desktop-packages] [Bug 1851896] Re: [snap] Changes in desktop file get overwritten
When I however add in the init file it gets sourced and shows up in chrome://version but does not work as prefers-color-scheme is still light. If I supply it at the command line it correctly works but shows up twice on chrome://version. Should I report this in a seperate bug or in the chromium bug tracker? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1851896 Title: [snap] Changes in desktop file get overwritten Status in chromium-browser package in Ubuntu: Invalid Bug description: Changes in the chromium_chromium.desktop file get overwritten. This includes flags like --force-dark-mode etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850651] Re: Authentication constantly re-requested for Google
Yes it will, I am working on it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: Fix Committed Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1850651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1850651] Re: Authentication constantly re-requested for Google
I know this is fixed in Thunderbird 69.0.1 and 68.2. can this be put into the repository for Ubuntu 16.04 LTS? Jeremy On Tue, Nov 19, 2019, 10:41 PM Olivier Tilloy wrote: > ** Changed in: thunderbird (Ubuntu Xenial) >Status: In Progress => Fix Committed > > ** Changed in: thunderbird (Ubuntu Disco) >Status: In Progress => Fix Committed > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1852540). > https://bugs.launchpad.net/bugs/1850651 > > Title: > Authentication constantly re-requested for Google > > Status in Mozilla Thunderbird: > Fix Released > Status in thunderbird package in Ubuntu: > Fix Released > Status in thunderbird source package in Xenial: > Fix Committed > Status in thunderbird source package in Bionic: > Fix Committed > Status in thunderbird source package in Disco: > Fix Committed > Status in thunderbird source package in Eoan: > Fix Committed > Status in thunderbird source package in Focal: > Fix Released > > Bug description: > When I use Thunderbird, it keeps failing to connect with my Google > (Gmail) accounts. It keeps asking for authentication via the web > portal, I seem to successfully give Thunderbird authentication, but no > messages come in and, soon afterwards, the web portal comes up asking > for login again. > > I am using OAuth2 (so this ( https://support.mozilla.org/en- > US/questions/1201406 ) doesn't help. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 > ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 > Uname: Linux 5.0.0-32-generic x86_64 > AddonCompatCheckDisabled: False > ApportVersion: 2.20.10-0ubuntu27.1 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: adam 3444 F pulseaudio >/dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio > BuildID: 20191007090404 > Channel: Unavailable > CurrentDesktop: ubuntu:GNOME > Date: Wed Oct 30 14:56:50 2019 > Extensions: extensions.sqlite corrupt or missing > ForcedLayersAccel: False > IfupdownConfig: ># interfaces(5) file used by ifup(8) and ifdown(8) >auto lo >iface lo inet loopback > IncompatibleExtensions: Unavailable (corrupt or non-existant > compatibility.ini or extensions.sqlite) > InstallationDate: Installed on 2017-08-03 (817 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > IpRoute: >default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 >10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown >169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown >172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 >192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 > metric 600 > Locales: extensions.sqlite corrupt or missing > Plugins: Shockwave Flash - > /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so > (browser-plugin-freshplayer-pepperflash) > PrefSources: prefs.js > Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 > RelatedPackageVersions: browser-plugin-freshplayer-pepperflash > 0.3.9-0ubuntu4 > RunningIncompatibleAddons: False > SourcePackage: thunderbird > Themes: extensions.sqlite corrupt or missing > UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) > dmi.bios.date: 01/21/2016 > dmi.bios.vendor: LENOVO > dmi.bios.version: G1ETB0WW (2.70 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 2347GU8 > dmi.board.vendor: LENOVO > dmi.board.version: Not Defined > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Not Available > dmi.modalias: > dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: > dmi.product.family: ThinkPad T430 > dmi.product.name: 2347GU8 > dmi.product.sku: LENOVO_MT_2347 > dmi.product.version: ThinkPad T430 > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/thunderbird/+bug/1850651/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: Fix Committed Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: When I use Thunderbird, it keeps failing to
[Desktop-packages] [Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
Ran into the same scanner issue today with a Brother MFC-6490CW under Ubuntu 18.04 (factory installed by Dell and fully updated before attempting printer/scanner install). Found pdc's post on askubuntu.com ( https://askubuntu.com/a/1054065/314730 ) first, which linked to staedtler-przyborski's symlink answer ( https://bugs.launchpad.net/ubuntu/+source/sane- backends/+bug/1728012/comments/25 ). Worked a treat - thanks so much! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1728012 Title: Many 3rd party scanner drivers are broken by a sane change Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Bionic: Fix Released Status in sane-backends package in Debian: Fix Released Bug description: To the sponsor: Please upload to bionic using the attached sane- backends_lp1728012_bionic.debdiff. [Impact] * Starting with Ubuntu 17.10, Ubuntu changed the directory where sane dll looks for third party drivers. This configuration effectively broke backward compatibility for all existing third-party drivers. * A large swath of these third party drivers (most of them) are no longer supported by the OEM, so maintaining compatibility is important. * No open source replacement drivers are currently available, nor does the community have the resources to easily replace them. * This bug represents a substantial portion of the scanners in use. Scanners known to be affected include, but are not limited to: - Brother Scanners (all Brother scanners before brscan4) - DCP-145C - DCP-163C - DCP-165C - DCP-167C - DCP-185C - DCP-195C - DCP-197C - DCP-365CN - DCP-373CW - DCP-375CW - DCP-377CW - DCP-383C - DCP-385C - DCP-387C - DCP-395CN - DCP-585CW - DCP-6690CW - DCP-7030 - DCP-7040 - DCP-7045N - DCP-8070D - DCP-8080DN - DCP-8085DN - DCP-9010CN - DCP-9040CN - DCP-9042CDN - DCP-9045CDN - DCP-J125 - DCP-J315W - DCP-J515W - DCP-J715W - MFC-250C - MFC-255CW - MFC-257CW - MFC-290C - MFC-295CN - MFC-297C - MFC-490CW - MFC-495CW - MFC-5490CN - MFC-5890CN - MFC-5895CW - MFC-6490CW - MFC-6890CDW - MFC-7320 - MFC-7340 - MFC-7345N - MFC-7440N - MFC-7450 - MFC-7840N - MFC-7840W - MFC-790CW - MFC-795CW - MFC-8370DN - MFC-8380DN - MFC-8480DN - MFC-8510DN - MFC-8680DN - MFC-8880DN - MFC-8890DW - MFC-9010CN - MFC-9120CN - MFC-9320CW - MFC-9440CN - MFC-9450CDN - MFC-9840CDW - MFC-990CW - MFC-J220 - MFC-J265W - MFC-J270W - MFC-J410 - MFC-J410W - MFC-J415W - MFC-J615W - MFC-J630W - Dell MFP Laser Printer 1135n - Epson Scanners - All scanners supported by the libsane-epk driver - All scanners supported by the iscan driver - Epson Perfection V10 - Epson Perfection V1000 - Epson WorkForce GT-1500 - Epson Perfection V33 - Samsung M2070 - Xerox Workcentre 3225 * This was working in the 17.04 release. 18.04 is an LTS release, so backporting is warranted for the 18.04 release. [Test Case] * Following the standard installation procedures for any of the affected scanner drivers results in the driver files being installed to /usr/lib/sane/, and sane looking for them in /usr/lib/x86_64-linux- gnu/sane. When xsane is run, the scanner is not found. * Install the libsane1, libsane-common and sane-utils packages from bionic-proposed and confirm that it now finds drivers in /usr/lib/sane. [Regression Potential] * The proposed change is based on an upstream commit, and the patch is functional and stable in both 19.04 and 19.10. Low regression risk. [Other Info] * Third party sane drivers in previous version of sane were located under /usr/lib/sane/, however, the current version of sane on Ubuntu only looks for 64 bit drivers under the /usr/lib/x86_64-linux-gnu/sane directory. /usr/lib64 and /usr/lib64/sane are other directories old drivers are known to install files to. * The addition of symlinks alone does not appear to fix this issue, though it may make the scanner detectable. Changes to udev rules are also needed to allow proper communications to the scanners. A selection of workarounds, including working (though not ideal) udev rules for a number of scanners has been posted to the sane troubleshooting guide: help.ubuntu.com/community/sane_Troubleshooting#The_symlink_and_udev_tricks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1850651] Re: Authentication constantly re-requested for Google
** Changed in: thunderbird (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: thunderbird (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: Fix Committed Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1850651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840726] Re: Write files to a CD or DVD does not mention how to install Brasero
[Expired for gnome-user-docs (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-user-docs (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1840726 Title: Write files to a CD or DVD does not mention how to install Brasero Status in gnome-user-docs package in Ubuntu: Expired Bug description: On https://help.ubuntu.com/stable/ubuntu-help/files-disc-write.html.en there are instructions how to write a CD/DVD, but it does not mention that you need to install Brasero to do so. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1840726/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
It seems to be a problem from the chip series itself since in 16.04.03 it also does not get detected. Or the internal mic is flawed, I still need to test in windows 10 to be sure if it is a alsa driver problem to this chip or a hardware problem -- 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: New 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 1853221] [NEW] Two monitors displaying same image
Public bug reported: I am using two monitors, they both are displaying the same image. In settings, only one monitor is recognized (technically they have the same name, though). I have tried to go into arandr to see what I could do but only one monitor is recognized there. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 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.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:40:28 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:075b] InstallationDate: Installed on 2019-11-02 (18 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=db637f82-b923-4a94-b32e-7c89cdc41956 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.12.0 dmi.board.name: 05HM5Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. 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/1853221 Title: Two monitors displaying same image Status in xorg package in Ubuntu: New Bug description: I am using two monitors, they both are displaying the same image. In settings, only one monitor is recognized (technically they have the same name, though). I have tried to go into arandr to see what I could do but only one monitor is recognized there. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 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.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:40:28 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:075b] InstallationDate: Installed on 2019-11-02 (18 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. XPS 13 9360 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=db637f82-b923-4a94-b32e-7c89cdc41956 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.12.0 dmi.board.name: 05HM5Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05HM5Y:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. 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:
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
indeed, the headphone mic is working perfectly, so it`s not detecting the internal, i am still to test the internal mic in others SOs to attest that is an alsa-driver bug. -- 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: New 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 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
** Attachment added: "modinfo-i915.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5306547/+files/modinfo-i915.txt -- 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/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in mutter package in Ubuntu: New Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
*-display description: VGA compatible controller product: HD Graphics 620 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 02 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:140 memory:eb00-ebff memory:a000-afff ioport:f000(size=64) memory:c-d The two monitors are 2560x1440, with no scaling. But I do use a 1.25 font scaling factor in gnome-tweaks. I am using the ubuntu-x-swat ppa, which was an attempt to resolve some previous graphics issues, but I can try removing this again if you'd like me to test? libdrm-amdgpu1: ubuntu-x-swat/updates/ubuntu libdrm-common: ubuntu-x-swat/updates/ubuntu libdrm-dev: ubuntu-x-swat/updates/ubuntu libdrm-intel1: ubuntu-x-swat/updates/ubuntu libdrm-nouveau2: ubuntu-x-swat/updates/ubuntu libdrm-radeon1: ubuntu-x-swat/updates/ubuntu libdrm2: ubuntu-x-swat/updates/ubuntu libegl-mesa0: ubuntu-x-swat/updates/ubuntu libegl1-mesa: ubuntu-x-swat/updates/ubuntu libgbm1: ubuntu-x-swat/updates/ubuntu libgl1-mesa-dev: ubuntu-x-swat/updates/ubuntu libgl1-mesa-dri: ubuntu-x-swat/updates/ubuntu libgl1-mesa-glx: ubuntu-x-swat/updates/ubuntu libglapi-mesa: ubuntu-x-swat/updates/ubuntu libglx-mesa0: ubuntu-x-swat/updates/ubuntu libllvm9: ubuntu-x-swat/updates/ubuntu libxatracker2: ubuntu-x-swat/updates/ubuntu mesa-common-dev: ubuntu-x-swat/updates/ubuntu mesa-va-drivers: ubuntu-x-swat/updates/ubuntu mesa-vdpau-drivers: ubuntu-x-swat/updates/ubuntu ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+attachment/5306546/+files/journalctl.txt -- 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/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in mutter package in Ubuntu: New Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852844] Re: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line
** Changed in: glib Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1852844 Title: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line Status in GLib: Fix Released Status in udisks: New Status in udisks2 package in Ubuntu: Triaged Bug description: An external disk device is declared in '/etc/fstab' with 'auto,nofail,users' options: UUID=aa083302-...-b66c0715eaf1 /media/ushakov/TOSHIBA_SYSTEM ext4 nodev,nosuid,auto,nofail,users 0 2 It is then successfully mounted automatically upon being connected. It can further be unmounted successfully without `sudo` from command line, e.g.: `umount $mount_point`. Meanwhile an attempt to unmount this device from Nautilus/Files UI results in an "Authentication Required" message: "Authentication is required to unmount External USB3.0 (/dev/sdc3) mounted by another user". The expected Nautilus/Files UI behavior would be that the disk device is unmounted silently or just with an non-intrusive notification upon a click on the "Unmount" button near the device label. Package suspected: nautilus: nautilus/bionic-updates,now 1:3.26.4-0~ubuntu18.04.4 amd64 [installed,automatic] $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-35.38~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 09:50:54 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'394' b'org.gnome.nautilus.window-state' b'geometry' b"'1279x749+193+153'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-10-15 (32 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1852844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 717870] Re: 1002:954f [ASRock P55M Pro] RV710: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
Launchpad has imported 5 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=35045. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2011-03-05T14:44:20+00:00 Freedesktop-treblig wrote: Hi, I've got a repeatable oops that happens when viewing full screen video in flash in chromium, under kwin (with effects enabled) and switching virtual desktop/workspace on ATI Technologies Inc RV710 [Radeon HD 4350]. Hardware: ATI Technologies Inc RV710 [Radeon HD 4350] in an ASRock P55M Pro motherboard, with an i7-860 CPU, and 8GB RAM, connected to Dell S2409W display via DVI. OS: Ubuntu Natty upto date as of today, 64bit install, running KDE. Kernel: Daily build from DRM next from http://kernel.ubuntu.com/~kernel- ppa/mainline/drm-next/current/ linux- image-2.6.38-996-generic_2.6.38-996.201103041138_amd64.deb claims to be commit e73f88af66fcc50083fae4b7e1c39b469179a97a DRM/mesa/etc: ii libdrm-radeon12.4.23-1ubuntu3 ii libdrm2 2.4.23-1ubuntu3 ii libgl1-mesa-dri 7.10.1~git20110215.cc1636b6-0 I've got a 3x3 virtual desktop setup, and am running Chromium and go to youtube and pop a video full screen; and move around the virtual desktop with ctrl-alt-arrows. The oops below was produced twice. I've got a bunch of related symptoms; I installed the daily build because I was getting instances of [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35! (which I think is EDEADLOCK) doing similar combinations of going in and out of full screen flash. I've also seen when I try to go into full screen rapid flickering as if it can't decide whether to go into full screen or stay out; once that's triggered that flickering can repeat itself when starting other apps. This corresponds to Ubuntu bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717870 and possibly also ubuntu bug 717889 Mar 5 22:12:17 major kernel: [ 495.890854] [ cut here ] Mar 5 22:12:17 major kernel: [ 495.890882] kernel BUG at /home/kernel-ppa/COD/linux/drivers/gpu/drm/ttm/ttm_bo.c:272! Mar 5 22:12:17 major kernel: [ 495.890917] invalid opcode: [#1] SMP Mar 5 22:12:17 major kernel: [ 495.890939] last sysfs file: /sys/devices/system/cpu/cpu7/topology/thread_siblings Mar 5 22:12:17 major kernel: [ 495.890971] CPU 1 Mar 5 22:12:17 major kernel: [ 495.890981] Modules linked in: ip6table_filter ip6_tables ebtable_nat ebtables ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ipt_REJECT binfmt_misc xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter ip_tables x_tables bridge stp kvm_intel kvm dm_crypt snd_hda_codec_hdmi snd_hda_codec_via snd_hda_intel snd_seq_midi snd_hda_codec snd_rawmidi snd_hwdep snd_seq_midi_event snd_seq snd_pcm snd_seq_device snd_timer snd ppdev soundcore parport_pc snd_page_alloc lp parport radeon usbhid usb_storage ttm hid firewire_ohci drm_kms_helper uas drm firewire_core r8169 pata_via crc_itu_t i2c_algo_bit configfs Mar 5 22:12:17 major kernel: [ 495.891289] Mar 5 22:12:17 major kernel: [ 495.893682] Pid: 42, comm: kworker/1:1 Not tainted 2.6.38-996-generic #201103041138 P55M Pro/To Be Filled By O.E.M. Mar 5 22:12:17 major kernel: [ 495.896183] RIP: 0010:[] [] ttm_bo_ref_bug+0x9/0x10 [ttm] Mar 5 22:12:17 major kernel: [ 495.898561] RSP: :8802277ebd90 EFLAGS: 00010202 Mar 5 22:12:17 major kernel: [ 495.900903] RAX: a00f6801 RBX: RCX: 880222bb3120 Mar 5 22:12:17 major kernel: [ 495.903223] RDX: RSI: RDI: 880222bb308c Mar 5 22:12:17 major kernel: [ 495.905545] RBP: 8802277ebd90 R08: R09: Mar 5 22:12:17 major kernel: [ 495.907870] R10: 8800c7453b58 R11: R12: 880222bb308c Mar 5 22:12:17 major kernel: [ 495.910371] R13: a00f3d80 R14: 880222bb3048 R15: Mar 5 22:12:17 major kernel: [ 495.912659] FS: () GS:8800c744() knlGS: Mar 5 22:12:17 major kernel: [ 495.914975] CS: 0010 DS: ES: CR0: 8005003b Mar 5 22:12:17 major kernel: [ 495.917310] CR2: f0969000 CR3: 0001dc19a000 CR4: 06e0 Mar 5 22:12:17 major kernel: [ 495.919642] DR0: DR1: DR2: Mar 5 22:12:17 major kernel: [ 495.921973] DR3: DR6: 0ff0 DR7: 0400 Mar 5 22:12:17 major kernel: [ 495.924274] Process kworker/1:1 (pid: 42, threadinfo 8802277ea000, task 8802277bc440) Mar 5 22:12:17 major kernel: [ 495.926774] Stack: Mar 5 22:12:17
[Desktop-packages] [Bug 1852844] Re: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line
** Changed in: udisks Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1852844 Title: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line Status in GLib: New Status in udisks: New Status in udisks2 package in Ubuntu: Triaged Bug description: An external disk device is declared in '/etc/fstab' with 'auto,nofail,users' options: UUID=aa083302-...-b66c0715eaf1 /media/ushakov/TOSHIBA_SYSTEM ext4 nodev,nosuid,auto,nofail,users 0 2 It is then successfully mounted automatically upon being connected. It can further be unmounted successfully without `sudo` from command line, e.g.: `umount $mount_point`. Meanwhile an attempt to unmount this device from Nautilus/Files UI results in an "Authentication Required" message: "Authentication is required to unmount External USB3.0 (/dev/sdc3) mounted by another user". The expected Nautilus/Files UI behavior would be that the disk device is unmounted silently or just with an non-intrusive notification upon a click on the "Unmount" button near the device label. Package suspected: nautilus: nautilus/bionic-updates,now 1:3.26.4-0~ubuntu18.04.4 amd64 [installed,automatic] $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-35.38~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 09:50:54 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'394' b'org.gnome.nautilus.window-state' b'geometry' b"'1279x749+193+153'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-10-15 (32 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1852844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1753509] Re: avahi-daemon adds/installs every printer on network
I could get rid of the auto browsing/adding with the following: firstly stop cups: sudo service cups stop then sudo gedit /etc/cups/cups.conf (or using any other editor) and comment... ## browselocalprotocols dnssd save and close then sudo gedit /etc/cups/cups-browsed.conf and set GreateIPPPrintersQueues to No or LocalOnly as described above save and close then stop avahi sudo service avahi-daemon stop then sudo gedit /etc/avahi/avahi-daemon.conf and insert or uncomment the following line: enable-dbus=no save and close now restart the services sudo service cups start sudo service avahi-daemon start You may have to go on and delete all undesirable printers, one by one, three clicks for each (why they make this so hard? In the campus there are hundreds of printers!). You should not see the printers being re- added as before. Final test: restart your system and see the list of printers in Settings. Good luck Jorge Sampaio -- 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/1753509 Title: avahi-daemon adds/installs every printer on network Status in cups-filters package in Ubuntu: Expired Bug description: When connected to a network, avahi-daemon adds & installs all printer on a network without being prompted. This is not desired behaviour. Discovery of the printers is good, but not automatic installation & addition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 5 09:29:05 2018 InstallationDate: Installed on 2017-09-29 (157 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1753509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845797]
Same issue on Lenovo Yoga C940, Ubuntu 19.10, kernel 5.3.0-23-generic x86_64. Mic not working, audio not working properly with missing speakers. Alsa info -> http://alsa- project.org/db/?f=863a8059dba17f148fb2d3b5b1705d29bc900218 -- 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/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1842954] Re: AMD GPU hang/crash/black screen after suspend(ing)
** Changed in: linux Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #891 https://gitlab.freedesktop.org/drm/amd/issues/891 -- 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/1842954 Title: AMD GPU hang/crash/black screen after suspend(ing) Status in Linux: Unknown Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Bug description: This is a freeze which is obviously caused by a bug in the xserver- xorg-video-amdgpu package ver: 19.0.1* which is shipped with Ubuntu 19.04 and 19.10. Upstream fix is needed. Workaround: sudo nano /etc/apt/sources.list, copy-paste one line which contains "main multiverse universe restricted" and change the distribution name "eoan" or "disco" to "bionic" (for this line only) So you will have a line like deb [url] bionic multiverse main restricted universe ctrl+o, save it sudo update sudo apt install xserver-xorg-core=2:1.19.6-1ubuntu4 sudo apt install xserver-xorg-video-amdgpu=18.0.1-1 sudo reboot If everything is OK then you should keep these packages by using: sudo apt-mark hold xserver-xorg-core=2:1.19.6-1ubuntu4 sudo apt-mark hold xserver-xorg-video-amdgpu=18.0.1-1 You can later unhold them by using the same commands with "unhold" If a newer bionic package version comes out (fe. a security update) you should unhold the packages do an apt update and use apt policy [package name without = and version] to check the new bionic versions that you can install using my original install commands with the proper version paramter. If something is not OK, then press E on grub menu, paste nomodeset parameter at the and of the kernel line then f10. After the kernel loading and the command line login you should just do an apt upgrade if you hadn't held the packages before. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1842954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1842954]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/891. -- 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/1842954 Title: AMD GPU hang/crash/black screen after suspend(ing) Status in Linux: Unknown Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Bug description: This is a freeze which is obviously caused by a bug in the xserver- xorg-video-amdgpu package ver: 19.0.1* which is shipped with Ubuntu 19.04 and 19.10. Upstream fix is needed. Workaround: sudo nano /etc/apt/sources.list, copy-paste one line which contains "main multiverse universe restricted" and change the distribution name "eoan" or "disco" to "bionic" (for this line only) So you will have a line like deb [url] bionic multiverse main restricted universe ctrl+o, save it sudo update sudo apt install xserver-xorg-core=2:1.19.6-1ubuntu4 sudo apt install xserver-xorg-video-amdgpu=18.0.1-1 sudo reboot If everything is OK then you should keep these packages by using: sudo apt-mark hold xserver-xorg-core=2:1.19.6-1ubuntu4 sudo apt-mark hold xserver-xorg-video-amdgpu=18.0.1-1 You can later unhold them by using the same commands with "unhold" If a newer bionic package version comes out (fe. a security update) you should unhold the packages do an apt update and use apt policy [package name without = and version] to check the new bionic versions that you can install using my original install commands with the proper version paramter. If something is not OK, then press E on grub menu, paste nomodeset parameter at the and of the kernel line then f10. After the kernel loading and the command line login you should just do an apt upgrade if you hadn't held the packages before. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1842954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]
@Arnaud D this bug is specifically about the Authorization dialog in the Software and Updates app. It is not a general problem with the mouse. In fact it is nothing to do with the mouse at all. -- 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/1734095 Title: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed] Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software and Updates app and attempt to change anything it does not popup the authorization dialog and will not let changes through. In sylog I see Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 3 identities that can be used for authentication. Only considering one. Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of begin_modal failed Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed to show modal dialog. Dismissing authentication request for action-id com.ubuntu.softwareproperties.applychanges cookie 1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740 Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: ERROR:root:Authentication canceled, changes have not been saved Before the upgrade it was ok. Other apps that require authorisation function as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Nov 23 10:07:44 2017 DisplayManager: lightdm InstallationDate: Installed on 2014-10-21 (1128 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)
This could be fix: https://www.phoronix.com/scan.php?page=news_item=Ubuntu-19.10-Radeon-RX-5700 -- 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/1848741 Title: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have graphics artefacts: screan tearing, pieces of the previous window appear in the newly opened window. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-08 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
attaching journalctl.log ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853199/+attachment/5306520/+files/journalctl.log -- 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/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in xorg package in Ubuntu: New Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It takes few login attempts to actually login back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 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 ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. 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.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/xorg/+bug/1853199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
It happened around this time (journalctl.log): Nov 19 20:38:00 tv xdg-desktop-por[3284]: xdg-desktop-portal-gtk: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Nov 19 20:38:00 tv gdm-password][1338]: pam_unix(gdm-password:session): session closed for user tv Nov 19 20:38:00 tv systemd[3095]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE Nov 19 20:38:00 tv systemd[3095]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'. Nov 19 20:38:00 tv pulseaudio[3108]: X connection to :0 broken (explicit kill or server shutdown). Nov 19 20:38:00 tv kernel: rfkill: input handler enabled -- 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/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in xorg package in Ubuntu: New Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It takes few login attempts to actually login back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 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 ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. 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.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/xorg/+bug/1853199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851918] Re: `hp-check -r` crashes with "AttributeError: module 'PIL.Image' has no attribute 'VERSION'"
** Tags added: regression-release rls-ee-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1851918 Title: `hp-check -r` crashes with "AttributeError: module 'PIL.Image' has no attribute 'VERSION'" Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Status in pillow package in Ubuntu: Confirmed Status in python-imaging package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install HPLIP on Ubuntu 19.10 with `sudo apt-get install hplip*` 2. Run `hp-check -r` Expected results: * `hp-check -r` runs without errors Actual results: * `hp-check -r` shows many errors and crashes: $ hp-check -r Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.19.6) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version warning: ubuntu-19.10 version is not supported. Using ubuntu-19.04 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 GNU/Linux Host: eoan Proc: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 GNU/Linux Distribution: ubuntu 19.10 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.19.6 HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not supported for ubuntu distro 19.10 version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.19.6 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/hplip/HP ppdbase=/usr/share/ppd/hplip doc=/usr/share/doc/hplip html=/usr/share/doc/hplip-doc icon=no cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv bin=/usr/bin apparmor=/etc/apparmor.d # Following values are determined at configure time and cannot be changed. [configure] network-build=yes libusb01-build=no pp-build=no gui-build=yes scanner-build=yes fax-build=yes dbus-build=yes cups11-build=no doc-build=yes shadow-build=no hpijs-install=yes foomatic-drv-install=yes foomatic-ppd-install=no foomatic-rip-hplip-install=no hpcups-install=yes cups-drv-install=yes cups-ppd-install=no internal-tag=3.19.6 restricted-build=no ui-toolkit=qt5 qt3=no qt4=no qt5=yes policy-kit=yes lite-build=no udev_sysfs_rules=no hpcups-only-build=no hpijs-only-build=no apparmor_build=no class-driver=no Current contents of
[Desktop-packages] [Bug 1852844] Re: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line
Thanks, reassigning ** Package changed: glib2.0 (Ubuntu) => udisks2 (Ubuntu) ** Also affects: udisks via https://github.com/storaged-project/udisks/issues/709 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1852844 Title: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line Status in GLib: New Status in udisks: Unknown Status in udisks2 package in Ubuntu: Triaged Bug description: An external disk device is declared in '/etc/fstab' with 'auto,nofail,users' options: UUID=aa083302-...-b66c0715eaf1 /media/ushakov/TOSHIBA_SYSTEM ext4 nodev,nosuid,auto,nofail,users 0 2 It is then successfully mounted automatically upon being connected. It can further be unmounted successfully without `sudo` from command line, e.g.: `umount $mount_point`. Meanwhile an attempt to unmount this device from Nautilus/Files UI results in an "Authentication Required" message: "Authentication is required to unmount External USB3.0 (/dev/sdc3) mounted by another user". The expected Nautilus/Files UI behavior would be that the disk device is unmounted silently or just with an non-intrusive notification upon a click on the "Unmount" button near the device label. Package suspected: nautilus: nautilus/bionic-updates,now 1:3.26.4-0~ubuntu18.04.4 amd64 [installed,automatic] $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-35.38~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 09:50:54 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'394' b'org.gnome.nautilus.window-state' b'geometry' b"'1279x749+193+153'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-10-15 (32 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1852844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853199] [NEW] Ctrl + c (copy) anywhere some times crashes gnome session
Public bug reported: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It takes few login attempts to actually login back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 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 ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. 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.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 crash eoan ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in xorg package in Ubuntu: New Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It takes few login attempts to actually login back. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 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 ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType:
[Desktop-packages] [Bug 1852844] Re: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line
Update: the issue at GNOME repository was closed ( https://gitlab.gnome.org/GNOME/glib/issues/1942#note_651026 ), and a new issue was filed for the `udisks` repository: https://github.com /storaged-project/udisks/issues/709 , with probable bug location at or near https://github.com/storaged- project/udisks/blob/master/src/udiskslinuxfilesystem.c#L1946 , as suggested at https://gitlab.gnome.org/GNOME/glib/issues/1942#note_651025 . ** Bug watch added: github.com/storaged-project/udisks/issues #709 https://github.com/storaged-project/udisks/issues/709 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1852844 Title: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line Status in GLib: New Status in glib2.0 package in Ubuntu: Triaged Bug description: An external disk device is declared in '/etc/fstab' with 'auto,nofail,users' options: UUID=aa083302-...-b66c0715eaf1 /media/ushakov/TOSHIBA_SYSTEM ext4 nodev,nosuid,auto,nofail,users 0 2 It is then successfully mounted automatically upon being connected. It can further be unmounted successfully without `sudo` from command line, e.g.: `umount $mount_point`. Meanwhile an attempt to unmount this device from Nautilus/Files UI results in an "Authentication Required" message: "Authentication is required to unmount External USB3.0 (/dev/sdc3) mounted by another user". The expected Nautilus/Files UI behavior would be that the disk device is unmounted silently or just with an non-intrusive notification upon a click on the "Unmount" button near the device label. Package suspected: nautilus: nautilus/bionic-updates,now 1:3.26.4-0~ubuntu18.04.4 amd64 [installed,automatic] $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-35.38~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 09:50:54 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'394' b'org.gnome.nautilus.window-state' b'geometry' b"'1279x749+193+153'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-10-15 (32 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1852844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
After days of fresh reinstallations and tests, I finally found what was causing this on my end and finally solved it by using a xorg configuration override 10-evdev.conf as shown on [1] Offender: Gaming mouse driver (Saitek Cyborg R.A.T.9 Wireless Mouse) Driver: libinput After a bit of research, I found that this mouse is known to be malfunctioning with the default settings on Xorg. Despite working at a first look, the default configuration is causing the below symptoms as explained by [2] After being plugged, the mouse will seems to work, but you may experience different issues : * You cannot move windows around when grabbing the window's title bar. (happens with Openbox and other Window manager) * You cannot click on buttons. * You cannot get the focus on windows. * You cannot open menus, even with keyboard shortcuts. * Display does not refresh (using Xcompmgr) * Closing certain windows restores functionality until the mouse locks into a new window. [1] https://github.com/rkruk/R.A.T.-Cyborg-Mouse-on-Linux [working solution for R.A.T.9 model] [2] https://wiki.archlinux.org/index.php/Mad_Catz_Mouse I hope this helps somes outta there -- 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/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Under GNOME 3, the use of the mouse-click stops occasionally, though I can still move the mouse around and can still click on items in the Activities screen and the top-bar. I can use alt-tab to cycle windows and can still type into already- active textboxes in windows, but I cannot click within the windows, and the mouse is not picked up at all by the windows. I can open the alt-f2 "run command" dialogue, but cannot type into it. The workaround I'm using is to open terminal (ctrl-alt-T) and run "gnome-shell -r", and restarting that command every time I have the problem again. Please ask if there's anything I forgot to mention. ADDITIONAL: The error tends to happen randomly, but it seems to happen upon opening a new window, changing windows, closing windows, or opening the activities pane (whether a change of window is thus instigated or not) ADDITIONAL 2: (sorry, it's early) The other workaround is to log out and to log in again, but that is also less than ideal ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-shell 3.6.3.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun May 19 07:02:18 2013 DisplayManager: gdm GsettingsChanges: b'org.gnome.desktop.interface' b'clock-show-date' b'true' b'org.gnome.desktop.interface' b'clock-show-seconds' b'true' b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 10'" b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 10'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 12'" InstallationDate: Installed on 2013-05-04 (14 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]
After days of fresh reinstallations and tests, I finally found what was causing this on my end and finally solved it by using a xorg configuration override 10-evdev.conf as shown on [1] Offender: Gaming mouse driver (Saitek Cyborg R.A.T.9 Wireless Mouse) Driver: libinput After a bit of research, I found that this mouse is known to be malfunctioning with the default settings on Xorg. Despite working at a first look, the default configuration is causing the below symptoms as explained by [2] After being plugged, the mouse will seems to work, but you may experience different issues : * You cannot move windows around when grabbing the window's title bar. (happens with Openbox and other Window manager) * You cannot click on buttons. * You cannot get the focus on windows. * You cannot open menus, even with keyboard shortcuts. * Display does not refresh (using Xcompmgr) * Closing certain windows restores functionality until the mouse locks into a new window. [1] https://github.com/rkruk/R.A.T.-Cyborg-Mouse-on-Linux [working solution for R.A.T.9 model] [2] https://wiki.archlinux.org/index.php/Mad_Catz_Mouse I hope this helps somes outta there -- 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/1734095 Title: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed] Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Ubuntu 17.10 (from 17.04), if I open the Software and Updates app and attempt to change anything it does not popup the authorization dialog and will not let changes through. In sylog I see Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Received 3 identities that can be used for authentication. Only considering one. Nov 23 10:07:04 tigger gnome-shell[2142]: pushModal: invocation of begin_modal failed Nov 23 10:07:04 tigger gnome-shell[2142]: polkitAuthenticationAgent: Failed to show modal dialog. Dismissing authentication request for action-id com.ubuntu.softwareproperties.applychanges cookie 1-28e9d285258e7cd70c2af2980886a55b-1-cff4894642cc4a6c033597370ee1f740 Nov 23 10:07:04 tigger software-properties-gnome.desktop[3367]: ERROR:root:Authentication canceled, changes have not been saved Before the upgrade it was ok. Other apps that require authorisation function as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Nov 23 10:07:44 2017 DisplayManager: lightdm InstallationDate: Installed on 2014-10-21 (1128 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-11-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-legacy-bugs/+bug/1734095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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 am having the same problem with a new dell-g3-3590, arecord -l gives: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3254 Analog [ALC3254 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 2: ALC3254 Alt Analog [ALC3254 Alt Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Its not detecting the internal mic nor the headfone mic. -- 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: New 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 1609750]
if you can recompile a kernel, using Mark Brown's for-next should have have all the latest changes from Google for Cyan. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Aug 4 14:12:03 2016 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE --- ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux-image-4.4.0-33-generic 4.4.0-33.52 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-33-generic N/A linux-backports-modules-4.4.0-33-generic N/A linux-firmware1.159 Tags: yakkety Uname: Linux 4.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609750]
In downstream bug report http://pad.lv/1609750 it was noted that this patch would be needed: https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f However I've tested 5.4rc7 and it does not seem to help. Do people know of other non-upstreamed patches required for the audio to work? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Aug 4 14:12:03 2016 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE --- ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux-image-4.4.0-33-generic 4.4.0-33.52 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-33-generic N/A linux-backports-modules-4.4.0-33-generic N/A linux-firmware1.159 Tags: yakkety Uname: Linux 4.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852679] Re: CLI to copy to clipboard does not work
Was hoping after some updates installed and a reboot that would resolve this but the problem still remains. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1852679 Title: CLI to copy to clipboard does not work Status in gnome-screenshot package in Ubuntu: New Bug description: I just upgraded today to 19.10. I have a keyboard shortcut setup to run gnome-screenshot --area -c to allow me to do quick screen grabs. I can confirm that if I use the screenshot dialog I can copy to the clipboard with that but using the CLI version of the same function does not work. It looks like it functions normal but when you go to paste the screenshot that you just took, nothing happens. lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 apt-cache policy gnome-screenshot gnome-screenshot: Installed: 3.33.90-1ubuntu1 Candidate: 3.33.90-1ubuntu1 Version table: *** 3.33.90-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1852679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 858450] Re: lcd flickers after dpms cycle
Launchpad has imported 6 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=39953. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2011-08-08T23:56:54+00:00 Cand-3 wrote: Created attachment 50058 lspci -vvnn My E-350 laptop screen flickers for ~5 minutes every time after waking from DPMS. The flicker persists through VT switches and changing the power profile to high. After the wait it stabilizes and picture is good again. It looks similar to a CRT on 60Hz, but xrandr is confident the mode is right for the lcd (60hz, not something lower). Lenovo G575 laptop AMD E-350 Linux 3.0.1 Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/858450/comments/0 On 2011-08-09T00:07:30+00:00 Cand-3 wrote: Created attachment 50060 dmesg Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/858450/comments/1 On 2011-08-09T00:08:56+00:00 Cand-3 wrote: Now that I tried to make it happen manually (sleep 1 && xset dpms force off), it didn't show itself; though for the last few days, it's always happened after X's 10-minute delay DPMS. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/858450/comments/2 On 2011-10-04T01:05:19+00:00 Simon Strandman wrote: I have this problem too on similar E350-based hardware. Sometimes I get this flicker, sometimes the screen is garbled (bug #36513). When I get a garbled screen the flicker usually persists even after a reboot. (Though this never happens in windows so I don't think it's a hardware issue.) Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/858450/comments/6 On 2011-10-15T20:03:41+00:00 Marc Deslauriers wrote: I am getting this on a C-50 based Acer Aspire One 522. I can reliably reproduce the issue with: xset dpms force off; sleep 10; xset dpms force on Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/858450/comments/7 On 2019-11-19T08:20:21+00:00 Martin-peres-n wrote: -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/208. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/858450/comments/12 ** Changed in: xserver-xorg-driver-ati Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #208 https://gitlab.freedesktop.org/drm/amd/issues/208 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/858450 Title: lcd flickers after dpms cycle Status in xserver-xorg-driver-ati: Unknown Status in xserver-xorg-video-ati package in Ubuntu: Fix Released Bug description: After installing Oneiric beta 2 on a Acer Aspire One 522 with an AMD C-50 chipset, when the screen is shut off with dpms and comes back on, the LCD flickers. The longer the screen is turned off, the more severe the flickering is when it is turned back on. When the flickering occurs, waiting a couple of minutes makes the flicker grow progressively better until it is gone completely. How to reproduce: xset dpms force off; sleep 10; xset dpms force on ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,resize,compiztoolbox,move,regex,place,animation,mousepoll,imgpng,expo,gnomecompat,snap,wall,vpswitch,grid,session,ezoom,fade,workarounds,unitymtgrabhandles,scale,unityshell] CompositorRunning: compiz Date: Sat Sep 24 15:24:04 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu DkmsStatus: bcmwl, 5.100.82.38+bdcom, 3.0.0-11-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: ATI Technologies Inc Device
[Desktop-packages] [Bug 1852907] Re: booting problem
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1852907 Title: booting problem Status in xorg package in Ubuntu: New Bug description: the booting problem was sometimes solved by turn the laptop off and wait for few minutes to turn it on again. but it was not always worked. my laptop was preinstalled with windows 8 and upgraded into windows 10. then i chosed to erased all data and install ubuntu 18 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 19:08:41 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics Controller [1179:fb71] InstallationDate: Installed on 2018-07-21 (484 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: TOSHIBA Satellite P845t ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=fa82f47e-1fa8-4ba5-8e85-89c92962e160 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.vendor: TOSHIBA dmi.bios.version: 6.50 dmi.board.asset.tag: NULL dmi.board.name: TOSHIBA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvr6.50:bd09/26/2012:svnTOSHIBA:pnSatelliteP845t:pvrPSPJ5U-009002:rvnTOSHIBA:rnTOSHIBA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: Satellite P845t dmi.product.version: PSPJ5U-009002 dmi.sys.vendor: TOSHIBA 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 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)
Since Ubuntu 19.04, I can not use Ubuntu on my VMware virtual machines on my MacBook Pro Retina (200% scaling). The desktop is white. This still occurs under Ubuntu 19.10 (even with a clean install). I hope this problem will be resolved quickly. I want to migrate to a newer version than my current version (Cosmic Cuttlefish). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/1825842 Title: [vmware] Background goes white when using scaling (200%, 300% or 400%) Status in mutter package in Ubuntu: Confirmed Status in xserver-xorg-video-vmware package in Ubuntu: Confirmed Bug description: As soon as I set my display to scaled (any percentage) via Settings -> Displays -> Scale, the background image disappears and become all white. When I choose a different background image via Settings -> Background initially nothing happens. As soon as I switch back to 100% scaling, the image I choose before now appears. This problem started right after updating to 19.04. No such issues with either 18.04 or 18.10. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 22 15:35:49 2019 DistUpgraded: 2019-04-21 17:34:15,063 DEBUG icon theme changed, re-reading DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2019-03-01 (51 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=c8dc93a3-fd95-4152-9c04-0211309b2dc7 ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 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/mutter/+bug/1825842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10 and Fedora 31 In these environments, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853182] [NEW] evince "save as" saves annotations to pdf without updating the timestamp of the file
Public bug reported: Tue Nov 19 12:41:50 EST 2019 brianhughes evince bug same as: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1690341 after successfully saving changes to PDF file (a form I filled out) and verifying that the changes are there, the timestamp of the file (ls -l from command line) is unchanged. screws up rsync'ed backups, etc. plus confusing as hell! $ evince --version GNOME Document Viewer 3.28.4 Ubuntu 18.04 LTS ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: evince timestamp ** Attachment added: "sadly, my attached description file is just called "file". sorry" https://bugs.launchpad.net/bugs/1853182/+attachment/5306482/+files/file -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1853182 Title: evince "save as" saves annotations to pdf without updating the timestamp of the file Status in evince package in Ubuntu: New Bug description: Tue Nov 19 12:41:50 EST 2019 brianhughes evince bug same as: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1690341 after successfully saving changes to PDF file (a form I filled out) and verifying that the changes are there, the timestamp of the file (ls -l from command line) is unchanged. screws up rsync'ed backups, etc. plus confusing as hell! $ evince --version GNOME Document Viewer 3.28.4 Ubuntu 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1853182/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844808] Re: in 19.10 can't delete file from desktop by clicking it and hitting delete key
It was just a few seconds before I captured the log, max 30 seconds, probably less than half that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1844808 Title: in 19.10 can't delete file from desktop by clicking it and hitting delete key Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: Just upgraded to 19.10 today. Previously, in 19.04, I could delete a file from the desktop by clicking on it and hitting the delete key. That no longer works. It's probably relevant that it doesn't appear to be possible to direct keyboard focus to the desktop itself any longer. When I click on an icon on the desktop and then hit the delete key, the keystroke is sent to the window that had focus before I clicked. This appears to be true regardless of what window focus mode I'm using (Click to Focus, Focus on Hover, or Secondary-Click). Note that the description of Secondary- Click, "Window is focused when hovered with the pointer. Hovering the desktop removes focus from the previous window," does not appear to be true. When I select that focus mode and hover my mouse over the desktop I remain focused on the previously focused window. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.01.4-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 11:12:42 2019 InstallationDate: Installed on 2019-09-12 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1844808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as
+1 Same here (https://youtrack.jetbrains.com/issue/IDEA-226221)... Also asked Jetbrains for workaround, also got as answer 'Go to Gnome and then to Ubuntu'. Hurray for closed source! For the time being a can not resume my normal workflow. Please apply the mutter fix!! -- 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/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress 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.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 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/mutter/+bug/1845281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850651] Re: Authentication constantly re-requested for Google
** Changed in: thunderbird (Ubuntu Disco) Status: Triaged => In Progress ** Changed in: thunderbird (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: In Progress Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: In Progress Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1850651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850651] Re: Authentication constantly re-requested for Google
** Branch linked: lp:~mozillateam/thunderbird/thunderbird.xenial ** Branch linked: lp:~mozillateam/thunderbird/thunderbird.disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: In Progress Status in thunderbird source package in Bionic: Fix Committed Status in thunderbird source package in Disco: In Progress Status in thunderbird source package in Eoan: Fix Committed Status in thunderbird source package in Focal: Fix Released Bug description: When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.sku: LENOVO_MT_2347 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1850651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853175] [NEW] [MIR] libmail-authenticationresults-perl
Public bug reported: [Availability] It is available for all architectures in the universe. https://launchpad.net/ubuntu/+source/libmail-authenticationresults-perl [Rationale] A new dependency of libmail-dkim-perl. [Security] No known CVEs. https://security-tracker.debian.org/tracker/source-package/libmail-authenticationresults-perl https://launchpad.net/ubuntu/+source/libmail-authenticationresults-perl/+cve [Quality assurance] - Desktop Packages team subscribed - dh_auto_test runs as part of build (353 tests) - autopkgtest capability was added in 1.20180923-2 [Dependencies] Depends on perl, libscalar-list-utils-perl - both are in the universe. [Standards compliance] debhelper [Maintenance] The upstream does not appear to be very active but the package is maintained by the Debian perl team (testing and unstable) https://github.com/marcbradshaw/Mail-AuthenticationResults https://packages.debian.org/search?keywords=libmail-authenticationresults-perl=names=all=all ** Affects: libmail-dkim-perl (Ubuntu) Importance: Undecided Status: New ** Package changed: libnfs (Ubuntu) => libmail-dkim-perl (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnfs in Ubuntu. https://bugs.launchpad.net/bugs/1853175 Title: [MIR] libmail-authenticationresults-perl Status in libmail-dkim-perl package in Ubuntu: New Bug description: [Availability] It is available for all architectures in the universe. https://launchpad.net/ubuntu/+source/libmail-authenticationresults- perl [Rationale] A new dependency of libmail-dkim-perl. [Security] No known CVEs. https://security-tracker.debian.org/tracker/source-package/libmail-authenticationresults-perl https://launchpad.net/ubuntu/+source/libmail-authenticationresults-perl/+cve [Quality assurance] - Desktop Packages team subscribed - dh_auto_test runs as part of build (353 tests) - autopkgtest capability was added in 1.20180923-2 [Dependencies] Depends on perl, libscalar-list-utils-perl - both are in the universe. [Standards compliance] debhelper [Maintenance] The upstream does not appear to be very active but the package is maintained by the Debian perl team (testing and unstable) https://github.com/marcbradshaw/Mail-AuthenticationResults https://packages.debian.org/search?keywords=libmail-authenticationresults-perl=names=all=all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-dkim-perl/+bug/1853175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852001] Re: Xorg freeze on high disk or cpu load or random
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => 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/1852001 Title: Xorg freeze on high disk or cpu load or random Status in xorg package in Ubuntu: Confirmed Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B16 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. 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 19.2.1-1ubuntu1 version.xserver-xorg-core:
[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
I have the same issue as echaskaris above. Audio plays, but volume control in the top right corner, as well as with keyboard keys defaults to the HDMI output, so there's no control. Setting it to line out restores volume control there for the duration of my session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Triaged Bug description: 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. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. 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 1849160] Re: after deb->snap transition, chromium no longer sees local password store
Darko, what is the output of "snap connections chromium | grep password" ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1849160 Title: after deb->snap transition, chromium no longer sees local password store Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Eoan: Fix Released Bug description: [Impact] After upgrading to eoan and accepting the deb->snap transition for chromium, the passwords saved in my browser are no longer available to the app, despite ~/snap/chromium/current/.config/chromium/Default/Login Data being present and fully-populated. If I go into settings, I see Saved Passwords: Saved passwords will appear here. The data doesn't appear to be lost, since I have a copy in ~/snap as well as in ~/.config/chromium, but somehow they're inaccessible. [Test Case] Install chromium-browser in disco (19.04), save a few passwords for login forms. Dist-upgrade to eoan (19.10), launch chromium, and verify that the saved passwords are still there. They can be inspected by browsing to chrome://settings/passwords. As an additional check, the output of `snap connections chromium | grep password` should look like this: password-manager-service chromium:password-manager-service :password-manager-service manual I.e. the interface should be marked as manually connected, even though the user hasn't explicitly connected it. [Regression Potential] Low. The change removes an assumption on upgrade paths that has become incorrect. Now the password-manager-service interface will always be connected on upgrade, which I think is sensible. Users who wish to disconnect the interface (unlikely use case) will also have to remove the chromium-browser transitional package, to prevent it from reconnecting the interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853149] Re: 78.0.3904.108-1 released for stable channel; fixes CVEs
** Branch linked: lp:~chromium-team/chromium-browser/bionic-stable ** Branch linked: lp:~chromium-team/chromium-browser/disco-stable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1853149 Title: 78.0.3904.108-1 released for stable channel; fixes CVEs Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium 78.0.3904.108-1 is released, which fixes multiple CVEs (CVE-2019-13723, CVE-2019-13724). Changelog is available at https://chromium.googlesource.com/chromium/src/+log/78.0.3904.97..78.0.3904.108?pretty=fuller=1. See: https://chromereleases.googleblog.com/2019/11/stable-channel- update-for-desktop_18.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store
the same behavior on ubuntu 19.04 with snap chromium 78.0.3904.97 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1849160 Title: after deb->snap transition, chromium no longer sees local password store Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Eoan: Fix Released Bug description: [Impact] After upgrading to eoan and accepting the deb->snap transition for chromium, the passwords saved in my browser are no longer available to the app, despite ~/snap/chromium/current/.config/chromium/Default/Login Data being present and fully-populated. If I go into settings, I see Saved Passwords: Saved passwords will appear here. The data doesn't appear to be lost, since I have a copy in ~/snap as well as in ~/.config/chromium, but somehow they're inaccessible. [Test Case] Install chromium-browser in disco (19.04), save a few passwords for login forms. Dist-upgrade to eoan (19.10), launch chromium, and verify that the saved passwords are still there. They can be inspected by browsing to chrome://settings/passwords. As an additional check, the output of `snap connections chromium | grep password` should look like this: password-manager-service chromium:password-manager-service :password-manager-service manual I.e. the interface should be marked as manually connected, even though the user hasn't explicitly connected it. [Regression Potential] Low. The change removes an assumption on upgrade paths that has become incorrect. Now the password-manager-service interface will always be connected on upgrade, which I think is sensible. Users who wish to disconnect the interface (unlikely use case) will also have to remove the chromium-browser transitional package, to prevent it from reconnecting the interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853149] Re: 78.0.3904.108-1 released for stable channel; fixes CVEs
** Changed in: chromium-browser (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1853149 Title: 78.0.3904.108-1 released for stable channel; fixes CVEs Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium 78.0.3904.108-1 is released, which fixes multiple CVEs (CVE-2019-13723, CVE-2019-13724). Changelog is available at https://chromium.googlesource.com/chromium/src/+log/78.0.3904.97..78.0.3904.108?pretty=fuller=1. See: https://chromereleases.googleblog.com/2019/11/stable-channel- update-for-desktop_18.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853120] Re: Xorg crashes with a bus error in OsLookupColor when using a second display
I don't think it's quite the same issue as 833 upstream, though the
symptoms are similar.
I disabled GLX and it didn't change any symptoms, which I think it would
if it were the same as 833 (?).
I did see a similar issue reported on Arch where the symptoms only
occurred when a USB C monitor was attached, and were fixed after an Arch
update (but lost the URL when X crashed; I'll share if I find it again).
It's not entirely consistent when it happens, but I can use Terminal,
Emacs and Hexchat without a crash but Firefox or Chromium or VSCode will
typically trigger a crash within a few minutes (even if they're running
solely on the primary screen).
When Chromium restarts after a crash and reopens it's windows on the
second screen that will reliably cause an immediate crash. The next time
it's restarted Chromium restores it's windows all on the primary screen,
and that doesn't cause a crash.
I've got gdb backtraces from several crashes, and they're all
consistent. I've attached one (gdb-backtrace.txt).
** Attachment added: "gdb-backtrace.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853120/+attachment/5306475/+files/gdb-backtrace.txt
--
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/1853120
Title:
Xorg crashes with a bus error in OsLookupColor when using a second
display
Status in xorg package in Ubuntu:
Incomplete
Bug description:
I'm using a Dell XPS 9380 ("developer edition") connected to an
external monitor via USB C.
I've been running Ubuntu 19.04 for months with an external monitor
with no issues. On upgrading to 19.10 xorg crashes with a bus error
within a few seconds or minutes of using the external monitor.
The xorg package installed is 1:7.7+19ubuntu12
The system is stable without the external monitor.
The crash is consistently repeatable and the stack trace looks very
similar each time.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
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
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov 19 09:50:40 2019
DistUpgraded: 2019-11-17 14:04:28,024 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
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00
[VGA controller])
Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
InstallationDate: Installed on 2019-07-09 (132 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
MachineType: Dell Inc. XPS 13 9380
ProcEnviron:
LANGUAGE=en_IE:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_IE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic
root=UUID=6b08154b-c421-45b7-bc75-c4feccc18654 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-11-17 (1 days ago)
dmi.bios.date: 10/01/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 088MRW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.0:bd10/01/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn088MRW:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.
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 19.2.1-1ubuntu1
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/xorg/+bug/1853120/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853120] Re: Xorg crashes with a bus error in OsLookupColor when using a second display
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853120/+attachment/5306476/+files/Xorg.0.log
--
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/1853120
Title:
Xorg crashes with a bus error in OsLookupColor when using a second
display
Status in xorg package in Ubuntu:
Incomplete
Bug description:
I'm using a Dell XPS 9380 ("developer edition") connected to an
external monitor via USB C.
I've been running Ubuntu 19.04 for months with an external monitor
with no issues. On upgrading to 19.10 xorg crashes with a bus error
within a few seconds or minutes of using the external monitor.
The xorg package installed is 1:7.7+19ubuntu12
The system is stable without the external monitor.
The crash is consistently repeatable and the stack trace looks very
similar each time.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
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
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov 19 09:50:40 2019
DistUpgraded: 2019-11-17 14:04:28,024 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
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00
[VGA controller])
Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
InstallationDate: Installed on 2019-07-09 (132 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
MachineType: Dell Inc. XPS 13 9380
ProcEnviron:
LANGUAGE=en_IE:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_IE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic
root=UUID=6b08154b-c421-45b7-bc75-c4feccc18654 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-11-17 (1 days ago)
dmi.bios.date: 10/01/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 088MRW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.0:bd10/01/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn088MRW:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.
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 19.2.1-1ubuntu1
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/xorg/+bug/1853120/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
** Changed in: mutter (Ubuntu Eoan) Status: New => Triaged ** Changed in: libreoffice (Ubuntu Eoan) Status: New => Triaged -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853149] Re: 78.0.3904.108-1 released for stable channel; fixes CVEs
** Branch linked: lp:~chromium-team/chromium-browser/xenial-stable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1853149 Title: 78.0.3904.108-1 released for stable channel; fixes CVEs Status in chromium-browser package in Ubuntu: In Progress Bug description: Chromium 78.0.3904.108-1 is released, which fixes multiple CVEs (CVE-2019-13723, CVE-2019-13724). Changelog is available at https://chromium.googlesource.com/chromium/src/+log/78.0.3904.97..78.0.3904.108?pretty=fuller=1. See: https://chromereleases.googleblog.com/2019/11/stable-channel- update-for-desktop_18.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853149] Re: 78.0.3904.108-1 released for stable channel; fixes CVEs
** Changed in: chromium-browser (Ubuntu) Status: New => Triaged ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => High ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1853149 Title: 78.0.3904.108-1 released for stable channel; fixes CVEs Status in chromium-browser package in Ubuntu: Triaged Bug description: Chromium 78.0.3904.108-1 is released, which fixes multiple CVEs (CVE-2019-13723, CVE-2019-13724). Changelog is available at https://chromium.googlesource.com/chromium/src/+log/78.0.3904.97..78.0.3904.108?pretty=fuller=1. See: https://chromereleases.googleblog.com/2019/11/stable-channel- update-for-desktop_18.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
In https://bugzilla.mozilla.org/show_bug.cgi?id=1592571, which is currently
identified as a duplicate of
https://bugzilla.mozilla.org/show_bug.cgi?id=1594686, it was pointed out that
this is probably due to bad code generation by clang 6. Two patches for clang 6
which seem to be required to generate correct code (in particular in the
context of nsTSubstringTuple) appear to be:
*
https://hg.mozilla.org/mozilla-central/rev/0d04a3f89940536d56cd5415a78316f0960e9f0a
(if not already compiling with 6.0.1)
*
https://hg.mozilla.org/mozilla-central/rev/dfe8ab123e01667be489a20b253e3cd3b20c10bd
Since this might also affect products other than firefox, it might make
sense to apply these patches to Ubuntu's clang 6 packages in general.
** Bug watch added: Mozilla Bugzilla #1592571
https://bugzilla.mozilla.org/show_bug.cgi?id=1592571
--
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/1850529
Title:
Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
Status in Mozilla Firefox:
Confirmed
Status in firefox package in Ubuntu:
Confirmed
Bug description:
After update from: 70.0+build2-0ubuntu0.16.04.1 to
71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
message that I can Refresh Firefox (crash) or Start in safe mode (also
crash).
Tech details:
Description: Ubuntu 16.04.6 LTS
Release: 16.04
package name: 71.0~b5+build1-0ubuntu0.16.04.1
Crash log details:
AdapterDeviceID: 0x1616
AdapterDriverVendor: mesa/i965
AdapterDriverVersion: 18.0.5.0
AdapterVendorID: 0x8086
BuildID: 20191028161640
ContentSandboxCapabilities: 119
ContentSandboxCapable: 1
ContentSandboxLevel: 4
CrashTime: 1572373123
DOMIPCEnabled: 1
FramePoisonBase: 9223372036600930304
FramePoisonSize: 4096
InstallTime: 1572364967
IsWayland: 0
IsWaylandDRM: 0
MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring tuple length is
invalid)
Notes: Ubuntu 16.04.6 LTSFP(D00-L1000-W-T000) WR? WR- OMTP? OMTP-
ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
ProductName: Firefox
ReleaseChannel: beta
SafeMode: 1
SecondsSinceLastCrash: 816
StartupCrash: 0
StartupTime: 1572373025
TelemetryEnvironment:
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20191028161640","version":"71.0","vendor":"Mozilla","displayVersion":"71.0b5","platformVersion":"71.0","xpcomAbi":"x86_64-gcc3","updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":15965,"virtualMaxMB":null,"cpu":{"count":4,"cores":2,"vendor":"GenuineIntel","family":6,"model":61,"stepping":4,"l2cacheKB":256,"l3cacheKB":3072,"speedMHz":2700,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2","hasAES"]},"os":{"name":"Linux","version":"4.15.0-66-generic","locale":"en-US"},"hdd":{"profile":{"model":null,"revision":null,"type":null},"binary":{"model":null,"revision":null,"type":null},"system":{"model":null,"revision":null,"type":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","Headless":false,"adapters":[{"description":"Mesa
DRI Intel(R) HD Graphics 5500 (Broadwell GT2)
","vendorID":"0x8086","deviceID":"0x1616","subsysID":null,"RAM":3072,"driver":null,"driverVendor":"mesa/i965","driverVersion":"18.0.5.0","driverDate":null,"GPUActive":true}],"monitors":[{"screenWidth":1366,"screenHeight":768}],"features":{"compositor":"none","gpuProcess":{"status":"blocked"},"wrQualified":{"status":"blocked-release-channel-intel"},"webrender":{"status":"unavailable-in-safe-mode"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":8,"telemetryEnabled":true,"locale":"en-US","intl":{},"update":{"channel":"beta","enabled":true,"autoDownload":false},"userPrefs":{"app.shield.optoutstudies.enabled":false,"browser.cache.disk.capacity":1048576,"browser.newtabpage.enabled":false,"browser.shell.checkDefaultBrowser":true,"browser.search.region":"US","browser.search.suggest.enabled":false,"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","browser.startup.page":3,"browser.urlbar.suggest.searches":false,"devtools.chrome.enabled":false,"devtools.debugger.remote-enabled":false,"extensions.blocklist.url":"https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%20/%20/","extensions.formautofill.addresses.enabled":false,"extensions.formautofill.creditCards.enabled":false,"privacy.donottrackheader.enabled":true},"sandbox":{"effectiveContentProcessLevel":4},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
ThreadIdNameMapping: 7556:"Gecko_IOThread",7557:"JS Watchdog",7558:"JS
Helper",7559:"JS Helper",7560:"JS Helper",7561:"JS
[Desktop-packages] [Bug 1850696] Re: Regression: cannot close notifications
** Also affects: gnome-shell (Ubuntu Eoan) Importance: Undecided Status: New ** Tags removed: rls-ee-incoming rls-ff-incoming ** Changed in: gnome-shell (Ubuntu Eoan) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu Eoan) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu Eoan) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1850696 Title: Regression: cannot close notifications Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Eoan: Triaged Bug description: Upstream reports: * https://gitlab.gnome.org/GNOME/gnome-shell/issues/1805 * https://gitlab.gnome.org/GNOME/gnome-shell/issues/1803 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1850696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
** Tags removed: rls-ee-incoming rls-ff-incoming ** Also affects: mutter (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: libreoffice (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu Eoan) Importance: Undecided => High ** Changed in: mutter (Ubuntu Eoan) Importance: Undecided => High ** Changed in: mutter (Ubuntu Eoan) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: libreoffice (Ubuntu Eoan) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in libreoffice source package in Eoan: New Status in mutter source package in Eoan: New Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853112] Re: Applications are closed when killing the Shell (like on a hang)
Rationale: this is a regression on X11 in eoan (maybe not worth fixing for it right now), but at least, should be fixed in focal IMHO ** Tags added: rls-ff-incoming -- 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/1853112 Title: Applications are closed when killing the Shell (like on a hang) Status in gnome-shell package in Ubuntu: New Bug description: - Open some non dbus activated apps (so, not terminal for instance) in your dock - Kill the shell with SIGKILL - Applications are being killed with the Shell being killed, apart from the dbus activated ones. This wasn't the case before 19.10 on X11. (caused by dbus user session?) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:42:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (543 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (314 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851896] Re: [snap] Changes in desktop file get overwritten
~/.chromium-browser.init is sourced by both the Ubuntu packages in the archive (where available) and by the snap. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1851896 Title: [snap] Changes in desktop file get overwritten Status in chromium-browser package in Ubuntu: Invalid Bug description: Changes in the chromium_chromium.desktop file get overwritten. This includes flags like --force-dark-mode etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 78435]
This bug is still a problem with latest firefox (70.0.1) on windows (32bit) and linux (amd64). This is extremely annoying as it means opening a tar.gz file in (for example) archive manager on linux fails every time other than the first time you click it. This does not seem time limited, my `/tmp/mozilla_user0` folder has mis-renamed files from yesterday. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/78435 Title: temporary filenames should handle multiple extensions (.tar.gz) Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-thunderbird When opening a file named foo.bar, the file is downloaded to /tmp. If the file is opened again in a short time, the file is again downloaded to /tmp but renamed foo-1.bar. If the file has a double extension (for example, opening a foo.tar.gz file with ark), the file is renamed as foo.tar-1.gz and thus ark is not able to open it properly. It should be foo-1.tar.gz instead. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/78435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 78435]
It's great see that this little bug isn't fixed since 11 years! Even it's not assigned to anyone. The bug still exists in Firefox quantum (i.e v57) May be it's time to say good bye to Firefox and look for some alternatives. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/78435 Title: temporary filenames should handle multiple extensions (.tar.gz) Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-thunderbird When opening a file named foo.bar, the file is downloaded to /tmp. If the file is opened again in a short time, the file is again downloaded to /tmp but renamed foo-1.bar. If the file has a double extension (for example, opening a foo.tar.gz file with ark), the file is renamed as foo.tar-1.gz and thus ark is not able to open it properly. It should be foo-1.tar.gz instead. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/78435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 78435]
What was the rational for changing the file name in the first place? What is wrong with presenting a overwrite warning/question to the user for equal file names? Silently changing file names is not very nice in my opinion. At least there should be an option to disable this mechanism. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/78435 Title: temporary filenames should handle multiple extensions (.tar.gz) Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-thunderbird When opening a file named foo.bar, the file is downloaded to /tmp. If the file is opened again in a short time, the file is again downloaded to /tmp but renamed foo-1.bar. If the file has a double extension (for example, opening a foo.tar.gz file with ark), the file is renamed as foo.tar-1.gz and thus ark is not able to open it properly. It should be foo-1.tar.gz instead. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/78435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 78435]
*** Bug 1127275 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/78435 Title: temporary filenames should handle multiple extensions (.tar.gz) Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-thunderbird When opening a file named foo.bar, the file is downloaded to /tmp. If the file is opened again in a short time, the file is again downloaded to /tmp but renamed foo-1.bar. If the file has a double extension (for example, opening a foo.tar.gz file with ark), the file is renamed as foo.tar-1.gz and thus ark is not able to open it properly. It should be foo-1.tar.gz instead. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/78435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1529932] Re: X session crashes with EQ overflowing
Launchpad has imported 13 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=93610. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-01-06T18:03:37+00:00 hardhu wrote: On my very old laptop, that is equipped with an Ati Mobility Radeon X700, sometimes (and, sadly, I have to use this word, because I found no regularity pattern for the occurrence of this bug) randomly the desktop session locks, that is I can only move the mouse pointer, but I cannot interact anymore with the desktop session. I am forced to login trough ssh from another pc and to restart the laptop. In Xorg.0.log I found these lines that are, in my opinion, related to the crash: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x5608e56a768e] (EE) 1: /usr/bin/X (mieqEnqueue+0x253) [0x5608e5689373] (EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x5608e5563152] (EE) 3: /usr/bin/X (xf86PostMotionEvent+0xd6) [0x5608e559a026] (EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x5322) [0x7f5e497b8322] (EE) 5: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x73d2) [0x7f5e497ba3d2] (EE) 6: /usr/bin/X (0x5608e54f3000+0x96ac8) [0x5608e5589ac8] (EE) 7: /usr/bin/X (0x5608e54f3000+0xbfc92) [0x5608e55b2c92] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e522c9000+0x352f0) [0x7f5e522fe2f0] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f5e523c60b7] (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f5e536ada08] (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f5e536b06cb] (EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x19c9) [0x7f5e4e3ae9c9] (EE) 13: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x1c0c) [0x7f5e4e3aec0c] (EE) 14: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f5e4e5b9000+0x26236) [0x7f5e4e5df236] (EE) 15: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x569b) [0x7f5e4d97869b] (EE) 16: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x7e8f) [0x7f5e4d97ae8f] (EE) 17: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x11953) [0x7f5e4d984953] (EE) 18: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xe770) [0x7f5e4d981770] (EE) 19: /usr/bin/X (0x5608e54f3000+0x13ca51) [0x5608e562fa51] (EE) 20: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xf74f) [0x7f5e4d98274f] (EE) 21: /usr/bin/X (0x5608e54f3000+0x1332a2) [0x5608e56262a2] (EE) 22: /usr/bin/X (0x5608e54f3000+0x5818f) [0x5608e554b18f] (EE) 23: /usr/bin/X (0x5608e54f3000+0x5c34b) [0x5608e554f34b] (EE) 24: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f5e522e9a40] (EE) 25: /usr/bin/X (_start+0x29) [0x5608e55396c9] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x5608e56a768e] (EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x5608e5563152] (EE) 2: /usr/bin/X (xf86PostMotionEvent+0xd6) [0x5608e559a026] (EE) 3: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x5322) [0x7f5e497b8322] (EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x73d2) [0x7f5e497ba3d2] (EE) 5: /usr/bin/X (0x5608e54f3000+0x96ac8) [0x5608e5589ac8] (EE) 6: /usr/bin/X (0x5608e54f3000+0xbfc92) [0x5608e55b2c92] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e522c9000+0x352f0) [0x7f5e522fe2f0] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f5e523c60b7] (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f5e536ada08] (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f5e536b06cb] (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x19c9) [0x7f5e4e3ae9c9] (EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x1c0c) [0x7f5e4e3aec0c] (EE) 13: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f5e4e5b9000+0x26236) [0x7f5e4e5df236] (EE) 14: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x569b) [0x7f5e4d97869b] (EE) 15: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x7e8f) [0x7f5e4d97ae8f] (EE) 16: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x11953) [0x7f5e4d984953] (EE) 17: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xe770) [0x7f5e4d981770] (EE) 18: /usr/bin/X (0x5608e54f3000+0x13ca51) [0x5608e562fa51] (EE) 19: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xf74f) [0x7f5e4d98274f] (EE) 20: /usr/bin/X (0x5608e54f3000+0x1332a2) [0x5608e56262a2] (EE) 21: /usr/bin/X (0x5608e54f3000+0x5818f) [0x5608e554b18f] (EE) 22: /usr/bin/X
[Desktop-packages] [Bug 1848009] Re: Delay launching application launcher gets longer the more apps are open
Marking as verified as no further issue has been found. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- 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/1848009 Title: Delay launching application launcher gets longer the more apps are open Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Fix Committed Bug description: [ Impact ] On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD. If I launch a bunch of applications - possibly a slightly unreasonable number, but a lot anyway - with minimal CPU or memory in use, the button to launch applications in the bottom left takes progressively longer to run. Video showing it: https://www.youtube.com/watch?v=BRbFk-n9KzQ [ Test case ] - Launch lots of applications - Click in the applications icon in the launcher (or press super+A) - Animation should not be delayed (some delay is still expected depending on the number of installed applications) [ Regression potential ] Windows in activities overview might have wrong positioning This is uploaded under the GNOME MRE: https://wiki.ubuntu.com/StableReleaseUpdates/GNOME --- Steps to reproduce. Open application launcher Note a ~0.6s delay before the icons fly onto the screen Open GNOME Software Install all the editors picks Launch a bunch of applications Click the application launcher Note a 4s delay before icons fly onto the screen. Expectation Honestly, no delay at all, but it should be at least consistent with when no applications are running, so 0.6s delay as per the state when no apps are launched. ProblemType: BugDistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 13:02:04 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848009/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820143] Re: Package python-vte missing from Ubuntu 19.04
You can't just remove stuff because you don't like it! That's appallingly bad manners. Abominade https://github.com/aliafshar/a8 depends on this package and overhauling it will require a lot of work - it doesn't use gi at all. Please reconsider adding the package back. Good distros don't break their customers. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/1820143 Title: Package python-vte missing from Ubuntu 19.04 Status in vte package in Ubuntu: Won't Fix Bug description: The python-vte package is missing from Ubuntu 19.04. Would you please add it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1820143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853149] [NEW] 78.0.3904.108-1 released for stable channel; fixes CVEs
Public bug reported: Chromium 78.0.3904.108-1 is released, which fixes multiple CVEs (CVE-2019-13723, CVE-2019-13724). Changelog is available at https://chromium.googlesource.com/chromium/src/+log/78.0.3904.97..78.0.3904.108?pretty=fuller=1. See: https://chromereleases.googleblog.com/2019/11/stable-channel- update-for-desktop_18.html ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-13723 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-13724 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1853149 Title: 78.0.3904.108-1 released for stable channel; fixes CVEs Status in chromium-browser package in Ubuntu: New Bug description: Chromium 78.0.3904.108-1 is released, which fixes multiple CVEs (CVE-2019-13723, CVE-2019-13724). Changelog is available at https://chromium.googlesource.com/chromium/src/+log/78.0.3904.97..78.0.3904.108?pretty=fuller=1. See: https://chromereleases.googleblog.com/2019/11/stable-channel- update-for-desktop_18.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851895] Re: [snap] No access to HTML documentation in /usr/share/doc
Okay and theoretically I should be able to remount the /usr/share folder as a loopback in media, right? But that would be a needlessly complicated solution. Would reinstalling the snap in classic mode fix the problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1851895 Title: [snap] No access to HTML documentation in /usr/share/doc Status in chromium-browser package in Ubuntu: Triaged Bug description: Due to the fact that snaps are very restricted one is unable to open local files outside of ones own home directory. An example where such an access is common are files from *-doc packages like `/usr/share/doc/python3-doc/html/index.html`. I don't know if this is fixable with the current interfaces or if this requires a classic confinement mode but I miss this feature as sometimes running a webserver is not an option... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851895/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851896] Re: [snap] Changes in desktop file get overwritten
Yes it probably was. I did not thought about snap overwriting that file. Thanks for the tip, I will do so. I am curious though - is the init file generally looked for by the default chromium build or the snap? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1851896 Title: [snap] Changes in desktop file get overwritten Status in chromium-browser package in Ubuntu: Incomplete Bug description: Changes in the chromium_chromium.desktop file get overwritten. This includes flags like --force-dark-mode etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853120] Re: Xorg crashes with a bus error in OsLookupColor when using a second display
Could you check if upstream
https://gitlab.freedesktop.org/xorg/xserver/issues/833 matches yours?
Does is get triggered by using some specific software?
--
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/1853120
Title:
Xorg crashes with a bus error in OsLookupColor when using a second
display
Status in xorg package in Ubuntu:
Incomplete
Bug description:
I'm using a Dell XPS 9380 ("developer edition") connected to an
external monitor via USB C.
I've been running Ubuntu 19.04 for months with an external monitor
with no issues. On upgrading to 19.10 xorg crashes with a bus error
within a few seconds or minutes of using the external monitor.
The xorg package installed is 1:7.7+19ubuntu12
The system is stable without the external monitor.
The crash is consistently repeatable and the stack trace looks very
similar each time.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
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
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov 19 09:50:40 2019
DistUpgraded: 2019-11-17 14:04:28,024 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
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00
[VGA controller])
Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
InstallationDate: Installed on 2019-07-09 (132 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
MachineType: Dell Inc. XPS 13 9380
ProcEnviron:
LANGUAGE=en_IE:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_IE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic
root=UUID=6b08154b-c421-45b7-bc75-c4feccc18654 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-11-17 (1 days ago)
dmi.bios.date: 10/01/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 088MRW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.0:bd10/01/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn088MRW:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.
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 19.2.1-1ubuntu1
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/xorg/+bug/1853120/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853120] Re: Xorg crashes with a bus error in OsLookupColor when using a second display
Thank you for your bug report. Could you add the gdb backtrace to the
report?
** Changed in: xorg (Ubuntu)
Importance: Undecided => High
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #833
https://gitlab.freedesktop.org/xorg/xserver/issues/833
--
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/1853120
Title:
Xorg crashes with a bus error in OsLookupColor when using a second
display
Status in xorg package in Ubuntu:
Incomplete
Bug description:
I'm using a Dell XPS 9380 ("developer edition") connected to an
external monitor via USB C.
I've been running Ubuntu 19.04 for months with an external monitor
with no issues. On upgrading to 19.10 xorg crashes with a bus error
within a few seconds or minutes of using the external monitor.
The xorg package installed is 1:7.7+19ubuntu12
The system is stable without the external monitor.
The crash is consistently repeatable and the stack trace looks very
similar each time.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
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
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov 19 09:50:40 2019
DistUpgraded: 2019-11-17 14:04:28,024 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
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00
[VGA controller])
Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
InstallationDate: Installed on 2019-07-09 (132 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
MachineType: Dell Inc. XPS 13 9380
ProcEnviron:
LANGUAGE=en_IE:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_IE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic
root=UUID=6b08154b-c421-45b7-bc75-c4feccc18654 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-11-17 (1 days ago)
dmi.bios.date: 10/01/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 088MRW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.0:bd10/01/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn088MRW:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.
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 19.2.1-1ubuntu1
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/xorg/+bug/1853120/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853126] Re: Go To Line... causes text cursor to disappear
Thank you for your bug report. Does it get displayed if you press enter to valide the line/close the popup widget? ** Changed in: gedit (Ubuntu) Importance: Undecided => Low ** Changed in: gedit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1853126 Title: Go To Line... causes text cursor to disappear Status in gedit package in Ubuntu: Incomplete Bug description: 1) I open an CMakeLists.txt (from llvm project) 2) cursor is in line 1 3) I Go To... 123 4) editor moves to some location, status shows Ln 123 Col 1 5) but cursor (keyboard's) is not visible (making me wonder *which* line on the screen is indeed 123?!) It is subtle GUI error. I never seen any editor make editing keyboard cursor disappear, which is why I thought to report it. I attached the screencast (the file is already open). gedit --version Version 3.28.1 gnome 3.28.2 Ubuntu 18.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1853126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853117] Re: after update to 19.10 I am notified about new updates available even when there is none available
Thank you for your bug report. Could you take a screenshot showing the notification? Also when you say 'none available', how/where do you check? ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete -- 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/1853117 Title: after update to 19.10 I am notified about new updates available even when there is none available Status in gnome-software package in Ubuntu: Incomplete Bug description: after update to ubuntu 19.10 I am notified about new updates available even when there is none available. It happens on daily basis. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:52:18 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-07-11 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10 gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-11-03 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1853117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as
+1 Hi, im also really looking forward to find this fix in ubuntu. Currently my Intellij is crashing steady. :( I also ask Jetbrains if they can provide a workaround but they told me that i have to wait for ubuntu. They cannot do that. -- 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/1845281 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"] Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress 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.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 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/mutter/+bug/1845281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853117] Re: after update to 19.10 I am notified about new updates available even when there is none available
** Description changed: after update to ubuntu 19.10 I am notified about new updates available - on daily basis even when there is none available. + even when there is none available. It happens on daily basis. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:52:18 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-07-11 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InstalledPlugins: - gnome-software-plugin-flatpak 3.30.6-2ubuntu10 - gnome-software-plugin-snap3.30.6-2ubuntu10 + gnome-software-plugin-flatpak 3.30.6-2ubuntu10 + gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-11-03 (15 days ago) -- 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/1853117 Title: after update to 19.10 I am notified about new updates available even when there is none available Status in gnome-software package in Ubuntu: New Bug description: after update to ubuntu 19.10 I am notified about new updates available even when there is none available. It happens on daily basis. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:52:18 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-07-11 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10 gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-11-03 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1853117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853126] [NEW] Go To Line... causes text cursor to disappear
Public bug reported: 1) I open an CMakeLists.txt (from llvm project) 2) cursor is in line 1 3) I Go To... 123 4) editor moves to some location, status shows Ln 123 Col 1 5) but cursor (keyboard's) is not visible (making me wonder *which* line on the screen is indeed 123?!) It is subtle GUI error. I never seen any editor make editing keyboard cursor disappear, which is why I thought to report it. I attached the screencast (the file is already open). gedit --version Version 3.28.1 gnome 3.28.2 Ubuntu 18.04.3 LTS ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Peek 2019-11-19 05-27.gif" https://bugs.launchpad.net/bugs/1853126/+attachment/5306464/+files/Peek%202019-11-19%2005-27.gif ** Summary changed: - Go To Line... causes cursor to disappear + Go To Line... causes text cursor to disappear ** Description changed: 1) I open an CMakeLists.txt (from llvm project) - 2) cursor is in line 1 + 2) cursor is visible in line 1 as per status Ln 1 3) I Go To... 123 - 4) editor moves to some location, status shows Ln 123 Col 1 + 4) editor moves to some location, status shows Ln 123, Col 1 5) but cursor (keyboard's) is not visible (making me wonder *which* line on the screen is indeed 123?!) It is subtle GUI error. I never seen any editor make editing keyboard cursor disappear, which is why I thought to report it. gedit --version Version 3.28.1 gnome 3.28.2 Ubuntu 18.04.3 LTS ** Description changed: 1) I open an CMakeLists.txt (from llvm project) - 2) cursor is visible in line 1 as per status Ln 1 + 2) cursor is in line 1 3) I Go To... 123 - 4) editor moves to some location, status shows Ln 123, Col 1 + 4) editor moves to some location, status shows Ln 123 Col 1 5) but cursor (keyboard's) is not visible (making me wonder *which* line on the screen is indeed 123?!) It is subtle GUI error. I never seen any editor make editing keyboard cursor disappear, which is why I thought to report it. + I attached the screencast (the file is already open). + gedit --version Version 3.28.1 gnome 3.28.2 Ubuntu 18.04.3 LTS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1853126 Title: Go To Line... causes text cursor to disappear Status in gedit package in Ubuntu: New Bug description: 1) I open an CMakeLists.txt (from llvm project) 2) cursor is in line 1 3) I Go To... 123 4) editor moves to some location, status shows Ln 123 Col 1 5) but cursor (keyboard's) is not visible (making me wonder *which* line on the screen is indeed 123?!) It is subtle GUI error. I never seen any editor make editing keyboard cursor disappear, which is why I thought to report it. I attached the screencast (the file is already open). gedit --version Version 3.28.1 gnome 3.28.2 Ubuntu 18.04.3 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1853126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1591727]
Created attachment 9108732 mozilla-bmo849632.patch -- 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/1591727 Title: When loading a webgl water demo it has wrong colors Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: When loading a webgl water demo it has wrong colors ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox-launchpad-plugin (not installed) ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc64-smp 4.4.10 Uname: Linux 4.4.0-24-powerpc64-smp ppc64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: powerpc CurrentDesktop: MATE Date: Sun Jun 12 19:13:36 2016 InstallationDate: Installed on 2016-04-08 (65 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta powerpc (20160323.1) SourcePackage: firefox-launchpad-plugin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1591727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1591727]
Created attachment 9108439 mozilla-bmo849632.patch So, I think this is skia once again. Skia can only handle little endian. Workarounds for other things were to swizzle skias input. I have a preliminary patch that fixes some of the color-issues for the webgl-water-example and http://mc.pp.se/webgl/webgltest.html It swizzles pixels read from webgl right at the source. Water-surface is still too blue and other webgl-examples are not working yet (e.g. firstpersontetris.com ) Any more hints would be welcome -- 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/1591727 Title: When loading a webgl water demo it has wrong colors Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: When loading a webgl water demo it has wrong colors ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox-launchpad-plugin (not installed) ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc64-smp 4.4.10 Uname: Linux 4.4.0-24-powerpc64-smp ppc64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: powerpc CurrentDesktop: MATE Date: Sun Jun 12 19:13:36 2016 InstallationDate: Installed on 2016-04-08 (65 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta powerpc (20160323.1) SourcePackage: firefox-launchpad-plugin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1591727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
For me, HDMI audio is selected in the options but sound plays in the desired device. What is annoying is that I have to go to settings every time I need to adjust the volume because the top right menu adjusts HDMI audio. Am I having the same issue? -- 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: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Triaged Bug description: 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. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. 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 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Hi Timo, I wanted to try the AMD64 version at: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2019-11-14/. But only unsigned kernels are shipped and I couldn't switch from UEFI or boot unsigned kernels, because it's a corporate machine. Do you have any ideas? Regards -- 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/1550779 Title: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
I would like to add that I also experience the behaviour reported in posts #16 (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570/comments/16) and #19 (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570/comments/19). -- 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: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Triaged Bug description: 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. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. 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 1853120] [NEW] Xorg crashes with a bus error in OsLookupColor when using a second display
Public bug reported:
I'm using a Dell XPS 9380 ("developer edition") connected to an external
monitor via USB C.
I've been running Ubuntu 19.04 for months with an external monitor with
no issues. On upgrading to 19.10 xorg crashes with a bus error within a
few seconds or minutes of using the external monitor.
The xorg package installed is 1:7.7+19ubuntu12
The system is stable without the external monitor.
The crash is consistently repeatable and the stack trace looks very
similar each time.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
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
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov 19 09:50:40 2019
DistUpgraded: 2019-11-17 14:04:28,024 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
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA
controller])
Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
InstallationDate: Installed on 2019-07-09 (132 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Dell Inc. XPS 13 9380
ProcEnviron:
LANGUAGE=en_IE:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_IE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic
root=UUID=6b08154b-c421-45b7-bc75-c4feccc18654 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-11-17 (1 days ago)
dmi.bios.date: 10/01/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.0
dmi.board.name: 088MRW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.8.0:bd10/01/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn088MRW:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9380
dmi.product.sku: 08AF
dmi.sys.vendor: Dell Inc.
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 19.2.1-1ubuntu1
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 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/1853120
Title:
Xorg crashes with a bus error in OsLookupColor when using a second
display
Status in xorg package in Ubuntu:
New
Bug description:
I'm using a Dell XPS 9380 ("developer edition") connected to an
external monitor via USB C.
I've been running Ubuntu 19.04 for months with an external monitor
with no issues. On upgrading to 19.10 xorg crashes with a bus error
within a few seconds or minutes of using the external monitor.
The xorg package installed is 1:7.7+19ubuntu12
The system is stable without the external monitor.
The crash is consistently repeatable and the stack trace looks very
similar each time.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
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
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Nov 19 09:50:40 2019
DistUpgraded: 2019-11-17 14:04:28,024 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
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00
[VGA controller])
Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af]
InstallationDate: Installed on 2019-07-09 (132 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
MachineType: Dell Inc. XPS 13 9380
ProcEnviron:
LANGUAGE=en_IE:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_IE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic
[Desktop-packages] [Bug 1853015] Re: nvidia-340 fails to build against linux 5.3.0-23-generic
I have tested the update, and I haven't experienced any regressions: ~: apt-cache policy nvidia-340 nvidia-340: Installed: 340.107-0ubuntu0.18.04.4 Candidate: 340.107-0ubuntu0.18.04.4 Version table: *** 340.107-0ubuntu0.18.04.4 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 340.107-0ubuntu0.18.04.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages 340.106-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages ... DKMS build: Building for 4.15.0-71-generic and 5.3.0-23-generic Building for architecture x86_64 Building initial module for 4.15.0-71-generic Done. nvidia: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-71-generic/updates/dkms/ nvidia_uvm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.15.0-71-generic/updates/dkms/ depmod... DKMS: install completed. Building initial module for 5.3.0-23-generic Done. nvidia: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.3.0-23-generic/updates/dkms/ nvidia_uvm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.3.0-23-generic/updates/dkms/ depmod... DKMS: install completed. Setting up nvidia-opencl-icd-340 (340.107-0ubuntu0.18.04.4) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for mime-support (3.60ubuntu1) ... Processing triggers for initramfs-tools (0.130ubuntu3.9) ... update-initramfs: Generating /boot/initrd.img-4.15.0-71-generic ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1853015 Title: nvidia-340 fails to build against linux 5.3.0-23-generic Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Committed Bug description: nvidia-340 fails to build against linux 5.3.0-23-generic. SRU Request: [Test Case] 1) Enable the -proposed repository, and install the new 340 NVIDIA driver (340.107-0ubuntu0.16.04.4). 2) Check that the kernel module can be built against the new kernel. 3) Restart your computer, and see if everything works correctly when accessing the desktop. [Regression Potential] Low. The update only fixes build issues with Linux versions 5.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1853015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844808] Re: in 19.10 can't delete file from desktop by clicking it and hitting delete key
Thanks, do you remember around what time you hit the bug to match the right part of the log?bb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1844808 Title: in 19.10 can't delete file from desktop by clicking it and hitting delete key Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: Just upgraded to 19.10 today. Previously, in 19.04, I could delete a file from the desktop by clicking on it and hitting the delete key. That no longer works. It's probably relevant that it doesn't appear to be possible to direct keyboard focus to the desktop itself any longer. When I click on an icon on the desktop and then hit the delete key, the keystroke is sent to the window that had focus before I clicked. This appears to be true regardless of what window focus mode I'm using (Click to Focus, Focus on Hover, or Secondary-Click). Note that the description of Secondary- Click, "Window is focused when hovered with the pointer. Hovering the desktop removes focus from the previous window," does not appear to be true. When I select that focus mode and hover my mouse over the desktop I remain focused on the previously focused window. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.01.4-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 11:12:42 2019 InstallationDate: Installed on 2019-09-12 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1844808/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852890] Re: Nautilus freezes when trying to delete an item from the desktop
Thanks, you should be able to delete from the desktop but that not working could be a bug in that new component gnome-shell-extension-desktop-icons There is bug #1844808 reported about a similar issue Keeping the nautilus bug as incomplete for now in case you are able to reproduce the problem in nautilus againb -- 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/1852890 Title: Nautilus freezes when trying to delete an item from the desktop Status in nautilus package in Ubuntu: Incomplete Bug description: When hitting the delete key on an item on the desktop, a beep is emitted, and nothing happens. When launching a separate Nautilus window, navigating to ~/Desktop, and trying to delete items from this folder, the Nautilus window freezes. At this point, no new Nautilus windows can be launched, and the window eventually emits a ""Files" is not responding" dialog. (When trying to reproduce this bug for this report, the whole screen froze and I had to escape with Alt+F2 - not sure if this is a separate bug). When launching nautilus from a terminal, and repeating the procedure above, no error message or other output is printed to the terminal. The file in question was steam.desktop, and I then deleted it using rm without any issue. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1: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: Sun Nov 17 08:05:39 2019 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1245, 746)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-11-07 (9 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2019.02.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852860] Re: Display settings not saved across sessions
** Package changed: grub2 (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Tags added: desktop-lts-wishlist -- 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/1852860 Title: Display settings not saved across sessions Status in gnome-shell package in Ubuntu: New Bug description: I am using: - Ubuntu 19.10 - Nvidia gtx1080 - nvidia xserver installed - two 4k monitors I changed the scaling and order of monitors in Ubuntu Display settings. However when I reboot or logout/login the display settings reset and i have to set them all over again each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813679] Re: vim-gtk can no longer save to non-group-writable files in GVFS SFTP mounts in 18.04
Thanks for the investigation, looks like it's a vim issue from your bisecting ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid ** Changed in: gvfs (Ubuntu) Status: New => Invalid ** Changed in: gvfs (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to non-group-writable files in GVFS SFTP mounts in 18.04 Status in gvfs package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Invalid Status in vim package in Ubuntu: New Bug description: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
Thank you for your bug report. What video card/driver do you use? Do you use some scaling/what values? -- 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/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in mutter package in Ubuntu: New Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853094] Re: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock
Could you also add your 'journalctl -b 0' log from a session having the 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/1853094 Title: Screen tearing in xorg gnome session on Latitude 7480 with WD19TB Thunderbolt dock Status in mutter package in Ubuntu: New Bug description: I have the WD19TB Thunderbolt dock connected to a Dell Latitude 7480 laptop with two external displays. The laptop itself is closed (internal display is not used). In a gnome xorg session, there is severe tearing on parts of the screen when dragging windows or scrolling content. Under a wayland session there is no screen tearing, but I have keyboard key repetition problems which make this mostly unusable day- to-day (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1849405). I can supply short phone videos of tearing occurring on the screens if required. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 19 14:02:09 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1853094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853115] [NEW] localauthority.conf - AdminIdentities: unix-group is ignored
Public bug reported: Allowed users and groups as admins for pkexec are defined in: /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin As you can see, I added unix-group:localadmin My user is localadmin-user1 who is in the local group localadmin. It does not matter if I create a new configuration file /etc/polkit-1/localauthority.conf.d/99-myadmins.conf or expand the original 51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin If I add the user himself instead of his group localadmin the user is listed the allowed list for pkexec. [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-user:localadmin-user1 How to reproduce: - create local user and group (here: localadmin) - add unix-group:localadmin to /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf - pkexec mount -> the local user in group localadmin is not listed - add unix-user:localadmin-user1 to /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf - pkexec mount -> the local user localadmin-user1 is listed Kubuntu 19.10 policykit-10.105-26ubuntu1 SSSD for system authorization including domain ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1853115 Title: localauthority.conf - AdminIdentities: unix-group is ignored Status in policykit-1 package in Ubuntu: New Bug description: Allowed users and groups as admins for pkexec are defined in: /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin As you can see, I added unix-group:localadmin My user is localadmin-user1 who is in the local group localadmin. It does not matter if I create a new configuration file /etc/polkit-1/localauthority.conf.d/99-myadmins.conf or expand the original 51-ubuntu-admin.conf [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-group:localadmin If I add the user himself instead of his group localadmin the user is listed the allowed list for pkexec. [Configuration] AdminIdentities=unix-group:sudo;unix-group:admin;unix-user:localadmin-user1 How to reproduce: - create local user and group (here: localadmin) - add unix-group:localadmin to /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf - pkexec mount -> the local user in group localadmin is not listed - add unix-user:localadmin-user1 to /etc/polkit-1/localauthority.conf.d/51-ubuntu-admin.conf - pkexec mount -> the local user localadmin-user1 is listed Kubuntu 19.10 policykit-10.105-26ubuntu1 SSSD for system authorization including domain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1853115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853117] [NEW] after update to 19.10 I am notified about new updates available even when there is none available
Public bug reported: after update to ubuntu 19.10 I am notified about new updates available on daily basis even when there is none available. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:52:18 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-07-11 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10 gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-11-03 (15 days ago) ** Affects: gnome-software (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 gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1853117 Title: after update to 19.10 I am notified about new updates available even when there is none available Status in gnome-software package in Ubuntu: New Bug description: after update to ubuntu 19.10 I am notified about new updates available on daily basis even when there is none available. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:52:18 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-07-11 (130 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu10 gnome-software-plugin-snap3.30.6-2ubuntu10 SourcePackage: gnome-software UpgradeStatus: Upgraded to eoan on 2019-11-03 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1853117/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852860] [NEW] Display settings not saved across sessions
You have been subscribed to a public bug: I am using: - Ubuntu 19.10 - Nvidia gtx1080 - nvidia xserver installed - two 4k monitors I changed the scaling and order of monitors in Ubuntu Display settings. However when I reboot or logout/login the display settings reset and i have to set them all over again each time. ** Affects: gnome-shell (Ubuntu) Importance: Low Status: New -- Display settings not saved across sessions https://bugs.launchpad.net/bugs/1852860 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell 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 1853112] [NEW] Applications are closed when killing the Shell (like on a hang)
Public bug reported: - Open some non dbus activated apps (so, not terminal for instance) in your dock - Kill the shell with SIGKILL - Applications are being killed with the Shell being killed, apart from the dbus activated ones. This wasn't the case before 19.10 on X11. (caused by dbus user session?) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:42:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (543 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (314 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: - Open some non dbus activated apps (so, not terminal for instance) in your dock - Kill the shell with SIGKILL - Applications are being killed with the Shell being killed, apart from the dbus activated ones. - This wasn't the case before 19.10. (caused by dbus user session?) + This wasn't the case before 19.10 on X11. (caused by dbus user session?) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:42:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (543 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (314 days ago) -- 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/1853112 Title: Applications are closed when killing the Shell (like on a hang) Status in gnome-shell package in Ubuntu: New Bug description: - Open some non dbus activated apps (so, not terminal for instance) in your dock - Kill the shell with SIGKILL - Applications are being killed with the Shell being killed, apart from the dbus activated ones. This wasn't the case before 19.10 on X11. (caused by dbus user session?) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 09:42:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-24 (543 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-01-08 (314 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853112/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11
I've updated my cyan (Acer Chromebook R11) to kernel 5.4rc7 from Ubuntu's mainline PPA, but the audio is still not working (no audio device visible according to pulseaudio). Are you aware of something else that still needs upstreaming beside the mentioned https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Aug 4 14:12:03 2016 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE --- ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux-image-4.4.0-33-generic 4.4.0-33.52 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-33-generic N/A linux-backports-modules-4.4.0-33-generic N/A linux-firmware1.159 Tags: yakkety Uname: Linux 4.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
