[Desktop-packages] [Bug 1880450] Re: Unmet package dependency "xserver-xorg-core (>= 2:1.17.2-2)"
The title of the bug and the text in the description don't match. Can you fix that? ** Tags added: bionic ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1880450 Title: Unmet package dependency "xserver-xorg-core (>= 2:1.17.2-2)" Status in xorg-server package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 18.04 x86_64 (fully patched) on a Dell XPS 8930 (https://www.amazon.com/gp/product/B078N85NCR). I recently performed a dist-upgrade to 5.3.0-53-generic. After the upgrade I lost X in non- recovery mode. In recovery mode I get a GUI at 800x600. 800x600 leaves a lot to be desired with a 32" monitor. I reinstalled the kernel components with no joy. Secure Boot is Off. Reboots did not help. The kernel components were: * linux-headers-5.3.0-53-generic * linux-image-5.3.0-53-generic * linux-modules-5.3.0-53-generic * linux-modules-extra-5.3.0-53-generic * linux-tools-5.3.0-53-generic I tried the Nvidia drivers 435 and 440 with no joy. Reboots did not help. I then removed the Nvidia drivers, and I tried the default Xorg server, but it errors with the following. Reboots did not help. # apt-get install xserver-xorg-video-nouveau nouveau-firmware Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xserver-xorg-video-nouveau : Depends: xorg-video-abi-23 Depends: xserver-xorg-core (>= 2:1.18.99.901) E: Unable to correct problems, you have held broken packages. I'm not sure which package is the problem here. I generically filed the report against Xorg, but I suspect there's a better choice of package. (There is no xserver-xorg-core package available to select). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1880450/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
Since bug 1852183 is released this is fixed for many but not all cases. More people chime in to be affected and there seems to be a spike of KDE users in that (which makes sense as they won't see a mutter change have any effect for them I guess). We already had a PPA [1] to try with something that fits the SRU policy [2] better but most likely won't help (yet would be great if it does). Furthermore I now created a PPA with the bigger fix [3] backported to focal. That might be a harder ride through the SRU policy, but if that is the only thing fixing it we might need to consider it (we can then still break out the patches of 0.20 as needed). I'd ask affected people to test both not just shortly but for quite a while as we all know these kind of issues are sometimes flaky and transient. Then please here give me feedback on how these PPAs would behave. [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4060 [2]: https://wiki.ubuntu.com/StableReleaseUpdates [3]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4076 P.S. also if you have multiple annoying issues after an upgrade that is sad to hear, but lets keep this bug about clipboard copy issues please and spawn other bugs for other - not necessarily related - problems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to spice-vdagent in Ubuntu. https://bugs.launchpad.net/bugs/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in qemu package in Ubuntu: Invalid Status in spice package in Ubuntu: Invalid Status in spice-protocol package in Ubuntu: Fix Released Status in spice-vdagent package in Ubuntu: Fix Released Status in virt-manager package in Ubuntu: Invalid Status in spice-protocol source package in Focal: Incomplete Status in spice-vdagent source package in Focal: Incomplete Status in spice-vdagent package in Debian: Fix Released Status in spice package in Fedora: Unknown Bug description: https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9 --- I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1872527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880512] [NEW] cups apparmor profile denied sys_nice
Public bug reported: May 24 17:02:54 dinar-comp kernel: [ 6432.118240] audit: type=1400 audit(1590328974.037:195): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=27786 comm="cups-browsed" capability=23 capname="sys_nice" this messages started to appear after upgrade ubuntu from 19.10 to 20.04. ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New -- 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/1880512 Title: cups apparmor profile denied sys_nice Status in cups-filters package in Ubuntu: New Bug description: May 24 17:02:54 dinar-comp kernel: [ 6432.118240] audit: type=1400 audit(1590328974.037:195): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=27786 comm="cups-browsed" capability=23 capname="sys_nice" this messages started to appear after upgrade ubuntu from 19.10 to 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1880512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880086] Re: [nvidia+xorg] High latency while running gtk4 demos like Fishbowl
** Summary changed: - [nvidia+xorg] High input latency while running gtk4 demos like Fishbowl + [nvidia+xorg] High latency while running gtk4 demos like Fishbowl ** Description changed: - High input latency while running gtk4 demos like Fishbowl, using the - Nvidia driver (on Xorg) + High latency while running gtk4 demos like Fishbowl, using the Nvidia + driver (on Xorg) -- 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/1880086 Title: [nvidia+xorg] High latency while running gtk4 demos like Fishbowl Status in mutter package in Ubuntu: In Progress Bug description: High latency while running gtk4 demos like Fishbowl, using the Nvidia driver (on Xorg) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1880086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879159] Re: Boot Problem
Can you please attach a photo of the "graphics problem"? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1879159 Title: Boot Problem Status in Ubuntu: Incomplete Bug description: It shows graphics problem during booting and unable to operate mouse. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-179.209-generic 4.4.219 Uname: Linux 4.4.0-179-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.23 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 17 13:19:12 2020 DistUpgraded: 2020-03-29 23:06:17,899 DEBUG /openCache(), new cache size 56855 DistroCodename: xenial 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: Dell 3rd Gen Core processor Graphics Controller [1028:0555] InstallationDate: Installed on 2020-03-24 (54 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Dell Inc. Inspiron 3520 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-179-generic root=UUID=2e048bbe-fc79-442e-ae8d-aac97ebb2938 ro quiet splash vt.handoff=7 init=/sbin/upstart SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2020-03-29 (48 days ago) dmi.bios.date: 05/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0486TW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/31/2018:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3520 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun May 17 13:15:51 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21569 vendor SEC xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1879159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879234] Re: Xorg freeze
Can you please attach a photo or video of the problem? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Tags added: amdgpu ** Summary changed: - Xorg freeze + [amdgpu] Xorg freeze -- 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/1879234 Title: [amdgpu] Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: when i was my computer on and start blinking middle of screen please solve it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 18 10:24:02 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000] MachineType: Gigabyte Technology Co., Ltd. A320M-S2H ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F23 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1879234/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880514] [NEW] Monitor setup doesn't apply until login
Public bug reported: I have my laptop sitting in half-clamshell on the desk hooked up to external monitor via HDMI. By default my monitor config is to have the screen displayed only on the monitor on my desk and not the laptop. This work fine as soon as I log in, however at the login stage it has defaulted to displaying the screens in extended mode, with primary display on my laptop, which means I have to move the PC, open it up and login there before the displays go back to the setting I have chosen. Generally not an issue except its a nuisance to have to move them around every time I login. Wondering if this is a big or if its intended behaviour ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 25 08:05:02 2020 InstallationDate: Installed on 2020-05-03 (21 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot of monitor setup" https://bugs.launchpad.net/bugs/1880514/+attachment/5376426/+files/monitor%20setup.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1880514 Title: Monitor setup doesn't apply until login Status in gdm3 package in Ubuntu: New Bug description: I have my laptop sitting in half-clamshell on the desk hooked up to external monitor via HDMI. By default my monitor config is to have the screen displayed only on the monitor on my desk and not the laptop. This work fine as soon as I log in, however at the login stage it has defaulted to displaying the screens in extended mode, with primary display on my laptop, which means I have to move the PC, open it up and login there before the displays go back to the setting I have chosen. Generally not an issue except its a nuisance to have to move them around every time I login. Wondering if this is a big or if its intended behaviour ? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 25 08:05:02 2020 InstallationDate: Installed on 2020-05-03 (21 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1880514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
closing, should be fixed ** Changed in: mesa (Ubuntu Bionic) Status: Incomplete => Fix Released ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836979 Title: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed” Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: Buggy as Kodi is, this seems to be a problem specifically with mesa- va-drivers. Kodi has worked just fine on my system, as recently as July 6th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to-desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- XBMC PPA) since its release in June, but in between July 6th and 16th, I did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers” package to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates Bionic repository), however, Kodi works again, without even requiring me to restart my machine. So, this is likely a problem with “mesa-va- drivers”. I tried looking in Xorg.0.log: [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620 [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines: [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz eP) …that’s all that appears in the log when I try to load Kodi and a crash happens. I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if you need more information, I’ve attached a hardinfo report, too. I hope this bug can get fixed, soon. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 329389] Re: "Party mode" ununderstandable and undocumented
** Changed in: rhythmbox (Ubuntu) Status: Triaged => In Progress ** Changed in: rhythmbox (Ubuntu) Assignee: (unassigned) => James Cuzella (trinitronx) ** Changed in: hundredpapercuts Assignee: (unassigned) => James Cuzella (trinitronx) ** Changed in: hundredpapercuts Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/329389 Title: "Party mode" ununderstandable and undocumented Status in One Hundred Papercuts: In Progress Status in Rhythmbox: New Status in rhythmbox package in Ubuntu: In Progress Bug description: Binary package hint: rhythmbox The manual does not explain what "party mode" is. The status bar help text is not helpful at all; when you hover the cursor over the Party Mode menu entry, it laconically says "Change the status of the party mode". (Is that even English?) I was scared that it would ruin all my playlists and send my email address to the spammers, but I tried it anyway. It seems to toggle a full-screen view. Then why is it not called "Full Screen"? Does it do something more? The top Google hit http://ubuntuforums.org/showthread.php?t=694932 seems inconclusive to me. Does Party mode involve changes in how the play queue can be manipulated and/or how the computer can be used? Minimal fix: * Describe Party Mode in the on-line help Bonus points: * Improve the Status bar help text vnix$ lsb_release -rd Description: Ubuntu 8.10 Release: 8.10 vnix$ apt-cache policy rhythmbox rhythmbox: Installed: 0.11.6svn20081008-0ubuntu4.2 Candidate: 0.11.6svn20081008-0ubuntu4.2 Version table: *** 0.11.6svn20081008-0ubuntu4.2 0 500 http://fi.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 0.11.6svn20081008-0ubuntu4 0 500 http://fi.archive.ubuntu.com intrepid/main Packages To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/329389/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879625] Re: [Precision 5530, Realtek ALC3266] No sound after reboot until headphones are unplugged and plugged back in
Well, I'm confused : how can I make this report useful ? Or is it worthless that I create such reports ? -- 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/1879625 Title: [Precision 5530, Realtek ALC3266] No sound after reboot until headphones are unplugged and plugged back in Status in alsa-driver package in Ubuntu: Incomplete Bug description: Looks like a frequent problem that hits my system : I have no sound on my headphones after I reboot my laptop until I unplug and plug back in the headphones. I *may* have sound through the PC speaker. I used to have none, but today sound came out of it. As I have upgraded to 20.04 and have done some modifications in config files some time ago with 19.xx, I'm unsure this is reliable information. I've tried to apply some solutions found here or there, without success. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stan 2001 F pulseaudio /dev/snd/pcmC0D0p: stan 2001 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 08:08:37 2020 InstallationDate: Installed on 2019-04-26 (389 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1570 F pulseaudio stan 2001 F pulseaudio /dev/snd/pcmC0D0p: stan 2001 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Precision 5530, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: Upgraded to focal on 2020-05-07 (12 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-10T16:49:20.600250 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880520] [NEW] In the settings of a VPN connection, when I change the Gateway I can't Apply.
Public bug reported: When I change the Gateway or anything at all in the Identity tab of a VPN connection settings the Apply button does not enable. Same for the Details tab. Only the IPv4/6 tabs seem to trigger the enablement of the Apply button. Background: I needed to change the gateway hostname for an existing VPN connection. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 25 09:57:39 2020 InstallationDate: Installed on 2020-03-15 (70 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1880520 Title: In the settings of a VPN connection, when I change the Gateway I can't Apply. Status in gnome-control-center package in Ubuntu: New Bug description: When I change the Gateway or anything at all in the Identity tab of a VPN connection settings the Apply button does not enable. Same for the Details tab. Only the IPv4/6 tabs seem to trigger the enablement of the Apply button. Background: I needed to change the gateway hostname for an existing VPN connection. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 25 09:57:39 2020 InstallationDate: Installed on 2020-03-15 (70 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1880520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880410] Re: pulseaudio doesn't enforce sample rate set in daemon.conf
Hi Daniel, I've already done this and forgot to link to it. Here you go: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/897 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #897 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/897 -- 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/1880410 Title: pulseaudio doesn't enforce sample rate set in daemon.conf Status in pulseaudio package in Ubuntu: New Bug description: Before submitting this bugreport I've went through the daemon.conf man page and the pulseaudio documentation, but have not found a solution to my problem. I've moved from Debian stable with pulseaudio version 12.2-4+deb10u1 to Kubuntu 20.04 with pulseaudio version 13.99.1-1ubuntu3.2. I'm experiencing cracking issues on external USB audio device Xonar U3 while listening to certain audio sources (system sounds included). This issue doesn't happen when using my laptop's internal audio device. Output of 'cat /proc/asound/card2/stream0' without audio stream running: C-Media Electronics Inc. USB Advanced Audio Device at usb-:00:14.0-2, full : USB Audio Playback: Status: Running Interface = 1 Altset = 1 Packet Size = 200 Momentary freq = 44100 Hz (0x2c.199a) Interface 1 Altset 1 Format: S16_LE Channels: 2 Endpoint: 1 OUT (ADAPTIVE) Rates: 8000, 16000, 44100, 48000 Bits: 16 Capture: Status: Stop Interface 2 Altset 1 Format: S16_LE Channels: 2 Endpoint: 2 IN (ASYNC) Rates: 8000, 16000, 44100, 48000 Bits: 16 The following behaviour happens with default settings in /etc/pulse/daemon.conf: Xonar U3 plugged in, firefox running: Momentary freq = 48000 Hz (0x30.) Xonar U3 plugged in, Clementine/Strawberry audio player running: Momentary freq = 44100 Hz (0x2c.199a) Xonar U3 plugged in with Deadbeef set to override sample rate to 48kHz: Momentary freq = 48000 Hz (0x30.) I've modified the daemon.conf as follows: ; default-sample-format = s16le #no change on this line, this is corresponding with the format the usb audio device suggests to be using ; default-sample-rate = 48000 ; alternate-sample-rate = 48000 However, when running video or audio sources with 44100Hz audio, applications do not respect the default-sample-rate and Momentary freq reports 44100Hz, while other sources either send 48kHz by default or have no problem respecting the setting (I've tried the game Into the Breach, VLC running 48kHz video and audio files). Complete /etc/pulse/daemon.conf contents: https://gist.github.com/zelmor/f224e6e4d300241e8431d3258e777e73 Checking syslog doesn't indicate any errors either, gist: https://gist.github.com/zelmor/5e59094be4d90ffa9e0ff6275594e370 ==Workarounds attempted== Modifying /etc/pulse/default.pa to include: load-module module-udev-detect tsched=0 Even after killing&restarting pulseaudio, this did not resolve anything. It also doesn't look like a good overall solution to the problem. Modifying daemon.conf to: ; resample-method = src-sinc-best-quality ; avoid-resampling = true Did not fix the issue. It is not possible to roll back PA to a previous version in Kubuntu 20.04 without breaking dependencies of the Plasma desktop, so this was not attempted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: zelmor 1994 F pulseaudio /dev/snd/controlC1: zelmor 1994 F pulseaudio /dev/snd/controlC0: zelmor 1994 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 24 16:30:11 2020 InstallationDate: Installed on 2020-04-28 (25 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET46WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7S11H00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20B7S11H00:pvrThinkPadT450:rvnLENOVO:rn20B7S11H00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20B7S11H00 dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T450 dmi.product.version: Think
[Desktop-packages] [Bug 1876914] Update Released
The verification of the Stable Release Update for gjs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1876914 Title: Update to 1.64.2 and SRU it Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Focal: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gjs/-/tags/1.64.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working, as well other gjs based apps like polari [ Regression potential ] Update fixed various memory leaks, and the critical ones are included in the test suite, so ideally there should not be problems. The ubuntu-dock must still work properly (as a change affected a class there) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1876914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876914] Re: Update to 1.64.2 and SRU it
This bug was fixed in the package gjs - 1.64.2-1ubuntu1~20.04.1 --- gjs (1.64.2-1ubuntu1~20.04.1) focal; urgency=medium * No-change backport to focal (LP: #1876914) gjs (1.64.2-1ubuntu1) groovy; urgency=medium * Merge with debian * debian/patches/api-test-timeout.patch: Dropped * debian/rules: Use timeout multiplier in tests gjs (1.64.2-1) unstable; urgency=medium * Team upload * New upstream stable release - Fix template use in GTK 4 - Don't crash if a callback doesn't return an expected array of values - Fix a crash when passing integer to strv in constructor - Skip some tests if GTK can't be initialised - Fix gjs_log_exception() for InternalError - Fix signal match mechanism - Drop all patches, applied upstream * Install installed-tests in default /usr/libexec/gjs/installed-tests * Install libraries with multiarch paths * Simplify dh_makeshlibs invocation using debhelper 12 defaults. The incantation we previously had in -V is a longwinded way to write dh_makeshlibs -VUpstream-Version (aka plain -V with no argument), which is the default in compat level 12 anyway. * Mark libgjs0g as Multi-Arch: same gjs (1.64.1-3) unstable; urgency=medium * Team upload * Release to unstable (transition: #954422) -- Marco Trevisan (Treviño) Tue, 05 May 2020 14:49:57 +0200 ** Changed in: gjs (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1876914 Title: Update to 1.64.2 and SRU it Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Focal: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gjs/-/tags/1.64.2 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working, as well other gjs based apps like polari [ Regression potential ] Update fixed various memory leaks, and the critical ones are included in the test suite, so ideally there should not be problems. The ubuntu-dock must still work properly (as a change affected a class there) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1876914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877226] Re: nvidia - external display unavailable after screen goes to sleep
Daniel et al, I wanted to provide an update based on the latest official mutter release as of today - 25.Mai. The issue still exists. However, I provide the following in the event it helps to refine the underlying issue. Please let me know if there are logs that would be helpful to you or additional steps you would like me to take to help with the diagnosis. >From the desktop with dual monitors running: 1) Goto lock screen (win+l) 2) initial screen shows both monitors active 3) both screens go blac 4) external monitor goes into standby mode due to loss of signal 5) primary laptop displays turns on momentarily and a resolution change is observed based on the size of the mouse. 6) primary display goes black. 7) logging back in and going to display settings 8) system no longer uses external display and returns to single display 9) open gnome-control-center -> displays. Single Display is active 10) Attempt to select join displays 11) Error at the top of gnome-control-center: Changes cannot be applied - This could be due to hardware limitations 12) select mirror - click apply 13) a keep settings dialogue will pop-up briefly before the screen goes blank. When the screen comes back on, both screens come back on, with a new keep settings dialogue. 14) select keep settings. gnome-control-center now shows Joing Displays as being active. not/not mirror. - As an additional note. If instead of going to the lock screen I suspend the system, which includes both monitors going into sleep mode, the above issue is not observed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1877226 Title: nvidia - external display unavailable after screen goes to sleep Status in gnome-control-center package in Ubuntu: New Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: On ubuntu 20.04 (Linux 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux) with nvidia proprietary driver 440.64 with an nvidia MX250 (Lenovo T590): 1) Attach monitor via HDMI 2) Monitor is properly detected. Gnome-control-center sees the correct monitor and sets it to join displays. No issue 3) activate lock screen (window key + L) 4) wait for screens to go to sleep 5) wake up screens to login again (external monitor flashes briefly) 6) login 7) system no longer uses external display and returns to single display 8) open gnome-control-center -> displays. Single Display is active 9) Attempt to select join displays 10) Error at the top of gnome-control-center: Changes cannot be applied - This could be due to hardware limitations 11) select mirror - click apply 12) a keep settings dialogue will pop-up briefly before the screen goes blank. When the screen comes back on, both screens come back on, with a new keep settings dialogue. 13) select keep settings. gnome-control-center now shows Joing Displays as being active. not/not mirror. Notes: -changing prime-select to nvidia vs adaptive does not change the issue -setting power profile to performance in nvidia-settings does not change the issue gnome-control-center info: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status nvidia-driver-440: Installed: 440.82+really.440.64-0ubuntu6 Candidate: 440.82+really.440.64-0ubuntu6 Version table: *** 440.82+really.440.64-0ubuntu6 500 500 http://de.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 06:16:15 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-24 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
As per the views on https://askubuntu.com/questions/1233058/chromium- snap-on-ubuntu-20-04-some-webapp-shortcuts-not-working- workaround/1233059#1233059, this bug affects many more people than indicated here. -- 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/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action Status in chromium-browser package in Ubuntu: Triaged Bug description: For chrome apps, the create shortcuts action should create desktop files but it doesn't. I suspect it has something to do with paths.  tracking:candidate installed: 62.0.3202.94 (123) 246MB - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Talked about this topic on https://forums.developer.nvidia.com/t/ubuntu-20-04-second-monitor- doesnt-work-ubuntu-and-nvidia-settings-detects-it/124380/13 generix said maybe's a problem with the Intel GPU Firmware. ** Also affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mesa-utils package in Ubuntu: New Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with noveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880536] [NEW] HDMI port is not working
Public bug reported: HDMI port is not working and I don't the second secreen in Display settings. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 25 11:13:51 2020 DistUpgraded: 2020-05-22 16:25:45,628 DEBUG /openCache(), new cache size 97390 DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5079] InstallationDate: Installed on 2020-04-02 (52 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20RD004FMH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic root=/dev/mapper/username--vg-root ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-05-22 (2 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R16ET21W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20RD004FMH dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR16ET21W(1.07):bd11/29/2019:svnLENOVO:pn20RD004FMH:pvrThinkPadE15:rvnLENOVO:rn20RD004FMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E15 dmi.product.name: 20RD004FMH dmi.product.version: ThinkPad E15 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 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 ** 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/1880536 Title: HDMI port is not working Status in xorg package in Ubuntu: New Bug description: HDMI port is not working and I don't the second secreen in Display settings. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 25 11:13:51 2020 DistUpgraded: 2020-05-22 16:25:45,628 DEBUG /openCache(), new cache size 97390 DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5079] InstallationDate: Installed on 2020-04-02 (52 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20RD004FMH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic root=/dev/mapper/username--vg-root ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-05-22 (2 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R16ET21W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20RD004FMH dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR16ET21W(1.07):bd11/29/2019:svnLENOVO:pn20RD004FMH:pvrThinkPadE15:rvnLENOVO:rn20RD004FMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E15 dmi.product.name: 20RD004FMH dmi.product.version: ThinkPad E15 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 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
[Desktop-packages] [Bug 1880410] Re: pulseaudio doesn't enforce sample rate set in daemon.conf
** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/897 Importance: Unknown Status: Unknown -- 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/1880410 Title: pulseaudio doesn't enforce sample rate set in daemon.conf Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: Before submitting this bugreport I've went through the daemon.conf man page and the pulseaudio documentation, but have not found a solution to my problem. I've moved from Debian stable with pulseaudio version 12.2-4+deb10u1 to Kubuntu 20.04 with pulseaudio version 13.99.1-1ubuntu3.2. I'm experiencing cracking issues on external USB audio device Xonar U3 while listening to certain audio sources (system sounds included). This issue doesn't happen when using my laptop's internal audio device. Output of 'cat /proc/asound/card2/stream0' without audio stream running: C-Media Electronics Inc. USB Advanced Audio Device at usb-:00:14.0-2, full : USB Audio Playback: Status: Running Interface = 1 Altset = 1 Packet Size = 200 Momentary freq = 44100 Hz (0x2c.199a) Interface 1 Altset 1 Format: S16_LE Channels: 2 Endpoint: 1 OUT (ADAPTIVE) Rates: 8000, 16000, 44100, 48000 Bits: 16 Capture: Status: Stop Interface 2 Altset 1 Format: S16_LE Channels: 2 Endpoint: 2 IN (ASYNC) Rates: 8000, 16000, 44100, 48000 Bits: 16 The following behaviour happens with default settings in /etc/pulse/daemon.conf: Xonar U3 plugged in, firefox running: Momentary freq = 48000 Hz (0x30.) Xonar U3 plugged in, Clementine/Strawberry audio player running: Momentary freq = 44100 Hz (0x2c.199a) Xonar U3 plugged in with Deadbeef set to override sample rate to 48kHz: Momentary freq = 48000 Hz (0x30.) I've modified the daemon.conf as follows: ; default-sample-format = s16le #no change on this line, this is corresponding with the format the usb audio device suggests to be using ; default-sample-rate = 48000 ; alternate-sample-rate = 48000 However, when running video or audio sources with 44100Hz audio, applications do not respect the default-sample-rate and Momentary freq reports 44100Hz, while other sources either send 48kHz by default or have no problem respecting the setting (I've tried the game Into the Breach, VLC running 48kHz video and audio files). Complete /etc/pulse/daemon.conf contents: https://gist.github.com/zelmor/f224e6e4d300241e8431d3258e777e73 Checking syslog doesn't indicate any errors either, gist: https://gist.github.com/zelmor/5e59094be4d90ffa9e0ff6275594e370 ==Workarounds attempted== Modifying /etc/pulse/default.pa to include: load-module module-udev-detect tsched=0 Even after killing&restarting pulseaudio, this did not resolve anything. It also doesn't look like a good overall solution to the problem. Modifying daemon.conf to: ; resample-method = src-sinc-best-quality ; avoid-resampling = true Did not fix the issue. It is not possible to roll back PA to a previous version in Kubuntu 20.04 without breaking dependencies of the Plasma desktop, so this was not attempted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: zelmor 1994 F pulseaudio /dev/snd/controlC1: zelmor 1994 F pulseaudio /dev/snd/controlC0: zelmor 1994 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 24 16:30:11 2020 InstallationDate: Installed on 2020-04-28 (25 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET46WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7S11H00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20B7S11H00:pvrThinkPadT450:rvnLENOVO:rn20B7S11H00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20B7S11H00 dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..et
[Desktop-packages] [Bug 1880243] Re: can't hide desktop icons neither with dconf-editor nor with gnome-shell-extension-desktop-icons
Thanks @vanvugt, so there are 3 UI ways of hiding the desktop icons, but only one works: $ gnome-shell-extension-prefs ... then switch off the desktop-icons extension. (Nevermind that gnome tweaks, under "Extensions", listed the desktop- icons gnome shell extension as disabled.) The bugs are then the mere existence of the other two UI ways of hiding desktop icons. -- 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/1880243 Title: can't hide desktop icons neither with dconf-editor nor with gnome- shell-extension-desktop-icons Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Bug description: In attempting to hide all desktop icons, I can't. 1. With dconf-editor, org/gnome/desktop/background/show-desktop-icons , I set the value to False, and yet the icons show. 2. With gnome-shell-extension-desktop-icons, despite disabling it, it still doesn't work (can change the size of the icons, but can't hide all icons when deactivating the extension). What's the appropriate approach to disable desktop icons? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-desktop-icons 20.04.0-1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 22 22:24:44 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1428 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to focal on 2020-05-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1880243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)
This is still happening despite the Ubuntu 20.04LTS installation being fully patched using Liveupdate as at 25 May 2020. In LibreOffice I have to hit Cntrl C repeatedly (more than 2 times or click the copy icon sometimes 9 times or more to get some data and this is just staying within Office so office related only. In the desktop other attempts to copy also to other applications and WINE applications still results in failures. The fix therefore has not worked. If mutter was changed and has rendered the computer useless (I regard it as such right now as it is highly unreliable and induces errors) then it should be removed until the module has been fixed and tested. DO NOT get the users to fix the problem.. that is why users have been driven away from Microsoft. -- 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/1852183 Title: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93) Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] 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. [ Test case ] 1. Use use libreoffice writer/calc 2. Copy text around 3. Paste it and ensure it always work [ Regression potential ] Copy/paste won't work as expected, for non-text types - 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&px=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 1880536] Re: HDMI port is not working
If you have the AMD Radeon option then it's likely the HDMI port is wired to that. But that GPU is also likely turned off by default so you will also be missing the HDMI port option. To fix that please try checking your BIOS and turn on both GPUs. But there's a second problem here which seems more likely... The kernel doesn't seem to recognise your very new Intel GPU. So even if the laptop only has a single GPU the HDMI port would be missing :) To fix that please install either: * https://releases.ubuntu.com/20.04/ or * https://releases.ubuntu.com/18.04.4/ ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1880536 Title: HDMI port is not working Status in linux package in Ubuntu: Won't Fix Bug description: HDMI port is not working and I don't the second secreen in Display settings. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 25 11:13:51 2020 DistUpgraded: 2020-05-22 16:25:45,628 DEBUG /openCache(), new cache size 97390 DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5079] InstallationDate: Installed on 2020-04-02 (52 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20RD004FMH ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic root=/dev/mapper/username--vg-root ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-05-22 (2 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R16ET21W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20RD004FMH dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR16ET21W(1.07):bd11/29/2019:svnLENOVO:pn20RD004FMH:pvrThinkPadE15:rvnLENOVO:rn20RD004FMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E15 dmi.product.name: 20RD004FMH dmi.product.version: ThinkPad E15 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 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/linux/+bug/1880536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)
Incidentally this bug has been happening and someone suggested updating Mutter to the latest version. I had to install mutter to then update it to try and fix it .. so now there are bugs due to software that was never installed in the first place !!! -- 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/1852183 Title: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93) Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] 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. [ Test case ] 1. Use use libreoffice writer/calc 2. Copy text around 3. Paste it and ensure it always work [ Regression potential ] Copy/paste won't work as expected, for non-text types - 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&px=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 1880243] Re: can't hide desktop icons neither with dconf-editor nor with gnome-shell-extension-desktop-icons
Yes I agree. The main bug people will hit is bug 1718850. -- 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/1880243 Title: can't hide desktop icons neither with dconf-editor nor with gnome- shell-extension-desktop-icons Status in gnome-shell-extension-desktop-icons package in Ubuntu: Invalid Bug description: In attempting to hide all desktop icons, I can't. 1. With dconf-editor, org/gnome/desktop/background/show-desktop-icons , I set the value to False, and yet the icons show. 2. With gnome-shell-extension-desktop-icons, despite disabling it, it still doesn't work (can change the size of the icons, but can't hide all icons when deactivating the extension). What's the appropriate approach to disable desktop icons? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-desktop-icons 20.04.0-1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 22 22:24:44 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-24 (1428 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to focal on 2020-05-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1880243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718850] Re: Gnome Tweaks: Extensions appear off by default and can't be toggled or configured
** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1718850 Title: Gnome Tweaks: Extensions appear off by default and can't be toggled or configured Status in Release Notes for Ubuntu: Fix Released Status in gnome-tweaks package in Ubuntu: Triaged Bug description: Go to the Extensions panel in Tweaks. System extensions (dock and appindicators) appear off by default, where they are obviously not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-tweak-tool 3.26.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 08:02:59 2017 ExecutablePath: /usr/bin/gnome-tweak-tool InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.13-2 SourcePackage: gnome-tweak-tool UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1718850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
Can this get escalated in any way? Surely such a basic operation as cut/copy and paste should be totally reliable, as it has been on all the systems I have used since 1970. A fundamental inability to do what a user requests is critical, in my view. I think I will have to ask people in the IT media what they think if this doesn't get sorted very soon. -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()
I'm new on here - sorry for any mistakes. I didn't know if it's worth adding, or where to add... that after I got this crash, I closed everything (and had my Android plugged in and mounted, but ejected it) and rebooted. Now, when I plug my phone back in, it makes the little alert noise, but I cannot find my phone drive. It doesn't show up in Files like it did last time, even when I click "other locations". (Files was what I was using to look at the phone files before the reboot) -- 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/1865300 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback() Status in GNOME Shell: Unknown Status in glib2.0 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9 --- Happened during normal use of the desktop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 29 19:51:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer InstallationDate: Installed on 2020-01-25 (35 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax PC (0x7f5f54fa6444) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423
/usr/sbin/pcscd --version pcsc-lite version 1.8.26. Copyright (C) 1999-2002 by David Corcoran . Copyright (C) 2001-2018 by Ludovic Rousseau . Copyright (C) 2003-2004 by Damien Sauveron . Report bugs to . Enabled features: Linux x86_64-pc-linux-gnu libsystemd serial usb libudev usbdropdir=/usr/lib/pcsc/drivers ipcdir=/run/pcscd filter configdir=/etc/reader.conf.d uname -a Linux rodigerlaptop1 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 20.04 HP Zbook 15 G3 laptop ActivKey SIM B/N: 0945423 This is USB key [ 6955.286635] usb 1-1: new full-speed USB device number 7 using xhci_hcd [ 6955.437171] usb 1-1: New USB device found, idVendor=09c3, idProduct=0014, bcdDevice= 2.07 [ 6955.437172] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 6955.437174] usb 1-1: Product: Activkey_Sim [ 6955.437174] usb 1-1: Manufacturer: ActivIdentity ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+attachment/5376522/+files/log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1879960 Title: pcscd doesn't support ActivKEy SIM B/N: 0945423 Status in pcsc-lite package in Ubuntu: New Bug description: I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not recognized by pcscd. Since it is not recognized, it is also not recognized by VMware Workstation VM which runs Windows. Banking software running in windows doesn't see the key and can't authenticate me. Few years ago, this was working on Ubuntu 18.04, so it must be something in version between. After restart of the pcscd service, USB key shows green light, but few seconds after it goes to red. sudo service pcscd status ● pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled) Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Main PID: 230408 (pcscd) Tasks: 5 (limit: 57614) Memory: 1.9M CGroup: /system.slice/pcscd.service └─230408 /usr/sbin/pcscd --foreground --auto-exit svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon. svi 21 15:48:01 rodigerlaptop1 pcscd[230408]: ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 ifdhandler.c:1221:IFDHPowerICC() PowerUp failed svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 0x80100016 Result of pcsc_scan sudo pcsc_scan Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader...found one Scanning present readers... 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Thu May 21 15:44:16 2020 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Event number: 0 Card state: Card inserted, Unresponsive card, So USB key is visible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pcscd 1.8.26-3 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 15:38:57 2020 SourcePackage: pcsc-lite UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880410] Re: pulseaudio doesn't enforce sample rate set in daemon.conf
I've missed a crucial point on the top of the daemon.conf file: The configuration file is a simple collection of variable declarations. If the configuration file parser encounters either ; or # it ignores the rest of the line until its end. Please close this 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/1880410 Title: pulseaudio doesn't enforce sample rate set in daemon.conf Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: Before submitting this bugreport I've went through the daemon.conf man page and the pulseaudio documentation, but have not found a solution to my problem. I've moved from Debian stable with pulseaudio version 12.2-4+deb10u1 to Kubuntu 20.04 with pulseaudio version 13.99.1-1ubuntu3.2. I'm experiencing cracking issues on external USB audio device Xonar U3 while listening to certain audio sources (system sounds included). This issue doesn't happen when using my laptop's internal audio device. Output of 'cat /proc/asound/card2/stream0' without audio stream running: C-Media Electronics Inc. USB Advanced Audio Device at usb-:00:14.0-2, full : USB Audio Playback: Status: Running Interface = 1 Altset = 1 Packet Size = 200 Momentary freq = 44100 Hz (0x2c.199a) Interface 1 Altset 1 Format: S16_LE Channels: 2 Endpoint: 1 OUT (ADAPTIVE) Rates: 8000, 16000, 44100, 48000 Bits: 16 Capture: Status: Stop Interface 2 Altset 1 Format: S16_LE Channels: 2 Endpoint: 2 IN (ASYNC) Rates: 8000, 16000, 44100, 48000 Bits: 16 The following behaviour happens with default settings in /etc/pulse/daemon.conf: Xonar U3 plugged in, firefox running: Momentary freq = 48000 Hz (0x30.) Xonar U3 plugged in, Clementine/Strawberry audio player running: Momentary freq = 44100 Hz (0x2c.199a) Xonar U3 plugged in with Deadbeef set to override sample rate to 48kHz: Momentary freq = 48000 Hz (0x30.) I've modified the daemon.conf as follows: ; default-sample-format = s16le #no change on this line, this is corresponding with the format the usb audio device suggests to be using ; default-sample-rate = 48000 ; alternate-sample-rate = 48000 However, when running video or audio sources with 44100Hz audio, applications do not respect the default-sample-rate and Momentary freq reports 44100Hz, while other sources either send 48kHz by default or have no problem respecting the setting (I've tried the game Into the Breach, VLC running 48kHz video and audio files). Complete /etc/pulse/daemon.conf contents: https://gist.github.com/zelmor/f224e6e4d300241e8431d3258e777e73 Checking syslog doesn't indicate any errors either, gist: https://gist.github.com/zelmor/5e59094be4d90ffa9e0ff6275594e370 ==Workarounds attempted== Modifying /etc/pulse/default.pa to include: load-module module-udev-detect tsched=0 Even after killing&restarting pulseaudio, this did not resolve anything. It also doesn't look like a good overall solution to the problem. Modifying daemon.conf to: ; resample-method = src-sinc-best-quality ; avoid-resampling = true Did not fix the issue. It is not possible to roll back PA to a previous version in Kubuntu 20.04 without breaking dependencies of the Plasma desktop, so this was not attempted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: zelmor 1994 F pulseaudio /dev/snd/controlC1: zelmor 1994 F pulseaudio /dev/snd/controlC0: zelmor 1994 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 24 16:30:11 2020 InstallationDate: Installed on 2020-04-28 (25 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET46WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7S11H00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20B7S11H00:pvrThinkPadT450:rvnLENOVO:rn20B7S11H00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20B7S11H00 dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T450 dmi.prod
[Desktop-packages] [Bug 1879893] Re: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock
This is also in bionic-proposed for testing, but tracking is broken because I forgot to include the changelog entry in .changes ** Changed in: xorg-server-hwe-18.04 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- 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/1879893 Title: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Status in xorg-server source package in Groovy: Fix Committed Status in xorg-server-hwe-18.04 source package in Groovy: Invalid Bug description: 1. Install Ubuntu 18.04.2 LTS with linux-oem-osp1 kernel, xserver-xorg-hwe-18.04 and nvidia-driver-440. 2. Select the performance mode in NVIDIA settings and reboot the system. 3. Connect dell-wd19tb-dock to the system. 4. Connect external HDMI monitor to dell-wd19tb-dock. 5. Open a terminal, some GUI applications and then execute `systemctl suspend` in the terminal. 6. Disconnect dell-wd19tb-dock after the system fell asleep. 7. Resume the system and login the GNOME desktop environment. Expected result: The terminal and other GUI applications will still exist. Actual result: All opened GUI applications in GNOME are gone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core-hwe-18.04 2:1.20.5+git20191008-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-1052.57-oem-osp1 5.0.21 Uname: Linux 5.0.0-1052-oem-osp1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 21 03:31:41 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-gilly+X33 InstallationDate: Installed on 2020-05-06 (14 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg-server-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880410] Re: pulseaudio doesn't enforce sample rate set in daemon.conf
Oh yes. I thought you mentioned the semicolons as only artistic formatting. ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- 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/1880410 Title: pulseaudio doesn't enforce sample rate set in daemon.conf Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Invalid Bug description: Before submitting this bugreport I've went through the daemon.conf man page and the pulseaudio documentation, but have not found a solution to my problem. I've moved from Debian stable with pulseaudio version 12.2-4+deb10u1 to Kubuntu 20.04 with pulseaudio version 13.99.1-1ubuntu3.2. I'm experiencing cracking issues on external USB audio device Xonar U3 while listening to certain audio sources (system sounds included). This issue doesn't happen when using my laptop's internal audio device. Output of 'cat /proc/asound/card2/stream0' without audio stream running: C-Media Electronics Inc. USB Advanced Audio Device at usb-:00:14.0-2, full : USB Audio Playback: Status: Running Interface = 1 Altset = 1 Packet Size = 200 Momentary freq = 44100 Hz (0x2c.199a) Interface 1 Altset 1 Format: S16_LE Channels: 2 Endpoint: 1 OUT (ADAPTIVE) Rates: 8000, 16000, 44100, 48000 Bits: 16 Capture: Status: Stop Interface 2 Altset 1 Format: S16_LE Channels: 2 Endpoint: 2 IN (ASYNC) Rates: 8000, 16000, 44100, 48000 Bits: 16 The following behaviour happens with default settings in /etc/pulse/daemon.conf: Xonar U3 plugged in, firefox running: Momentary freq = 48000 Hz (0x30.) Xonar U3 plugged in, Clementine/Strawberry audio player running: Momentary freq = 44100 Hz (0x2c.199a) Xonar U3 plugged in with Deadbeef set to override sample rate to 48kHz: Momentary freq = 48000 Hz (0x30.) I've modified the daemon.conf as follows: ; default-sample-format = s16le #no change on this line, this is corresponding with the format the usb audio device suggests to be using ; default-sample-rate = 48000 ; alternate-sample-rate = 48000 However, when running video or audio sources with 44100Hz audio, applications do not respect the default-sample-rate and Momentary freq reports 44100Hz, while other sources either send 48kHz by default or have no problem respecting the setting (I've tried the game Into the Breach, VLC running 48kHz video and audio files). Complete /etc/pulse/daemon.conf contents: https://gist.github.com/zelmor/f224e6e4d300241e8431d3258e777e73 Checking syslog doesn't indicate any errors either, gist: https://gist.github.com/zelmor/5e59094be4d90ffa9e0ff6275594e370 ==Workarounds attempted== Modifying /etc/pulse/default.pa to include: load-module module-udev-detect tsched=0 Even after killing&restarting pulseaudio, this did not resolve anything. It also doesn't look like a good overall solution to the problem. Modifying daemon.conf to: ; resample-method = src-sinc-best-quality ; avoid-resampling = true Did not fix the issue. It is not possible to roll back PA to a previous version in Kubuntu 20.04 without breaking dependencies of the Plasma desktop, so this was not attempted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: zelmor 1994 F pulseaudio /dev/snd/controlC1: zelmor 1994 F pulseaudio /dev/snd/controlC0: zelmor 1994 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun May 24 16:30:11 2020 InstallationDate: Installed on 2020-04-28 (25 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET46WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7S11H00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET46WW(1.11):bd03/02/2015:svnLENOVO:pn20B7S11H00:pvrThinkPadT450:rvnLENOVO:rn20B7S11H00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20B7S11H00 dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc
[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
Ideally please discuss it with the developers at: https://gitlab.gnome.org/GNOME/mutter/-/issues/1268 Not here. ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1268 https://gitlab.gnome.org/GNOME/mutter/-/issues/1268 -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879893] Re: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock
Can we say which of bug 1421808 / bug 1787332 / bug 1787338 this might be? -- 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/1879893 Title: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Status in xorg-server source package in Groovy: Fix Committed Status in xorg-server-hwe-18.04 source package in Groovy: Invalid Bug description: 1. Install Ubuntu 18.04.2 LTS with linux-oem-osp1 kernel, xserver-xorg-hwe-18.04 and nvidia-driver-440. 2. Select the performance mode in NVIDIA settings and reboot the system. 3. Connect dell-wd19tb-dock to the system. 4. Connect external HDMI monitor to dell-wd19tb-dock. 5. Open a terminal, some GUI applications and then execute `systemctl suspend` in the terminal. 6. Disconnect dell-wd19tb-dock after the system fell asleep. 7. Resume the system and login the GNOME desktop environment. Expected result: The terminal and other GUI applications will still exist. Actual result: All opened GUI applications in GNOME are gone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core-hwe-18.04 2:1.20.5+git20191008-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-1052.57-oem-osp1 5.0.21 Uname: Linux 5.0.0-1052-oem-osp1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 21 03:31:41 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-gilly+X33 InstallationDate: Installed on 2020-05-06 (14 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg-server-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
Daniel, sorry, but as far as I am concerned this is an ubuntu bug. That ubuntu uses, as a fundamental component (not just an add-on), something else is surely an ubuntu problem? If my car breaks down I don't search for the supplier of a component, I go to the car maker. I do not know if other linux flavours use the same components. I am just an ubuntu user. -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857539] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?)
Noticed here too. Fresh new groovy installation this weekend. -- 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/1857539 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path (shutdown?) Status in nautilus package in Ubuntu: Triaged Bug description: after turn on pc ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 01:52:06 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-12-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f3fb437f962:mov0x380(%rax),%rax PC (0x7f3fb437f962) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423
I don't see any problem in your log. The card is detected and the ATR is available. You can test with the command pcsc_scan from the package pcsc-tools. Please generate a new log including the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1879960 Title: pcscd doesn't support ActivKEy SIM B/N: 0945423 Status in pcsc-lite package in Ubuntu: New Bug description: I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not recognized by pcscd. Since it is not recognized, it is also not recognized by VMware Workstation VM which runs Windows. Banking software running in windows doesn't see the key and can't authenticate me. Few years ago, this was working on Ubuntu 18.04, so it must be something in version between. After restart of the pcscd service, USB key shows green light, but few seconds after it goes to red. sudo service pcscd status ● pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled) Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Main PID: 230408 (pcscd) Tasks: 5 (limit: 57614) Memory: 1.9M CGroup: /system.slice/pcscd.service └─230408 /usr/sbin/pcscd --foreground --auto-exit svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon. svi 21 15:48:01 rodigerlaptop1 pcscd[230408]: ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 ifdhandler.c:1221:IFDHPowerICC() PowerUp failed svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 0x80100016 Result of pcsc_scan sudo pcsc_scan Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader...found one Scanning present readers... 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Thu May 21 15:44:16 2020 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Event number: 0 Card state: Card inserted, Unresponsive card, So USB key is visible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pcscd 1.8.26-3 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 15:38:57 2020 SourcePackage: pcsc-lite UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423
sudo service pcscd status ● pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled) Active: inactive (dead) TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) drodiger@rodigerlaptop1:~$ sudo pcsc_scan Using reader plug'n play mechanism Scanning present readers... 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Mon May 25 13:13:00 2020 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Event number: 0 Card state: Card inserted, Unresponsive card, Scanning present readers... Waiting for the first reader...found one Scanning present readers... 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Mon May 25 13:13:16 2020 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Event number: 0 Card state: Card inserted, Unresponsive card, / Reporting this Unresponsive Card, when it should detect the card? sudo service pcscd status ● pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled) Active: inactive (dead) since Mon 2020-05-25 13:14:24 CEST; 29s ago TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Process: 16280 ExecStart=/usr/sbin/pcscd --foreground --auto-exit (code=exited, status=0/SUCCESS) Main PID: 16280 (code=exited, status=0/SUCCESS) svi 25 13:12:59 rodigerlaptop1 pcscd[16280]: 0268 commands.c:249:CmdPowerOn Card absent or mute svi 25 13:12:59 rodigerlaptop1 pcscd[16280]: 0007 ifdhandler.c:1221:IFDHPowerICC() PowerUp failed svi 25 13:12:59 rodigerlaptop1 pcscd[16280]: 0004 eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 0x80100016 svi 25 13:13:11 rodigerlaptop1 pcscd[16280]: 11584403 ccid_usb.c:857:WriteUSB() write failed (1/7): -4 LIBUSB_ERROR_NO_DEVICE svi 25 13:13:16 rodigerlaptop1 pcscd[16280]: 04928359 commands.c:249:CmdPowerOn Card absent or mute svi 25 13:13:16 rodigerlaptop1 pcscd[16280]: 0240 commands.c:249:CmdPowerOn Card absent or mute svi 25 13:13:16 rodigerlaptop1 pcscd[16280]: 0260 commands.c:249:CmdPowerOn Card absent or mute svi 25 13:13:16 rodigerlaptop1 pcscd[16280]: 0006 ifdhandler.c:1221:IFDHPowerICC() PowerUp failed svi 25 13:13:16 rodigerlaptop1 pcscd[16280]: 0004 eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 0x80100016 svi 25 13:14:24 rodigerlaptop1 systemd[1]: pcscd.service: Succeeded. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1879960 Title: pcscd doesn't support ActivKEy SIM B/N: 0945423 Status in pcsc-lite package in Ubuntu: New Bug description: I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not recognized by pcscd. Since it is not recognized, it is also not recognized by VMware Workstation VM which runs Windows. Banking software running in windows doesn't see the key and can't authenticate me. Few years ago, this was working on Ubuntu 18.04, so it must be something in version between. After restart of the pcscd service, USB key shows green light, but few seconds after it goes to red. sudo service pcscd status ● pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled) Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Main PID: 230408 (pcscd) Tasks: 5 (limit: 57614) Memory: 1.9M CGroup: /system.slice/pcscd.service └─230408 /usr/sbin/pcscd --foreground --auto-exit svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon. svi 21 15:48:01 rodigerlaptop1 pcscd[230408]: ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 ifdhandler.c:1221:IFDHPowerICC() PowerUp failed svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 0x80100016 Result of pcsc_scan sudo pcsc_scan Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader...found one Scanning present readers... 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Thu May 21 15:44:16 2020 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Event number: 0 Card state: Card inserted, Unresponsive card, So USB key is visible ProblemType: Bug DistroRe
[Desktop-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423
sudo lsusb |grep ActivKey Bus 001 Device 008: ID 09c3:0014 HID Global ActivIdentity ActivKey SIM USB Token lsusb -D /dev/bus/usb/001/008 Device: ID 09c3:0014 HID Global ActivIdentity ActivKey SIM USB Token Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize016 idVendor 0x09c3 HID Global idProduct 0x0014 ActivIdentity ActivKey SIM USB Token bcdDevice2.07 iManufacturer 1 ActivIdentity iProduct2 Activkey_Sim iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x005d bNumInterfaces 1 bConfigurationValue 1 iConfiguration 3 CCID 1.10 bmAttributes 0x80 (Bus Powered) MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 4 CCID Bulk Interface ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.10 (Warning: Only accurate for version 1.0) nMaxSlotIndex 0 bVoltageSupport 7 5.0V 3.0V 1.8V dwProtocols 3 T=0 T=1 dwDefaultClock 4800 dwMaxiumumClock 4800 bNumClockSupported 0 dwDataRate 12903 bps dwMaxDataRate 412903 bps bNumDataRatesSupp. 0 dwMaxIFSD 254 dwSyncProtocols dwMechanical dwFeatures 00010030 Auto clock change Auto baud rate change TPDU level exchange dwMaxCCIDMsgLen 271 bClassGetResponse 00 bClassEnvelope 00 wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 16 can't get device qualifier: Resource temporarily unavailable can't get debug descriptor: Resource temporarily unavailable Device Status: 0x (Bus Powered) service pcscd restart root@rodigerlaptop1:/dev/bus/usb/001# lsusb Bus 004 Device 004: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 004 Device 003: ID 0424:5807 Microchip Technology, Inc. (formerly SMSC) Hub Bus 004 Device 002: ID 2109:0820 VIA Labs, Inc. USB3.1 Hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 006: ID 2109: VIA Labs, Inc. Bus 003 Device 012: ID 0451:3421 Texas Instruments, Inc. USB2.0 Hub Bus 003 Device 011: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub Bus 003 Device 008: ID 03f0:0667 HP, Inc Bus 003 Device 005: ID 03f0:0269 HP, Inc Bus 003 Device 003: ID 0424:2807 Microchip Technology, Inc. (formerly SMSC) Hub Bus 003 Device 002: ID 2109:2820 VIA Labs, Inc. USB2.0 Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 004: ID 04f2:b51c Chicony Electronics Co., Ltd HP HD Camera Bus 001 Device 003: ID 0b0e:245e GN Netcom Jabra Link 370 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 006: ID 8087:0a2b Intel Corp. Bus 001 Device 009: ID 09c3:0014 HID Global ActivIdentity ActivKey SIM USB Token Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.
[Desktop-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423
pcscd log when I pulled USB out and put it back in. ** Attachment added: "Log2.txt" https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+attachment/5376525/+files/log2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1879960 Title: pcscd doesn't support ActivKEy SIM B/N: 0945423 Status in pcsc-lite package in Ubuntu: New Bug description: I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not recognized by pcscd. Since it is not recognized, it is also not recognized by VMware Workstation VM which runs Windows. Banking software running in windows doesn't see the key and can't authenticate me. Few years ago, this was working on Ubuntu 18.04, so it must be something in version between. After restart of the pcscd service, USB key shows green light, but few seconds after it goes to red. sudo service pcscd status ● pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled) Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Main PID: 230408 (pcscd) Tasks: 5 (limit: 57614) Memory: 1.9M CGroup: /system.slice/pcscd.service └─230408 /usr/sbin/pcscd --foreground --auto-exit svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon. svi 21 15:48:01 rodigerlaptop1 pcscd[230408]: ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 ifdhandler.c:1221:IFDHPowerICC() PowerUp failed svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 0x80100016 Result of pcsc_scan sudo pcsc_scan Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader...found one Scanning present readers... 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Thu May 21 15:44:16 2020 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Event number: 0 Card state: Card inserted, Unresponsive card, So USB key is visible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pcscd 1.8.26-3 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 15:38:57 2020 SourcePackage: pcsc-lite UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423
It gets new USB Device ID every time I plugin the Key ID 11, re plugin, ID 12... root@rodigerlaptop1:/dev/bus/usb/001# ls -la total 0 drwxr-xr-x 2 root root 180 svi 25 13:29 . drwxr-xr-x 6 root root 120 svi 25 13:11 .. crw-rw-r-- 1 root root 189, 0 svi 25 13:11 001 crw-rw-r-- 1 root root 189, 1 svi 25 13:11 002 crw-rw-r-- 1 root root 189, 2 svi 25 13:11 003 crw-rw-r-- 1 root root 189, 3 svi 25 13:11 004 crw-rw-r-- 1 root root 189, 4 svi 25 13:11 005 crw-rw-r-- 1 root root 189, 5 svi 25 13:11 006 crw-rw-r-- 1 root root 189, 10 svi 25 13:29 011 root@rodigerlaptop1:/dev/bus/usb/001# ls -la total 0 drwxr-xr-x 2 root root 180 svi 25 13:33 . drwxr-xr-x 6 root root 120 svi 25 13:11 .. crw-rw-r-- 1 root root 189, 0 svi 25 13:11 001 crw-rw-r-- 1 root root 189, 1 svi 25 13:11 002 crw-rw-r-- 1 root root 189, 2 svi 25 13:11 003 crw-rw-r-- 1 root root 189, 3 svi 25 13:11 004 crw-rw-r-- 1 root root 189, 4 svi 25 13:11 005 crw-rw-r-- 1 root root 189, 5 svi 25 13:11 006 crw-rw-r-- 1 root root 189, 11 svi 25 13:33 012 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1879960 Title: pcscd doesn't support ActivKEy SIM B/N: 0945423 Status in pcsc-lite package in Ubuntu: New Bug description: I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not recognized by pcscd. Since it is not recognized, it is also not recognized by VMware Workstation VM which runs Windows. Banking software running in windows doesn't see the key and can't authenticate me. Few years ago, this was working on Ubuntu 18.04, so it must be something in version between. After restart of the pcscd service, USB key shows green light, but few seconds after it goes to red. sudo service pcscd status ● pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled) Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Main PID: 230408 (pcscd) Tasks: 5 (limit: 57614) Memory: 1.9M CGroup: /system.slice/pcscd.service └─230408 /usr/sbin/pcscd --foreground --auto-exit svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon. svi 21 15:48:01 rodigerlaptop1 pcscd[230408]: ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 ifdhandler.c:1221:IFDHPowerICC() PowerUp failed svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 0x80100016 Result of pcsc_scan sudo pcsc_scan Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader...found one Scanning present readers... 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Thu May 21 15:44:16 2020 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Event number: 0 Card state: Card inserted, Unresponsive card, So USB key is visible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pcscd 1.8.26-3 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 15:38:57 2020 SourcePackage: pcsc-lite UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423
After pcscd restart, I see ActivKey got new Device ID -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1879960 Title: pcscd doesn't support ActivKEy SIM B/N: 0945423 Status in pcsc-lite package in Ubuntu: New Bug description: I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not recognized by pcscd. Since it is not recognized, it is also not recognized by VMware Workstation VM which runs Windows. Banking software running in windows doesn't see the key and can't authenticate me. Few years ago, this was working on Ubuntu 18.04, so it must be something in version between. After restart of the pcscd service, USB key shows green light, but few seconds after it goes to red. sudo service pcscd status ● pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled) Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Main PID: 230408 (pcscd) Tasks: 5 (limit: 57614) Memory: 1.9M CGroup: /system.slice/pcscd.service └─230408 /usr/sbin/pcscd --foreground --auto-exit svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon. svi 21 15:48:01 rodigerlaptop1 pcscd[230408]: ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 ifdhandler.c:1221:IFDHPowerICC() PowerUp failed svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 0x80100016 Result of pcsc_scan sudo pcsc_scan Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader...found one Scanning present readers... 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Thu May 21 15:44:16 2020 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Event number: 0 Card state: Card inserted, Unresponsive card, So USB key is visible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pcscd 1.8.26-3 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 15:38:57 2020 SourcePackage: pcsc-lite UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1393649] Re: Character 洣 missing
This was fixed at some point. 洣 now exists in sunpinyin. ** Changed in: sunpinyin (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sunpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1393649 Title: Character 洣 missing Status in sunpinyin package in Ubuntu: Fix Released Bug description: I am unsure if the bug is in sunpinyin itself or in sunpinyin-data. I suspect sunpinyin-data since that would make sense. Following https://wiki.ubuntu.com/Bugs/FindRightPackage gives "ibus- ui-gtk3": ryan@RyanVaio:~$ xprop WM_CLASS WM_CLASS(STRING) = "ibus-ui-gtk3", "Ibus-ui-gtk3" But, that's probably just the GUI component. In short, the problem is that this character doesn't show up in the character list: 洣 It's a real character, pronounced "mi3", and unfortunately happens to be part of a close family member's name. I have to copy-paste this character every time, and it's kind of a pain to do so. In case for some reason the font you're using doesn't display the character shown above, I've attached a small png image to this report. system details: ryan@RyanVaio:~$ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 ryan@RyanVaio:~$ dpkg -l | grep sunpinyin ii ibus-sunpinyin2.0.3-5build1 amd64sunpinyin engine for ibus ii libsunpinyin3:amd64 2.0.3+git20130507-1ubuntu1 amd64Simplified Chinese Input Method from SUN (runtime) ii sunpinyin-data0.1.22+20120112-1 amd64Statistical language model data from open-gram Running xubuntu 14.04 fully updated on a vaio pro 11. What I expect to happen: * I type "mi", the character list shows up, and scrolling through several pages of characters I find the "洣" character among the list (probably near the end). What actually happens: * I type "mi", scroll through several pages of characters, unable to find "洣", so I have to go copy-paste it from my notes instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sunpinyin/+bug/1393649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880559] [NEW] file roller not cleaning up temp files upon (disk full) failure
Public bug reported: file-roller 3.36.2, Copyright © 2001-2012 Free Software Foundation, Inc. on 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux When file-roller extracts a directory to a nearly fill media it stops with a generic message 'An error occurred while extracting files.' During the attempt to extract the files a temporary directory was created on the target medium (the directory is obscured by prefixing with .fr-). When clicking close the temporary directory is not cleaned up. And a subsequent attempt will create another temporary folder. So instead of informing the user that the target media is full file- roller fills the media with more 'junk' suggested solution: #1 cleanup tmp upon failure, #2 inform user of media-full reason. ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1880559 Title: file roller not cleaning up temp files upon (disk full) failure Status in file-roller package in Ubuntu: New Bug description: file-roller 3.36.2, Copyright © 2001-2012 Free Software Foundation, Inc. on 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux When file-roller extracts a directory to a nearly fill media it stops with a generic message 'An error occurred while extracting files.' During the attempt to extract the files a temporary directory was created on the target medium (the directory is obscured by prefixing with .fr-). When clicking close the temporary directory is not cleaned up. And a subsequent attempt will create another temporary folder. So instead of informing the user that the target media is full file- roller fills the media with more 'junk' suggested solution: #1 cleanup tmp upon failure, #2 inform user of media-full reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1880559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879206] Re: cups hplip not install printer
Could you try lpadmin -p DJ3630 -E -v ipp://localhost:6/ipp/print -m everywhere -- 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/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879893] Re: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock
I didn't see any crash log under /var/crash after this issue happened so bug 1421808 / bug 1787332 / bug 1787338 might be irrelevant. -- 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/1879893 Title: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Status in xorg-server source package in Groovy: Fix Committed Status in xorg-server-hwe-18.04 source package in Groovy: Invalid Bug description: 1. Install Ubuntu 18.04.2 LTS with linux-oem-osp1 kernel, xserver-xorg-hwe-18.04 and nvidia-driver-440. 2. Select the performance mode in NVIDIA settings and reboot the system. 3. Connect dell-wd19tb-dock to the system. 4. Connect external HDMI monitor to dell-wd19tb-dock. 5. Open a terminal, some GUI applications and then execute `systemctl suspend` in the terminal. 6. Disconnect dell-wd19tb-dock after the system fell asleep. 7. Resume the system and login the GNOME desktop environment. Expected result: The terminal and other GUI applications will still exist. Actual result: All opened GUI applications in GNOME are gone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core-hwe-18.04 2:1.20.5+git20191008-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-1052.57-oem-osp1 5.0.21 Uname: Linux 5.0.0-1052-oem-osp1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 21 03:31:41 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-gilly+X33 InstallationDate: Installed on 2020-05-06 (14 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg-server-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880562] [NEW] package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia
Public bug reported: al instalar el draiver genero un error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 07:58:10 2020 ErrorMessage: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-05-17 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/1880562 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: al instalar el draiver genero un error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 07:58:10 2020 ErrorMessage: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-05-17 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1880562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878838] Re: [nvidia] Black screen (wrong VT) upon login
Thanks for not getting dragged down in my stupidity. I spent some more time on this, and haven't figured out how I did something so dumb, but I was missing vmwgfx.ko because I was missing the linux-modules-extras package for -29 and -31. With that in place, all's well. Sorry for the noise, just wanted to close the loop. -- 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/1878838 Title: [nvidia] Black screen (wrong VT) upon login Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: OS: Fresh install of ubuntu 20.04 Steps: 1. Enter password to login (Black screen is shown) Workaround: 2. After blank screen is shown, press Ctrl+Alt+F3. (It'll show terminal with login prompt) 3. Don't login, simply press Ctrl+Alt+F2. (Now desktop is shown, black screen is gone) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 14:08:29 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438] InstallationDate: Installed on 2020-04-28 (16 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2a627b38-a2bd-4bec-9551-703eab56e5da ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/gdm3/+bug/1878838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860830] Re: Geolocation not working − the Google maps API always returns error codes
It is an issue with the Google API key used in Ubuntu builds (see comment #2). -- 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/1860830 Title: Geolocation not working − the Google maps API always returns error codes Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Happened as soon as Firefox was updated to 72.0.1. I noticed sites could not determine my location. Troubleshooting page shows "missing" under Location service key. I have another computer running Lubuntu 18.04LTS, which I rarely use. Just for fun, I booted it up and as soon as the software updater updated Firefox to 72.0.1, location stopped working. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 72.0.1+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: frank 2125 F pulseaudio /dev/snd/controlC1: frank 2125 F pulseaudio BuildID: 20200107212822 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 19:58:30 2020 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) IpRoute: default via 192.168.0.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.8 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-82fc5472-37b3-46d6-a6fa-f47e11180406 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:727 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=72.0.1/20200107212822 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to bionic on 2019-07-05 (203 days ago) dmi.bios.date: 03/24/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.27 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1442 dmi.board.vendor: Hewlett-Packard dmi.board.version: 67.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.27:bd03/24/2011:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr048D10242B202:rvnHewlett-Packard:rn1442:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 048D10242B202 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860830/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880396] Re: Traditional Chinese option not survived after reboot
Thanks for the advice. I've done the steps and the setting still got rolled backed to simplified Chinese. After some trying, I found that the `user` file got "touched" after every login(the date modified is updated). Is this a expected behavior? Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1880396 Title: Traditional Chinese option not survived after reboot Status in ibus-libpinyin package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS, ibus-libpinyin 1.11.1-3 expect: after changing from simplified chinese to traditional chinese, the setting should survive after reboot. phenomenon: option got reset to simplified chinese after reboot. using ibus pinyin input method, ticked 'Traditional' option for 'Chinese' label. The setting works but not kept after reboot. After reboot, the input mode turned back to simplified chinese. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1880396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880564] [NEW] ubuntu-drivers-common now pulls in build tools on end-user systems
Public bug reported: In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of build-essential on upgrades (or just binutils and make and patch if you pass --no-install-recommends). This needs to be reverted and fixed differently. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: High Status: Triaged ** Tags: regression-update rls-ff-incoming rls-gg-incoming ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1880564 Title: ubuntu-drivers-common now pulls in build tools on end-user systems Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of build-essential on upgrades (or just binutils and make and patch if you pass --no-install-recommends). This needs to be reverted and fixed differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1880564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880564] Re: ubuntu-drivers-common now pulls in build tools on end-user systems
This should be fixed before 20.04.1, so we don't install compilers on user system by default. ** Changed in: ubuntu-drivers-common (Ubuntu) Milestone: None => ubuntu-20.04.1 ** Tags added: rls-gg-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1880564 Title: ubuntu-drivers-common now pulls in build tools on end-user systems Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: In bug 1875339, a depends on dpkg-dev was added. This is pulling in all of build-essential on upgrades (or just binutils and make and patch if you pass --no-install-recommends). This needs to be reverted and fixed differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1880564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880305] Re: Failed to mount Windows share: Software caused connection abort
** No longer affects: nautilus (Ubuntu) -- 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/1880305 Title: Failed to mount Windows share: Software caused connection abort Status in samba package in Ubuntu: New Bug description: Since upgrading from 19.10 to 20.04 I cannot access folders on my NAS. What happens: In Nautilus (1:3.36.2-0ubuntu1) I do the following 1. Go to Other Locations 2. Click on Windows Network 3. Double Click on WORKGROUP 4. Double Click on DYLAN (the NAS at 192.168.1.5) 5. Double Click on public (a folder that does not require a password) I get the error message 'Unable to access location. Failed to mount windows share: Software caused connection abort'. What should happen: Following the above steps the public folder opens and shows the files and folders in it. My backups using Deja Dup also get this error. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 23 14:13:33 2020 InstallationDate: Installed on 2015-06-21 (1797 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-15 (7 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1880305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423
from your log I can see when you removed the device: 0016 [139787462866688] ccid_usb.c:857:WriteUSB() write failed (1/10): -4 LIBUSB_ERROR_NO_DEVICE Your problem is that reader can not power up the card after the reader is inserted again. 0003 [139787471259392] ifdhandler.c:1221:IFDHPowerICC() PowerUp failed What is strange is that the first time the card power up is very slow but works fine. The second time the reader responds very quickly with an error. I don't think the driver can do much to solve that. Do you have the same result if you use a different smart card? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1879960 Title: pcscd doesn't support ActivKEy SIM B/N: 0945423 Status in pcsc-lite package in Ubuntu: New Bug description: I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not recognized by pcscd. Since it is not recognized, it is also not recognized by VMware Workstation VM which runs Windows. Banking software running in windows doesn't see the key and can't authenticate me. Few years ago, this was working on Ubuntu 18.04, so it must be something in version between. After restart of the pcscd service, USB key shows green light, but few seconds after it goes to red. sudo service pcscd status ● pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled) Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Main PID: 230408 (pcscd) Tasks: 5 (limit: 57614) Memory: 1.9M CGroup: /system.slice/pcscd.service └─230408 /usr/sbin/pcscd --foreground --auto-exit svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon. svi 21 15:48:01 rodigerlaptop1 pcscd[230408]: ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 ifdhandler.c:1221:IFDHPowerICC() PowerUp failed svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 0x80100016 Result of pcsc_scan sudo pcsc_scan Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader...found one Scanning present readers... 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Thu May 21 15:44:16 2020 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Event number: 0 Card state: Card inserted, Unresponsive card, So USB key is visible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pcscd 1.8.26-3 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 15:38:57 2020 SourcePackage: pcsc-lite UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864558] Re: Printer adds automatically at boot with notification or if printer deleted
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1864558 Title: Printer adds automatically at boot with notification or if printer deleted Status in cups package in Ubuntu: Confirmed Bug description: When booting 20.04 I get a notification on the logon screen each time advising that my wireless printer has been setup. If I remove the printer via settings, then as soon as it's removed, it gets re-added and I see the same notification as I do on the logon screen about the printer having been setup. I've attached a screenshot of this notification. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 24 21:49:43 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1864558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879893] Re: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock
I have tested xorg-server-hwe-18.04 2:1.20.8-2ubuntu2.1~18.04.1 in bionic-proposed and it can fix the issue. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1879893 Title: GNOME crashed when resuming from sleep in NVIDIA performance mode with disconnecting dell-wd19tb-dock Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xorg-server source package in Focal: Fix Committed Status in xorg-server-hwe-18.04 source package in Focal: Invalid Status in xorg-server source package in Groovy: Fix Committed Status in xorg-server-hwe-18.04 source package in Groovy: Invalid Bug description: 1. Install Ubuntu 18.04.2 LTS with linux-oem-osp1 kernel, xserver-xorg-hwe-18.04 and nvidia-driver-440. 2. Select the performance mode in NVIDIA settings and reboot the system. 3. Connect dell-wd19tb-dock to the system. 4. Connect external HDMI monitor to dell-wd19tb-dock. 5. Open a terminal, some GUI applications and then execute `systemctl suspend` in the terminal. 6. Disconnect dell-wd19tb-dock after the system fell asleep. 7. Resume the system and login the GNOME desktop environment. Expected result: The terminal and other GUI applications will still exist. Actual result: All opened GUI applications in GNOME are gone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core-hwe-18.04 2:1.20.5+git20191008-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-1052.57-oem-osp1 5.0.21 Uname: Linux 5.0.0-1052-oem-osp1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 21 03:31:41 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-gilly+X33 InstallationDate: Installed on 2020-05-06 (14 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg-server-hwe-18.04 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1879893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880570] [NEW] Dock - running applications are not/delayed updated
Public bug reported: The running applications, displayed in the dock are sometimes not updated, or only updated with a long delay (after 20-30 seconds). However restarting with `alt`+`F2` -> "r" -> `enter`, fixes the problem temporarily, just to come back shortly after. At first I thought it was something caused by my update to 20.04, but it even happens with a fresh install (dock location is at the bottom). I think there are multiple ways to trigger this behavior, but what worked reliably so far is to close the last running application, so that the dock is completely empty (no favorite applications in the dock - only the "Show applications" button on the dock). So far this triggered the bug every time, but I'm quite sure there were also other ways to get into this "dock no longer/delayed updating" state with other means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 25 16:36:18 2020 InstallationDate: Installed on 2020-05-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1880570 Title: Dock - running applications are not/delayed updated Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: The running applications, displayed in the dock are sometimes not updated, or only updated with a long delay (after 20-30 seconds). However restarting with `alt`+`F2` -> "r" -> `enter`, fixes the problem temporarily, just to come back shortly after. At first I thought it was something caused by my update to 20.04, but it even happens with a fresh install (dock location is at the bottom). I think there are multiple ways to trigger this behavior, but what worked reliably so far is to close the last running application, so that the dock is completely empty (no favorite applications in the dock - only the "Show applications" button on the dock). So far this triggered the bug every time, but I'm quite sure there were also other ways to get into this "dock no longer/delayed updating" state with other means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 25 16:36:18 2020 InstallationDate: Installed on 2020-05-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864215] Re: Please add webp loader to gdk-pixbuf
See also bug #1407644 (libwebp) and bug #1318327 (eog). Still a problem in focal fossa. ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1864215 Title: Please add webp loader to gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: New Bug description: Attempting to load a webp image -- for instance, https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp or https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file format" error. Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in libwebp, but isn't this really a gdk-pixbuf issue? If it really does belong to libwebp, my apologies, please dup this bug to 1407644 (I'm confident it doesn't belong to eog since I don't use that program; I have other programs that use libgdk-pixbuf). You can probably use eog to test this, or run /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i webp (I assume the loader would mention webp if there was a loader for it). I have these packages installed in addition to libgdk-pixbuf2.0-0: libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes the format: $ file /tmp/FKK78W.jpg.webp /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 1200x533, Scaling: [none]x[none], YUV color, decoders should clamp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 Date: Fri Feb 21 08:48:36 2020 InstallationDate: Installed on 2019-10-10 (133 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1864215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879960] Re: pcscd doesn't support ActivKEy SIM B/N: 0945423
This one is still working on Windows PC. And it was also working on previous version of Ubuntu 19.04 I notice, that first time I plug it in, VMWAre Workstation with Windows VM also see this in its USB device list. But then windows software just can't read it. So, first time after reboot, Key even becomes Green, but than when it try's to access it, it changes to Red. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1879960 Title: pcscd doesn't support ActivKEy SIM B/N: 0945423 Status in pcsc-lite package in Ubuntu: New Bug description: I have ActivKey SIM B/N: 0945423 (from banking authorization) which is not recognized by pcscd. Since it is not recognized, it is also not recognized by VMware Workstation VM which runs Windows. Banking software running in windows doesn't see the key and can't authenticate me. Few years ago, this was working on Ubuntu 18.04, so it must be something in version between. After restart of the pcscd service, USB key shows green light, but few seconds after it goes to red. sudo service pcscd status ● pcscd.service - PC/SC Smart Card Daemon Loaded: loaded (/lib/systemd/system/pcscd.service; indirect; vendor preset: enabled) Active: active (running) since Thu 2020-05-21 15:47:40 CEST; 24s ago TriggeredBy: ● pcscd.socket Docs: man:pcscd(8) Main PID: 230408 (pcscd) Tasks: 5 (limit: 57614) Memory: 1.9M CGroup: /system.slice/pcscd.service └─230408 /usr/sbin/pcscd --foreground --auto-exit svi 21 15:47:40 rodigerlaptop1 systemd[1]: Started PC/SC Smart Card Daemon. svi 21 15:48:01 rodigerlaptop1 pcscd[230408]: ccid_usb.c:857:WriteUSB() write failed (1/12): -4 LIBUSB_ERROR_NO_DEVICE svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 02310986 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0264 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0343 commands.c:249:CmdPowerOn Card absent or mute svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0005 ifdhandler.c:1221:IFDHPowerICC() PowerUp failed svi 21 15:48:04 rodigerlaptop1 pcscd[230408]: 0003 eventhandler.c:305:EHStatusHandlerThread() Error powering up card: 2148532246 0x80100016 Result of pcsc_scan sudo pcsc_scan Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader...found one Scanning present readers... 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Thu May 21 15:44:16 2020 Reader 0: ActivIdentity Activkey_Sim [CCID Bulk Interface] 00 00 Event number: 0 Card state: Card inserted, Unresponsive card, So USB key is visible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pcscd 1.8.26-3 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 15:38:57 2020 SourcePackage: pcsc-lite UpgradeStatus: Upgraded to focal on 2020-05-11 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1879960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880570] Re: Dock - running applications are not/delayed updated
Looks like at least one more person has the same issue: https://askubuntu.com/questions/1234400/icons-take-several-seconds-to-appear-disappear-from-the-dock-when-the-app-is-ope It also looks like it is happening independently on the dock position, at least with the dock "left", I get the same behavior -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1880570 Title: Dock - running applications are not/delayed updated Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: The running applications, displayed in the dock are sometimes not updated, or only updated with a long delay (after 20-30 seconds). However restarting with `alt`+`F2` -> "r" -> `enter`, fixes the problem temporarily, just to come back shortly after. At first I thought it was something caused by my update to 20.04, but it even happens with a fresh install (dock location is at the bottom). I think there are multiple ways to trigger this behavior, but what worked reliably so far is to close the last running application, so that the dock is completely empty (no favorite applications in the dock - only the "Show applications" button on the dock). So far this triggered the bug every time, but I'm quite sure there were also other ways to get into this "dock no longer/delayed updating" state with other means. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 25 16:36:18 2020 InstallationDate: Installed on 2020-05-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868116] Re: QEMU monitor no longer works
** Changed in: qemu (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1868116 Title: QEMU monitor no longer works Status in QEMU: New Status in qemu package in Ubuntu: Invalid Status in vte2.91 package in Ubuntu: Fix Released Status in qemu package in Debian: Fix Released Bug description: Repro: VTE $ meson _build && ninja -C _build && ninja -C _build install qemu: $ ../configure --python=/usr/bin/python3 --disable-werror --disable-user --disable-linux-user --disable-docs --disable-guest-agent --disable-sdl --enable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt --disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi --disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir --disable-seccomp --disable-glusterfs --disable-tpm --disable-numa --disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs --disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma --disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock --disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user --disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs --disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat --disable-qed --disable-parallels --disable-sheepdog --disable-avx2 --disable-nettle --disable-gnutls --disable-capstone --disable-tools --disable-libpmem --disable-iconv --disable-cap-ng $ make Test: $ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH ./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive media=cdrom,file=http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso - switch to monitor with CTRL+ALT+2 - try to enter something Affects head of both usptream git repos. --- original bug --- It was observed that the QEMU console (normally accessible using Ctrl+Alt+2) accepts no input, so it can't be used. This is being problematic because there are cases where it's required to send commands to the guest, or key combinations that the host would grab (as Ctrl-Alt-F1 or Alt-F4). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu 1:4.2-3ubuntu2 Uname: Linux 5.6.0-rc6+ x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 12:16:31 2020 Dependencies: InstallationDate: Installed on 2017-06-13 (1009 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND qemu-system-x86 Sl+ 1000 1000 34275 25235 29.2 qemu-system-x86_64 -m 4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel kvm -device nec-usb-xhci -serial vc -serial stdio -hda /home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio kvm-nx-lpage-re S0 0 34284 2 0.0 [kvm-nx-lpage-re] kvm-pit/34275 S0 0 34286 2 0.0 [kvm-pit/34275] MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 zswap.enabled=1 zswap.zpool=z3fold resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 SourcePackage: qemu UpgradeStatus: Upgraded to focal on 2019-12-22 (87 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1868116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376561/+files/CRDA.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376562/+files/CurrentDmesg.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] [NEW] PCI/internal sound card not detected on ubuntu focal
Public bug reported: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers ** Affects: ubuntu Importance: Undecided Status: New ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: apport-collected focal ** Description changed: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output is also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu - @Hui Wang asked me to report this as a new bug in - https://bugs.launchpad.net/ubuntu/+source/linux-oem- - osp1/+bug/1864061/comments/64 + @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: timidity 1144 F timidity + /dev/snd/pcmC0D0p: timidity 1144 F...m timidity + /dev/snd/seq:timidity 1144 F timidity + /dev/snd/timer: timidity 1144 f timidity + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 + Lsusb: + Bus 0
[Desktop-packages] [Bug 1880571] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376560/+files/AlsaInfo.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376563/+files/Dependencies.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376565/+files/Lspci.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376564/+files/IwConfig.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376569/+files/ProcCpuinfoMinimal.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376570/+files/ProcEnviron.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376571/+files/ProcInterrupts.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376568/+files/Lsusb-v.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376572/+files/ProcModules.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376567/+files/Lsusb-t.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376573/+files/RfKill.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376566/+files/Lspci-vt.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] Re: PCI/internal sound card not detected on ubuntu focal
I had thought that appending options snd-hda-intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf had fixed the problem. But the problem has since reappeared. -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376575/+files/WifiSyslog.txt ** Description changed: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. - HDMI sound output is also does not work when the internal sound output does not work, USB sound output works. + HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: timidity 1144 F timidity - /dev/snd/pcmC0D0p: timidity 1144 F...m timidity - /dev/snd/seq:timidity 1144 F timidity - /dev/snd/timer: timidity 1144 f timidity + USERPID ACCESS COMMAND + /dev/snd/controlC0: timidity 1144 F timidity + /dev/snd/pcmC0D0p: timidity 1144 F...m timidity + /dev/snd/seq:timidity 1144 F timidity + /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 8087:0a2b Intel Corp. - Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2b Intel Corp. + Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-5.4.0-31-generic N/A - linux-backports-modules-5.4.0-31-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-31-generic N/A + linux-backports-modules-5.4.0-31-generic N/A + linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: - + _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-
[Desktop-packages] [Bug 1880571] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1880571/+attachment/5376574/+files/UdevDb.txt -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880492] Re: nautilus takes a long time to shut down
Thanks for the bug report. I was able to reproduce this on Focal with Nautilus version 3.36.2. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #423 https://gitlab.gnome.org/GNOME/nautilus/-/issues/423 -- 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/1880492 Title: nautilus takes a long time to shut down Status in nautilus package in Ubuntu: Confirmed Bug description: Start nautilus from the command line. Immediately close the open window with Ctrl-W. (this took me less than a second) The nautilus window closes immediately, but nautilus takes 13.5 sec to shut down: jlquinn@cerberus:~$ time nautilus Nautilus-Share-Message: 23:12:39.682: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) real 0m13.557s user 0m0.900s sys 0m0.103s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-102.103-generic 4.15.18 Uname: Linux 4.15.0-102-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 24 23:11:42 2020 InstallationDate: Installed on 2016-05-30 (1455 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-09-17 (616 days ago) usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1880492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880492] Re: nautilus takes a long time to shut down
Appears to already be reported upstream here: https://gitlab.gnome.org/GNOME/nautilus/-/issues/423 -- 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/1880492 Title: nautilus takes a long time to shut down Status in nautilus package in Ubuntu: Confirmed Bug description: Start nautilus from the command line. Immediately close the open window with Ctrl-W. (this took me less than a second) The nautilus window closes immediately, but nautilus takes 13.5 sec to shut down: jlquinn@cerberus:~$ time nautilus Nautilus-Share-Message: 23:12:39.682: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) real 0m13.557s user 0m0.900s sys 0m0.103s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-102.103-generic 4.15.18 Uname: Linux 4.15.0-102-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 24 23:11:42 2020 InstallationDate: Installed on 2016-05-30 (1455 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-09-17 (616 days ago) usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1880492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880396] Re: Traditional Chinese option not survived after reboot
I'm aware of one reason (there may be more) why ~/.config/dconf/user is changed at login. I'm thinking of bug #1873692, which is about to be fixed, btw. OTOH it's unlikely that e.g. gnome-shell would interfere with an ibus-libpinyin specific setting. Hmm.. As I said, I can't reproduce the problem. Just to be safe, and avoid possible misunderstandings, the command line way to access the setting is this: gsettings get com.github.libpinyin.ibus-libpinyin.libpinyin init- simplified-chinese If you switch to Traditional, that command outputs "false". Can you please confirm that your switching actually changes that dconf value to "false", and that it gets changed back to "true" only by logging out and logging in again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1880396 Title: Traditional Chinese option not survived after reboot Status in ibus-libpinyin package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS, ibus-libpinyin 1.11.1-3 expect: after changing from simplified chinese to traditional chinese, the setting should survive after reboot. phenomenon: option got reset to simplified chinese after reboot. using ibus pinyin input method, ticked 'Traditional' option for 'Chinese' label. The setting works but not kept after reboot. After reboot, the input mode turned back to simplified chinese. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1880396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] Re: PCI/internal sound card not detected on ubuntu focal
Seeing 'timidity' in the data collected by apport I have just uninstalled timidity. This has immediately restored the availability of the sound output. Also after rebooting, sound output is working again (I have since rebooted twice). -- 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/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880492] Re: nautilus takes a long time to shut down
** Tags added: focal -- 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/1880492 Title: nautilus takes a long time to shut down Status in nautilus package in Ubuntu: Confirmed Bug description: Start nautilus from the command line. Immediately close the open window with Ctrl-W. (this took me less than a second) The nautilus window closes immediately, but nautilus takes 13.5 sec to shut down: jlquinn@cerberus:~$ time nautilus Nautilus-Share-Message: 23:12:39.682: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) real 0m13.557s user 0m0.900s sys 0m0.103s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-102.103-generic 4.15.18 Uname: Linux 4.15.0-102-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 24 23:11:42 2020 InstallationDate: Installed on 2016-05-30 (1455 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-09-17 (616 days ago) usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1880492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2
I wanted to let you know that I am experiencing very similar behaviour on Kubuntu 20.04 after updating from 18.04 to 20.04, and I have my doubts that it's related to Mutter. For now I can confirm that I have an issue on KDE Plasma - to be able to paste (middle mouse click, Ctrl+C/V or Copy/Paste context menu options), I have to copy the same text twice, in one of the ways described below: 1. select text (ie. double click it), then click anywhere to lose focus from it, then select exactly the same text again - then I am able to paste with middle mouse button; or: 2. when text is already selected, I need to hit Ctrl+C twice, then I can paste it with Ctrl+V. Above is suspiciously close to what Davide mentioned above in comment https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1879968/comments/3 and that's why I decided my problem is probably related. My suspicion - this may be related to some application I use. On KDE this issue manifests almost right away after logging in now, but there's a short period after logging in, when it doesn't happen yet. Maybe I've got something in autostart that triggers it. On other environments (Openbox, LXQT and Gnome Shell) I did not experience this problem, however I did test only for a minute. My plan for next few days is to switch to LXQT and wait for the problem to happen again, and let you know. -- 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/1879968 Title: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2 Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: In Ubuntu 19.10 and 20.04 there was a bug that caused copy and paste operations to fail pretty often: the text that was pasted was not the text that was just copied. See the long discussion at bug #1852183. The bug was recently marked closed, since the package mutter - 3.36.2-1ubuntu1~20.04.1 landed in focal-updates and makes the bug occur much less frequently. Unfortunately the bug still exists, and is not difficult to reproduce. I am running Ubuntu 20.04 and have the new 3.36.2-1ubuntu1~20.04.1 version of mutter. I just opened two LibreOffice Writer windows side by side, and repeatedly selected some text in the left window, copied it, then attempted to paste it into the right window. In my experiment, approximately 1 in every 20 paste operations failed: it did not paste the text that was just copied, but instead the text that was copied before that. Now, an error rate of 1 in 20 may not seem so bad. On the other hand, if you spend all day writing a document and copy and paste dozens of times during the day, then you may hit this bug multiple times per day (as I have been recently), which is a significant annoyance. I tested in LibreOffice since that is where I have seen the bug most often, but I have also seen it occur in other applications as well. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880571] Re: PCI/internal sound card not detected on ubuntu focal
** Also affects: timidity (Ubuntu) Importance: Undecided Status: New ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1880571 Title: PCI/internal sound card not detected on ubuntu focal Status in Ubuntu: New Status in alsa-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Invalid Status in timidity package in Ubuntu: New Bug description: After booting the system the internal laptop speakers and the internal microphone are sometimes not detected, pavucontrol only shows a "Dummy Output". They were working fine under ubuntu 18.04, stopped working after upgrading to 19.10 and are still not working under 20.04. HDMI sound output also does not work when the internal sound output does not work, USB sound output works. The internal speakers and microphone are nearly always detected after running pulseaudio -k && sudo alsa force-reload lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 5.4.0-31-generic #35-Ubuntu @Hui Wang asked me to report this as a new bug in https://bugs.launchpad.net/ubuntu/+source/linux-oem-osp1/+bug/1864061/comments/64 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 1144 F timidity /dev/snd/pcmC0D0p: timidity 1144 F...m timidity /dev/snd/seq:timidity 1144 F timidity /dev/snd/timer: timidity 1144 f timidity CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=aeba982d-83c5-4cbf-83ca-f98664866381 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 058f:3822 Alcor Micro Corp. HD Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: TUXEDO Computers TUXEDO InfinityBook 14v1 Package: pulseaudio 1:13.99.1-1ubuntu3.2 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=efdd2912-a6af-4acf-a006-5d3e7fb3462b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (16 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/30/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 18.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: X35 dmi.board.vendor: TUXEDO Computers dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: X35 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr18.13:bd09/30/2016:svnTUXEDOComputers:pnTUXEDOInfinityBook14v1:pvrTBDbyOEM:rvnTUXEDOComputers:rnX35:rvrType2-BoardVersion:cvnX35:ct10:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: TUXEDO InfinityBook 14v1 dmi.product.sku: Type1Sku0 dmi.product.version: TBD by OEM dmi.sys.vendor: TUXEDO Computers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1880571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880562] Re: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-k
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided => Low ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Invalid -- 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/1880562 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 Status in nvidia-graphics-drivers-340 package in Ubuntu: Invalid Bug description: al instalar el draiver genero un error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 07:58:10 2020 ErrorMessage: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 InstallationDate: Installed on 2020-05-17 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: intentando sobreescribir `/lib/udev/rules.d/71-nvidia.rules', que está también en el paquete nvidia-kernel-common-440 440.82+really.440.64-0ubuntu6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1880562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874288] Re: Copy a screenshot of an area to clipboard prevents mouse click if used on modal UI elements
Do you need more information to reproduce this bug? -- 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/1874288 Title: Copy a screenshot of an area to clipboard prevents mouse click if used on modal UI elements Status in Gnome Screenshot: New Status in gnome-screenshot package in Ubuntu: New Bug description: Steps to reproduce: --- - Register a keyboard shortcut to trigger a "Copy a screenshot of an area to clipboard", i.e Shift+Ctrl+$ - Keyboard shortcut works fine and your mouse cursor becomes a cross-hair - Now open, for example, a selectbox in Firefox Application, or any UI item capturing mouse and try to trigger a screenshot in this state: for example, try to screenshot your active Application menu dropdown (Application > File > Save)… - At this moment, screenshot utility won’t change your mouse pointer into a crosshair and a bug occurs which prevents gnome-shell to respond to any mouse-click: I can’t click anymore on Dock icons, top bar actions and can’t click on Applications which are not in focus (I have to use Super+Tab to give focus to other applications) - However, mouse "hover" is still captured by applications (I can see UI tooltips appearing) but I can’t click anymore For the moment, the only way to recover my mouse click is to reboot Ubuntu or restart gdm3 service. Description: Ubuntu 20.04 LTS Release: 20.04 gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status gnome-shell: Installed: 3.36.1-5ubuntu1 Candidate: 3.36.1-5ubuntu1 Version table: *** 3.36.1-5ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status gnome-screenshot: Installed: 3.36.0-1ubuntu1 Candidate: 3.36.0-1ubuntu1 Version table: *** 3.36.0-1ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status What you expected to happen: Area screenshot should be saved into clipboard, even if a UI dropdown menu /selectbox element is activated (select-box, button, application top-menu bar…) What happened instead: -- Screenshot utility freezes and makes all gnome-shell unclickable To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screenshot/+bug/1874288/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873996] Re: DevTools does not open at 84.0.4115.5
I haven't had a chance to look into it yet, but it is on my radar.
** 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/1873996
Title:
DevTools does not open at 84.0.4115.5
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
https://bugs.chromium.org/p/chromium/issues/detail?id=1071961
Steps to reproduce the problem:
1. Ctrl+Shift+I or right-click, click Inspect
2. Navigate to chrome://inspect/#pages, click inspect
3.
What is the expected behavior?
DevTools to open
What went wrong?
DevTools does not open.
Did this work before? Yes Chromium 83
Chrome version: 84.0.4115.5 Channel: dev
$ chromium-browser --temp-profile
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:597:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:597:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:600:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:784:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:784:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:787:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.511: Theme parsing
error: gtk.css:1096:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
error: gtk.css:1096:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
error: gtk.css:1099:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2286:8: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2286:18: Using Pango syntax for the font: style
property is deprecated; please use CSS syntax
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2291:8: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2291:18: Using Pango syntax for the font: style
property is deprecated; please use CSS syntax
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4357:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4357:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4419:12: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4419:12: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4428:16: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4428:16: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4443:22: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4443:22: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4499:12: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4501:16: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4501:16: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4549:12: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing error:
gtk.css:4549:12: Expected a string.
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open i915 (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: i915
MESA-LOADER: failed to open kms_swrast (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
[21919:21919:0421/034207.195874:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot
read property 'Runtime' of undefined", source:
devtools://devtools/bundled/root/root-legacy.js (1)
[21919:21919:0421/034207.195989:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot
read property 'Runtime' of undefined", source:
devtools://devtools/bundled/root/root-legacy.js (1)
[21919:21919:0421/034207.197368:ERROR:CONSOLE(70)] "Uncaught TypeError:
Cannot read property 'setInspectedTabId' of undefined"
[Desktop-packages] [Bug 1880492] Re: nautilus takes a long time to shut down
per request in #ubuntu-bugs: setting to Triaged, adding upstream bug, setting importance to Low. ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/-/issues/423 Importance: Unknown Status: Unknown ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: Confirmed => Triaged -- 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/1880492 Title: nautilus takes a long time to shut down Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: Start nautilus from the command line. Immediately close the open window with Ctrl-W. (this took me less than a second) The nautilus window closes immediately, but nautilus takes 13.5 sec to shut down: jlquinn@cerberus:~$ time nautilus Nautilus-Share-Message: 23:12:39.682: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) real 0m13.557s user 0m0.900s sys 0m0.103s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.5 ProcVersionSignature: Ubuntu 4.15.0-102.103-generic 4.15.18 Uname: Linux 4.15.0-102-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 24 23:11:42 2020 InstallationDate: Installed on 2016-05-30 (1455 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-09-17 (616 days ago) usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1880492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1771880] Re: Seahorse unable to import pkcs12 certificates
Not seahorse but the same problem described in #33, my Mint 19.3 was not being able to sign with Libreoffice 6.0.7.3 (nor other apps like AutoFirma) It was solved by: - downgrading to openjdk 1.8 (sudo apt install openjdk-8-jre; sudo update-java-alternatives -s java-1.8.0-openjdk-amd64 ) - leaving just one profile for thunderbird with name default - upgrading to LibreOffice 6.4.2 Maybe not all the steps were neede, maybe LibreOffice was a matter of reinstalling with no need to upgrade (Autofirma worked just reinstalling) but now it works Regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1771880 Title: Seahorse unable to import pkcs12 certificates Status in seahorse: New Status in gnome-keyring package in Ubuntu: Confirmed Status in seahorse package in Ubuntu: Confirmed Status in gnome-keyring package in Fedora: New Status in seahorse package in Fedora: Unknown Bug description: seahorse 3.20.0-5 / gnome-keyring 3.28.0.2-1ubuntu1.18.04.1 / Ubuntu 18.04 LTS / GNOME 3.28.1 When trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, seahorse GUI application shows the 'import' button greyed out, while mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers". This problem doesn't occur on Ubuntu 16.04 LTS (Seahorse 3.18.0), as I've just tested on my wife's laptop, but happens in my Laptop with Ubuntu 18.04 LTS (Seahorse 3.20.0-5). Because that problem, it's not possible to digitally sign documents with LibreOffice. To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1771880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879206] Re: cups hplip not install printer
~$ lpadmin -p DJ3630 -E -v ipp://localhost:6/ipp/print -m everywhere lpadmin: Unable to query printer: Successo -- 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/1879206 Title: cups hplip not install printer Status in cups package in Ubuntu: Incomplete Status in hplip package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 20.04 I can't print anymore. Description: Ubuntu 20.04 LTS Release: 20.04 cups: Installato: 2.3.1-9ubuntu1.1 Candidato: 2.3.1-9ubuntu1.1 Tabella versione: *** 2.3.1-9ubuntu1.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2.3.1-9ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages hplip: Installato: 3.20.3+dfsg0-2 Candidato: 3.20.3+dfsg0-2 Tabella versione: *** 3.20.3+dfsg0-2 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I tried to reinstall the printer, but it is not being re-saved by cups / hplip ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 18 02:24:07 2020 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for DeskJet_3630: hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658 MachineType: LENOVO 80G0 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: /etc/cups/ppd/DeskJet_3630.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880586] [NEW] Serious regression (low FPS) in overview animation 3.36/20.024
Public bug reported: This is a downstream report to help track upstream https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2697. The issue has been described at length (maybe excessively) upstream, so I'm pointing to a "sum up" comment here https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/2697#note_788658. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Description changed: - This is a downstream report to track upstream + This is a downstream report to help track upstream https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2697. The issue has been described at length (maybe excessively) upstream, so I'm pointing to a "sum up" comment here https://gitlab.gnome.org/GNOME /gnome-shell/-/issues/2697#note_788658. -- 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/1880586 Title: Serious regression (low FPS) in overview animation 3.36/20.024 Status in gnome-shell package in Ubuntu: New Bug description: This is a downstream report to help track upstream https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2697. The issue has been described at length (maybe excessively) upstream, so I'm pointing to a "sum up" comment here https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2697#note_788658. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880589] [NEW] Screen Tearing - Ubuntu 20.04
Public bug reported: I am using the free drivers for my Nvidia card, since the private drivers gave more trouble than ever. I reported it too and the suggestion they gave me was to remove them and use the free drivers, but I have a serious problem with screen tearing, and I can't find a solution anywhere about it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 25 12:18:36 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:100d] NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 635M] [1043:100d] InstallationDate: Installed on 2020-04-24 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. K46CM ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=2d00d17e-c566-412e-bdfd-529af92571e2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K46CM.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K46CM dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK46CM.317:bd05/17/2013:svnASUSTeKCOMPUTERINC.:pnK46CM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK46CM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K46CM dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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 corruption focal 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/1880589 Title: Screen Tearing - Ubuntu 20.04 Status in xorg package in Ubuntu: New Bug description: I am using the free drivers for my Nvidia card, since the private drivers gave more trouble than ever. I reported it too and the suggestion they gave me was to remove them and use the free drivers, but I have a serious problem with screen tearing, and I can't find a solution anywhere about it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 25 12:18:36 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:100d] NVIDIA Corporation GF108M [GeForce GT 635M] [10de:0de3] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GF108M [GeForce GT 635M] [1043:100d] InstallationDate: Installed on 2020-04-24 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. K46CM ProcEnviron: LANGUAGE=es_CO:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CO.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=2d00d17e-c566-412e-bdfd-529af92571e2 ro quiet splash vt.handoff=7 Sour
[Desktop-packages] [Bug 1873996] Re: DevTools does not open at 84.0.4115.5
Ok. Thanks. The console is open all of the time here for testing and
experimentation. Random tabs crashing are simpler to deal with than
console not opening at all.
Not sure what precisely is undefined at root-legacy.js and
devtools_compatibility.js. Did notice that changes were recently made at
https://github.com/ChromeDevTools/devtools-
frontend/blob/5e43b27e8b453a22e365561b6a9a08d47999e6d4/front_end/root/module.json
and https://github.com/ChromeDevTools/devtools-
frontend/blob/6d51bf00ea3cdb7ef4d935bb52c15e25708f21fb/front_end/RuntimeInstantiator.js
--
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/1873996
Title:
DevTools does not open at 84.0.4115.5
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
https://bugs.chromium.org/p/chromium/issues/detail?id=1071961
Steps to reproduce the problem:
1. Ctrl+Shift+I or right-click, click Inspect
2. Navigate to chrome://inspect/#pages, click inspect
3.
What is the expected behavior?
DevTools to open
What went wrong?
DevTools does not open.
Did this work before? Yes Chromium 83
Chrome version: 84.0.4115.5 Channel: dev
$ chromium-browser --temp-profile
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:597:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:597:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.509: Theme parsing
error: gtk.css:600:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:784:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:784:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.510: Theme parsing
error: gtk.css:787:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.511: Theme parsing
error: gtk.css:1096:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
error: gtk.css:1096:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.512: Theme parsing
error: gtk.css:1099:17: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2286:8: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2286:18: Using Pango syntax for the font: style
property is deprecated; please use CSS syntax
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2291:8: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.517: Theme parsing
error: gtk.css:2291:18: Using Pango syntax for the font: style
property is deprecated; please use CSS syntax
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4357:14: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4357:14: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4419:12: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4419:12: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.523: Theme parsing
error: gtk.css:4428:16: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4428:16: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4443:22: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4443:22: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4499:12: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4501:16: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4501:16: Expected a string.
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing
error: gtk.css:4549:12: not a number
(chromium-browser:21919): Gtk-WARNING **: 03:41:50.524: Theme parsing error:
gtk.css:4549:12: Expected a string.
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open i915 (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: i915
MESA-LOADER: failed to open kms_swrast (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths
/usr/lib/i386-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
[21919:21919:0421/034207.195874:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot
read property
[Desktop-packages] [Bug 1880594] [NEW] Ubuntu-server slow after upgrade to 20.04
Public bug reported: After upgrading to 20.04 my ubuntu-server seems very slow. Also using tab to autocomplete commands takes ~10 Seconds to complete ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-server 1.450 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 19:57:43 2020 InstallationDate: Installed on 2020-03-10 (75 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-04-26 (29 days ago) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1880594 Title: Ubuntu-server slow after upgrade to 20.04 Status in ubuntu-meta package in Ubuntu: New Bug description: After upgrading to 20.04 my ubuntu-server seems very slow. Also using tab to autocomplete commands takes ~10 Seconds to complete ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-server 1.450 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 25 19:57:43 2020 InstallationDate: Installed on 2020-03-10 (75 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-04-26 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1880594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880596] [NEW] [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertable laptops in tablet mode with physical keyboard disabled
Public bug reported:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell fields
like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text fields
of foreign toolkits that are expected not to trigger the OSK automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04. Only
the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under Xorg,
but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing in
the device's laptop mode, i.e. with the physical keyboard enabled. This seems
intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly Wayland
and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said to
have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
** Affects: gnome-shell
Importance: Unknown
Status: Unknown
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1242
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
Importance: Unknown
Status: Unknown
--
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/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertable laptops in tablet mode with physical
keyboard disabled
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
New
Bug description:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell
fields like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign
[Desktop-packages] [Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertable laptops in tablet mode with physical keyboard disabled
** Description changed:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
- Related upstream bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
+ Related upstream bugs:
+ https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
+ https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell
fields like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04. Only
the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under Xorg,
but this should not be necessary)
- (On Wayland there is a different changed behavior with the OSK not
- appearing in the device's laptop mode, i.e. with the physical keyboard
- enabled. This seems intended and a different issue as per
- https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872)
+ (On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
+ https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
- This bug report was created on Dell XPS 9575 2-in-1, where the bug
reproduces.
+
+ This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said to
have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 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/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertable laptops in tablet mode with physical
keyboard disabled
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
New
Bug description:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
[Note: Please someone add a bug watch for
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378. I set one
for the other and then Launchpad somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell
fields like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothin
[Desktop-packages] [Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertable laptops in tablet mode with physical keyboard disabled
sudo libinput list-devices > list-devices.txt:
was generated in laptop mode i.e. with the physical keyboard enabled.
** Description changed:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
- Related upstream bugs:
+ Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gitlab.gnome.org/GNOME/mutter/-/issues/1242
+
+ [Note: Please someone add a bug watch for https://gitlab.gnome.org/GNOME
+ /gnome-shell/-/issues/2378. I set one for the other and then Launchpad
+ somehow did not let me again]
Reproduction with Ubuntu 20.04 on affected convertible devices like Dell XPS
9575 2-in-1:
1. Log into gnome-shell Xorg session ("Ubuntu")
2. Fold the display back, to switch to tablet mode. (On properly supported
devices, this disables the physical keyboard)
3. Use touch screen to touch any text input field, including gnome-shell
fields like Activities > Search
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text
4. Swipe from bottom of screen in order to summon OSK on demand:
-> EXPECTED RESULT (occurred on Ubuntu 18.04 through 19.10): The OSK appears
-> ACTUAL RESULT: nothing happens, you cannot enter text (e.g. into text
fields of foreign toolkits that are expected not to trigger the OSK
automatically)
Note that the EXPECTED RESULT still happens under Wayland in 20.04. Only
the Xorg session is affected by the issue described in this bug.
Also note that Accessibility was NOT necessary to be enabled in 19.10
and before. (When enabling it in 20.04, the OSK does appear under Xorg,
but this should not be necessary)
(On Wayland there is a different changed behavior with the OSK not appearing
in the device's laptop mode, i.e. with the physical keyboard enabled. This
seems intended and a different issue as per
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/872 and
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2353 )
-
This bug report was created on Dell XPS 9575 2-in-1, where the bug reproduces.
I can confirm that the EXPECTED behavior occurred under Xorg in 19.10 on this
machine as well as on the Asus Zenbook Flip UX561UD, and stopped with 20.04.
It probably also worked with 19.04 and possibly 18.10, but I ran mostly
Wayland and so am not entirely sure. (I never ran 18.04 on these devices)
Other hardware reported to reproduce the issue (and in part are said to
have been working in 19.10 and before, down to 18.04) include:
In bug #1866556;
Lenovo ThinkPad L390 Yoga
Asus ZenBook UX370UAF
Acer Switch 11 V sw5-173 (said to have worked with 18.04)
(Possibly HP ENVY x360 15-cp0 and Lenovo ThinkPad X201 Tablet, though the
tablet mode seems unsupported on these devices and so the issue might be
different)
In upstream bug:
Dell Inspiron 15 700 2-in-1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
Uname: Linux 5.4.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon May 25 19:59:40 2020
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-13 (619 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-01-04 (141 days ago)
** Attachment added: "list-devices.txt"
https://bugs.launchpad.net/gnome-shell/+bug/1880596/+attachment/5376642/+files/list-devices.txt
** Summary changed:
- [Focal regression] On-screen keyboard (OSK) does not appear on touch under
Xorg on convertable laptops in tablet mode with physical keyboard disabled
+ [Focal regression] On-screen keyboard (OSK) does not appear on touch under
Xorg on convertible laptops in tablet mode with physical keyboard disabled
** Summary changed:
- [Focal regression] On-screen keyboard (OSK) does not appear on touch under
Xorg on convertible laptops in tablet mode with physical keyboard disabled
+ [Focal regression] On-screen keyboard (OSK) does not appear on touch under
Xorg on convertible laptops in tablet mode when physical keyboard disabled
--
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/1880596
Title:
[Focal regression] On-screen keyboard (OSK) does not appear on touch
under Xorg on convertible laptops in tablet mode when physical
keyboard disabled
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
New
Bug description:
Opening new bug as instructed by Sebastien Bacher (seb128) in bug #1866556.
Related upstream bugs:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2378
https://gi
[Desktop-packages] [Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
@seb128: Created the new bug #1880596 -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal Status in gnome-shell package in Ubuntu: Confirmed Bug description: After upgrading to Focal, the OSK never appears for me under Xorg - Does not appear automatically when selecting text fields - Cannot be summoned on-demand by swiping up from bottom screen border (which worked on Eoan also under Xorg) Under Wayland, both these things continued to work after the Focal upgrade if the laptop is in tablet mode (but not if it is in regular laptop mode - not sure if this changed on upgrade). I could repro this on two "2-in-1" fold-able laptops: Dell XPS 9575 2-in-1 Asus Zenbook flip UX561UD. (Note: There was an older bug #1760399 about OSK not working under Xorg, but this one was fixed in Cosmic) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 Uname: Linux 5.5.4-050504-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 8 17:33:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-13 (541 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-04 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
