[Desktop-packages] [Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
verify fixed with mutter 42.9-0ubuntu7 in jammy-proposed. SEV16_DVT1_C4 202309-32111 1. enable proposed 2. sudo apt update 3. sudo apt dist-upgrade 4. sudo reboot -i 5. sudo dpkg -l | grep mutter (make sure all mutter related were ugpraded to 42.9ubuntu7) 6. Connect external monitor to the affected system 7. Switch display modes to mirror mode 8. Observe the mirror mode can be set successfully. So the issue is resolved. ** Tags removed: verification-needed ** Tags added: verification-done verification-done-jammy ** Tags removed: verification-needed-jammy -- 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2051829] [NEW] Nautilus file manager failed to connect to samba share with user without password
Public bug reported: Ubuntu 23.10 nautilus: Installed: 1:45~rc-1ubuntu1 I expected successful connection to a samba share with specific user without password. I have home samba server running on ubuntu server. It provides one share with disabled anonymous access but with a user without password (blank). Windows explorer, mac finder and other clients works fine, even terminal smbclient, but then i try to connect with nautilus from ubuntu desktop as "registered user" but leave password blank -> i got "invalid argument". When i create another samba user on the server with a password - connection was successful. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 12:18:54 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2023-12-27 (35 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2023.09.06 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session ** Attachment added: "image_2024-01-31_122839837.png" https://bugs.launchpad.net/bugs/2051829/+attachment/5743877/+files/image_2024-01-31_122839837.png -- 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/2051829 Title: Nautilus file manager failed to connect to samba share with user without password Status in nautilus package in Ubuntu: New Bug description: Ubuntu 23.10 nautilus: Installed: 1:45~rc-1ubuntu1 I expected successful connection to a samba share with specific user without password. I have home samba server running on ubuntu server. It provides one share with disabled anonymous access but with a user without password (blank). Windows explorer, mac finder and other clients works fine, even terminal smbclient, but then i try to connect with nautilus from ubuntu desktop as "registered user" but leave password blank -> i got "invalid argument". When i create another samba user on the server with a password - connection was successful. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-15.15-generic 6.5.3 Uname: Linux 6.5.0-15-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jan 31 12:18:54 2024 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2023-12-27 (35 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2023.09.06 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2051829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-2022991 -- 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/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Triaged Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1992783] Re: Internet connection crashed during update from 20.04 to 22.04. Tried to fix the install with sudo apt --fix-broken install
Problem solved by adding the package name after the command (sudo apt --fix-broken install firefox) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1992783 Title: Internet connection crashed during update from 20.04 to 22.04. Tried to fix the install with sudo apt --fix-broken install Status in firefox package in Ubuntu: New Bug description: The rest of the update completed and version 22.04 is running. System is running fine but can't install a new package with apt-get install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1586 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Oct 13 14:03:06 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 10 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-27 (200 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev wlp170s0 proto dhcp metric 600 169.254.0.0/16 dev wlp170s0 scope link metric 1000 192.168.1.0/24 dev wlp170s0 proto kernel scope link src 192.168.1.104 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to jammy on 2022-08-29 (44 days ago) dmi.bios.date: 12/14/2021 dmi.bios.release: 3.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.07 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0A dmi.board.vendor: Framework dmi.board.version: AA dmi.chassis.asset.tag: FRANBMCPAA1445003R dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AA dmi.modalias: dmi:bvnINSYDECorp.:bvr03.07:bd12/14/2021:br3.7:svnFramework:pnLaptop:pvrAA:rvnFramework:rnFRANBMCP0A:rvrAA:cvnFramework:ct10:cvrAA:skuFRANBMCP0A: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0A dmi.product.version: AA dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1992783] [NEW] Internet connection crashed during update from 20.04 to 22.04. Tried to fix the install with sudo apt --fix-broken install
Public bug reported: The rest of the update completed and version 22.04 is running. System is running fine but can't install a new package with apt-get install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1586 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Oct 13 14:03:06 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 10 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-27 (200 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev wlp170s0 proto dhcp metric 600 169.254.0.0/16 dev wlp170s0 scope link metric 1000 192.168.1.0/24 dev wlp170s0 proto kernel scope link src 192.168.1.104 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to jammy on 2022-08-29 (44 days ago) dmi.bios.date: 12/14/2021 dmi.bios.release: 3.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.07 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0A dmi.board.vendor: Framework dmi.board.version: AA dmi.chassis.asset.tag: FRANBMCPAA1445003R dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AA dmi.modalias: dmi:bvnINSYDECorp.:bvr03.07:bd12/14/2021:br3.7:svnFramework:pnLaptop:pvrAA:rvnFramework:rnFRANBMCP0A:rvrAA:cvnFramework:ct10:cvrAA:skuFRANBMCP0A: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0A dmi.product.version: AA dmi.sys.vendor: Framework ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1992783 Title: Internet connection crashed during update from 20.04 to 22.04. Tried to fix the install with sudo apt --fix-broken install Status in firefox package in Ubuntu: New Bug description: The rest of the update completed and version 22.04 is running. System is running fine but can't install a new package with apt-get install ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 104.0+build3-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1586 F pulseaudio BuildID: 20220818191623 CasperMD5CheckResult: unknown Channel: Unavailable Date: Thu Oct 13 14:03:06 2022 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 10 ForcedLayersAccel: False InstallationDate: Installed on 2022-03-27 (200 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) IpRoute: default via 192.168.1.1 dev wlp170s0 proto dhcp metric 600 169.254.0.0/16 dev wlp170s0 scope link metric 1000 192.168.1.0/24 dev wlp170s0 proto kernel scope link src 192.168.1.104 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 104.0+build3-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to jammy on 2022-08-29 (44 days ago) dmi.bios.date: 12/14/2021 dmi.bios.release: 3.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.07 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0A dmi.board.vendor: Framework dmi.board.version: AA dmi.chassis.asset.tag: FRANBMCPAA1445003R
[Desktop-packages] [Bug 1966580] Re: Erroneously huge mouse pointer with snap-packaged firefox in jammy
Laptop: HP Spectre x360 Convertible 14-ea0xxx Graphics: Intel TigerLake-LP GT2 [Iris Xe Graphics] Resolution: 3000x2000 Mostly uncustomized out-of-the-box Ubuntu, the one notable choice being to use the gnome-xorg session type (declining to use the Ubuntu customisations to gnome-session, declining to use Wayland) More than that, I can't give you, as I've long since uninstalled snapd, and am unwilling to reinstall it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966580 Title: Erroneously huge mouse pointer with snap-packaged firefox in jammy Status in firefox package in Ubuntu: Incomplete Bug description: I just upgraded to jammy, and the mouse cursor now becomes comically huge whilst it's over a Firefox window. I suspect this might be something to do with this being a HiDPI laptop. I'm also fairly upset about the overcomplicated - and apparently broken - snaps being enforced on me, so I've fixed this by uninstalling snapd, and obtaining Firefox directly from Mozilla instead - which works absolutely fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966580] Re: Erroneously huge mouse pointer with snap-packaged firefox in jammy
Sorry, I am opposed to Canonical forcing snap on Ubuntu users and do not wish to spend my personal time on supporting that. I'll just use a non-snap distribution mechanism instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966580 Title: Erroneously huge mouse pointer with snap-packaged firefox in jammy Status in firefox package in Ubuntu: New Bug description: I just upgraded to jammy, and the mouse cursor now becomes comically huge whilst it's over a Firefox window. I suspect this might be something to do with this being a HiDPI laptop. I'm also fairly upset about the overcomplicated - and apparently broken - snaps being enforced on me, so I've fixed this by uninstalling snapd, and obtaining Firefox directly from Mozilla instead - which works absolutely fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966091] Re: Random noises with 5.13.0-37-generic and later but not with 5.13.0-35-generic
I can confirm that. Fixed with 5.13.0-41-generic. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- 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/1966091 Title: Random noises with 5.13.0-37-generic and later but not with 5.13.0-35-generic Status in pulseaudio package in Ubuntu: Fix Released Bug description: After a recent update to linux-image-5.13.0-37-generic, I started experiencing random noises about every five seconds. After rebooting into linux-image-5.13.0-35-generic, the noises were gone. Some details that I've noticed: 1. When launching pulseaudio manually, not as a daemon, the problem disappears. 2. If I set the log-level in /etc/pulse/daemon.conf to debug and reload it, the log has a lot of: Mar 23 17:22:44 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Mar 23 17:22:43 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Mar 23 17:22:39 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Mar 23 17:22:38 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Which roughly correspond with the noises. 3. The usual "rm -f -r ~/.config/pulse && pulseaudio -k && sudo alsa force-reload" doesn't seem to help. Only a kernel downgrade does. 4. This happens both in Firefox (where I first noticed it) as well as in Totem and in system sounds. 5. I tried to report the bug using "ubuntu-bug audio", but it showed me six inputs of which three looked the same, and for each of them it told me that it pulseaudio wasn't configured to use it. I'm ready to collect logs and other info within the next days. Additional Info $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: Ubuntu 20.04.4 LTS Release: 20.04 Codename: focal $ apt-cache policy linux-image-generic-hwe-20.04 linux-image-generic-hwe-20.04: Installed: 5.13.0.37.42~20.04.22 Candidate: 5.13.0.37.42~20.04.22 Version table: *** 5.13.0.37.42~20.04.22 500 500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages 500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages $ apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.13 Candidate: 1:13.99.1-1ubuntu3.13 Version table: *** 1:13.99.1-1ubuntu3.13 500 500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967995] Re: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound
This got fixed for me with 5.13.0-41-generic. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Released -- 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/1967995 Title: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Fix Released Bug description: In the last 24 hours, my system has started having skipping/stuttering audio when gaming, or watching videos on youtube in chrome, and no audio at all when using VLC to play music files or watching youtube in Firefox. I believe I did a system update in the last week or so but I don't know if that is the cause. Description: Ubuntu 20.04.4 LTS Release: 20.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 00:05:34 2022 InstallationDate: Installed on 2020-08-31 (582 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Headset successful Symptom_Card: G930 - Logitech G930 Headset Symptom_PulseAudioLog: Apr 05 23:40:42 nzxt dbus-daemon[1169]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.40' (uid=125 pid=1765 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Apr 05 23:41:59 nzxt systemd[1655]: pulseaudio.service: Succeeded. Apr 05 23:42:09 nzxt systemd[1655]: pulseaudio.socket: Succeeded. Apr 05 23:49:33 nzxt sudo[8926]: root : TTY=unknown ; PWD=/home/raj ; USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; COMMAND=/usr/bin/xdg-open https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/b77c80a0-b575-11ec-b9ed-40a8f0305cb4? Apr 05 23:54:56 nzxt sudo[11680]: root : TTY=unknown ; PWD=/home/raj ; USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; COMMAND=/usr/bin/xdg-open https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/77aee818-b576-11ec-b78d-40a8f0308420? Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450 I AORUS PRO WIFI-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.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450 I AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1967995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966091] Re: Random noises with 5.13.0-37-generic and later but not with 5.13.0-35-generic
Also with new 5.13.0-40-generic the issue is still available for me. -- 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/1966091 Title: Random noises with 5.13.0-37-generic and later but not with 5.13.0-35-generic Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a recent update to linux-image-5.13.0-37-generic, I started experiencing random noises about every five seconds. After rebooting into linux-image-5.13.0-35-generic, the noises were gone. Some details that I've noticed: 1. When launching pulseaudio manually, not as a daemon, the problem disappears. 2. If I set the log-level in /etc/pulse/daemon.conf to debug and reload it, the log has a lot of: Mar 23 17:22:44 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Mar 23 17:22:43 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Mar 23 17:22:39 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Mar 23 17:22:38 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Which roughly correspond with the noises. 3. The usual "rm -f -r ~/.config/pulse && pulseaudio -k && sudo alsa force-reload" doesn't seem to help. Only a kernel downgrade does. 4. This happens both in Firefox (where I first noticed it) as well as in Totem and in system sounds. 5. I tried to report the bug using "ubuntu-bug audio", but it showed me six inputs of which three looked the same, and for each of them it told me that it pulseaudio wasn't configured to use it. I'm ready to collect logs and other info within the next days. Additional Info $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: Ubuntu 20.04.4 LTS Release: 20.04 Codename: focal $ apt-cache policy linux-image-generic-hwe-20.04 linux-image-generic-hwe-20.04: Installed: 5.13.0.37.42~20.04.22 Candidate: 5.13.0.37.42~20.04.22 Version table: *** 5.13.0.37.42~20.04.22 500 500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages 500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages $ apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.13 Candidate: 1:13.99.1-1ubuntu3.13 Version table: *** 1:13.99.1-1ubuntu3.13 500 500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960614] Re: Add mid: scheme handler to thunderbird.desktop
Thank you, Olivier. I am happy to see that it works out of the box in 20.04 focal LTS. The fix was released a month ago, but since I anyway had custom association configured in ~/.config/mimeapps.list, I forgot to check it earlier. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1960614 Title: Add mid: scheme handler to thunderbird.desktop Status in thunderbird package in Ubuntu: Fix Released Bug description: Since thunderbird-91 version (actually even earlier, but only ESR releases are packaged in Ubuntu) it is possible to open particular messages from command line using Message-ID: thunderbird mid:a...@example.com See e.g. https://bugzilla.mozilla.org/264270 However to open links from other application "mid:" scheme should be advertised in the thunderbird.desktop file: MimeType=x-scheme-handler/mailto;application/x-xpinstall;x-scheme- handler/mid; Please, adjust this field in the desktop file. To check that the change has effect the following command may be used: xdg-open mid:a...@example.com Notice that it is not upstream issue. Thunderbird developers left desktop integration up to maintainers of Linux distributions. Long time ago it was possible to create such links to particular messages using thunderlink extension but migration from XUL to WebExtension add-ons broke it. Support of mid: scheme restores linking of mail messages from other applications. There is a related issue: request to add message/rfc822 MIME type in lp:1861262 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1960614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967995] Re: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound
Similar issue for me with a Jabra Evolve 75 headset. As soon as microphone is used, e.g. for a call, the driver seems to get into a corrupted state where sound from speakers have crackling sound as long as microphone is active. The issue doesn't appear when starting with kernel 5.13.0-35. Looks like there have been some changes to usb-audio drivers with kernel version 5.13.0-37. -- 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/1967995 Title: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Confirmed Bug description: In the last 24 hours, my system has started having skipping/stuttering audio when gaming, or watching videos on youtube in chrome, and no audio at all when using VLC to play music files or watching youtube in Firefox. I believe I did a system update in the last week or so but I don't know if that is the cause. Description: Ubuntu 20.04.4 LTS Release: 20.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 00:05:34 2022 InstallationDate: Installed on 2020-08-31 (582 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Headset successful Symptom_Card: G930 - Logitech G930 Headset Symptom_PulseAudioLog: Apr 05 23:40:42 nzxt dbus-daemon[1169]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.40' (uid=125 pid=1765 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Apr 05 23:41:59 nzxt systemd[1655]: pulseaudio.service: Succeeded. Apr 05 23:42:09 nzxt systemd[1655]: pulseaudio.socket: Succeeded. Apr 05 23:49:33 nzxt sudo[8926]: root : TTY=unknown ; PWD=/home/raj ; USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; COMMAND=/usr/bin/xdg-open https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/b77c80a0-b575-11ec-b9ed-40a8f0305cb4? Apr 05 23:54:56 nzxt sudo[11680]: root : TTY=unknown ; PWD=/home/raj ; USER=raj ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; COMMAND=/usr/bin/xdg-open https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+filebug/77aee818-b576-11ec-b78d-40a8f0308420? Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - Logitech G930 Headset, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: B450 I AORUS PRO WIFI-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.:bvrF50:bd11/27/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnB450IAORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450IAORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450 I AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1967995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1430068] Re: Unable to launch gnome-system-monitor
executing > sudo echo 512 > /proc/sys/fs/inotify/max_user_instances does not work because it won't open the file as root but as your current user. This is because "> /proc/sys/fs/inotify/max_user_instances" is not part of what sudo executes. The command is interpreted by your shell as follows: open the file "/proc/sys/fs/inotify/max_user_instances " for writing and execute the programm "sudo" with the following arguments ["echo", "512"] and replace the output(stdout) of the program with said file for starting it. Since your shell is not running as root, it cannot open "/proc/sys/fs/inotify/max_user_instances" for writing. You can either get a shell running as root (with "sudo -i" for example), or do "echo 512 | sudo tee /proc/sys/fs/inotify/max_user_instances". The 2nd way works by passing the output of echo to sudo with in turn will pass it on to tee which then will open the file, which it can do because sudo invoked tee as root. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1430068 Title: Unable to launch gnome-system-monitor Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: When you have too many open files, you can't launch gnome-system- monitor: $ gnome-system-monitor (gnome-system-monitor:23720): glibmm-CRITICAL **: unhandled exception (type Glib::Error) in signal handler: domain: g-io-error-quark code : 0 what : Unable to find default local directory monitor type (gnome-system-monitor:23720): Gtk-CRITICAL **: gtk_window_present_with_time: assertion 'GTK_IS_WINDOW (window)' failed ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gnome-system-monitor 3.8.2.1-2ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 10 09:32:12 2015 InstallationDate: Installed on 2014-06-26 (255 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to utopic on 2014-10-27 (133 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1430068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966580] [NEW] Erroneously huge mouse pointer with snap-packaged firefox in jammy
Public bug reported: I just upgraded to jammy, and the mouse cursor now becomes comically huge whilst it's over a Firefox window. I suspect this might be something to do with this being a HiDPI laptop. I'm also fairly upset about the overcomplicated - and apparently broken - snaps being enforced on me, so I've fixed this by uninstalling snapd, and obtaining Firefox directly from Mozilla instead - which works absolutely fine. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966580 Title: Erroneously huge mouse pointer with snap-packaged firefox in jammy Status in firefox package in Ubuntu: New Bug description: I just upgraded to jammy, and the mouse cursor now becomes comically huge whilst it's over a Firefox window. I suspect this might be something to do with this being a HiDPI laptop. I'm also fairly upset about the overcomplicated - and apparently broken - snaps being enforced on me, so I've fixed this by uninstalling snapd, and obtaining Firefox directly from Mozilla instead - which works absolutely fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964393] Re: gnome-shell crashed with assertion failure in meta_kms_update_set_power_save: !update->plane_assignments
I saw on https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1289561 that you introduced a new environment variable MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING and subscribed to jammy-proposed to try it out. The problem does not occur since the updates! I haven't even set the environment variable. Updated packages were: 2022-03-12 10:59:50 install libadwaita-1-0:amd64 1.1~rc-1 2022-03-12 10:59:50 install gir1.2-adw-1:amd64 1.1~rc-1 2022-03-12 10:59:50 install libopengl0:amd64 1.4.0-1 2022-03-12 10:59:50 install libmutter-10-0:amd64 42~beta-1ubuntu1 2022-03-12 10:59:50 install gir1.2-mutter-10:amd64 42~beta-1ubuntu1 2022-03-12 10:59:52 install xcvt:amd64 0.1.1-3 I also installed lutris since I reproduced the bug, probably uninteresting, but mention it nevertheless due to mesa-utils. 2022-03-11 20:25:52 install fluid-soundfont-gm:all 3.1-5.3 2022-03-11 20:25:53 install fluid-soundfont-gs:all 3.1-5.3 2022-03-11 20:25:53 install libz-mingw-w64:all 1.2.11+dfsg-3 2022-03-11 20:25:53 install libwine-development:amd64 6.0+repack-1ubuntu1 2022-03-11 20:25:58 install python3-lxml:amd64 4.8.0-1 2022-03-11 20:25:58 install python3-setproctitle:amd64 1.2.2-2 2022-03-11 20:25:58 install python3-magic:all 2:0.4.24-2 2022-03-11 20:25:58 install mesa-utils:amd64 8.4.0-1build1 2022-03-11 20:25:58 install lutris:all 0.5.9.1-1 2022-03-11 20:25:58 install python3-soupsieve:all 2.3.1-1 2022-03-11 20:25:58 install python3-bs4:all 4.10.0-2 2022-03-11 20:25:58 install python3-evdev:amd64 1.4.0+dfsg-1build1 2022-03-11 20:25:58 install python3-webencodings:all 0.5.1-4 2022-03-11 20:25:58 install python3-html5lib:all 1.1-3 -- 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/1964393 Title: gnome-shell crashed with assertion failure in meta_kms_update_set_power_save: !update->plane_assignments Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I think the crash occurs when turning the screen blank after idle time. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 9 19:11:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-02-26 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-9.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-9.so.0 g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861262] Re: Add message/rfc822 to thunderbird.desktop
> If I understand correctly, that's not an issue that can be fixed
> by merely updating the desktop file or packaging parameters
> of thunderbird in Ubuntu, it would have to be addressed
> by the upstream project.
I have added a comment to make users (who will face a problem despite a
fix) aware of idiosyncrasy of handling command line options by
thunderbird.
I do not expect that Ubuntu team will ship additional wrapper to deal
with the issue. Those, who desperately need it working, may write a
script that creates a symlink with ".eml" suffix and a desktop file to
open "message/rfc822" files using this script.
I am afraid that security issues might happen because mozilla soft
relies too much on heuristics and does not allow to explicitly express
intention through command line options. It is even impossible to ensure
that nothing following should be considered as options, remaining
arguments are URIs or files ("--" separator for a lot of tools).
Anyway the fix is a step forward. At least files having ".eml" suffix
may be conveniently viewed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1861262
Title:
Add message/rfc822 to thunderbird.desktop
Status in thunderbird package in Ubuntu:
Fix Released
Bug description:
Please add message/rfc822 to thunderbird.desktop:
-MimeType=x-scheme-handler/mailto;application/x-xpinstall;
+MimeType=x-scheme-handler/mailto;application/x-xpinstall;message/rfc822;
It will allow to open *.eml files. I attach an example eml file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1861262/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861262] Re: Add message/rfc822 to thunderbird.desktop
Thank you for updating the .desktop file. The issue is more hairy than it seems at first glance. E.g. https://debbugs.gnu.org/ sends "Content-disposition" header with ".mbox" suffix when a single comment in mbox format is requested (to reply to particular message). Thunderbird believes that a suitable action is to compose a new message with downloaded file as an attachment. There is no command line option to force thunderbird to open a file as namely mail message. The position of developers is that such file must have ".eml" extension otherwise it is not a message. See https://bugzilla.mozilla.org/show_bug.cgi?id=1755454 for details (bug title has been changed to fix a loosely related issue). ** Bug watch added: Mozilla Bugzilla #1755454 https://bugzilla.mozilla.org/show_bug.cgi?id=1755454 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1861262 Title: Add message/rfc822 to thunderbird.desktop Status in thunderbird package in Ubuntu: Fix Released Bug description: Please add message/rfc822 to thunderbird.desktop: -MimeType=x-scheme-handler/mailto;application/x-xpinstall; +MimeType=x-scheme-handler/mailto;application/x-xpinstall;message/rfc822; It will allow to open *.eml files. I attach an example eml file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1861262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960614] Re: Add mid: scheme handler to thunderbird.desktop
** Tags added: desktop-file focal jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1960614 Title: Add mid: scheme handler to thunderbird.desktop Status in thunderbird package in Ubuntu: New Bug description: Since thunderbird-91 version (actually even earlier, but only ESR releases are packaged in Ubuntu) it is possible to open particular messages from command line using Message-ID: thunderbird mid:a...@example.com See e.g. https://bugzilla.mozilla.org/264270 However to open links from other application "mid:" scheme should be advertised in the thunderbird.desktop file: MimeType=x-scheme-handler/mailto;application/x-xpinstall;x-scheme- handler/mid; Please, adjust this field in the desktop file. To check that the change has effect the following command may be used: xdg-open mid:a...@example.com Notice that it is not upstream issue. Thunderbird developers left desktop integration up to maintainers of Linux distributions. Long time ago it was possible to create such links to particular messages using thunderlink extension but migration from XUL to WebExtension add-ons broke it. Support of mid: scheme restores linking of mail messages from other applications. There is a related issue: request to add message/rfc822 MIME type in lp:1861262 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1960614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960614] Re: Add mid: scheme handler to thunderbird.desktop
Workaround: add to the ~/.config/mimeapps.list file [Added Associations] x-scheme-handler/mid=thunderbird.desktop; [Default Applications] x-scheme-handler/mid=thunderbird.desktop; -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1960614 Title: Add mid: scheme handler to thunderbird.desktop Status in thunderbird package in Ubuntu: New Bug description: Since thunderbird-91 version (actually even earlier, but only ESR releases are packaged in Ubuntu) it is possible to open particular messages from command line using Message-ID: thunderbird mid:a...@example.com See e.g. https://bugzilla.mozilla.org/264270 However to open links from other application "mid:" scheme should be advertised in the thunderbird.desktop file: MimeType=x-scheme-handler/mailto;application/x-xpinstall;x-scheme- handler/mid; Please, adjust this field in the desktop file. To check that the change has effect the following command may be used: xdg-open mid:a...@example.com Notice that it is not upstream issue. Thunderbird developers left desktop integration up to maintainers of Linux distributions. Long time ago it was possible to create such links to particular messages using thunderlink extension but migration from XUL to WebExtension add-ons broke it. Support of mid: scheme restores linking of mail messages from other applications. There is a related issue: request to add message/rfc822 MIME type in lp:1861262 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1960614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960614] [NEW] Add mid: scheme handler to thunderbird.desktop
Public bug reported: Since thunderbird-91 version (actually even earlier, but only ESR releases are packaged in Ubuntu) it is possible to open particular messages from command line using Message-ID: thunderbird mid:a...@example.com See e.g. https://bugzilla.mozilla.org/264270 However to open links from other application "mid:" scheme should be advertised in the thunderbird.desktop file: MimeType=x-scheme-handler/mailto;application/x-xpinstall;x-scheme- handler/mid; Please, adjust this field in the desktop file. To check that the change has effect the following command may be used: xdg-open mid:a...@example.com Notice that it is not upstream issue. Thunderbird developers left desktop integration up to maintainers of Linux distributions. Long time ago it was possible to create such links to particular messages using thunderlink extension but migration from XUL to WebExtension add-ons broke it. Support of mid: scheme restores linking of mail messages from other applications. There is a related issue: request to add message/rfc822 MIME type in lp:1861262 ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1960614 Title: Add mid: scheme handler to thunderbird.desktop Status in thunderbird package in Ubuntu: New Bug description: Since thunderbird-91 version (actually even earlier, but only ESR releases are packaged in Ubuntu) it is possible to open particular messages from command line using Message-ID: thunderbird mid:a...@example.com See e.g. https://bugzilla.mozilla.org/264270 However to open links from other application "mid:" scheme should be advertised in the thunderbird.desktop file: MimeType=x-scheme-handler/mailto;application/x-xpinstall;x-scheme- handler/mid; Please, adjust this field in the desktop file. To check that the change has effect the following command may be used: xdg-open mid:a...@example.com Notice that it is not upstream issue. Thunderbird developers left desktop integration up to maintainers of Linux distributions. Long time ago it was possible to create such links to particular messages using thunderlink extension but migration from XUL to WebExtension add-ons broke it. Support of mid: scheme restores linking of mail messages from other applications. There is a related issue: request to add message/rfc822 MIME type in lp:1861262 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1960614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956865] [NEW] [snap] firefox webauthn not working with tomu u2f
Public bug reported:
Similar to
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947746/ using
webauthn with my tomu device did not work out of the box.
The device id does not seem to be registered. Adding
/etc/udev/rules.d/10-tomu.rules with
```
ACTION=="add|change", KERNEL=="hidraw*", SUBSYSTEM=="hidraw",
ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="0e90", TAG+="uaccess"
TAG+="snap_firefox_firefox"
ACTION=="add|change", SUBSYSTEM=="usb", ATTRS{idVendor}=="16d0",
ATTRS{idProduct}=="0e90", TAG+="uaccess"
```
fixed this.
It used to work fine following the instructions from
https://github.com/gl-sergei/u2f-token with the .deb package.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1956865
Title:
[snap] firefox webauthn not working with tomu u2f
Status in firefox package in Ubuntu:
New
Bug description:
Similar to
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1947746/ using
webauthn with my tomu device did not work out of the box.
The device id does not seem to be registered. Adding
/etc/udev/rules.d/10-tomu.rules with
```
ACTION=="add|change", KERNEL=="hidraw*", SUBSYSTEM=="hidraw",
ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="0e90", TAG+="uaccess"
TAG+="snap_firefox_firefox"
ACTION=="add|change", SUBSYSTEM=="usb", ATTRS{idVendor}=="16d0",
ATTRS{idProduct}=="0e90", TAG+="uaccess"
```
fixed this.
It used to work fine following the instructions from
https://github.com/gl-sergei/u2f-token with the .deb package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956865/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
This issue is spamming the log with messages Failed to get Yr.no forecast data: 404 Not Found -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Fix Released Status in libgweather package in Ubuntu: Fix Released Status in gnome-weather source package in Focal: Confirmed Status in libgweather source package in Focal: Confirmed Status in gnome-weather package in Fedora: New Bug description: [Impact] The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.2 == This version switches the yr.no backend to use met.no instead. Please note that this backport is only meant as a compatibility layer. Where at all possible, the newer libgweather 40 should be used as applications cannot fully comply with the met.no ToS otherwise. [Test case] - gnome-weather shows the weather forecast - gnome-shell shows the weather forecast in the calendar menu [Regression potential] - Weather forecast is totally broken now and can't be more broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
It seems, Belgium eID (Comment #36) uses PKCS#11, not native messaging: https://github.com/Fedict/eid-mw/blob/master/plugins_tools/xpi/new-src/manifest.json However the problem is essentially the same: native manifest. Olivier filed a bug in Firefox bugzilla: https://bugzilla.mozilla.org/1734371 "Firefox snap can't load PKCS#11 modules on the host system" I suppose, the title of this bug does not reflect scale of the problem. All browser add-ons that relies on native manifests are affected in Chromium and Firefox. I came across this issue testing an extension in Firefox using Ubuntu-21.10 live image. I am considering whether it is feasible to run a kind of thin proxy server on host that creates a socket inside a directory mounted to snap and runs a binary in response to connection (something like inetd). It requires a stub for native messaging app that connects to the server and pass through requests and responses. Generally it does not differ too much from D-Bus and ideally requires support from Firefox for robust checks if particular add-on is allowed to run a specific app. -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in Mozilla Firefox: New Status in KeePassXC Snap Builds: Unknown Status in chromium-browser package in Ubuntu: Triaged Status in firefox package in Ubuntu: Confirmed Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926305] Re: 20.04 Online Accounts - Google Shared Drives
Thank you for looking into it. I appreciate it may not be an easy process. However corporate environments will not be upgraded until the next LTS. This is quite an important feature for end users and administrators alike. As a workaround we use rclone, but to have it all ready to go in the Desktop environment would really make a big difference. Just a thought for Canonical to consider. But thanks again for your help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926305 Title: 20.04 Online Accounts - Google Shared Drives Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: Just tested out 21.04 and Google Shared Drives works just fine. Any chance the 20.04 LTS gnome-online-accounts could be updated to support it? If that is not possible, any way to build the package from source? Patch available here: https://gitlab.gnome.org/GNOME/gvfs/-/commit/5fa777ddc6dafc71e72f499fd699f508a711924c#11a2f3edde24e314d0420b86f0caf06e5de195a1 Problem is that building requires dependencies newer than package. Tried this with 3-36 as gnome on 20.04 is 3.36 https://gitlab.gnome.org/GNOME/gvfs/-/tree/gnome-3-36 Example error: meson.build:305:2: ERROR: Invalid version of dependency, need 'polkit-gobject-1' ['>= 0.114'] found '0.105' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926305] Re: 20.04 Online Accounts - Google Shared Drives
** Tags removed: bot-comment -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926305 Title: 20.04 Online Accounts - Google Shared Drives Status in gnome-online-accounts package in Ubuntu: New Bug description: Just tested out 21.04 and Google Shared Drives works just fine. Any chance the 20.04 LTS gnome-online-accounts could be updated to support it? If that is not possible, any way to build the package from source? Patch available here: https://gitlab.gnome.org/GNOME/gvfs/-/commit/5fa777ddc6dafc71e72f499fd699f508a711924c#11a2f3edde24e314d0420b86f0caf06e5de195a1 Problem is that building requires dependencies newer than package. Tried this with 3-36 as gnome on 20.04 is 3.36 https://gitlab.gnome.org/GNOME/gvfs/-/tree/gnome-3-36 Example error: meson.build:305:2: ERROR: Invalid version of dependency, need 'polkit-gobject-1' ['>= 0.114'] found '0.105' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926305] Re: 20.04 Online Accounts - Google Shared Drives
** Package changed: ubuntu => gnome-online-accounts (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926305 Title: 20.04 Online Accounts - Google Shared Drives Status in gnome-online-accounts package in Ubuntu: New Bug description: Just tested out 21.04 and Google Shared Drives works just fine. Any chance the 20.04 LTS gnome-online-accounts could be updated to support it? If that is not possible, any way to build the package from source? Patch available here: https://gitlab.gnome.org/GNOME/gvfs/-/commit/5fa777ddc6dafc71e72f499fd699f508a711924c#11a2f3edde24e314d0420b86f0caf06e5de195a1 Problem is that building requires dependencies newer than package. Tried this with 3-36 as gnome on 20.04 is 3.36 https://gitlab.gnome.org/GNOME/gvfs/-/tree/gnome-3-36 Example error: meson.build:305:2: ERROR: Invalid version of dependency, need 'polkit-gobject-1' ['>= 0.114'] found '0.105' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804333] Re: Cheese detects only low-res YUYV stream from camera
bInterfaceClass 1 Audio
bInterfaceSubClass 2 Streaming
bInterfaceProtocol 0
iInterface 0
AudioStreaming Interface Descriptor:
bLength 7
bDescriptorType36
bDescriptorSubtype 1 (AS_GENERAL)
bTerminalLink 3
bDelay 2 frames
wFormatTag 1 PCM
AudioStreaming Interface Descriptor:
bLength11
bDescriptorType36
bDescriptorSubtype 2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 2
bSubframeSize 2
bBitResolution 16
bSamFreqType1 Discrete
tSamFreq[ 0]16000
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 13
Transfer TypeIsochronous
Synch Type Synchronous
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 4
bRefresh0
bSynchAddress 0
AudioControl Endpoint Descriptor:
bLength 7
bDescriptorType37
bDescriptorSubtype 1 (EP_GENERAL)
bmAttributes 0x01
Sampling Frequency
bLockDelayUnits 0 Undefined
wLockDelay 0 Undefined
Device Qualifier (for other device speed):
bLength10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize064
bNumConfigurations 1
Device Status: 0x
(Bus Powered)
=
usbview returns:
IPEVO Ziggi-HD Plus
Manufacturer: IPEVO Inc.
Speed: 480Mb/s (high)
Bus: 7
Address: 2
USB Version: 2.00
Device Class: ef(misc )
Device Subclass: 02
Device Protocol: 01
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 1778
Product Id: 0221
Revision Number: 10.21
Config Number: 1
Number of Interfaces: 4
Attributes: 80
MaxPower Needed: 500mA
Interface Number: 0
Name: uvcvideo
Alternate Number: 0
Class: 0e(video)
Sub Class: 01
Protocol: 00
Number of Endpoints: 1
Endpoint Address: 83
Direction: in
Attribute: 3
Type: Int.
Max Packet Size: 64
Interval: 16ms
Interface Number: 1
Name: uvcvideo
Alternate Number: 0
Class: 0e(video)
Sub Class: 02
Protocol: 00
Number of Endpoints: 0
Interface Number: 1
Name: uvcvideo
Alternate Number: 1
Class: 0e(video)
Sub Class: 02
Protocol: 00
Number of Endpoints: 1
Endpoint Address: 81
Direction: in
Attribute: 5
Type: Isoc
Max Packet Size: 3048
Interval: 125us
Interface Number: 3
Name: snd-usb-audio
Alternate Number: 0
Class: 01(audio)
Sub Class: 01
Protocol: 00
Number of Endpoints: 0
Interface Number: 4
Name: snd-usb-audio
Alternate Number: 0
Class: 01(audio)
Sub Class: 02
Protocol: 00
Number of Endpoints: 0
Interface Number: 4
Name: snd-usb-audio
Alternate Number: 1
Class: 01(audio)
Sub Class: 02
Protocol: 00
Number of Endpoints: 1
Endpoint Address: 82
Direction: in
Attribute: 13
Type: Isoc
Max Packet Size: 512
Interval: 1ms
To manage notifications about this bug go to:
https://bugs.launchpad.net/cheese/+bug/1804333/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804333] Re: Cheese detects only low-res YUYV stream from camera
ol 0
iInterface 0
AudioStreaming Interface Descriptor:
bLength 7
bDescriptorType36
bDescriptorSubtype 1 (AS_GENERAL)
bTerminalLink 3
bDelay 2 frames
wFormatTag 1 PCM
AudioStreaming Interface Descriptor:
bLength11
bDescriptorType36
bDescriptorSubtype 2 (FORMAT_TYPE)
bFormatType 1 (FORMAT_TYPE_I)
bNrChannels 2
bSubframeSize 2
bBitResolution 16
bSamFreqType1 Discrete
tSamFreq[ 0]16000
Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 13
Transfer TypeIsochronous
Synch Type Synchronous
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 4
bRefresh0
bSynchAddress 0
AudioControl Endpoint Descriptor:
bLength 7
bDescriptorType37
bDescriptorSubtype 1 (EP_GENERAL)
bmAttributes 0x01
Sampling Frequency
bLockDelayUnits 0 Undefined
wLockDelay 0 Undefined
Device Qualifier (for other device speed):
bLength10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize064
bNumConfigurations 1
Device Status: 0x
(Bus Powered)
=
usbview returns:
IPEVO Ziggi-HD Plus
Manufacturer: IPEVO Inc.
Speed: 480Mb/s (high)
Bus: 7
Address: 2
USB Version: 2.00
Device Class: ef(misc )
Device Subclass: 02
Device Protocol: 01
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 1778
Product Id: 0221
Revision Number: 10.21
Config Number: 1
Number of Interfaces: 4
Attributes: 80
MaxPower Needed: 500mA
Interface Number: 0
Name: uvcvideo
Alternate Number: 0
Class: 0e(video)
Sub Class: 01
Protocol: 00
Number of Endpoints: 1
Endpoint Address: 83
Direction: in
Attribute: 3
Type: Int.
Max Packet Size: 64
Interval: 16ms
Interface Number: 1
Name: uvcvideo
Alternate Number: 0
Class: 0e(video)
Sub Class: 02
Protocol: 00
Number of Endpoints: 0
Interface Number: 1
Name: uvcvideo
Alternate Number: 1
Class: 0e(video)
Sub Class: 02
Protocol: 00
Number of Endpoints: 1
Endpoint Address: 81
Direction: in
Attribute: 5
Type: Isoc
Max Packet Size: 3048
Interval: 125us
Interface Number: 3
Name: snd-usb-audio
Alternate Number: 0
Class: 01(audio)
Sub Class: 01
Protocol: 00
Number of Endpoints: 0
Interface Number: 4
Name: snd-usb-audio
Alternate Number: 0
Class: 01(audio)
Sub Class: 02
Protocol: 00
Number of Endpoints: 0
Interface Number: 4
Name: snd-usb-audio
Alternate Number: 1
Class: 01(audio)
Sub Class: 02
Protocol: 00
Number of Endpoints: 1
Endpoint Address: 82
Direction: in
Attribute: 13
Type: Isoc
Max Packet Size: 512
Interval: 1ms
To manage notifications about this bug go to:
https://bugs.launchpad.net/cheese/+bug/1804333/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916469] Re: Apps don't use Wayland by default
** Description changed: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) - qdirstat - vlc kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1916469 Title: Apps don't use Wayland by default Status in firefox package in Ubuntu: Confirmed Status in qdirstat package in Ubuntu: New Status in telegram-desktop package in Ubuntu: New Status in vlc package in Ubuntu: New Bug description: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916469] [NEW] Ubuntu universe Wayland problem
Public bug reported: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) qdirstat vlc kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") ** Affects: ubuntu Importance: Undecided Status: New ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Affects: qdirstat (Ubuntu) Importance: Undecided Status: New ** Affects: telegram-desktop (Ubuntu) Importance: Undecided Status: New ** Affects: vlc (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute wayland ** Tags added: wayland ** Tags added: hirsute ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Also affects: telegram-desktop (Ubuntu) Importance: Undecided Status: New ** Also affects: qdirstat (Ubuntu) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: vlc (Ubuntu) Importance: Undecided Status: New ** Description changed: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: - telegram (Wayland support work with snap version) + telegram-desktop (Wayland support work with snap version) qdirstat vlc kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1916469 Title: Ubuntu universe Wayland problem Status in Ubuntu: New Status in firefox package in Ubuntu: New Status in qdirstat package in Ubuntu: New Status in telegram-desktop package in Ubuntu: New Status in vlc package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) qdirstat vlc kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1916469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908823] Re: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled
With me the problem always occurs when in a running connection the channel is changed. This may happen in a busy neighborhood, if in the Router (FritzBox 7530) the automatic channel selection (recommended) is selected. It certainly may happen too if a Repeater is in use. If I switch of and on manually the WIFI, this procedure is treated as a new connection, and the installed password is found automatically with no request, quite as it aught to be. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1908823 Title: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled Status in network-manager-applet package in Ubuntu: Confirmed Bug description: The WiFi connection is aborted an the nm_applet shows the window to enter the WLAN password. The password is pre-filled an you can click the ok button to reconnect. The error occurs sometimes very often (e.g. 10 times/minute) or seldom (only one per day). The problem occurs in Xubuntu 20.04.1 LTS since update to kernel 5.4.0-56 (5.4.0-58 too). With other Xubuntu versions (e.g. 18.04 LTS) or kernel 5.4.0-54 or earlier the problem did not appear. Other OS (eg W10 or div Android) do not see this problem too. Additional asked information: 1) lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 2) apt-cache policy network-manager network-manager: Installiert: 1.22.10-1ubuntu2.2 Installationskandidat: 1.22.10-1ubuntu2.2 Versionstabelle: *** 1.22.10-1ubuntu2.2 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.22.10-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 3) What you expected to happen: WLAN witch in the background with no net abort. 4) What happened instead: Network abort, window-popup with focus to password, interrupted work. All hardware that I know show the problem on laptops with Intel WLAN devices. In /var/log/syslog you can find the error beginning with a "wpa_supplicant[xxx]: l2_packet_send - sendto: No buffer space available" entry. Some lines later you see the entry "asking for a new key". The problem can be reproduced by forcing a WLAN reconnect. This happens, when the router changes the channel or when the wifi signal strength tends to modify the way from the computer to the router (direct connect or via a repeater or changing the repeater e.g. in a Mesh). This behaviour ca be seen in the 2,4GHz and in the 5GHz net. In the sent .apport file you see the switch from repeater (2c:91:..) to router (44:4e:..) at "Dec 29 14:18" as the repeater is forced to reboot to produce the error. For further information you can see the discussion at https://answers.launchpad.net/ubuntu/+question/694566 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager-gnome 1.8.24-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Dec 20 14:19:27 2020 ExecutablePath: /usr/bin/nm-applet IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-12-28 (357 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.146.1 dev wlp3s0 proto dhcp metric 600 linkdown 169.254.0.0/16 dev wlp3s0 scope link metric 1000 linkdown 192.168.146.0/24 dev wlp3s0 proto kernel scope link src 192.168.146.113 metric 600 linkdown ProcEnviron: LANGUAGE=de_DE PATH=(custom, user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager-applet UpgradeStatus: Upgraded to focal on 2020-10-28 (52 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connecting started none enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1908823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901428] Re: PCI/internal sound card not detected
After I added lines below to subl /etc/modprobe.d/alsa-base.conf options snd-hda-intel model=clevo-p950 options snd-hda-intel model=generic options snd-hda-intel dmic_detect=0 options snd-hda-intel model=laptop-dmic options snd-hda-intel probe_mask=1 "Speakers - Built-in Audio" - appeared (Output Device) "Microphone - Built-in Audio" - appeared (Input Device) I can hear sounds now, but the microphone doesn't work. -- 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/1901428 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Hello there! Sounds and the microphone don't work. There is only Dummy Output in the output list. Input list is empty. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.9.1-050901-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1679 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Oct 25 19:28:34 2020 InstallationDate: Installed on 2020-10-22 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2020 dmi.bios.release: 15.24 dmi.bios.vendor: AMI dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 44.41 dmi.modalias: dmi:bvnAMI:bvrF.24:bd03/10/2020:br15.24:efr44.41:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 6ZL48EA#ACB dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-25T19:23:12.181325 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901428] [NEW] PCI/internal sound card not detected
Public bug reported: Hello there! Sounds and the microphone don't work. There is only Dummy Output in the output list. Input list is empty. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.9.1-050901-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1679 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Oct 25 19:28:34 2020 InstallationDate: Installed on 2020-10-22 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2020 dmi.bios.release: 15.24 dmi.bios.vendor: AMI dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 44.41 dmi.modalias: dmi:bvnAMI:bvrF.24:bd03/10/2020:br15.24:efr44.41:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 6ZL48EA#ACB dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-25T19:23:12.181325 ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1901428 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Hello there! Sounds and the microphone don't work. There is only Dummy Output in the output list. Input list is empty. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.9.1-050901-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: max1679 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Oct 25 19:28:34 2020 InstallationDate: Installed on 2020-10-22 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/10/2020 dmi.bios.release: 15.24 dmi.bios.vendor: AMI dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 44.41 dmi.modalias: dmi:bvnAMI:bvrF.24:bd03/10/2020:br15.24:efr44.41:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 6ZL48EA#ACB dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-25T19:23:12.181325 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100% with a USB 2.0 speaker
I can't change the status to confirmed. What's the point in instructions that people are prevented from following? Very frustrating. -- 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/1857335 Title: System volume slider only works between ~90% and 100% with a USB 2.0 speaker Status in pulseaudio package in Ubuntu: Won't Fix Bug description: This is only with my USB 2.0 speaker[1] - with other devices, it works fine and the slider's 0% corresponds to silent and 100% full. With my USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0 Device', it only has an effect between about 90% and 100%. I took a video of the problem and uploaded it here: http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4 [1] https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 10:00:17 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (156 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100% with a USB 2.0 speaker
Still a problem: Ubuntu 20.04.1 LTS -- 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/1857335 Title: System volume slider only works between ~90% and 100% with a USB 2.0 speaker Status in pulseaudio package in Ubuntu: Won't Fix Bug description: This is only with my USB 2.0 speaker[1] - with other devices, it works fine and the slider's 0% corresponds to silent and 100% full. With my USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0 Device', it only has an effect between about 90% and 100%. I took a video of the problem and uploaded it here: http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4 [1] https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 10:00:17 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (156 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
I have a similar problem on my Dell XPS 13 - if I boot the laptop with the headphones (3.5mm) plugged in, then it essentially disabled the 3.5mm headphone jack - nothing I've tried re-enabled it again (eg unplugging/replugging the headphone, all the settings, etc). Only a reboot without the headphones plugged in and plugging them in after logging in, fixes the problem. I don't have this problem on my Lenovo T480s. Perhaps this is a different problem? -- 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/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in gnome-control-center: Unknown Status in PulseAudio: New Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: Invalid Status in pulseaudio source package in Focal: In Progress Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100%.
Not sure why there has been no activity...it certainly shouldn't be 'expired', in my view. ** Changed in: gnome-control-center (Ubuntu) Status: Expired => New -- 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/1857335 Title: System volume slider only works between ~90% and 100%. Status in gnome-control-center package in Ubuntu: New Bug description: This is only with my USB 2.0 speaker[1] - with other devices, it works fine and the slider's 0% corresponds to silent and 100% full. With my USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0 Device', it only has an effect between about 90% and 100%. I took a video of the problem and uploaded it here: http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4 [1] https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 10:00:17 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (156 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1857335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876308] Re: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted
*** This bug is a duplicate of bug 1872476 *** https://bugs.launchpad.net/bugs/1872476 I have read the explication of Sergio Durigan Junior in bug 1872476 and I am convinced now that there is a problem in Samba and not in GIO. So I shall mark this bug as a duplicate of 1872476 now. Thanks, Sergio! ** This bug has been marked a duplicate of bug 1872476 Shared files are shown as folders -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1876308 Title: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted Status in gvfs package in Ubuntu: Incomplete Bug description: If the samba protocol is reduced to SMB-1 (option client max protocol = NT1 in smb.conf), in all samba shares mounted with gio mount, the mounting used by file managers like Nautilus or Thunar, ordinary files are displayed as empty folders and therefore not usable. The problem seems to be new in Ubuntu 20.04 (samba 4.11 and GIO 2.64.2) because it did not exist in Ubuntu 18.04 LTS (samba 4.7 and GIO 2.56.4). In a shell opened by smbclient or in samba-shares mounted via mount.cifs, in Ubuntu 20.02 all files are displayed correctly and usable, even when the protocol is reduced to SMB-1 (client max protocol = NT1 in smb.conf or mount-option vers 1.0). Therefore the problem seems not to be a bug in samba 4.11 but one in the used GIO version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1876308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876308] Re: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted
I tried the update in a virtual machine. It seems to work. The files on the NAS are no more shown as empty folders even if they are mounted via GIO. But it is not the same machine where the bug had occurred before, so I must go on testing to be shure. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1876308 Title: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted Status in gvfs package in Ubuntu: Incomplete Bug description: If the samba protocol is reduced to SMB-1 (option client max protocol = NT1 in smb.conf), in all samba shares mounted with gio mount, the mounting used by file managers like Nautilus or Thunar, ordinary files are displayed as empty folders and therefore not usable. The problem seems to be new in Ubuntu 20.04 (samba 4.11 and GIO 2.64.2) because it did not exist in Ubuntu 18.04 LTS (samba 4.7 and GIO 2.56.4). In a shell opened by smbclient or in samba-shares mounted via mount.cifs, in Ubuntu 20.02 all files are displayed correctly and usable, even when the protocol is reduced to SMB-1 (client max protocol = NT1 in smb.conf or mount-option vers 1.0). Therefore the problem seems not to be a bug in samba 4.11 but one in the used GIO version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1876308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876308] Re: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted
It seems to be the same problem as bug 1872476, but there it seems to affect samba. I found that samba 4.11.7 alone works fine and that the bug only occurs if the samba shares are mounted with gio mount. Therefore I suppose it is a gio bug. Before installing a patched samba version in my system I would like to know what has been done there. A patched samba can be quite a security risk. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1876308 Title: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted Status in gvfs package in Ubuntu: Incomplete Bug description: If the samba protocol is reduced to SMB-1 (option client max protocol = NT1 in smb.conf), in all samba shares mounted with gio mount, the mounting used by file managers like Nautilus or Thunar, ordinary files are displayed as empty folders and therefore not usable. The problem seems to be new in Ubuntu 20.04 (samba 4.11 and GIO 2.64.2) because it did not exist in Ubuntu 18.04 LTS (samba 4.7 and GIO 2.56.4). In a shell opened by smbclient or in samba-shares mounted via mount.cifs, in Ubuntu 20.02 all files are displayed correctly and usable, even when the protocol is reduced to SMB-1 (client max protocol = NT1 in smb.conf or mount-option vers 1.0). Therefore the problem seems not to be a bug in samba 4.11 but one in the used GIO version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1876308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876308] [NEW] in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted
Public bug reported: If the samba protocol is reduced to SMB-1 (option client max protocol = NT1 in smb.conf), in all samba shares mounted with gio mount, the mounting used by file managers like Nautilus or Thunar, ordinary files are displayed as empty folders and therefore not usable. The problem seems to be new in Ubuntu 20.04 (samba 4.11 and GIO 2.64.2) because it did not exist in Ubuntu 18.04 LTS (samba 4.7 and GIO 2.56.4). In a shell opened by smbclient or in samba-shares mounted via mount.cifs, in Ubuntu 20.02 all files are displayed correctly and usable, even when the protocol is reduced to SMB-1 (client max protocol = NT1 in smb.conf or mount-option vers 1.0). Therefore the problem seems not to be a bug in samba 4.11 but one in the used GIO version. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Description changed: If the samba protocol is reduced to SMB-1 (option client max protocol = NT1 in smb.conf), in all samba shares mounted with gio mount, the mounting used by file managers like Nautilus or Thunar, ordinary files are displayed as empty folders and therefore not usable. The problem seems to be new in Ubuntu 20.04 (samba 4.11 and GIO 2.64.2) because it did not exist in Ubuntu 18.04 LTS (samba 4.7 and GIO 2.56.4). - In a shell opened by smbclient or in samba-shares mounted via gvfs- - mount, in Ubuntu 20.02 all files are displayed correctly and usable, - even when the protocol is reduced to SMB-1 (client max protocol = NT1 in - smb.conf or mount-option vers 1.0). Therefore the problem seems not to - be a bug in samba 4.11 but one in the used GIO version. + In a shell opened by smbclient or in samba-shares mounted via + mount.cifs, in Ubuntu 20.02 all files are displayed correctly and + usable, even when the protocol is reduced to SMB-1 (client max protocol + = NT1 in smb.conf or mount-option vers 1.0). Therefore the problem seems + not to be a bug in samba 4.11 but one in the used GIO version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1876308 Title: in GIO 2.64.2 (Ubuntu 20.04) smb file attributes corrupted Status in gvfs package in Ubuntu: New Bug description: If the samba protocol is reduced to SMB-1 (option client max protocol = NT1 in smb.conf), in all samba shares mounted with gio mount, the mounting used by file managers like Nautilus or Thunar, ordinary files are displayed as empty folders and therefore not usable. The problem seems to be new in Ubuntu 20.04 (samba 4.11 and GIO 2.64.2) because it did not exist in Ubuntu 18.04 LTS (samba 4.7 and GIO 2.56.4). In a shell opened by smbclient or in samba-shares mounted via mount.cifs, in Ubuntu 20.02 all files are displayed correctly and usable, even when the protocol is reduced to SMB-1 (client max protocol = NT1 in smb.conf or mount-option vers 1.0). Therefore the problem seems not to be a bug in samba 4.11 but one in the used GIO version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1876308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845795] Re: authentication window got stuck over other windows at top left
*** This bug is a duplicate of bug 1824874 *** https://bugs.launchpad.net/bugs/1824874 ** This bug has been marked a duplicate of bug 1824874 undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed] -- 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/1845795 Title: authentication window got stuck over other windows at top left Status in gnome-shell package in Ubuntu: Confirmed Bug description: The "Authentication required" screen appeared while I was changing software repository settings, but it is stuck there: 1. I can click "cancel" but there is no effect 2. The window is now always on top of any other window, despite the original Software Repository Settings windows has been closed (actually, terminated manually) As you can see in the screenshot, The Firefox windows has focus now as I am typing in the address bar, but still the "dead" authentication window is on top. Using Ubuntu 19.10 on a Yoga Lenovo S940, upgraded from 19.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867977] Re: [amdgpu] Gnome shell crashed when attempt to lock screen / open app drawer with an active window
Here's the result of apport-cli /var/crash/_usr_bin_gnome- shell.1000.crash https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868046 -- 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/1867977 Title: [amdgpu] Gnome shell crashed when attempt to lock screen / open app drawer with an active window Status in gnome-shell package in Ubuntu: Incomplete Bug description: Step to reproduce the bug 1. Have a active/focused window (e.g. terminal) 2. Press the bottom left "Show application" button / try to lock the screen with Win + L shortcut key After that, Gnome shell crashes. I have Ubuntu 19.10 with GNOME Shell 3.34.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867977] Re: [amdgpu] Gnome shell crashed when attempt to lock screen / open app drawer with an active window
If I look into /var/crash/ folder, the closest filename match I found is _usr_bin_gnome-shell.1000.crash Is that the right file to run the command? When I encounter crash, there was no report dialog, but I saw a thick blank border around windows. Does it means that Gnome didn't crash but just restarts itself? -- 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/1867977 Title: [amdgpu] Gnome shell crashed when attempt to lock screen / open app drawer with an active window Status in gnome-shell package in Ubuntu: Incomplete Bug description: Step to reproduce the bug 1. Have a active/focused window (e.g. terminal) 2. Press the bottom left "Show application" button / try to lock the screen with Win + L shortcut key After that, Gnome shell crashes. I have Ubuntu 19.10 with GNOME Shell 3.34.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867977] Re: [amdgpu] Gnome shell crashed when attempt to lock screen / open app drawer with an active window
There was nothing related to the crash I encounter in https://errors.ubuntu.com/user/ID. -- 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/1867977 Title: [amdgpu] Gnome shell crashed when attempt to lock screen / open app drawer with an active window Status in gnome-shell package in Ubuntu: Incomplete Bug description: Step to reproduce the bug 1. Have a active/focused window (e.g. terminal) 2. Press the bottom left "Show application" button / try to lock the screen with Win + L shortcut key After that, Gnome shell crashes. I have Ubuntu 19.10 with GNOME Shell 3.34.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867977] Re: Gnome shell crashed when attempt to lock screen / open app drawer with an active window
The bug may be Ubuntu-specific, as I did not encounter any crash yet in regular gnome session (the gnome-session package) -- 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/1867977 Title: [amdgpu] Gnome shell crashed when attempt to lock screen / open app drawer with an active window Status in gnome-shell package in Ubuntu: Incomplete Bug description: Step to reproduce the bug 1. Have a active/focused window (e.g. terminal) 2. Press the bottom left "Show application" button / try to lock the screen with Win + L shortcut key After that, Gnome shell crashes. I have Ubuntu 19.10 with GNOME Shell 3.34.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867977] Re: Gnome shell crashed when attempt to lock screen / open app drawer with an active window
There was actually something like this in error log generated by journalctl -b0 But I can't find these lines in log generated by ubuntu-bug ``` Mar 19 12:23:08 ubuntu-desktop gnome-shell[26624]: JS WARNING: [resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to method Clutter.Actor.destroy: expected 0, got 1 Mar 19 12:23:08 ubuntu-desktop kernel: gnome-shell[26624]: segfault at 61626786 ip 7feee2b5b0b0 sp 7fff2fd76a28 error 4 in libgobject-2.0.so.0.6200.1[7feee2b3+33000] Mar 19 12:23:08 ubuntu-desktop kernel: Code: fc 03 00 00 77 3c 48 c1 e8 02 48 8d 15 69 32 02 00 48 8b 04 c2 48 81 fe fc 03 00 00 76 31 48 83 e6 fc 45 31 c0 48 85 c0 74 0e 40 16 04 74 05 48 85 f6 75 35 45 31 c0 44 89 c0 c3 66 0f 1f 44 Mar 19 12:23:08 ubuntu-desktop systemd[8684]: gnome-shell-x11.service: Main process exited, code=killed, status=11/SEGV Mar 19 12:23:08 ubuntu-desktop polkitd(authority=local)[1214]: Unregistered Authentication Agent for unix-session:13 (system bus name :1.3180, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_HK.UTF-8) (disconnected from bus) Mar 19 12:23:08 ubuntu-desktop gsd-media-keys[22316]: Couldn't lock screen: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying Mar 19 12:23:08 ubuntu-desktop systemd[8684]: gnome-shell-x11.service: Failed with result 'signal'. Mar 19 12:23:08 ubuntu-desktop systemd[8684]: gnome-shell-x11.service: Service has no hold-off time (RestartSec=0), scheduling restart. Mar 19 12:23:08 ubuntu-desktop systemd[8684]: gnome-shell-x11.service: Scheduled restart job, restart counter is at 3. Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopped target GNOME X11 Session (session: ubuntu). Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopping GNOME X11 Session (session: ubuntu). Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopped target GNOME X11 Session. Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopping GNOME X11 Session. Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopped target GNOME Shell on X11. Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopping GNOME Shell on X11. Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Stopped GNOME Shell on X11. Mar 19 12:23:08 ubuntu-desktop systemd[8684]: Starting GNOME Shell on X11... ``` -- 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/1867977 Title: [amdgpu] Gnome shell crashed when attempt to lock screen / open app drawer with an active window Status in gnome-shell package in Ubuntu: Incomplete Bug description: Step to reproduce the bug 1. Have a active/focused window (e.g. terminal) 2. Press the bottom left "Show application" button / try to lock the screen with Win + L shortcut key After that, Gnome shell crashes. I have Ubuntu 19.10 with GNOME Shell 3.34.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867977] Re: Gnome shell crashed when attempt to lock screen / open app drawer with an active window
I ran the command "ubuntu-bug gnome-shell" right after the bug happens. Here's the log generated: https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1868035 -- 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/1867977 Title: Gnome shell crashed when attempt to lock screen / open app drawer with an active window Status in gnome-shell package in Ubuntu: Incomplete Bug description: Step to reproduce the bug 1. Have a active/focused window (e.g. terminal) 2. Press the bottom left "Show application" button / try to lock the screen with Win + L shortcut key After that, Gnome shell crashes. I have Ubuntu 19.10 with GNOME Shell 3.34.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868035] [NEW] Gnome shell crashed when attempt to lock screen / open app drawer with an active window
*** This bug is a duplicate of bug 1867977 *** https://bugs.launchpad.net/bugs/1867977 Public bug reported: Please refer to https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1867977 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 12:14:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-14 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868035 Title: Gnome shell crashed when attempt to lock screen / open app drawer with an active window Status in gnome-shell package in Ubuntu: New Bug description: Please refer to https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1867977 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 19 12:14:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-14 (4 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867977] Re: Gnome shell crashed when attempt to lock screen / open app drawer with an active window
** Summary changed: - Gnome shell crashed when attempt to lock screen with Win + L with an active window + Gnome shell crashed when attempt to lock screen / open app drawer with an active window ** Description changed: - Whenever I press Win + L with a active/focused window (e.g. terminal), - Gnome shell crashes. + Step to reproduce the bug + + 1. Have a active/focused window (e.g. terminal) + + 2. lock screen with Win + L / press the bottom left "Show application" + button + + + After that, Gnome shell crashes. + + + I have Ubuntu 19.10 with GNOME Shell 3.34.1 ** Description changed: Step to reproduce the bug 1. Have a active/focused window (e.g. terminal) - 2. lock screen with Win + L / press the bottom left "Show application" - button - + 2. Try to lock screen with Win + L / press the bottom left "Show + application" button After that, Gnome shell crashes. - I have Ubuntu 19.10 with GNOME Shell 3.34.1 ** Description changed: Step to reproduce the bug 1. Have a active/focused window (e.g. terminal) - 2. Try to lock screen with Win + L / press the bottom left "Show - application" button + 2. Press the bottom left "Show application" button / try to lock the + screen with Win + L shortcut key After that, Gnome shell crashes. + I have Ubuntu 19.10 with GNOME Shell 3.34.1 -- 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/1867977 Title: Gnome shell crashed when attempt to lock screen / open app drawer with an active window Status in gnome-shell package in Ubuntu: New Bug description: Step to reproduce the bug 1. Have a active/focused window (e.g. terminal) 2. Press the bottom left "Show application" button / try to lock the screen with Win + L shortcut key After that, Gnome shell crashes. I have Ubuntu 19.10 with GNOME Shell 3.34.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867977] Re: Gnome shell crashed when attempt to lock screen with Win + L with a terminal window
Update: turns out that Gnome will if there are output in the terminal doesn't cause the crash As long as I press Win + L with an active/focused window, Gnome would crash. ** Description changed: - Steps to reproduce the bug: - - 1. Open a terminal window - - 2. Type something and press "Enter", e.g. "aaa" (Gnome will only crash - when there are output in the terminal window) - - 3. Press Win + L with terminal as the active window - - - After that, Gnome shell will crash. + Whenever I press Win + L with a active/focused window (e.g. terminal), + Gnome shell crashes. ** Summary changed: - Gnome shell crashed when attempt to lock screen with Win + L with a terminal window + Gnome shell crashed when attempt to lock screen with Win + L with an active window -- 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/1867977 Title: Gnome shell crashed when attempt to lock screen with Win + L with an active window Status in gnome-shell package in Ubuntu: New Bug description: Whenever I press Win + L with a active/focused window (e.g. terminal), Gnome shell crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867977] Re: Gnome shell crashed when attempt to lock screen with Win + L with a terminal window
Here are the error log generated from journalctl -b0 The most recent crash happens at Mar 19 03:30 ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867977/+attachment/5338502/+files/log.txt -- 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/1867977 Title: Gnome shell crashed when attempt to lock screen with Win + L with a terminal window Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce the bug: 1. Open a terminal window 2. Type something and press "Enter", e.g. "aaa" (Gnome will only crash when there are output in the terminal window) 3. Press Win + L with terminal as the active window After that, Gnome shell will crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867977] [NEW] Gnome shell crashed when attempt to lock screen with Win + L with a terminal window
Public bug reported: Steps to reproduce the bug: 1. Open a terminal window 2. Type something and press "Enter", e.g. "aaa" (Gnome will only crash when there are output in the terminal window) 3. Press Win + L with terminal as the active window After that, Gnome shell will crash. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Steps to reproduce the bug" https://bugs.launchpad.net/bugs/1867977/+attachment/5338501/+files/Screenshot%20from%202020-03-19%2003-24-54.png -- 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/1867977 Title: Gnome shell crashed when attempt to lock screen with Win + L with a terminal window Status in gnome-shell package in Ubuntu: New Bug description: Steps to reproduce the bug: 1. Open a terminal window 2. Type something and press "Enter", e.g. "aaa" (Gnome will only crash when there are output in the terminal window) 3. Press Win + L with terminal as the active window After that, Gnome shell will crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857656] Re: [resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to method Clutter.Actor.destroy: expected 0, got 1
I experience this bug too. Gnome crashed while I attempt to login by pressing Win + L Here are the log generated from the command ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857656/+attachment/5338283/+files/journal.txt -- 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/1857656 Title: [resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to method Clutter.Actor.destroy: expected 0, got 1 Status in gnome-shell package in Ubuntu: Incomplete Bug description: 1) Ubuntu 19.10 2) GNOME Shell 3.34.1 3) No error. 4) Error in Logs. 12:23:41 PM gnome-shell: JS WARNING: [resource:///org/gnome/gjs/modules/signals.js 135]: Too many arguments to method Clutter.Actor.destroy: expected 0, got 1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (115 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: wayland-session eoan Uname: Linux 5.3.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100%.
I had to install 'pavucontrol' and it exhibited the same behaviour, as does the 'top panel control' (if I understand that correctly). I couldn't find 'keus' though. -- 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/1857335 Title: System volume slider only works between ~90% and 100%. Status in gnome-control-center package in Ubuntu: Incomplete Bug description: This is only with my USB 2.0 speaker[1] - with other devices, it works fine and the slider's 0% corresponds to silent and 100% full. With my USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0 Device', it only has an effect between about 90% and 100%. I took a video of the problem and uploaded it here: http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4 [1] https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 10:00:17 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (156 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1857335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865862] [NEW] 'sound' settings require changing device and back again
Public bug reported: I have two actual audio devices plugged in: 1. speaker under my monitor plugged into the 3.5mm headphone jack, 2. a set of USB headphones. The 'Sound' settings panel shows three devices: 1. Headphones - built in audio 2. Digital output (s/pdif) - Jambra UC Voice 750 MS 3. Headphones - Jambra UC Voice 750 MS (I don't really know what 2 is - I usually ignore it) Normally, after plugging the headphones in, it has 3 selected, but the 'Test' button still plays through 1. I have to change the 'output device' to 1, then back to 3 in order to make it work on 3. So, this bug is that the control centre does not reflect reality when you launch it. It looks like it is automatically selecting the headphones just plugged in, but it hasn't actually changed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 17:59:30 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (227 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (127 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1865862 Title: 'sound' settings require changing device and back again Status in gnome-control-center package in Ubuntu: New Bug description: I have two actual audio devices plugged in: 1. speaker under my monitor plugged into the 3.5mm headphone jack, 2. a set of USB headphones. The 'Sound' settings panel shows three devices: 1. Headphones - built in audio 2. Digital output (s/pdif) - Jambra UC Voice 750 MS 3. Headphones - Jambra UC Voice 750 MS (I don't really know what 2 is - I usually ignore it) Normally, after plugging the headphones in, it has 3 selected, but the 'Test' button still plays through 1. I have to change the 'output device' to 1, then back to 3 in order to make it work on 3. So, this bug is that the control centre does not reflect reality when you launch it. It looks like it is automatically selecting the headphones just plugged in, but it hasn't actually changed. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 17:59:30 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (227 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (127 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1865862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859098] [NEW] Exiting Writer's Print Preview mode is slow in long documents
Public bug reported: (Cross-posting from https://bugs.documentfoundation.org/show_bug.cgi?id=129900 as problem not reproducible on Windows.) Compared to LibreOffice 5, exiting Print Preview in long documents on LO6 is extremely slow. With a 1,500 page document, for example, exiting Print Preview is instant in LO5, but takes 5-6 seconds (!) in LO6. To reproduce: 1. In LibreOffice 6 Writer, fill a document with text so that it comprises at least a few hundred pages. 2. Enter Print Preview (e.g. File -> Print Preview). 3. Observe it takes a second or two (based on document length) to display the Print Preview screen. This is similar to LibreOffice 5. 4. Press Escape to exit Print Preview mode. 5. Observe a significant delay (approx. 5-6 seconds for a 1,500 page document) with CPU usage spiking before returning to normal view. There is no such delay in LibreOffice 5.3.0.3 Writer. I tend to flip back and forth between Normal View and Print Preview when editing a document, and this new delay makes this very awkward. Ubuntu 19.10 Version: 6.3.4.2 Build ID: 1:6.3.4-0ubuntu0.19.10.1 CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice-writer 1:6.3.4-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 10:53:20 2020 InstallationDate: Installed on 2013-04-11 (2464 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to eoan on 2019-11-07 (63 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2015-03-26T08:56:12.843910 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1859098 Title: Exiting Writer's Print Preview mode is slow in long documents Status in libreoffice package in Ubuntu: New Bug description: (Cross-posting from https://bugs.documentfoundation.org/show_bug.cgi?id=129900 as problem not reproducible on Windows.) Compared to LibreOffice 5, exiting Print Preview in long documents on LO6 is extremely slow. With a 1,500 page document, for example, exiting Print Preview is instant in LO5, but takes 5-6 seconds (!) in LO6. To reproduce: 1. In LibreOffice 6 Writer, fill a document with text so that it comprises at least a few hundred pages. 2. Enter Print Preview (e.g. File -> Print Preview). 3. Observe it takes a second or two (based on document length) to display the Print Preview screen. This is similar to LibreOffice 5. 4. Press Escape to exit Print Preview mode. 5. Observe a significant delay (approx. 5-6 seconds for a 1,500 page document) with CPU usage spiking before returning to normal view. There is no such delay in LibreOffice 5.3.0.3 Writer. I tend to flip back and forth between Normal View and Print Preview when editing a document, and this new delay makes this very awkward. Ubuntu 19.10 Version: 6.3.4.2 Build ID: 1:6.3.4-0ubuntu0.19.10.1 CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice-writer 1:6.3.4-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 10:53:20 2020 InstallationDate: Installed on 2013-04-11 (2464 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to eoan on 2019-11-07 (63 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2015-03-26T08:56:12.843910 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1859098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857335] Re: System volume slider only works between ~90% and 100%.
FWIW, the speaker works fine on a Huawei Mate 30 Pro/Android 10. -- 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/1857335 Title: System volume slider only works between ~90% and 100%. Status in gnome-control-center package in Ubuntu: New Bug description: This is only with my USB 2.0 speaker[1] - with other devices, it works fine and the slider's 0% corresponds to silent and 100% full. With my USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0 Device', it only has an effect between about 90% and 100%. I took a video of the problem and uploaded it here: http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4 [1] https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 10:00:17 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (156 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1857335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857335] [NEW] System volume slider only works between ~90% and 100%.
Public bug reported: This is only with my USB 2.0 speaker[1] - with other devices, it works fine and the slider's 0% corresponds to silent and 100% full. With my USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0 Device', it only has an effect between about 90% and 100%. I took a video of the problem and uploaded it here: http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4 [1] https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 10:00:17 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (156 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1857335 Title: System volume slider only works between ~90% and 100%. Status in gnome-control-center package in Ubuntu: New Bug description: This is only with my USB 2.0 speaker[1] - with other devices, it works fine and the slider's 0% corresponds to silent and 100% full. With my USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0 Device', it only has an effect between about 90% and 100%. I took a video of the problem and uploaded it here: http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4 [1] https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 10:00:17 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (156 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1857335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 78435]
What was the rational for changing the file name in the first place? What is wrong with presenting a overwrite warning/question to the user for equal file names? Silently changing file names is not very nice in my opinion. At least there should be an option to disable this mechanism. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/78435 Title: temporary filenames should handle multiple extensions (.tar.gz) Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: mozilla-thunderbird When opening a file named foo.bar, the file is downloaded to /tmp. If the file is opened again in a short time, the file is again downloaded to /tmp but renamed foo-1.bar. If the file has a double extension (for example, opening a foo.tar.gz file with ark), the file is renamed as foo.tar-1.gz and thus ark is not able to open it properly. It should be foo-1.tar.gz instead. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/78435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775302] Re: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR ***
I think the more files you already have in the folder the higher the chance that another new file will trigger the bug. The more time it needs to sort the list the more time for the race condition to occur, and each new file is another shot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1775302 Title: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR *** Status in eog package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding eog. This problem was most recently seen with package version 3.26.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6214176f5dcd8b5e97adde63323ccb09827d853c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1775302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775302] Re: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR ***
No plugins as far as I know. Also no UI elements. It doesn't look like a segfault, but rather a failed assert() in glibc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1775302 Title: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR *** Status in eog package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding eog. This problem was most recently seen with package version 3.26.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6214176f5dcd8b5e97adde63323ccb09827d853c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1775302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775302] Re: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR ***
https://errors.ubuntu.com/oops/b9742d32-072f-11ea-aff5-fa163e983629 https://errors.ubuntu.com/oops/4c711916-072a-11ea-b6b3-fa163e102db1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1775302 Title: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR *** Status in eog package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding eog. This problem was most recently seen with package version 3.26.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6214176f5dcd8b5e97adde63323ccb09827d853c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1775302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775302] Re: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR ***
I'm running Ubuntu 19.04, and I did send the bug report. It is 100% reproducible, I have a folder which an application is writing about ~100 new PNG images per second into (ie. new image files added to the folder), up to about 100,000 images. If I try to open one of those images _during_ this process the bug is triggered 100%. If I open an image after the process is finished it works just fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1775302 Title: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR *** Status in eog package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding eog. This problem was most recently seen with package version 3.26.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6214176f5dcd8b5e97adde63323ccb09827d853c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1775302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775302] Re: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR ***
This bug is triggered when many new files are added to the folder in which an image is opened. (eog:6555): GLib-WARNING **: 23:38:42.199: Accessing a sequence while it is being sorted or searched is not allowed (eog:6555): GLib-WARNING **: 23:38:42.200: Accessing a sequence while it is being sorted or searched is not allowed corrupted size vs. prev_size Aborted (core dumped) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1775302 Title: /usr/bin/eog:*** Error in `eog': corrupted size vs. prev_size: ADDR *** Status in eog package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding eog. This problem was most recently seen with package version 3.26.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6214176f5dcd8b5e97adde63323ccb09827d853c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1775302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)
I have a Lenovo E585 w/ a Ryzen 5 2500U. I'm having the same issues, horizontal screen tears, parts of a window showing up where they shouldn't. It's mostly on Firefox, but happens when I view PDFs as well. I'm getting different problems on Steam, there it's small colored squares that flash on and off. I'm also having a problem where every time I wake from sleep I get a black screen, not sure if related but maybe it is? I'm happy to upload lspci and dmesg info if that would help! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1848741 Title: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have graphics artefacts: screan tearing, pieces of the previous window appear in the newly opened window. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-08 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844354] Re: Starting indicator-multiload (with peculiar config) crashes gnome-shell
Daniel, yes, this is the same crash as in bug 1787512. It's not a duplicate IMO, since I'd researched the exact repro steps. Any developer can trigger the crash now, by following the repro steps. That's why I didn't use ubuntu-bug either; just follow the repro steps and trigger the crash yourself, rather than blankly staring at my recording of it. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844354 Title: Starting indicator-multiload (with peculiar config) crashes gnome- shell Status in gnome-shell package in Ubuntu: New Bug description: ## Steps to reproduce ## 1. On bionic, apt install -y indicator-multiload dconf-editor 2. dconf load /de/mh21/indicator-multiload/ < crasher.dconf-dump 3. Run indicator-multiload ## Actual result ## Whole desktop crashes. gnome-shell dies with SIGABRT, logging this assertion failure: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512 ## Expected result ## An applet appears, showing CPU/RAM load graphs. If not that -- an error is reported. If not that -- gnome-shell continues to work, rather than crashing and destroying everything unsaved I've been working on. The desktop should not crash because of one shitty program. Especially so if that program has put itself into ~/.config/autostart -- effectively rendering the OS dead to a simpleton user. lsb_release -d: Ubuntu 18.04.3 LTS gnome-shell version: 3.28.4-0ubuntu18.04.1 indicator-multiload version: 0.4-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844354] Re: Starting indicator-multiload (with peculiar config) crashes gnome-shell
Please NOTE: the report is against gnome-shell, NOT indicator-multiload!
It's not so important to fix the indicator app. Rather, gnome-shell
needs to become sturdier.
There's a change to be made to gnome-shell so that it perseveres
assertion failures and keeps running.
Lurking around, I've seen plentiful variations of gnome-shell assertion-
crashing posted, with varying backtraces. I've also personally
witnessed, on multiple occasions, "Ubuntu dying" as they say, with very
similar symptoms and the exact same workaround, mv ~/.config{,.bugz}.
Mind that, in each of that crash story, reported and not, we've caused
suffering and disappointment in hundreds of people. The data is there at
errors.ubuntu.com waiting for you to check out.
Now that I've spent a day unearthing a concrete working reproducer, can
I expect a *PROPER FIX* for this disaster, not just a measly patch-over
as dozens of bugs before?
--
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/1844354
Title:
Starting indicator-multiload (with peculiar config) crashes gnome-
shell
Status in gnome-shell package in Ubuntu:
New
Bug description:
## Steps to reproduce ##
1. On bionic, apt install -y indicator-multiload dconf-editor
2. dconf load /de/mh21/indicator-multiload/ < crasher.dconf-dump
3. Run indicator-multiload
## Actual result ##
Whole desktop crashes.
gnome-shell dies with SIGABRT, logging this assertion failure:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512
## Expected result ##
An applet appears, showing CPU/RAM load graphs.
If not that -- an error is reported.
If not that -- gnome-shell continues to work, rather than crashing and
destroying everything unsaved I've been working on.
The desktop should not crash because of one shitty program. Especially
so if that program has put itself into ~/.config/autostart --
effectively rendering the OS dead to a simpleton user.
lsb_release -d: Ubuntu 18.04.3 LTS
gnome-shell version: 3.28.4-0ubuntu18.04.1
indicator-multiload version: 0.4-0ubuntu5
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish()
Hey Daniel! I hope you'll take a look here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354 TL;DR: I'd distilled the issue and worked out a gnome-shell crasher to reproduce this in clean VM. Hope that helps. -- 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/1787512 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed: (icon_info_get_pixbuf_ready (icon_info))"] Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.2-0ubuntu0.18.04.1, the problem page at https://errors.ubuntu.com/problem/3fab26f2eb2d02e167c5fa790b9895190d812bbe contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844354] Re: Starting indicator-multiload crashes gnome-shell
Repro steps have been verified in clean VM and now refined to include the crasher. ** Description changed: ## Steps to reproduce ## - 1. On bionic, apt install -y indicator-multiload - 2. Run indicator-multiload + 1. On bionic, apt install -y indicator-multiload dconf-editor + 2. dconf load /de/mh21/indicator-multiload/ < crasher.dconf-dump + 3. Run indicator-multiload lsb_release -d: Ubuntu 18.04.3 LTS gnome-shell version: 3.28.4-0ubuntu18.04.1 indicator-multiload version: 0.4-0ubuntu5 - ## Actual result ## Whole desktop crashes. gnome-shell dies with SIGABRT, logging this assertion failure: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512 - ## Expected result ## An applet appears, showing CPU/RAM load graphs. If not that -- an error is reported. If not that -- gnome-shell continues to work, rather than crashing and destroying everything unsaved I've been working on. The desktop should not crash because of one shitty program. Especially - so if that program puts itself into ~/.config/autostart -- effectively - rendering the OS dead to a simpleton user. + so if that program has put itself into ~/.config/autostart -- + effectively rendering the OS dead to a simpleton user. ** Attachment added: "A presumably invalid, or corrupt, dconf fragment for indicator-multiload" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354/+attachment/5289194/+files/crasher.dconf-dump ** Summary changed: - Starting indicator-multiload crashes gnome-shell + Starting indicator-multiload (with peculiar config) crashes gnome-shell ** Description changed: ## Steps to reproduce ## 1. On bionic, apt install -y indicator-multiload dconf-editor 2. dconf load /de/mh21/indicator-multiload/ < crasher.dconf-dump 3. Run indicator-multiload - - lsb_release -d: Ubuntu 18.04.3 LTS - gnome-shell version: 3.28.4-0ubuntu18.04.1 - indicator-multiload version: 0.4-0ubuntu5 ## Actual result ## Whole desktop crashes. gnome-shell dies with SIGABRT, logging this assertion failure: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512 ## Expected result ## An applet appears, showing CPU/RAM load graphs. If not that -- an error is reported. If not that -- gnome-shell continues to work, rather than crashing and destroying everything unsaved I've been working on. The desktop should not crash because of one shitty program. Especially so if that program has put itself into ~/.config/autostart -- effectively rendering the OS dead to a simpleton user. + + + lsb_release -d: Ubuntu 18.04.3 LTS + gnome-shell version: 3.28.4-0ubuntu18.04.1 + indicator-multiload version: 0.4-0ubuntu5 -- 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/1844354 Title: Starting indicator-multiload (with peculiar config) crashes gnome- shell Status in gnome-shell package in Ubuntu: New Bug description: ## Steps to reproduce ## 1. On bionic, apt install -y indicator-multiload dconf-editor 2. dconf load /de/mh21/indicator-multiload/ < crasher.dconf-dump 3. Run indicator-multiload ## Actual result ## Whole desktop crashes. gnome-shell dies with SIGABRT, logging this assertion failure: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512 ## Expected result ## An applet appears, showing CPU/RAM load graphs. If not that -- an error is reported. If not that -- gnome-shell continues to work, rather than crashing and destroying everything unsaved I've been working on. The desktop should not crash because of one shitty program. Especially so if that program has put itself into ~/.config/autostart -- effectively rendering the OS dead to a simpleton user. lsb_release -d: Ubuntu 18.04.3 LTS gnome-shell version: 3.28.4-0ubuntu18.04.1 indicator-multiload version: 0.4-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844354] Re: Starting indicator-multiload crashes gnome-shell
The repro steps aren't as exact as I'd like, since I found this on a live machine with long history of rough usage (including wiping /var by accident, and restoring from there), so the steps are a bit difficult to isolate. I'll try refining the steps as needed in a VM. -- 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/1844354 Title: Starting indicator-multiload crashes gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: ## Steps to reproduce ## 1. On bionic, apt install -y indicator-multiload 2. Run indicator-multiload lsb_release -d: Ubuntu 18.04.3 LTS gnome-shell version: 3.28.4-0ubuntu18.04.1 indicator-multiload version: 0.4-0ubuntu5 ## Actual result ## Whole desktop crashes. gnome-shell dies with SIGABRT, logging this assertion failure: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512 ## Expected result ## An applet appears, showing CPU/RAM load graphs. If not that -- an error is reported. If not that -- gnome-shell continues to work, rather than crashing and destroying everything unsaved I've been working on. The desktop should not crash because of one shitty program. Especially so if that program puts itself into ~/.config/autostart -- effectively rendering the OS dead to a simpleton user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844354] [NEW] Starting indicator-multiload crashes gnome-shell
Public bug reported: ## Steps to reproduce ## 1. On bionic, apt install -y indicator-multiload 2. Run indicator-multiload lsb_release -d: Ubuntu 18.04.3 LTS gnome-shell version: 3.28.4-0ubuntu18.04.1 indicator-multiload version: 0.4-0ubuntu5 ## Actual result ## Whole desktop crashes. gnome-shell dies with SIGABRT, logging this assertion failure: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512 ## Expected result ## An applet appears, showing CPU/RAM load graphs. If not that -- an error is reported. If not that -- gnome-shell continues to work, rather than crashing and destroying everything unsaved I've been working on. The desktop should not crash because of one shitty program. Especially so if that program puts itself into ~/.config/autostart -- effectively rendering the OS dead to a simpleton user. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1844354 Title: Starting indicator-multiload crashes gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: ## Steps to reproduce ## 1. On bionic, apt install -y indicator-multiload 2. Run indicator-multiload lsb_release -d: Ubuntu 18.04.3 LTS gnome-shell version: 3.28.4-0ubuntu18.04.1 indicator-multiload version: 0.4-0ubuntu5 ## Actual result ## Whole desktop crashes. gnome-shell dies with SIGABRT, logging this assertion failure: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512 ## Expected result ## An applet appears, showing CPU/RAM load graphs. If not that -- an error is reported. If not that -- gnome-shell continues to work, rather than crashing and destroying everything unsaved I've been working on. The desktop should not crash because of one shitty program. Especially so if that program puts itself into ~/.config/autostart -- effectively rendering the OS dead to a simpleton user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844354] Re: Starting indicator-multiload crashes gnome-shell
Also, I'd like to see feedback from @vanvugt (as he has triaged a lot of gnome-shell crash reports), and Michael Hofmann as the original maintainer of indicator-multiload. -- 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/1844354 Title: Starting indicator-multiload crashes gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: ## Steps to reproduce ## 1. On bionic, apt install -y indicator-multiload 2. Run indicator-multiload lsb_release -d: Ubuntu 18.04.3 LTS gnome-shell version: 3.28.4-0ubuntu18.04.1 indicator-multiload version: 0.4-0ubuntu5 ## Actual result ## Whole desktop crashes. gnome-shell dies with SIGABRT, logging this assertion failure: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512 ## Expected result ## An applet appears, showing CPU/RAM load graphs. If not that -- an error is reported. If not that -- gnome-shell continues to work, rather than crashing and destroying everything unsaved I've been working on. The desktop should not crash because of one shitty program. Especially so if that program puts itself into ~/.config/autostart -- effectively rendering the OS dead to a simpleton user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish()
Found it. In my case, this crash was triggered by .config/autostart/indicator- multiload.desktop If I rm the autostart file, gnome-shell logs in and works fine. If run directly, indicator-multiload crashes gnome-shell. Package version 0.4-0ubuntu5. -- 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/1787512 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed: (icon_info_get_pixbuf_ready (icon_info))"] Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.2-0ubuntu0.18.04.1, the problem page at https://errors.ubuntu.com/problem/3fab26f2eb2d02e167c5fa790b9895190d812bbe contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish()
Nope, it didn't work. Neither did this, the same failed assertion crash persisted: gsettings set org.gnome.desktop.search-providers disabled "['org.gnome.Nautilus.desktop']" -- 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/1787512 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed: (icon_info_get_pixbuf_ready (icon_info))"] Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.2-0ubuntu0.18.04.1, the problem page at https://errors.ubuntu.com/problem/3fab26f2eb2d02e167c5fa790b9895190d812bbe contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish()
@vanvugt hi! Nice triage, appreciated. Confirming I now have had this on 18.04, gnome-shell version 3.28.4-0ubuntu18.04.1. *Removing or renaming $HOME/.config*, as a universal workaround, also works in this case. I'm going to test if disabling search-providers (as mentioned in #1722599) helps, with the (I suspect, corrupted) $HOME/.config in place intact. Since gnome-shell crashes and any GUI isn't accessible, here's the gsettings command doing the equivalent: gsettings set org.gnome.desktop.search-providers disable-external true -- 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/1787512 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() ["assertion failed: (icon_info_get_pixbuf_ready (icon_info))"] Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.28.2-0ubuntu0.18.04.1, the problem page at https://errors.ubuntu.com/problem/3fab26f2eb2d02e167c5fa790b9895190d812bbe contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
https://gitlab.gnome.org/GNOME/nautilus/issues/1157 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1157 https://gitlab.gnome.org/GNOME/nautilus/issues/1157 -- 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/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Won't Fix Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
Related bug in official nautilus repo https://gitlab.gnome.org/GNOME/nautilus/issues/244 ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #244 https://gitlab.gnome.org/GNOME/nautilus/issues/244 -- 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/181 Title: Restore interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Won't Fix Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1505774] Re: Feature request: Display each network adapter in network history graph
I agree with this. I almost always use a VPN, and it seems to me like 'Network History' is adding together the bandwidth for all interfaces. The effect of this is that it shows double the bandwidth when I am connected to VPN compared to when I am not connected. I presume it is adding both wlp58s0 and tun0 - or something to that effect. I am using expressvpn, and speedtest.net to measure. I would expect 'network history' to use the device associated with tun0. If anything, I would expect it to show /less/ bandwidth when connected to VPN (due to the overhead), but certainly not more. Ideally, I'd like options - to select the interface, take the default route interface, or show them all, like in this request. At least, it should be clear about which interface is being measured, or however else it is being calculated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1505774 Title: Feature request: Display each network adapter in network history graph Status in gnome-system-monitor package in Ubuntu: New Bug description: The system monitor nicely shows CPU usage for each core and graphs a line for each one. It would be nice if the network history graph could do the same for each network adapter (excluding loopback). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1505774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832106] [NEW] Some packages could not be installed
Public bug reported: sudo apt-get install xserver-xorg-video-intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 8 12:10:54 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc] InstallationDate: Installed on 2019-06-06 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 002: ID 0bda:5686 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E7470 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=4c3f6446-77d8-4152-8446-dbda7f591ea6 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.6 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.6:bd05/20/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1832106 Title: Some packages could not be installed Status in xorg package in Ubuntu: New Bug description: sudo apt-get install xserver-xorg-video-intel ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jun 8 12:10:54 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc] InstallationDate: Installed on 2019-06-06 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. Bus 001 Device 002: ID 0bda:5686 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E7470 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=4c3f6446-77d8-4152-8446-dbda7f591ea6 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.6 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.6:bd05/20/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another
Using lightdm and xfce this problem exists as well. Additionally with this setup there are no monitors.xml in ~/.config. Although the login screen is on the main monitor, which is awkward. There are also other slightly funny situations, as when closing the lid on laptop then connecting laptop to additional monitors, the monitor setup is sometimes(?) restored. That is most likely due to that laptop was earlier connected to these monitors, then disconnected and then later connected again. Still really annoying bug when using laptop on- and off-site. -- 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/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1547024] Re: [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise Problem
Same problem on ux501vw, Ubuntu 18.10 -- 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/1547024 Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Static Noise Problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm not sure what's happening, my sound works great, there's just a static noise in the background that can get very annoying. Let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 4.5.0-040500rc4-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zkanda 1519 F pulseaudio CurrentDesktop: MATE Date: Thu Feb 18 21:34:15 2016 InstallationDate: Installed on 2016-02-16 (2 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160216) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [N501VW, Realtek ALC668, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.204:bd11/12/2015:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N501VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1547024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic
*** This bug is a duplicate of bug 1576559 *** https://bugs.launchpad.net/bugs/1576559 Also having this issue, the "headset" profile is not missing Name: OrigAudio_HP Alias: OrigAudio_HP Class: 0x00260404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) RSSI: -60 -- 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/1768625 Title: Bluetooth headset HSP/HFP mode not working in Bionic Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is a previous bug with almost the same title, but for Xenial (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I have had this issue in Artful, and when commented on the old bug, I was asked to raise a new one instead. I waited to see if Bionic fixed it for me, but it does not seem to work still. So! Steps to reproduce: 1. enable bluetooth on computer and switch on the headset. 2. pair and connect the headset 3. go to settings to switch headset to HSP/HFP mode to enable mic 4. save and close window. Expected behaviour: 1. mic should be enabled and headset should be usable to attend calls on laptop. Behaviour in error: 1. Headset profile switches back to A2DP and mic is not enabled. I am using a generic bluetooth headset on a fresh updated Kubuntu 18.04 bionic with plasma DE. Software versions: Kernel: 4.15.0-20-generic Bluez version: 5.48-0ubuntu3 pulseaudio: 1:11.1-1ubuntu7 pulseaudio-module-bluetooth: 1:11.1-1ubuntu7 Additional information: Running "pacmd list-cards" says that HSF/HFP is 'not available' on the headset: Output from Headset section: profiles: a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, available: unknown) headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, available: no) off: Off (priority 0, available: yes) active profile: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1188569] Re: Some keyboard shortcuts randomly stop working
unity-settings-daemon 15.04.1+19.04.20190209-0ubuntu2 built for Ubuntu-18.04 bionic works for me. Please, backport changes to the LTS version. I have faced a problem with non-working keyboard language switcher in unity desktop. It works till next screen lock. An irritating workaround is to set shortcut again in system settings → Keyboard → Shortcuts → Typing → Switch to next source. The trivial patch I have had to apply is removing gnome-settings-daemon- common dependency. --- unity-settings-daemon-15.04.1+19.04.20190209.orig/debian/control 2019-03-13 04:44:44.0 + +++ unity-settings-daemon-15.04.1+19.04.20190209/debian/control 2019-03-13 03:56:15.778916801 + @@ -58,7 +58,6 @@ accountsservice (>= 0.6.34), gsettings-desktop-schemas (>= 3.15.4), nautilus-data (>= 2.91.3-1), - gnome-settings-daemon-common (>= 3.16), gsettings-ubuntu-schemas (>= 0.0.7+17.10.20170922), Recommends: ibus (>= 1.5.0), pulseaudio, -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1188569 Title: Some keyboard shortcuts randomly stop working Status in GNOME Shell: New Status in Unity: Confirmed Status in unity package in Ubuntu: Invalid Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: Hi, Certain shortcuts randomly stops working in my computer. They are Super+s (workspace switcher), Super+Up (switch to workspace above) and Super+Down (switch to workspace below). Other shortcuts work fine. A few notes that might help: 1- Reassigning shortcuts make them work again except for Super+s. 2- Rebooting make shortcuts work. 3- I have been using these shortcuts with many previous ubuntu versions and my preferences are old. 4- I am not sure of certain steps that produces the problem. The shortcuts sometimes stop working but once they stop, they do not work unless I reassign them or reboot. I am using Ubuntu 13.04. Thank you ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,grid,mousepoll,place,wall,snap,resize,vpswitch,session,animation,gnomecompat,imgpng,commands,move,workarounds,fade,unitymtgrabhandles,expo,scale,ezoom,unityshell] Date: Fri Jun 7 13:40:06 2013 InstallationDate: Installed on 2013-05-27 (11 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1188569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417470] Re: PDF+Latex export creates multipage pdf, pages missing
Thank you for the hint. However, before a fix can be developed, we need a *minimal* example (maybe two rectangles and a text, or however simple you can make it) for debugging the code. Please understand that is (almost) impossible to debug this with a complicated file as the above example, so there will (most probably) not be a fix before someome has found a minimal example. Even if you paid someone to do develop a fix, then this person would look for such an example as the first step of fixing the bug. As we are all volunteers, developers' time is very limited, so your help with creating a minimal example is needed before a fix will be developed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1417470 Title: PDF+Latex export creates multipage pdf, pages missing Status in Inkscape: Triaged Status in inkscape package in Ubuntu: Fix Released Status in inkscape package in Debian: Fix Released Bug description: In 0.91 the z-order information in svg is used to create multipage PDF+LaTeX documents as per bug 771957. However, for the SVGs I have been converting to PDF+LaTeX in this way, the TeX-file instructs to load more pages than the PDF has, for example the PDF has only three pages and the TeX file also includes page=4. This basically breaks the PDF+LaTeX export for me and I have to use EPS+LaTeX + epstopdf package. The bug occurs on OpenSuse 13.1 and Windows 8.1. Attached a zip file with two svg files and their broken PDF+LaTeX counterparts. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1417470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417470] Re: PDF+Latex export creates multipage pdf, pages missing
What we need to solve the bug is a minimized version of the problem. Can anyone try to remove as much as possible from the example file without removing the error? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1417470 Title: PDF+Latex export creates multipage pdf, pages missing Status in Inkscape: Triaged Status in inkscape package in Ubuntu: Fix Released Status in inkscape package in Debian: Fix Released Bug description: In 0.91 the z-order information in svg is used to create multipage PDF+LaTeX documents as per bug 771957. However, for the SVGs I have been converting to PDF+LaTeX in this way, the TeX-file instructs to load more pages than the PDF has, for example the PDF has only three pages and the TeX file also includes page=4. This basically breaks the PDF+LaTeX export for me and I have to use EPS+LaTeX + epstopdf package. The bug occurs on OpenSuse 13.1 and Windows 8.1. Attached a zip file with two svg files and their broken PDF+LaTeX counterparts. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1417470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1417470] Re: PDF+Latex export creates multipage pdf, pages missing
Confirmed for 1.0alpha (66f58bd637, 2019-02-10) and current 0.92.x branch (4f452baadd, 2019-02-17, custom): "expCross.svg" from Chris creates a PDF with 7 pages, but a TeX file which includes "page=8". ** Changed in: inkscape Status: Fix Released => Triaged ** Changed in: inkscape Milestone: 0.92.2 => 1.0alpha ** Changed in: inkscape Assignee: Max Gaukler (mgmax) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1417470 Title: PDF+Latex export creates multipage pdf, pages missing Status in Inkscape: Triaged Status in inkscape package in Ubuntu: Fix Released Status in inkscape package in Debian: Fix Released Bug description: In 0.91 the z-order information in svg is used to create multipage PDF+LaTeX documents as per bug 771957. However, for the SVGs I have been converting to PDF+LaTeX in this way, the TeX-file instructs to load more pages than the PDF has, for example the PDF has only three pages and the TeX file also includes page=4. This basically breaks the PDF+LaTeX export for me and I have to use EPS+LaTeX + epstopdf package. The bug occurs on OpenSuse 13.1 and Windows 8.1. Attached a zip file with two svg files and their broken PDF+LaTeX counterparts. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1417470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803021] Re: No tutorials
Backported to 0.92.x (will be released as 0.92.5). https://gitlab.com/inkscape/inkscape/merge_requests/533/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1803021 Title: No tutorials Status in Inkscape: Fix Committed Status in inkscape package in Ubuntu: Fix Committed Bug description: When selecting `Help -> Tutorials` the error message is shown and no tutorial is loaded. Failed to load the requested file /usr/share/inkscape/tutorials /tutorial-basic.svg ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: inkscape 0.92.3-4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: i3 Date: Tue Nov 13 05:18:54 2018 InstallationDate: Installed on 2018-11-01 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: inkscape UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1803021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803021] Re: No tutorials
** Changed in: inkscape Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1803021 Title: No tutorials Status in Inkscape: Fix Committed Status in inkscape package in Ubuntu: In Progress Bug description: When selecting `Help -> Tutorials` the error message is shown and no tutorial is loaded. Failed to load the requested file /usr/share/inkscape/tutorials /tutorial-basic.svg ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: inkscape 0.92.3-4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: i3 Date: Tue Nov 13 05:18:54 2018 InstallationDate: Installed on 2018-11-01 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: inkscape UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1803021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803021] Re: No tutorials
fixed upstream for 1.0-alpha: https://gitlab.com/inkscape/inkscape/commit/b928f75a6e40661f9e2dff482d738a536276764a -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1803021 Title: No tutorials Status in inkscape package in Ubuntu: Won't Fix Bug description: When selecting `Help -> Tutorials` the error message is shown and no tutorial is loaded. Failed to load the requested file /usr/share/inkscape/tutorials /tutorial-basic.svg ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: inkscape 0.92.3-4 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: i3 Date: Tue Nov 13 05:18:54 2018 InstallationDate: Installed on 2018-11-01 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: inkscape UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1803021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729539] Re: copy/paste failed in gedit after a few hours of work
It works now since 4 days. ** Changed in: gedit (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1729539 Title: copy/paste failed in gedit after a few hours of work Status in gedit: Incomplete Status in gedit package in Ubuntu: Invalid Bug description: After a few hours of work, copy in gedit does not work with other applications. In clipit, no copied lines. It is new with ubuntu 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gedit 3.22.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 2 10:19:21 2017 InstallationDate: Installed on 2016-01-31 (640 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: Upgraded to artful on 2017-10-28 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1729539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814025] [NEW] Screen flickering on many programm
Public bug reported: While using VSCode, Firefox Developer Edition, Google Chrome. Watching youtube videos or coding the screen flickering really bad ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: i3 Date: Thu Jan 31 10:55:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1c20] InstallationDate: Installed on 2019-01-11 (19 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. UX430UAR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b2e09cf1-c874-41a4-86ee-c64c58e32f29 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Card0" Driver "intel" Option "Backlight" "intel_backlight" EndSection dmi.bios.date: 10/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR 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.:bvrUX430UAR.300:bd10/06/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901260730.8e9ad5~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.0~git1901260730.8e9ad5~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git1901101932.b1c016~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1901211932.33ee0c~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1901240732.ca1391~oibaf~b ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814025 Title: Screen flickering on many programm Status in xorg package in Ubuntu: New Bug description: While using VSCode, Firefox Developer Edition, Google Chrome. Watching youtube videos or coding the screen flickering really bad ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: i3 Date: Thu Jan 31 10:55:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1c20] InstallationDate: Installed on 2019-01-11 (19 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. UX430UAR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b2e09cf1-c874-41a4-86ee-c64c58e32f29 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Card0" Driver "intel" Option "Backlight" "intel_backlight" EndSection dmi.bios.date: 10/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR 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:
[Desktop-packages] [Bug 1417470] Re: PDF+Latex export creates multipage pdf, pages missing
Chris, the version you posted is two years old. If you are using Linux or Windows there is definitely a newer version. For Mac, there is currently no installer for the latest version because we couldn't find developers for that, but you can try MacPorts. Please test again with https://inkscape.org/de/release/inkscape-0.92.4/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1417470 Title: PDF+Latex export creates multipage pdf, pages missing Status in Inkscape: Fix Released Status in inkscape package in Ubuntu: Fix Released Status in inkscape package in Debian: Fix Released Bug description: In 0.91 the z-order information in svg is used to create multipage PDF+LaTeX documents as per bug 771957. However, for the SVGs I have been converting to PDF+LaTeX in this way, the TeX-file instructs to load more pages than the PDF has, for example the PDF has only three pages and the TeX file also includes page=4. This basically breaks the PDF+LaTeX export for me and I have to use EPS+LaTeX + epstopdf package. The bug occurs on OpenSuse 13.1 and Windows 8.1. Attached a zip file with two svg files and their broken PDF+LaTeX counterparts. To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1417470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764724] Re: logn(x) parsed as log(n)(x)
Done. https://gitlab.gnome.org/GNOME/gnome-calculator/issues/92 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1764724 Title: logn(x) parsed as log(n)(x) Status in gnome-calculator package in Ubuntu: Confirmed Bug description: "logn" is common notation for log base n, e.g. log2(x) is log base 2 of x. gnome-calculator appears to always parse this notation as log(n)(x). So, log10(2) is log(10)(2) = 2, rather than log10(2) ~= 0.301. Arbitrary bases are already supported if the base is input as a subscript. But, typing the base without subscript is common enough that it should be accounted for. gnome-calculator should at least show an error like "function 'log10' is not defined," to avoid silently reporting incorrect results. Ubuntu 17.10, gnome-calculator 3.25.92. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1764724/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 986816] Re: Inkscape crashed with SIGSEGV when saving drawing for first time
Does the bug still happen with the latest inkscape version (0.92.3)? ** Changed in: inkscape Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/986816 Title: Inkscape crashed with SIGSEGV when saving drawing for first time Status in Inkscape: Incomplete Status in inkscape package in Ubuntu: New Bug description: I created a new drawing with a copule of text boxes and three objects - two copied from the original - which was an intersection of two rounded boxes. The document saved successfully and then I got a message popup that there had been an error with Inkscape and had to close. I was able to open the document in inkscape after I selected to restart Inkscape. I am using Ubuntu 12.04, last updated mid April. Inkscape version 0.48.3.1-1ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: inkscape 0.48.3.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu4 Architecture: amd64 Date: Sun Apr 22 11:37:45 2012 ExecutablePath: /usr/bin/inkscape InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcCmdline: inkscape ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f02445f8390:movzbl (%rsi),%ecx PC (0x7f02445f8390) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%ecx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: inkscape StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: inkscape crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/986816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1370953] Re: layout switch is delayed
I'm experiencing same bug on elementary OS 5.0. It really driving me nuts. Added initial bounty on this. https://www.bountysource.com/issues/63898369-slow-keyboard-layouts-switch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in console-setup package in Ubuntu: Confirmed Status in gconf package in Ubuntu: Confirmed Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729539] Re: copy/paste failed in gedit after a few hours of work
it seems that it is the same bug as #1745907 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1729539 Title: copy/paste failed in gedit after a few hours of work Status in gedit: Incomplete Status in gedit package in Ubuntu: New Bug description: After a few hours of work, copy in gedit does not work with other applications. In clipit, no copied lines. It is new with ubuntu 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gedit 3.22.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 2 10:19:21 2017 InstallationDate: Installed on 2016-01-31 (640 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: Upgraded to artful on 2017-10-28 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1729539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729539] Re: copy/paste failed in gedit after a few hours of work
same bug with ubuntu 18.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1729539 Title: copy/paste failed in gedit after a few hours of work Status in gedit: Unknown Status in gedit package in Ubuntu: Incomplete Bug description: After a few hours of work, copy in gedit does not work with other applications. In clipit, no copied lines. It is new with ubuntu 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gedit 3.22.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 2 10:19:21 2017 InstallationDate: Installed on 2016-01-31 (640 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gedit UpgradeStatus: Upgraded to artful on 2017-10-28 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1729539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788911] Re: crash of inkscape open a gif file
after ubuntu reinstallation, it is working ** Changed in: inkscape (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1788911 Title: crash of inkscape open a gif file Status in inkscape package in Ubuntu: Invalid Bug description: very basic operations are broken. Open or import a jpg file falls with bus error ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: inkscape 0.92.3-1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 24 19:51:29 2018 InstallationDate: Installed on 2018-06-17 (68 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: inkscape UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1788911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799232] Re: Thunderbolt displays jump to the right occasionally
I'm currently going down the road of replacing the startech device. The only thing that made me wonder if it was a software problem is that using the 'screen display' utility to move one screen, apply, then revert, seemed to fix the problem, albeit temporarily. I noticed while debugging on Windows that the same problem happens there, so that seems to suggest it isn't software...but the same trick to temporarily fix it, using the corresponding Windows utility to move the displays, does not seem to fix it. I wonder if the ubuntu 'screen display' utility does some kind of 'reset' on the thunderbolt interface and/or the startech adaptor. In any case, it is looking like hardware...what do you think? -- 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/1799232 Title: Thunderbolt displays jump to the right occasionally Status in xorg-server package in Ubuntu: Incomplete Bug description: I have two monitors connected to my Dell XPS 13 via the USB-C output. For the majority of the time, it works fine. Occasionally, one or both of the images on the displays jump to the right, so that the right few inches appear on the left. To rectify the problem, I run the 'displays' app, move one of the displays a little, click 'apply', and then, instead of 'keep settings', I 'revert' them to their original, and then everything is fine for a while. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 22 15:17:27 2018 DistUpgraded: 2018-05-23 09:09:55,083 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:075b] InstallationDate: Installed on 2017-10-11 (376 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=15ace73f-6b30--a755-85264a11ae1e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-23 (152 days ago) dmi.bios.date: 05/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.7.1 dmi.board.name: 05JK94 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.7.1:bd05/21/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn05JK94:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 xserver.bootTime: Tue Oct 31 11:01:05 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5193 vendor SHP xserver.version: 2:1.19.3-1ubuntu1.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1799232/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
