[Desktop-packages] [Bug 1852885] [NEW] x11-common is dead
Public bug reported: x11-common is dead i cant use xorg or default server. just work wayland only. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: x11-common 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 10:59:36 2019 Dependencies: lsb-base 11.0.1ubuntu1 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] InstallationDate: Installed on 2019-01-22 (298 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122) MachineType: LENOVO 20KH007UVA PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH007UVA dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KH007UVA:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007UVA:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH007UVA dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99+git1909241510.0c4275~oibaf~d version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1909260954.031752~oibaf~d version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1909260954.031752~oibaf~d version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1852885 Title: x11-common is dead Status in xorg package in Ubuntu: New Bug description: x11-common is dead i cant use xorg or default server. just work wayland only. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: x11-common 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 10:59:36 2019 Dependencies: lsb-base 11.0.1ubuntu1 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225c] InstallationDate: Installed on 2019-01-22 (298 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190122) MachineType: LENOVO 20KH007UVA PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH007UVA dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KH007UVA:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KH007UVA:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KH007UVA dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor:
[Desktop-packages] [Bug 1844281] Re: Opening an URL in other software tries to start new firefox instance instead of new tab
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1844281 Title: Opening an URL in other software tries to start new firefox instance instead of new tab Status in firefox package in Ubuntu: Expired Bug description: Since upgraded to Eoan I have issues opening an URL from within other applications. It starts: /usr/lib/firefox/firefox https://paste.ubuntu.com/p/ But while in Disco it just opened a new tab in firefox when it was already running, I now get an error message that firefox is still running and I need to close it. This while it should just open an additional tab with the URL I clicked. --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jean-louis 2554 F pulseaudio BuildID: 2019091951 Channel: Unavailable CurrentDesktop: ubuntu:GNOME DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:997 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing DistroRelease: Ubuntu 19.10 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-15 (640 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 10.10.1.1 dev enxa44cc890f4c8 proto dhcp metric 100 default via 10.10.1.1 dev wlan0 proto dhcp metric 600 10.10.1.0/24 dev enxa44cc890f4c8 proto kernel scope link src 10.10.1.182 metric 100 10.10.1.0/24 dev wlan0 proto kernel scope link src 10.10.1.221 metric 600 169.254.0.0/16 dev enxa44cc890f4c8 scope link metric 1000 Package: firefox 69.0+build2-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:997 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=65.0/20190128173924 (Out of date) Profile0 (Default) - LastVersion=69.0/2019091951 (In use) RunningIncompatibleAddons: False Tags: eoan wayland-session Uname: Linux 5.3.0-10-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-16 (0 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 07/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.0 dmi.board.name: 0NKT5P dmi.board.vendor: Dell Inc. dmi.board.version: X00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.0:bd07/26/2019:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0NKT5P:rvrX00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H
Also noticed that v3d.ko is not included as one of the kernel modules int he build. This seems to cause Xorg to pick the VMware display driver instead of the Qualcom display driver. -- 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/1852035 Title: Cannot use full resolution (2560x1440) of Dell U2715H Status in xorg package in Ubuntu: New Bug description: While using Ubuntu 19.10 with either MATE or GNOME, I can use only 1920x1080 resolution instead of the full 2560x1440. If extra pixels are configured, they fall off the right side or bottom of the display and are not visible. Reproduced on Raspberry Pi 4 with 3GB max workaround. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: User Name 5.3.0-1008.9-raspi2 5.3.1 Uname: Linux 5.3.0-1008-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 18:18:23 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M video=HDMI-A-1:1920x1080@60 smsc95xx.macaddr=DC:A6:32:38:DF:15 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792932] Re: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
** Changed in: xorg-server Status: Unknown => New -- 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/1792932 Title: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. Status in X.Org X server: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: New Status in xorg-server source package in Bionic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280 https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80 --- Test Case: Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box Actual Result Black screen or dropped to the login screen if the user skips ubiquity-dm Workaround: Add nomodeset on the kernel command line or from the boot menu, press F6 then select nomodeset Possibly a duplicate of bug 1432137 Fix: Backport a patch from 1.20.2 Regression potential: None really, we've had this xserver version since 18.10 and in the HWE backport, this patch backport is for 18.04 stock xserver but should work the same. It just skips initializing glamor if the system is using software fallback. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AssertionMessage: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. CasperVersion: 1.395 CompositorRunning: None Date: Mon Sep 17 12:42:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92 __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101 dixRegisterPrivateKey () Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1792932/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1852691] Re: Disable touchscreen gesture
** Changed in: xf86-input-wacom (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1852691 Title: Disable touchscreen gesture Status in xf86-input-wacom package in Ubuntu: New Bug description: [Impact] Wacom touchscreen doesn't works well when in-driver gesture was enabled (lp: 1774242), the issue can be fixed by disabling in-driver gestures for touchscreens. Config file that instructs driver to disable in-driver gestures for touchscreens: # Prevent the Wacom driver from providing its own gestures for # touchscreen devices. # Section "InputClass" Identifier "Wacom touchscreen gestures" MatchDriver "wacom" MatchIsTouchscreen "true" Option "Gesture" "off" EndSection [Test Case] 1) Enable the bionic-proposed repository, and install the xf86-input-wacom package 2) Restart and see if the Wacom touchscreen multi-touch gestures (2-finger zoom/rotate and 3+ finger gestures) work as desired. Also check /var/log/Xorg.0.log to see if Wacom touchscreen using wacom driver instead libinput driver. [Regression Potential] Low To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1852691/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792932] Re: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
** Also affects: xorg-server (Ubuntu Xenial) Importance: Undecided Status: New ** Bug watch removed: Linux Kernel Bug Tracker #150731 https://bugzilla.kernel.org/show_bug.cgi?id=150731 ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #53 https://gitlab.freedesktop.org/xorg/xserver/issues/53 ** Changed in: xorg-server Importance: Medium => Unknown ** Changed in: xorg-server Remote watch: freedesktop.org Bugzilla #97313 => gitlab.freedesktop.org/xorg/xserver/issues #53 ** Changed in: xorg-server (Ubuntu Xenial) Importance: Undecided => High -- 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/1792932 Title: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: New Status in xorg-server source package in Bionic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280 https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80 --- Test Case: Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box Actual Result Black screen or dropped to the login screen if the user skips ubiquity-dm Workaround: Add nomodeset on the kernel command line or from the boot menu, press F6 then select nomodeset Possibly a duplicate of bug 1432137 Fix: Backport a patch from 1.20.2 Regression potential: None really, we've had this xserver version since 18.10 and in the HWE backport, this patch backport is for 18.04 stock xserver but should work the same. It just skips initializing glamor if the system is using software fallback. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AssertionMessage: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. CasperVersion: 1.395 CompositorRunning: None Date: Mon Sep 17 12:42:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92 __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101 dixRegisterPrivateKey () Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2
[Desktop-packages] [Bug 1845149] Re: set fallback drivers to avoid updating pci-id lists
** No longer affects: xorg-server-hwe-18.04 (Ubuntu) ** Changed in: xorg-server (Ubuntu Bionic) Status: Invalid => Won't Fix -- 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/1845149 Title: set fallback drivers to avoid updating pci-id lists Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Won't Fix Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] The AMD/Intel pci-id's keep changing when new platforms are enabled. Currently, the new ones need to be added to the kernel, libdrm, mesa and xorg-server. This duplication is silly, as there's a limited number of drivers for a platform, so use a default (fallback) DRI driver for a vendor. For Intel it's i965, for AMD it's radeonsi. [Test case] check that the correct driver is still used on an Xorg session and DRI works [Regression potential] shouldn't be any To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1845149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850064] Re: Please upgrade it to 68.x on Ubuntu 18.04 LTS
** Changed in: thunderbird (Ubuntu Bionic) Importance: Undecided => High -- 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/1850064 Title: Please upgrade it to 68.x on Ubuntu 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Bionic: Fix Committed Bug description: Now the official upgrade way from 60 to 68 got open by mozilla. Plus there are security fixes and performance enhancements. https://www.mozilla.org/en-US/security/known-vulnerabilities/thunderbird/#thunderbird68.2 NOTE TO SRU TEAM: Please do not release this package without consulting first. This is a security update pushed via -proposed to get a bit more testing. Will be released via it's own processes. Packages that are part of this security update: thunderbird, mozilla- devscripts, jsunit and enigmail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1850064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852097] Re: Google Calendar provider is missing in Thunderbird 68.2.1 in bionic-proposed
** Changed in: thunderbird (Ubuntu) Importance: Undecided => High -- 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/1852097 Title: Google Calendar provider is missing in Thunderbird 68.2.1 in bionic- proposed Status in thunderbird package in Ubuntu: New Bug description: The Google Calendar provider is missing in Thunderbird 68.2.1 in bionic-proposed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xul-ext-lightning 1:68.2.1+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr2089 F pulseaudio BuildID: 20191031185816 Channel: Unavailable CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Nov 11 17:19:31 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-11-29 (346 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 141.23.192.1 dev wlp6s0 proto dhcp metric 600 141.23.192.0/19 dev wlp6s0 proto kernel scope link src 141.23.216.93 metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-b6869c51-47ea-4d0c-b5a8-08b020190419 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=68.2.1/20191031185816 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-b6869c51-47ea-4d0c-b5a8-08b020190419 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET57W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LTS01800 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET57W(1.34):bd06/03/2019:svnLENOVO:pn20LTS01800:pvrThinkPadL480:rvnLENOVO:rn20LTS01800:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LTS01800 dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1852097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852877] [NEW] Nothing happens after entering the password to install Tribler
Public bug reported: I went to tribler.org to install Tribler and I chose to install the program with Ubuntu Software. When I click to install and enter my password and click OK, the installation doesn't start. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 00:54:24 2019 InstallationDate: Installed on 2019-11-15 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu10 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1852877 Title: Nothing happens after entering the password to install Tribler Status in gnome-software package in Ubuntu: New Bug description: I went to tribler.org to install Tribler and I chose to install the program with Ubuntu Software. When I click to install and enter my password and click OK, the installation doesn't start. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-software 3.30.6-2ubuntu10 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 00:54:24 2019 InstallationDate: Installed on 2019-11-15 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu10 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1852877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852874] [NEW] Version 78.0.3904.97 (Official Build) snap (64-bit) cannot connect to internet with VPN enabled. Connects fine with VPN disabled.
Public bug reported: Chromium Version 78.0.3904.70 (Official Build) snap (64-bit) on Ubuntu 19.10, Intel® Core™ i7-8550U CPU @ 1.80GHz × 8, GeForce GTX 1050/PCIe/SSE2. Since my upgrade to 19.10, snap chromium will not connect when VPN is enabled. Chromium does connect when VPN is disabled. Access NetworkManager service is enabled in chromium snap. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 14:52:46 2019 InstallationDate: Installed on 2019-10-05 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: chromium-browser UpgradeStatus: Upgraded to eoan on 2019-10-26 (21 days ago) ** Affects: chromium-browser (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 chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1852874 Title: Version 78.0.3904.97 (Official Build) snap (64-bit) cannot connect to internet with VPN enabled. Connects fine with VPN disabled. Status in chromium-browser package in Ubuntu: New Bug description: Chromium Version 78.0.3904.70 (Official Build) snap (64-bit) on Ubuntu 19.10, Intel® Core™ i7-8550U CPU @ 1.80GHz × 8, GeForce GTX 1050/PCIe/SSE2. Since my upgrade to 19.10, snap chromium will not connect when VPN is enabled. Chromium does connect when VPN is disabled. Access NetworkManager service is enabled in chromium snap. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 14:52:46 2019 InstallationDate: Installed on 2019-10-05 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: chromium-browser UpgradeStatus: Upgraded to eoan on 2019-10-26 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1852874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852863] Re: Don't know
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1852863 Title: Don't know Status in xorg package in Ubuntu: Incomplete Bug description: only to start via secured mode ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 16 19:50:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32: added GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller [10cf:150a] InstallationDate: Installed on 2014-09-25 (1878 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: FUJITSU LIFEBOOK AH530 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-92-generic root=UUID=3b781983-e52b-4947-831e-3a130b33f860 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd04/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH530 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Nov 16 11:58:52 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1852863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852864] Re: Fractional Scaling shows a black bar
Thank you for your bug report. Not sure what desktop you are using but that screenshot isn't Ubuntu. Those HiDPI daemon settings don't exist in GNOME/Ubuntu. Does it happen on Ubuntu as well? Could you add a journalctl log after getting the issue? ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1852864 Title: Fractional Scaling shows a black bar Status in gnome-shell package in Ubuntu: Incomplete Bug description: The right part of the external screen shows a black bar when using fractional scaling. This started happening this week. Somebody else is also experiencing this problem: * [ubuntu discourse post](https://discourse.ubuntu.com/t/x11-hidpi-scaling-available-for-testing-on-disco/10293/23) * [photo](https://ubuntucommunity.s3-us-east-2.amazonaws.com/original/2X/5/509069037c78c1e5b461e526236ffeb207de1025.jpg) Attached monitors: * External 4K * Laptop: qhd Tried connection types: * HDMI (30hz), * HDMI over usb-c * DP over usb-c Fractional scaling was set up in this way: `gsettings set org.gnome.mutter experimental-features "['x11-randr-fractional-scaling']"` It doesn't seem to be monitor related. It works when: * using wayland * turning off fractional scaling * during boot and login Installed software: * ubuntu 19.04 * Gnome 3.32.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852844] Re: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line
Thank you for your bug report. That looks like an upstream issue, could you report it there https://gitlab.gnome.org/GNOME/nautilus ? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1852844 Title: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line Status in nautilus package in Ubuntu: New Bug description: An external disk device is declared in '/etc/fstab' with 'auto,nofail,users' options: UUID=aa083302-...-b66c0715eaf1 /media/ushakov/TOSHIBA_SYSTEM ext4 nodev,nosuid,auto,nofail,users 0 2 It is then successfully mounted automatically upon being connected. It can further be unmounted successfully without `sudo` from command line, e.g.: `umount $mount_point`. Meanwhile an attempt to unmount this device from Nautilus/Files UI results in an "Authentication Required" message: "Authentication is required to unmount External USB3.0 (/dev/sdc3) mounted by another user". The expected Nautilus/Files UI behavior would be that the disk device is unmounted silently or just with an non-intrusive notification upon a click on the "Unmount" button near the device label. Package suspected: nautilus: nautilus/bionic-updates,now 1:3.26.4-0~ubuntu18.04.4 amd64 [installed,automatic] $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-35.38~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 09:50:54 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'394' b'org.gnome.nautilus.window-state' b'geometry' b"'1279x749+193+153'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-10-15 (32 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852870] Re: core dumps when installing mono-devel in ppc64le/ubuntu:18.04
** Description changed: (moderators: this is a resubmit since my browser generated an error when I tried to submit before, please delete if this ends up being a duplicate) When installing 'mono-devel' from the default repositories of ppc64le/ubuntu:18.04 with apt, core dumps are generated with no obvious - errors in the terminal's output. These core dumps do not occur in the - x86-64 version of ubuntu:18.04 (x86-64). Mono runtime appears to be + errors in the terminal's output. I have not noticed this behavior with + other packages deployed via apt (however, I have not ruled out it being + a dependency of mono-devel causing them). These core dumps do not occur + in the x86-64 version of ubuntu:18.04. Mono runtime appears to be functioning despite evidence something went wrong during package deployment. Attached is the terminal output and commands to reproduce in Docker. # lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 # apt-cache policy mono-devel mono-devel: - Installed: 4.6.2.7+dfsg-1ubuntu1 - Candidate: 4.6.2.7+dfsg-1ubuntu1 - Version table: - *** 4.6.2.7+dfsg-1ubuntu1 500 - 500 http://ports.ubuntu.com/ubuntu-ports bionic/universe ppc64el Packages - 100 /var/lib/dpkg/status + Installed: 4.6.2.7+dfsg-1ubuntu1 + Candidate: 4.6.2.7+dfsg-1ubuntu1 + Version table: + *** 4.6.2.7+dfsg-1ubuntu1 500 + 500 http://ports.ubuntu.com/ubuntu-ports bionic/universe ppc64el Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mono in Ubuntu. https://bugs.launchpad.net/bugs/1852870 Title: core dumps when installing mono-devel in ppc64le/ubuntu:18.04 Status in mono package in Ubuntu: New Bug description: (moderators: this is a resubmit since my browser generated an error when I tried to submit before, please delete if this ends up being a duplicate) When installing 'mono-devel' from the default repositories of ppc64le/ubuntu:18.04 with apt, core dumps are generated with no obvious errors in the terminal's output. I have not noticed this behavior with other packages deployed via apt (however, I have not ruled out it being a dependency of mono-devel causing them). These core dumps do not occur in the x86-64 version of ubuntu:18.04. Mono runtime appears to be functioning despite evidence something went wrong during package deployment. Attached is the terminal output and commands to reproduce in Docker. # lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 # apt-cache policy mono-devel mono-devel: Installed: 4.6.2.7+dfsg-1ubuntu1 Candidate: 4.6.2.7+dfsg-1ubuntu1 Version table: *** 4.6.2.7+dfsg-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/universe ppc64el Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1852870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852870] [NEW] core dumps when installing mono-devel in ppc64le/ubuntu:18.04
Public bug reported: (moderators: this is a resubmit since my browser generated an error when I tried to submit before, please delete if this ends up being a duplicate) When installing 'mono-devel' from the default repositories of ppc64le/ubuntu:18.04 with apt, core dumps are generated with no obvious errors in the terminal's output. These core dumps do not occur in the x86-64 version of ubuntu:18.04 (x86-64). Mono runtime appears to be functioning despite evidence something went wrong during package deployment. Attached is the terminal output and commands to reproduce in Docker. # lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 # apt-cache policy mono-devel mono-devel: Installed: 4.6.2.7+dfsg-1ubuntu1 Candidate: 4.6.2.7+dfsg-1ubuntu1 Version table: *** 4.6.2.7+dfsg-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/universe ppc64el Packages 100 /var/lib/dpkg/status ** Affects: mono (Ubuntu) Importance: Undecided Status: New ** Attachment added: "terminal with commands issued and output" https://bugs.launchpad.net/bugs/1852870/+attachment/5305943/+files/ubuntu-1804ppc64le-mono-devel.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mono in Ubuntu. https://bugs.launchpad.net/bugs/1852870 Title: core dumps when installing mono-devel in ppc64le/ubuntu:18.04 Status in mono package in Ubuntu: New Bug description: (moderators: this is a resubmit since my browser generated an error when I tried to submit before, please delete if this ends up being a duplicate) When installing 'mono-devel' from the default repositories of ppc64le/ubuntu:18.04 with apt, core dumps are generated with no obvious errors in the terminal's output. These core dumps do not occur in the x86-64 version of ubuntu:18.04 (x86-64). Mono runtime appears to be functioning despite evidence something went wrong during package deployment. Attached is the terminal output and commands to reproduce in Docker. # lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 # apt-cache policy mono-devel mono-devel: Installed: 4.6.2.7+dfsg-1ubuntu1 Candidate: 4.6.2.7+dfsg-1ubuntu1 Version table: *** 4.6.2.7+dfsg-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/universe ppc64el Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1852870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1683383]
this is informative https://www.asupergame.com/bike-games https://www.asupergame.com/bike-games -- 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/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: From duplicate bug 1720364 report. Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher in mate-control-center 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. --- Original description below: This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04 Zesty Zapus. This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. Apparently, the bug has reappeared after the patch that used to fix the problem (208_switch_on_release.diff) has been removed from X.Org 1.19 packages. There is an updated patch in the upstream ticket https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-core 2:1.19.3-1ubuntu1 Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 17 17:46:35 2017 InstallationDate: Installed on 2015-05-01 (716 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg-server UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852864] [NEW] Fractional Scaling shows a black bar
Public bug reported: The right part of the external screen shows a black bar when using fractional scaling. This started happening this week. Somebody else is also experiencing this problem: * [ubuntu discourse post](https://discourse.ubuntu.com/t/x11-hidpi-scaling-available-for-testing-on-disco/10293/23) * [photo](https://ubuntucommunity.s3-us-east-2.amazonaws.com/original/2X/5/509069037c78c1e5b461e526236ffeb207de1025.jpg) Attached monitors: * External 4K * Laptop: qhd Tried connection types: * HDMI (30hz), * HDMI over usb-c * DP over usb-c Fractional scaling was set up in this way: `gsettings set org.gnome.mutter experimental-features "['x11-randr-fractional-scaling']"` It doesn't seem to be monitor related. It works when: * using wayland * turning off fractional scaling * during boot and login Installed software: * ubuntu 19.04 * Gnome 3.32.1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1852864 Title: Fractional Scaling shows a black bar Status in gnome-shell package in Ubuntu: New Bug description: The right part of the external screen shows a black bar when using fractional scaling. This started happening this week. Somebody else is also experiencing this problem: * [ubuntu discourse post](https://discourse.ubuntu.com/t/x11-hidpi-scaling-available-for-testing-on-disco/10293/23) * [photo](https://ubuntucommunity.s3-us-east-2.amazonaws.com/original/2X/5/509069037c78c1e5b461e526236ffeb207de1025.jpg) Attached monitors: * External 4K * Laptop: qhd Tried connection types: * HDMI (30hz), * HDMI over usb-c * DP over usb-c Fractional scaling was set up in this way: `gsettings set org.gnome.mutter experimental-features "['x11-randr-fractional-scaling']"` It doesn't seem to be monitor related. It works when: * using wayland * turning off fractional scaling * during boot and login Installed software: * ubuntu 19.04 * Gnome 3.32.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852864/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1843157] Re: SUPER+D does not maximize minimized opened windows with SUPER+D after right-click on desktop
Hi, it doesn't work even after that this one gets closed. Il 15/11/19 06:24, Sebastien Bacher ha scritto: > Thank you for your bug report. Do you mean it doesn't work while the > menu is open or it doesn't work even after that this one gets closed? On > 19.10 it works as expected, the menu blocks the keybinding but once > close it's still valid > > ** Changed in: nautilus (Ubuntu) > Importance: Undecided => Low > > ** Changed in: nautilus (Ubuntu) > Status: New => Incomplete > -- 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/1843157 Title: SUPER+D does not maximize minimized opened windows with SUPER+D after right-click on desktop Status in nautilus package in Ubuntu: Incomplete Bug description: If I do SUPER+D the desktop will be shown minimizing all opened windows. It I right-click on desktop, then I can't reuse SUPER+D to maximize those windows. In the previous Ubuntu versions it worked fine. If I don't right-click on desktop SUPER+D works. I'm using Ubuntu 18.04, just installed. lsb_release -rd: Description: Ubuntu 18.04.3 LTS Release: 18.04 apt-cache policy nemo: nemo: Installato: 3.6.5-1 Candidato: 3.6.5-1 Tabella versione: *** 3.6.5-1 500 500 http://it.archive.ubuntu.com/ubuntu bionic/universe amd64 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 8 08:17:33 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'geometry' b"'890x545+428+170'" b'org.gnome.nautilus.window-state' b'maximized' b'true' b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" InstallationDate: Installed on 2019-09-07 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1843157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852863] [NEW] Don't know
Public bug reported: only to start via secured mode ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 16 19:50:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32: added GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller [10cf:150a] InstallationDate: Installed on 2014-09-25 (1878 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: FUJITSU LIFEBOOK AH530 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-92-generic root=UUID=3b781983-e52b-4947-831e-3a130b33f860 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd04/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH530 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Nov 16 11:58:52 2019 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 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/1852863 Title: Don't know Status in xorg package in Ubuntu: New Bug description: only to start via secured mode ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39 Uname: Linux 3.13.0-92-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Nov 16 19:50:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.32: added GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller [10cf:150a] InstallationDate: Installed on 2014-09-25 (1878 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: FUJITSU LIFEBOOK AH530 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-92-generic root=UUID=3b781983-e52b-4947-831e-3a130b33f860 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2011 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB06 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd04/15/2011:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH530 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
** Changed in: df-libreoffice Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183]
Note that when copy/paste is failing, some more icons are automatically added into the top taskbar, and then are removed when the graphic objet is deleted -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183]
Can confirm this suspected 'mutter' bad effect on calc 6.3.3 and mutter 3.34.1: -happen with a calc spreadsheet when trying to copy/paste a formula cell: 1) from a column's cell, right click to copy it 2) select the first same column's cell to paste: get a graphic created (kind of image with 4 cells which are draggable and extendable) instead of the normal pasting result. 3) deleting that graphic objet, then re-copying the original cell, finally the pasting is done as expected. This has been seen for each copy/paste since calc 6.3.3 upgrade, not prior. Also note that now LO is unable to load/open an ods file : after the Nov 11th upgrades; Does not get error from a terminal. Only get a dialog box telling calc has silently crashed and will then try to recover the ods file: but there is no file listed to recover. Indeed that ods file load/open as usual with version prior to Focal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: Confirmed Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245473]
this is informative https://www.asupergame.com/bike-games https://www.asupergame.com/bike-games -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1245473 Title: Binding ctrl+shift, alt+shift, etc for switching keyboard layout makes shortcuts with ctrl+shift, etc not working in any program Status in GNOME Settings Daemon: Fix Released Status in GNOME Shell: Won't Fix Status in Unity: Confirmed Status in X.Org X server: Unknown Status in firefox package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in kubuntu-meta package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-settings-daemon package in Debian: New Status in gnome-settings-daemon package in Fedora: Won't Fix Status in gnome-settings-daemon package in openSUSE: Confirmed Bug description: Tried only with ctrl+shift, maybe behaves the same for other modifier key combinations when used as shortcut for switching layouts. - Set ctrl+shift as shortcut for switching keyboard layouts - Try to use ctrl+shift+v, ctrl+shift+c in Terminal -- it doesn't work (actually Terminal window loses focus when ctrl+shift is pressed, and layout is switched) -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Mon Oct 28 16:40:02 2013 InstallationDate: Installed on 2013-10-23 (5 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1245473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Also continuing from my messages earlier today, I had some promising looking output from the following two commands... aplay -l List of PLAYBACK Hardware Devices card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audi] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytchtcx2072x [bytcht-cx2072x], device 0: Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: bytchtcx2072x [bytcht-cx2072x], device 1: Deep-Buffer Audio (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 cat /proc/asound/cards 0 [Audio ]: HdmiLpeAudio - Intel HDMI/DP LPE Audio Intel HDMI/DP LPE Audio 1 [bytchtcx2072x ]: bytcht-cx2072x - bytcht-cx2072x ASUSTeKCOMPUTERINC.-E200HA-1.0-E200HA Does this help at all? Is there a reason the HDMI/DP LPE audio output would be picked as the default? Any advice on testing this further? -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA 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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
Every time my monitor returns from power-saving mode i have to change the sound settings. Again and again and again, every single day. If i disable HDMI audio using Pavucontrol, it will still be enabled automatically the moment my monitor comes back from power saving mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Triaged Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734887] Re: No caps lock indicator on login screen
I understand that backporting this in 3.28 (18.04) may be impossible. I'm then wondering what workaround we have , gnome-shell extension ? -- 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/1734887 Title: No caps lock indicator on login screen Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Disco: Fix Released Status in gnome-shell source package in Eoan: Fix Released Bug description: Expected results: Pressing the Caps Lock key should cause an indicator to appear on the login screen. Actual results: Pressing the Caps Lock key does not cause the login screen to change in any way. Reproducing: 1. Install Ubuntu 17.10 Desktop ISO and log in, press Caps Lock key, see no indicator. (gdm3 3.26.1-3ubuntu3) 2. Install Fedora 27 Workstation ISO and log in, press Caps Lock key, see an indicator. (gdm-3.26.2.1-1.fc27.x86_64) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.26.1-3ubuntu3 Uname: Linux 4.14.2-041402-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Tue Nov 28 08:24:31 2017 InstallationDate: Installed on 2017-11-05 (22 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1734887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852851] [NEW] Dell Pen PN579X exhibits upstream linuxwacom eraser bug
Public bug reported: I found the 'Dell Premium Active Pen (PN579X)' that I just received and as presently sold by Dell elicits the problem described at https://github.com/linuxwacom/xf86-input-wacom/issues/39. I generated a patch file from https://github.com/linuxwacom/xf86-input- wacom/commit/3b338312eb275f2d9a602805931fa47d863a0209 and applied it to the source, rebuilt, reinstalled and can confirm that it did resolve the issue. The upstream fix is based against a newer version of the package. To backport, I did need to resolve a minor conflict so that would apply cleanly to the current version in eoan. I uploaded the patchfile as an attachment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 06:19:30 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu InstallationDate: Installed on 2019-10-31 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.9 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.9:bd08/02/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xf86-input-wacom (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu ** Attachment added: "patch file applied to the quilt for xserver-xorg-input-wacom package" https://bugs.launchpad.net/bugs/1852851/+attachment/5305871/+files/0001-Ignore-ABS_MISC-as-a-source-of-device-type-informati.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1852851 Title: Dell Pen PN579X exhibits upstream linuxwacom eraser bug Status in xf86-input-wacom package in Ubuntu: New Bug description: I found the 'Dell Premium Active Pen (PN579X)' that I just received and as presently sold by Dell elicits the problem described at https://github.com/linuxwacom/xf86-input-wacom/issues/39. I generated a patch file from https://github.com/linuxwacom/xf86-input- wacom/commit/3b338312eb275f2d9a602805931fa47d863a0209 and applied it to the source, rebuilt, reinstalled and can confirm that it did resolve the issue. The upstream fix is based against a newer version of the package. To backport, I did need to resolve a minor conflict so that would apply cleanly to the current version in eoan. I uploaded the patchfile as an attachment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 06:19:30 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu InstallationDate: Installed on 2019-10-31 (16 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.9
[Desktop-packages] [Bug 1569147] Re: onscreen keyboard doesn't trigger url bar's drop-down list
Fixed in firefox 70.0.1. No idea if the fix came from upstream or not.
** Changed in: firefox (Ubuntu)
Status: New => Fix Released
--
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/1569147
Title:
onscreen keyboard doesn't trigger url bar's drop-down list
Status in firefox package in Ubuntu:
Fix Released
Bug description:
Steps:
1) start firefox 45.0.1 for ubuntu canonical
2) using an onscreen keyboard like "onboard", type a partial url that's in
your history
= No dropdown list of suggested url's appears
Notes:
1) Typing the same characters on the physical keyboard produces the expected
dropdown list
2) Safe mode or disabling all extensions makes no difference
3) Occasionally the dropdown list may work once immediately after startup but
never more than once
4) Firefox 45 broke Windows 8 onscreen keyboard support (related?)
https://www.mozilla.org/en-US/firefox/45.0/releasenotes/
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 45.0.1+build1-0ubuntu0.14.04.2
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
NonfreeKernelModules: nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: flamin 2342 F pulseaudio
BuildID: 20160325004402
Channel: Unavailable
CurrentDesktop: Unity
Date: Mon Apr 11 23:21:37 2016
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2014-07-09 (642 days ago)
InstallationMedia: sonar 13.10 - Release amd64
IpRoute:
default via 192.168.0.30 dev eth0 proto static
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.32 metric 1
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
PrefSources: prefs.js
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=45.0.1/20160325004402 (In use)
RelatedPackageVersions:
totem-mozilla 3.10.1-1ubuntu4
rhythmbox-mozilla 3.0.2-0ubuntu2
gnome-shell 3.10.4-0ubuntu5.2
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to trusty on 2014-07-09 (642 days ago)
WifiSyslog:
dmi.bios.date: 12/07/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PAD Ver. F.20
dmi.board.name: 30EC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.25
dmi.chassis.asset.tag: CNU0121PR0
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvr68PADVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.20:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8730w
dmi.product.version: F.20
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1569147/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1569147] Re: onscreen keyboard doesn't trigger url bar's drop-down list
This bug is fixed in firefox 70.0.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/1569147
Title:
onscreen keyboard doesn't trigger url bar's drop-down list
Status in firefox package in Ubuntu:
Fix Released
Bug description:
Steps:
1) start firefox 45.0.1 for ubuntu canonical
2) using an onscreen keyboard like "onboard", type a partial url that's in
your history
= No dropdown list of suggested url's appears
Notes:
1) Typing the same characters on the physical keyboard produces the expected
dropdown list
2) Safe mode or disabling all extensions makes no difference
3) Occasionally the dropdown list may work once immediately after startup but
never more than once
4) Firefox 45 broke Windows 8 onscreen keyboard support (related?)
https://www.mozilla.org/en-US/firefox/45.0/releasenotes/
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: firefox 45.0.1+build1-0ubuntu0.14.04.2
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
NonfreeKernelModules: nvidia
AddonCompatCheckDisabled: False
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: flamin 2342 F pulseaudio
BuildID: 20160325004402
Channel: Unavailable
CurrentDesktop: Unity
Date: Mon Apr 11 23:21:37 2016
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2014-07-09 (642 days ago)
InstallationMedia: sonar 13.10 - Release amd64
IpRoute:
default via 192.168.0.30 dev eth0 proto static
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.32 metric 1
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
PrefSources: prefs.js
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=45.0.1/20160325004402 (In use)
RelatedPackageVersions:
totem-mozilla 3.10.1-1ubuntu4
rhythmbox-mozilla 3.0.2-0ubuntu2
gnome-shell 3.10.4-0ubuntu5.2
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: Upgraded to trusty on 2014-07-09 (642 days ago)
WifiSyslog:
dmi.bios.date: 12/07/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PAD Ver. F.20
dmi.board.name: 30EC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.25
dmi.chassis.asset.tag: CNU0121PR0
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvr68PADVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.20:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8730w
dmi.product.version: F.20
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1569147/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851918] Re: `hp-check -r` crashes with "AttributeError: module 'PIL.Image' has no attribute 'VERSION'"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hplip (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1851918 Title: `hp-check -r` crashes with "AttributeError: module 'PIL.Image' has no attribute 'VERSION'" Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Status in pillow package in Ubuntu: Confirmed Status in python-imaging package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install HPLIP on Ubuntu 19.10 with `sudo apt-get install hplip*` 2. Run `hp-check -r` Expected results: * `hp-check -r` runs without errors Actual results: * `hp-check -r` shows many errors and crashes: $ hp-check -r Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.19.6) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version warning: ubuntu-19.10 version is not supported. Using ubuntu-19.04 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 GNU/Linux Host: eoan Proc: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 GNU/Linux Distribution: ubuntu 19.10 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.19.6 HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not supported for ubuntu distro 19.10 version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.19.6 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/hplip/HP ppdbase=/usr/share/ppd/hplip doc=/usr/share/doc/hplip html=/usr/share/doc/hplip-doc icon=no cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv bin=/usr/bin apparmor=/etc/apparmor.d # Following values are determined at configure time and cannot be changed. [configure] network-build=yes libusb01-build=no pp-build=no gui-build=yes scanner-build=yes fax-build=yes dbus-build=yes cups11-build=no doc-build=yes shadow-build=no hpijs-install=yes foomatic-drv-install=yes foomatic-ppd-install=no foomatic-rip-hplip-install=no hpcups-install=yes cups-drv-install=yes cups-ppd-install=no internal-tag=3.19.6 restricted-build=no ui-toolkit=qt5 qt3=no qt4=no qt5=yes policy-kit=yes lite-build=no udev_sysfs_rules=no hpcups-only-build=no
[Desktop-packages] [Bug 1851918] Re: `hp-check -r` crashes with "AttributeError: module 'PIL.Image' has no attribute 'VERSION'"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-imaging (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1851918 Title: `hp-check -r` crashes with "AttributeError: module 'PIL.Image' has no attribute 'VERSION'" Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Status in pillow package in Ubuntu: Confirmed Status in python-imaging package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install HPLIP on Ubuntu 19.10 with `sudo apt-get install hplip*` 2. Run `hp-check -r` Expected results: * `hp-check -r` runs without errors Actual results: * `hp-check -r` shows many errors and crashes: $ hp-check -r Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.19.6) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version warning: ubuntu-19.10 version is not supported. Using ubuntu-19.04 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 GNU/Linux Host: eoan Proc: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 GNU/Linux Distribution: ubuntu 19.10 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.19.6 HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not supported for ubuntu distro 19.10 version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.19.6 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/hplip/HP ppdbase=/usr/share/ppd/hplip doc=/usr/share/doc/hplip html=/usr/share/doc/hplip-doc icon=no cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv bin=/usr/bin apparmor=/etc/apparmor.d # Following values are determined at configure time and cannot be changed. [configure] network-build=yes libusb01-build=no pp-build=no gui-build=yes scanner-build=yes fax-build=yes dbus-build=yes cups11-build=no doc-build=yes shadow-build=no hpijs-install=yes foomatic-drv-install=yes foomatic-ppd-install=no foomatic-rip-hplip-install=no hpcups-install=yes cups-drv-install=yes cups-ppd-install=no internal-tag=3.19.6 restricted-build=no ui-toolkit=qt5 qt3=no qt4=no qt5=yes policy-kit=yes lite-build=no udev_sysfs_rules=no hpcups-only-build=no
[Desktop-packages] [Bug 1851918] Re: `hp-check -r` crashes with "AttributeError: module 'PIL.Image' has no attribute 'VERSION'"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pillow (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1851918 Title: `hp-check -r` crashes with "AttributeError: module 'PIL.Image' has no attribute 'VERSION'" Status in HPLIP: New Status in hplip package in Ubuntu: Confirmed Status in pillow package in Ubuntu: Confirmed Status in python-imaging package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install HPLIP on Ubuntu 19.10 with `sudo apt-get install hplip*` 2. Run `hp-check -r` Expected results: * `hp-check -r` runs without errors Actual results: * `hp-check -r` shows many errors and crashes: $ hp-check -r Saving output in log file: /home/mate/hp-check.log HP Linux Imaging and Printing System (ver. 3.19.6) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version warning: ubuntu-19.10 version is not supported. Using ubuntu-19.04 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 GNU/Linux Host: eoan Proc: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 GNU/Linux Distribution: ubuntu 19.10 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.19.6 HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not supported for ubuntu distro 19.10 version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.19.6 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/hplip/HP ppdbase=/usr/share/ppd/hplip doc=/usr/share/doc/hplip html=/usr/share/doc/hplip-doc icon=no cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv bin=/usr/bin apparmor=/etc/apparmor.d # Following values are determined at configure time and cannot be changed. [configure] network-build=yes libusb01-build=no pp-build=no gui-build=yes scanner-build=yes fax-build=yes dbus-build=yes cups11-build=no doc-build=yes shadow-build=no hpijs-install=yes foomatic-drv-install=yes foomatic-ppd-install=no foomatic-rip-hplip-install=no hpcups-install=yes cups-drv-install=yes cups-ppd-install=no internal-tag=3.19.6 restricted-build=no ui-toolkit=qt5 qt3=no qt4=no qt5=yes policy-kit=yes lite-build=no udev_sysfs_rules=no hpcups-only-build=no
[Desktop-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Following on from the comment above, if I look for "Audio" with a capital A in the dmesg output, this is a shortened version of what I get (the backend DAIs message is repeated multiple times in the real output)... dmesg | grep Audio [0.159834] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [9.038350] input: Intel HDMI/DP LPE Audio HDMI/DP,pcm=0 as /devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card0/input11 [9.038558] input: Intel HDMI/DP LPE Audio HDMI/DP,pcm=1 as /devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card0/input12 [9.038738] input: Intel HDMI/DP LPE Audio HDMI/DP,pcm=2 as /devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card0/input13 [ 16.076038] Audio Port: ASoC: no backend DAIs enabled for Audio Port -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA 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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840024] Re: Your icon design level confuses branding with design skill
*** This bug is a duplicate of bug 1841187 *** https://bugs.launchpad.net/bugs/1841187 ** This bug is no longer a duplicate of bug 1841142 Can you show skill in your icons? ** This bug has been marked a duplicate of bug 1841187 You should avoid working icon paradox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1840024 Title: Your icon design level confuses branding with design skill Status in yaru-theme package in Ubuntu: Invalid Bug description: This. :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1840024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840074] Re: Is it a good idea to draw logos and icons exclusively for !!!$!$%?
*** This bug is a duplicate of bug 1839837 *** https://bugs.launchpad.net/bugs/1839837 ** This bug is no longer a duplicate of bug 1841142 Can you show skill in your icons? ** This bug has been marked a duplicate of bug 1839837 Your icon theme suffers from uncanny valley effect -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1840074 Title: Is it a good idea to draw logos and icons exclusively for !!!$!$%? Status in yaru-theme package in Ubuntu: Invalid Bug description: I dunno. Are you sure? :)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1840074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841432] Re: Folders are typically brighter outside
*** This bug is a duplicate of bug 1841187 *** https://bugs.launchpad.net/bugs/1841187 ** This bug has been marked a duplicate of bug 1841187 You should avoid working icon paradox -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1841432 Title: Folders are typically brighter outside Status in yaru-theme package in Ubuntu: Invalid Bug description: Folder is brighter outside. >:] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1841432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1839837] Re: Your icon theme suffers from uncanny valley effect
** This bug is no longer a duplicate of bug 1841142 Can you show skill in your icons? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1839837 Title: Your icon theme suffers from uncanny valley effect Status in yaru-theme package in Ubuntu: Opinion Bug description: Your icon theme suffers from uncanny valley effect. :)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1839837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840038] Re: Avoid abuse of futuristic metaforms
*** This bug is a duplicate of bug 1839837 *** https://bugs.launchpad.net/bugs/1839837 ** This bug is no longer a duplicate of bug 1841142 Can you show skill in your icons? ** This bug has been marked a duplicate of bug 1839837 Your icon theme suffers from uncanny valley effect -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1840038 Title: Avoid abuse of futuristic metaforms Status in yaru-theme package in Ubuntu: Invalid Bug description: Don't do it, it looks bad. :)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1840038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
I'm running Ubuntu 19.10 on an Asus E200H laptop. I'm getting no sound output. CX2027x kernel modules seem to be available but there appear to be issues during boot. Including the following information to help track down the issue (if there's anything else that I should provide please let me know): (base) zenoarrow@zenoarrow-E200HA:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan uname -a Linux zenoarrow-E200HA 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux dmesg | grep cx2072x [9.287864] cx2072x i2c-14F10720:00: codec version: 14f150f2,00100101 [ 11.889796] bytcht_cx2072x bytcht_cx2072x: snd-soc-dummy-dai <-> media-cpu-dai mapping ok [ 11.890348] bytcht_cx2072x bytcht_cx2072x: snd-soc-dummy-dai <-> deepbuffer-cpu-dai mapping ok [ 11.895693] bytcht_cx2072x bytcht_cx2072x: cx2072x-hifi <-> ssp2-port mapping ok [ 11.895903] bytcht_cx2072x bytcht_cx2072x: ASoC: sink widget Playback overwritten [ 11.895928] bytcht_cx2072x bytcht_cx2072x: ASoC: source widget Capture overwritten [ 11.896417] cx2072x i2c-14F10720:00: ASoC: Failed to create Playback debugfs file: -17 [ 11.896425] cx2072x i2c-14F10720:00: ASoC: Failed to create Capture debugfs file: -17 [ 11.915242] input: bytcht-cx2072x Headset as /devices/pci:00/808622A8:00/bytcht_cx2072x/sound/card1/input14 [ 124.561900] Modules linked in: rfcomm twofish_generic twofish_x86_64_3way twofish_x86_64 twofish_common serpent_sse2_x86_64 serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_generic cast_common des_generic algif_skcipher camellia_generic camellia_x86_64 xcbc md4 pci_stub algif_hash vboxpci(OE) af_alg vboxnetadp(OE) vboxnetflt(OE) xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 vboxdrv(OE) ah4 l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel af_key xfrm_algo pppox ccm bnep ip6table_filter ip6_tables iptable_filter bpfilter binfmt_misc nls_iso8859_1 snd_soc_sst_byt_cht_cx2072x joydev snd_hdmi_lpe_audio mei_hdcp intel_rapl_msr intel_powerclamp coretemp kvm_intel kvm irqbypass punit_atom_debug crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper asus_nb_wmi intel_cstate uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev [ 124.561970] intel_chtdc_ti_pwrbtn input_leds mc ecdh_generic ecc ath10k_pci ath10k_core ath mac80211 cfg80211 libarc4 intel_xhci_usb_role_switch roles sof_acpi_dev snd_sof_intel_byt snd_sof_intel_bdw snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_intel_sst_acpi snd_intel_sst_core snd_soc_sst_atom_hifi2_platform snd_soc_cx2072x snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_pcm snd_seq_midi snd_seq_midi_event i915 snd_rawmidi snd_seq snd_seq_device snd_timer drm_kms_helper drm snd i2c_algo_bit fb_sys_fops syscopyarea mei_txe sysfillrect soundcore sysimgblt mei processor_thermal_device elan_i2c intel_rapl_common int3400_thermal int3403_thermal intel_soc_dts_iosf acpi_thermal_rel int340x_thermal_zone int3406_thermal intel_int0002_vgpio soc_button_array asus_wireless spi_pxa2xx_platform acpi_pad 8250_dw dw_dmac mac_hid dw_dmac_core sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block hid_asus asus_wmi sparse_keymap dmesg | grep audio [9.191038] [drm] HDaudio controller not detected, using LPE audio instead [ 11.794904] input: Intel HDMI/DP LPE Audio HDMI/DP,pcm=0 as /devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card0/input11 [ 11.795188] input: Intel HDMI/DP LPE Audio HDMI/DP,pcm=1 as /devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card0/input12 [ 11.795434] input: Intel HDMI/DP LPE Audio HDMI/DP,pcm=2 as /devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card0/input13 [ 124.561900] Modules linked in: rfcomm twofish_generic twofish_x86_64_3way twofish_x86_64 twofish_common serpent_sse2_x86_64 serpent_generic blowfish_generic blowfish_x86_64 blowfish_common cast5_generic cast_common des_generic algif_skcipher camellia_generic camellia_x86_64 xcbc md4 pci_stub algif_hash vboxpci(OE) af_alg vboxnetadp(OE) vboxnetflt(OE) xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 vboxdrv(OE) ah4 l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel af_key xfrm_algo pppox ccm bnep ip6table_filter ip6_tables iptable_filter bpfilter binfmt_misc nls_iso8859_1 snd_soc_sst_byt_cht_cx2072x joydev snd_hdmi_lpe_audio mei_hdcp intel_rapl_msr intel_powerclamp coretemp kvm_intel kvm irqbypass punit_atom_debug crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper asus_nb_wmi intel_cstate uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops btbcm videobuf2_v4l2 btintel videobuf2_common bluetooth videodev find /lib/modules/$(uname -r)
[Desktop-packages] [Bug 1852844] [NEW] Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line
Public bug reported: An external disk device is declared in '/etc/fstab' with 'auto,nofail,users' options: UUID=aa083302-...-b66c0715eaf1 /media/ushakov/TOSHIBA_SYSTEM ext4 nodev,nosuid,auto,nofail,users 0 2 It is then successfully mounted automatically upon being connected. It can further be unmounted successfully without `sudo` from command line, e.g.: `umount $mount_point`. Meanwhile an attempt to unmount this device from Nautilus/Files UI results in an "Authentication Required" message: "Authentication is required to unmount External USB3.0 (/dev/sdc3) mounted by another user". The expected Nautilus/Files UI behavior would be that the disk device is unmounted silently or just with an non-intrusive notification upon a click on the "Unmount" button near the device label. Package suspected: nautilus: nautilus/bionic-updates,now 1:3.26.4-0~ubuntu18.04.4 amd64 [installed,automatic] $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-35.38~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 09:50:54 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'394' b'org.gnome.nautilus.window-state' b'geometry' b"'1279x749+193+153'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-10-15 (32 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1852844 Title: Nautilus/Files UI requires sudo access to unmount a disk that can be unmounted successfully without sudo using command line Status in nautilus package in Ubuntu: New Bug description: An external disk device is declared in '/etc/fstab' with 'auto,nofail,users' options: UUID=aa083302-...-b66c0715eaf1 /media/ushakov/TOSHIBA_SYSTEM ext4 nodev,nosuid,auto,nofail,users 0 2 It is then successfully mounted automatically upon being connected. It can further be unmounted successfully without `sudo` from command line, e.g.: `umount $mount_point`. Meanwhile an attempt to unmount this device from Nautilus/Files UI results in an "Authentication Required" message: "Authentication is required to unmount External USB3.0 (/dev/sdc3) mounted by another user". The expected Nautilus/Files UI behavior would be that the disk device is unmounted silently or just with an non-intrusive notification upon a click on the "Unmount" button near the device label. Package suspected: nautilus: nautilus/bionic-updates,now 1:3.26.4-0~ubuntu18.04.4 amd64 [installed,automatic] $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 ProcVersionSignature: Ubuntu 5.0.0-35.38~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-35-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 09:50:54 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'394' b'org.gnome.nautilus.window-state' b'geometry' b"'1279x749+193+153'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency']" InstallationDate: Installed on 2019-10-15 (32 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1852844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
This also happens in other office and text applications (geany, under ms office 2010 with wine, etc.) and other systems such as manjaro linux with gnome-shell 1:3.34.1+12+ga43c22e3a-1 and mutter 3.34.1+52+g403d8fcc-1 under Xorg. Wouldn't it be a mutter bug linked to implementation of the new clipboard? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 Status in LibreOffice: New Status in Mutter: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1420988] Re: no audio input from combo jack on ALC283 (Acer Aspire V15 Nitro Black Edition)
The workaround proposed in comment 4 ended up fixing my issue with an Intel NUC front connector jack. -- 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/1420988 Title: no audio input from combo jack on ALC283 (Acer Aspire V15 Nitro Black Edition) Status in alsa-driver package in Ubuntu: Confirmed Bug description: Happens on Linux Mint 17.1 (Ubuntu 14.04). Linux kernel is 3.19 in order to get the touchpad working The external microphone connected to the combo jack of this laptop doesn't work, the output does work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1420988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 981620] Re: Printing a LibreOffice document via PDF workflow is much slower than with PostScript workflow
** Changed in: cups (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/981620 Title: Printing a LibreOffice document via PDF workflow is much slower than with PostScript workflow Status in cups package in Ubuntu: Fix Released Bug description: If Libreoffice's printing workflow language is set to PDF (from the Printer Settings dialog -> Properties -> Device), printing appears to be quite a bit slower than if it's set to a Postscript level. In particular, when printing multiple copies of a one page document, the time between individual pages is much longer with PDF than with PS. (For 30 pages, this makes the total printing time some 10 vs 2 minutes.) The difference is even notable if print quality is set to fast-draft, black only, with simple documents (text only, no photos). When printing to a file, both ways seem to be equally fast, so I haven't set LibreOffice as the affected program. BTW, the resulting sample PDFs are about three times *smaller* than the corresponding PS files. Ubuntu 11.10 (64 bit), LibreOffice 3.4.4; Printer: HP Photosmart C4380, connected via wifi Driver (according to CUPS v1.5.0): hpcups 3.11.7 (color, 2-sided printing) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/981620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
