[Desktop-packages] [Bug 1739510] Re: ill install you signature
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1739510 Title: ill install you signature Status in xorg package in Ubuntu: Expired Bug description: hope you can help me. i cant affort another computer and spain is acting violence ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Dec 21 01:27:15 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:81ed] InstallationDate: Installed on 2017-12-19 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:651b Microdia Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 276d:1160 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic.efi.signed root=UUID=d6ad60b5-3719-45b3-8b42-1bb91b324af7 ro nopat vesafb.invalid=1 plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81ED dmi.board.vendor: HP dmi.board.version: 62.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/20/2017:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81ED:rvr62.39:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 250 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 21 00:06:27 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1739510/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901470] Re: [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead
Comment #29 shows this problem is originating in the i915 kernel driver. So there's no need to include 'xorg-server' here, Xorg is only following the (incomplete) list of modes exposed by the kernel. ** No longer affects: xorg-server (Ubuntu) -- 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/1901470 Title: [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead Status in linux package in Ubuntu: Confirmed Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Modeline"Mode
[Desktop-packages] [Bug 1357804] Re: Ubuntu 14.04 does not support 2560x1080 resolution.
Ubuntu 14.04 and 16.04 are no longer supported. Anyone using Intel graphics and a newer release should refer to bug 1901470 instead. Everyone else, please open a new bug if you encounter problems. ** Package changed: xrandr (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: Confirmed => 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/1357804 Title: Ubuntu 14.04 does not support 2560x1080 resolution. Status in xorg-server package in Ubuntu: Won't Fix Bug description: I recently installed Ubuntu 14.04 on a mac mini and bought a 2560 x 1080 ultrawide LG monitor for it. Problem is that it doesn't display the proper resolution, the maximum being 1920 x 1080 under ubuntu settings. Any suggestions on what I should do? Please give clear instructions as I am not an Ubuntu expert. My graphics card: NVIDIA Corporation C79 [GeForce 9400] If there is currently no solution, would someone please pass this on to the Ubuntu developers so that they start working on implementing this resolution into the operating system? Thank you, Ian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1357804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1357804] [NEW] Ubuntu 14.04 does not support 2560x1080 resolution.
You have been subscribed to a public bug: I recently installed Ubuntu 14.04 on a mac mini and bought a 2560 x 1080 ultrawide LG monitor for it. Problem is that it doesn't display the proper resolution, the maximum being 1920 x 1080 under ubuntu settings. Any suggestions on what I should do? Please give clear instructions as I am not an Ubuntu expert. My graphics card: NVIDIA Corporation C79 [GeForce 9400] If there is currently no solution, would someone please pass this on to the Ubuntu developers so that they start working on implementing this resolution into the operating system? Thank you, Ian ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: Won't Fix ** Tags: bot-comment -- Ubuntu 14.04 does not support 2560x1080 resolution. https://bugs.launchpad.net/bugs/1357804 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1537047] Re: Selected button not adequately highlighted in GTK3 themes (orange highlight too thin)
Yeah, let's not get focal or Yaru involved here. If anyone has a problem with focal or Yaru they should open a new bug with a screenshot of whatever is bothering them. ** Tags removed: focal ** No longer affects: yaru-theme (Ubuntu) -- 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/1537047 Title: Selected button not adequately highlighted in GTK3 themes (orange highlight too thin) Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: With Ubuntu's GTK+ 3 Theme, the orange dotted line is so thin, it's practically invisible and the red button highlight is missing. This makes it appear that the window is not in focus and you must use the mouse to select the dialog buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1537047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901470] Re: [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 or 2560x1080 not listed, defaults to 1920x1080 instead
** Summary changed: - [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 not listed, defaults to 1920x1080 instead + [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 or 2560x1080 not listed, defaults to 1920x1080 instead ** Tags added: regression-release ** Summary changed: - [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 or 2560x1080 not listed, defaults to 1920x1080 instead + [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead -- 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/1901470 Title: [modeset][i915] Native resolution (EDID detailed mode higher than FHD) not listed, defaults to 1920x1080 instead Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option
[Desktop-packages] [Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
*** This bug is a duplicate of bug 1901470 *** https://bugs.launchpad.net/bugs/1901470 ** This bug is no longer a duplicate of bug 1929456 XrandR does not propose 21:9 resolution ** This bug has been marked a duplicate of bug 1901470 [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 or 2560x1080 not listed, defaults to 1920x1080 instead -- 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/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Incomplete Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929456] Re: XrandR does not propose 21:9 resolution
*** This bug is a duplicate of bug 1901470 *** https://bugs.launchpad.net/bugs/1901470 I have decoded your monitor's EDID and it does show the desired resolution but only as a "Detailed mode". So that would appear to make this a duplicate of bug 1901470. EDID version: 1.3 Manufacturer: GSM Model 23025 Serial Number 10845 Made in week 9 of 2015 Digital display Maximum image size: 80 cm x 34 cm Gamma: 2.20 DPMS levels: Standby Suspend Off RGB color display First detailed timing is preferred timing Color Characteristics Red: 0.6513, 0.3320 Green: 0.3066, 0.6308 Blue: 0.1503, 0.0595 White: 0.3134, 0.3291 Established Timings I & II 720x40070.082 Hz 9:531.467 kHz 28.320 MHz (IBM) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (DMT) 640x48075.000 Hz 4:337.500 kHz 31.500 MHz (DMT) 800x60060.317 Hz 4:337.879 kHz 40.000 MHz (DMT) 800x60075.000 Hz 4:346.875 kHz 49.500 MHz (DMT) 1024x76860.004 Hz 4:348.363 kHz 65.000 MHz (DMT) 1024x76875.029 Hz 4:360.023 kHz 78.750 MHz (DMT) 1280x1024 75.025 Hz 5:479.976 kHz 135.000 MHz (DMT) 1152x87075.062 Hz 192:145 68.681 kHz 100.000 MHz (Apple) Standard Timings 1152x86475.000 Hz 4:367.500 kHz 108.000 MHz (DMT) 1280x1024 60.020 Hz 5:463.981 kHz 108.000 MHz (DMT) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (DMT) 1600x90060.000 Hz 16:960.000 kHz 108.000 MHz (DMT, RB) 1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz (DMT) Detailed mode: Clock 185.580 MHz, 798 mm x 334 mm 2560 2624 2688 2784 ( 64 64 96) 1080 1083 1093 ( 3 10 18) -hsync -vsync VertFreq: 60.000 Hz, HorFreq: 66.659 kHz Detailed mode: Clock 148.500 MHz, 798 mm x 334 mm 1920 2008 2052 2200 ( 88 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 67.500 kHz Display Product Name: LG ULTRAWIDE Display Range Limits Monitor ranges (GTF): 56-75 Hz V, 30-90 kHz H, max dotclock 240 MHz Has 1 extension block Checksum: 0x7b CTA-861 Extension Block Revision 3 Underscans PC formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 1 native detailed modes 25 bytes of CTA data blocks Video Data Block 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (VIC 16, native) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (VIC 4) 720x48059.940 Hz 16:931.469 kHz 27.000 MHz (VIC 3) 1920x1080 30.000 Hz 16:933.750 kHz 74.250 MHz (VIC 34) 1920x1080i 50.000 Hz 16:928.125 kHz 74.250 MHz (VIC 20) 720x57650.000 Hz 16:931.250 kHz 27.000 MHz (VIC 18) 1920x1080i 60.000 Hz 16:933.750 kHz 74.250 MHz (VIC 5) 1920x1080 50.000 Hz 16:956.250 kHz 148.500 MHz (VIC 31) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (VIC 1) 1280x72050.000 Hz 16:937.500 kHz 74.250 MHz (VIC 19) Audio Data Block Linear PCM, max channels 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 Speaker Allocation Data Block Speaker map: FL/FR - Front Left/Right Vendor-Specific Data Block, OUI 0x000c03 (HDMI) Source physical address 1.0.0.0 Detailed mode: Clock 148.500 MHz, 598 mm x 337 mm 1920 2008 2052 2200 ( 88 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 67.500 kHz Detailed mode: Clock 74.250 MHz, 598 mm x 337 mm 1920 2008 2052 2200 ( 88 44 148) 540 542 547 562 ( 2 5 15) +hsync +vsync VertFreq: 60.000i Hz, HorFreq: 33.750 kHz Detailed mode: Clock 74.250 MHz, 598 mm x 337 mm 1280 1390 1430 1650 (110 40 220) 720 725 730 750 ( 5 5 20) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 45.000 kHz Detailed mode: Clock 27.000 MHz, 598 mm x 337 mm 720 736 798 858 ( 16 62 60) 480 489 495 525 ( 9 6 30) -hsync -vsync VertFreq: 59.940 Hz, HorFreq: 31.469 kHz Detailed mode: 00 00 00 ff 00 35 30 39 4e 54 4b 46 30 41 38 34 35 0a .509NTKF0A845. Checksum: 0x8c ** This bug has been marked a duplicate of bug 1901470 [modeset][i915] Native resolution (EDID detailed mode) of 2560x1440 or 2560x1080 not listed, defaults to 1920x1080 instead -- 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/1929456 Title: XrandR does not propose 21:9 resolution Status in xorg package in Ubuntu: Confirmed Bug description: If come here over bug 1895301 "XrandR does not propose 3440x1440 21:9 resolution".
[Desktop-packages] [Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
*** This bug is a duplicate of bug 1929456 *** https://bugs.launchpad.net/bugs/1929456 Thanks Sebastian. Let's use bug 1929456 for now... ** This bug has been marked a duplicate of bug 1929456 XrandR does not propose 21:9 resolution -- 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/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Incomplete Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929456] Re: XrandR does not propose 21:9 resolution
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1929456 Title: XrandR does not propose 21:9 resolution Status in xorg package in Ubuntu: Confirmed Bug description: If come here over bug 1895301 "XrandR does not propose 3440x1440 21:9 resolution". In bug 1895301 sombody wrote "We just need one person experiencing the bug to open a bug with the relevant system details automatically attached." - so I did. I have a similar problem with a 21:9 monitor with a resolution of 2560x1080. It's a LG 25UB55-B on a HP docking station A7E32A, DVI output with adapter to HDMI, HDMI cable and input to the monitor via HDMI. Laptop is an HP Elitebook 8440p (Intel i5-520 with Intel HD Graphics (ILK)), internal display with 1366*768 is in use as well. I had Ubuntu 18.04 LTS before until January this year, with automatic updates on, so presumably up to date. There it worked fine out of the box, i.e. since first install I had the full resolution of 21:9 in 2560x1080 on my external monitor. I didn't change any hardware, just installed Ubuntu 20.04 from DVD, an it stopped working. I got only 16:9 with 1920x1080. I've updated to Ubuntu 20.10, tried Ubuntu 21.04 (from DVD as well), changed cable and adapter, nothing helped. Did some reseach with google and found the mentioned bug 1895301. The workaround worked, I got full resolution of 2560x1080 on the external display. It is not permanent, so at the moment of filing this bug, I'm still back on the 16:9 with 1920x1080. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Mon May 24 20:23:52 2021 DistUpgraded: 2021-05-23 15:18:23,444 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] InstallationDate: Installed on 2021-02-10 (103 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP EliteBook 8440p ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-53-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2021-05-23 (1 days ago) dmi.bios.date: 09/13/2013 dmi.bios.release: 15.36 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.24 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.34 dmi.chassis.asset.tag: CZC040C94D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 48.52 dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.24:bd09/13/2013:br15.36:efr48.52:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.34:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.product.sku: J2544631 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1929456/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1929343] Re: Alt-Shift-Tab to Switch Windows in reverse direction not working
*** This bug is a duplicate of bug 36812 *** https://bugs.launchpad.net/bugs/36812 ** This bug has been marked a duplicate of bug 36812 Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts -- 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/1929343 Title: Alt-Shift-Tab to Switch Windows in reverse direction not working Status in gnome-shell package in Ubuntu: Incomplete Bug description: I remember back in Ubuntu 14 (or 16) I was able to press Alt-Tab and then hold Shift to move across the windows in reverse direction. Now in Ubuntu 20.10 this no longer works. However, moving between applications (Super-Tab) does work in forward as well as reverse direction (while holding Shift). This is annoying when moving across many windows quickly, I sometimes "overshoot" by one, and then have to cycle all the way around again. So hereby a request to implement Alt-Shift-Tab for work similarly to Super-Shift-Tab. Release: Ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929343/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929475] [NEW] Bluetooth sound card conecctivity issues
Public bug reported: I have Bluetooth 5.0 device soundcore life q10, while I'm using WiFi my Headphone disconnects often and microphone doesn't listed on audio settings. connecting wired mode it works perfectly. if you need any other query I'm a happy to answer your query. And I checked some forums many people also having this issues so can you make it as soon as possible. thank you for valuable service. have a good day. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saravanan 1350 F pulseaudio /dev/snd/pcmC0D0p: saravanan 1350 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 25 06:13:04 2021 InstallationDate: Installed on 2021-05-05 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2018 dmi.bios.release: 1.45 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.45 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.45:bd07/23/2018:br1.45:efr2.50:svnAcer:pnAspireE5-575:pvrV1.45:rvnAcer:rnIronman_SK:rvrV1.45:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: SKL dmi.product.name: Aspire E5-575 dmi.product.sku: Aspire E5-575_1094_1.45 dmi.product.version: V1.45 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1929475 Title: Bluetooth sound card conecctivity issues Status in alsa-driver package in Ubuntu: New Bug description: I have Bluetooth 5.0 device soundcore life q10, while I'm using WiFi my Headphone disconnects often and microphone doesn't listed on audio settings. connecting wired mode it works perfectly. if you need any other query I'm a happy to answer your query. And I checked some forums many people also having this issues so can you make it as soon as possible. thank you for valuable service. have a good day. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saravanan 1350 F pulseaudio /dev/snd/pcmC0D0p: saravanan 1350 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 25 06:13:04 2021 InstallationDate: Installed on 2021-05-05 (19 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2018 dmi.bios.release: 1.45 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.45 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.45 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.50 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.45:bd07/23/2018:br1.45:efr2.50:svnAcer:pnAspireE5-575:pvrV1.45:rvnAcer:rnIronman_SK:rvrV1.45:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: SKL dmi.product.name: Aspire E5-575 dmi.product.sku: Aspire E5-575_1094_1.45 dmi.product.version: V1.45 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1929475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911379] Re: [SRU] Avoid error message when the file doesn't exist
** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1911379 Title: [SRU] Avoid error message when the file doesn't exist Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Groovy: Fix Released Status in wslu source package in Hirsute: Fix Released Bug description: [Impact] this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. [Test Case] * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. [Regression Potential] This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1911379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915605] Re: Firefox (circle spinning while run program) problem on Ubuntu bionic family - 18.04.5
I am very happy. Today after update (16 packages) I noticed that this bug is gone. So this problem is solved now. This bug now is not exist so I can use bionic and it is useful. Thanks for work for this system. ** Changed in: firefox (Ubuntu) Status: Incomplete => 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/1915605 Title: Firefox (circle spinning while run program) problem on Ubuntu bionic family - 18.04.5 Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Fix Released Bug description: Dear Launchpad Team, I have problem with Firefox on Ubuntu 18.04.5 system. When I run firefox this loading too long (circle spinning - animation of my cursor). I noticed this bug also on Xubuntu 18.04.4 on another computer. On Lubuntu 18.04.5 system on another computer I don't have these kind of bug so it is problem with Ubuntu and Xubuntu system. On Ubuntu 20.04 and Ubuntu 20.04.1 I don't have these bug. Of course I have updated system. I noticed also that if I will run firefox for the first time after booting my system this bug is not exist. I have this bug for the second run of the firefox and next. I have this problem also booting my computer with live USB with clear system image with Ubuntu 18.04.5. Like I earlier said this is problem with the system. When I use Ubuntu 20.04 I don't have this problem. My system is clean this is fresh install. I don't know what is problem but I am sure that everyone with Ubuntu 18.04.5 have this problem. Firefox is the newest 85.0.1 version. On older vesion I also had this problem in Ubuntu 18.04.5. Firefox start with no errors. No errors is a shown in terminal. Problem is with spinning with the cursor. When I run firefox cursor is spinning but firefox normally works. This cursor spinning only when I move this cursor on GNOME environment (top of the screen I don't know what is the name of this. This is graphic bar? When I run firefox in this "graphic bar" are shown name of the program (in my case firefox). On Ubuntu 20.04 my cursor doesn't spinning. Like I said this is problem only with Ubuntu 18.04.5 and Xubuntu 18.04.4 system. So this is the problem with bionic family but on Lubuntu 18.04.4 and 18.04.5 and doesn't have this problem too. I tried reinstall firefox but this doesn't help. I also deleted files for firex in /home but this also doesn't help. I think that this problem is more complicated. Can you fix it? I am sure that everyone have this problem. Some output from terminal: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 UPDATE: Today I updated to the newest version of the firefox - 86.0 and bug still exists. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1915605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928360] Re: Switch to Fcitx 5 for Chinese
Gunnar, indeed, it had much less in it than I expected; I don't know much about the snap packaging for Chromium, but it looked to me like it was trying to do bluetooth things and that's all that was denied. I'm no fcitx expert but I didn't think it looked related. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1928360 Title: Switch to Fcitx 5 for Chinese Status in Lubuntu default settings: New Status in Ubuntu Kylin: In Progress Status in apparmor package in Ubuntu: New Status in language-selector package in Ubuntu: Fix Released Bug description: In Debian 11 Fcitx 5 will be the default IM framework for Chinese on non-GNOME desktops. I can think it's time to make the equivalent changes in Ubuntu 21.10 as well. I'd appreciate input on the topic from the Ubuntu Kylin team as well as other Chinese speaking users. To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-default-settings/+bug/1928360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929456] Re: XrandR does not propose 21:9 resolution
As I said, the workaround worked. To help others looking for a solution and finding this bug, I will show it here for my configuration: 1.) Open a terminal 2.) Call xrandr to see, how your desired device is called. In my case, it's called "HDMI-1". If you have more than one, you may guess, but output should by clear enough. 3.) Call cvt with desired resolution and frequency. In my case it must be 2560x1080 with 30 (Hz), If you are unsure you have to try (I tried 60 Hz first - didn't work in the last step no. 6): cvt 2560 1080 30 Output in my case is # 2560x1080 29.97 Hz (CVT) hsync: 33.03 kHz; pclk: 106.75 MHz Modeline "2560x1080_30.00" 106.75 2560 2640 2896 3232 1080 1083 1093 1102 -hsync +vsync 4.) Call xrandr to set new mode, copy everything after "Modeline": xrandr --newmode "2560x1080_30.00" 106.75 2560 2640 2896 3232 1080 1083 1093 1102 -hsync +vsync (The name in quotation marks could be changed, but no need to do so.) 5.) Call xrandr to add this mode by it's name to your desired device: xrandr --addmode HDMI-1 2560x1080_30.00 6.) Call xrandr to set your desired device (here. HDMI-1) to the mode xrandr --output HDMI-1 --mode 2560x1080_30.00 Instead of step 6 via terminal you could use the GUI to change the resolution, it should be there now. Hope this may help somebody. It is not persistent. I made a script and added it to autostart. There may be other ways, maybe a config file for xrandr? -- 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/1929456 Title: XrandR does not propose 21:9 resolution Status in xorg package in Ubuntu: New Bug description: If come here over bug 1895301 "XrandR does not propose 3440x1440 21:9 resolution". In bug 1895301 sombody wrote "We just need one person experiencing the bug to open a bug with the relevant system details automatically attached." - so I did. I have a similar problem with a 21:9 monitor with a resolution of 2560x1080. It's a LG 25UB55-B on a HP docking station A7E32A, DVI output with adapter to HDMI, HDMI cable and input to the monitor via HDMI. Laptop is an HP Elitebook 8440p (Intel i5-520 with Intel HD Graphics (ILK)), internal display with 1366*768 is in use as well. I had Ubuntu 18.04 LTS before until January this year, with automatic updates on, so presumably up to date. There it worked fine out of the box, i.e. since first install I had the full resolution of 21:9 in 2560x1080 on my external monitor. I didn't change any hardware, just installed Ubuntu 20.04 from DVD, an it stopped working. I got only 16:9 with 1920x1080. I've updated to Ubuntu 20.10, tried Ubuntu 21.04 (from DVD as well), changed cable and adapter, nothing helped. Did some reseach with google and found the mentioned bug 1895301. The workaround worked, I got full resolution of 2560x1080 on the external display. It is not permanent, so at the moment of filing this bug, I'm still back on the 16:9 with 1920x1080. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Mon May 24 20:23:52 2021 DistUpgraded: 2021-05-23 15:18:23,444 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] InstallationDate: Installed on 2021-02-10 (103 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP EliteBook 8440p ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-53-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2021-05-23 (1 days ago) dmi.bios.date: 09/13/2013 dmi.bios.release: 15.36 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.24 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.34 dmi.chassis.asset.tag: CZC040C94D
[Desktop-packages] [Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
** Description changed: + [Impact] + The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ - https://developer.yr.no/doc/guides/getting-started-from-forecast-xml/ + + https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS + + == + Version 3.36.2 + == + + This version switches the yr.no backend to use met.no instead. Please note + that this backport is only meant as a compatibility layer. Where at all + possible, the newer libgweather 40 should be used as applications cannot + fully comply with the met.no ToS otherwise. + + + [Test case] + + - gnome-weather shows the weather forecast + - gnome-shell shows the weather forecast in the calendar menu + + + [Regression potential] + + - Weather forecast is totally broken now and can't be more broken. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Confirmed Status in libgweather package in Ubuntu: Confirmed Status in gnome-weather package in Fedora: New Bug description: [Impact] The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS == Version 3.36.2 == This version switches the yr.no backend to use met.no instead. Please note that this backport is only meant as a compatibility layer. Where at all possible, the newer libgweather 40 should be used as applications cannot fully comply with the met.no ToS otherwise. [Test case] - gnome-weather shows the weather forecast - gnome-shell shows the weather forecast in the calendar menu [Regression potential] - Weather forecast is totally broken now and can't be more broken. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
I'm experiencing the bug and opened a bug with the relevant system details automatically attached, it's bug 1929456. Hope this may help. -- 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/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Incomplete Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929456] [NEW] XrandR does not propose 21:9 resolution
Public bug reported: If come here over bug 1895301 "XrandR does not propose 3440x1440 21:9 resolution". In bug 1895301 sombody wrote "We just need one person experiencing the bug to open a bug with the relevant system details automatically attached." - so I did. I have a similar problem with a 21:9 monitor with a resolution of 2560x1080. It's a LG 25UB55-B on a HP docking station A7E32A, DVI output with adapter to HDMI, HDMI cable and input to the monitor via HDMI. Laptop is an HP Elitebook 8440p (Intel i5-520 with Intel HD Graphics (ILK)), internal display with 1366*768 is in use as well. I had Ubuntu 18.04 LTS before until January this year, with automatic updates on, so presumably up to date. There it worked fine out of the box, i.e. since first install I had the full resolution of 21:9 in 2560x1080 on my external monitor. I didn't change any hardware, just installed Ubuntu 20.04 from DVD, an it stopped working. I got only 16:9 with 1920x1080. I've updated to Ubuntu 20.10, tried Ubuntu 21.04 (from DVD as well), changed cable and adapter, nothing helped. Did some reseach with google and found the mentioned bug 1895301. The workaround worked, I got full resolution of 2560x1080 on the external display. It is not permanent, so at the moment of filing this bug, I'm still back on the 16:9 with 1920x1080. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Mon May 24 20:23:52 2021 DistUpgraded: 2021-05-23 15:18:23,444 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:172a] InstallationDate: Installed on 2021-02-10 (103 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP EliteBook 8440p ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-53-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2021-05-23 (1 days ago) dmi.bios.date: 09/13/2013 dmi.bios.release: 15.36 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.24 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.34 dmi.chassis.asset.tag: CZC040C94D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 48.52 dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.24:bd09/13/2013:br15.36:efr48.52:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.34:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8440p dmi.product.sku: J2544631 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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 groovy third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1929456 Title: XrandR does not propose 21:9 resolution Status in xorg package in Ubuntu: New Bug description: If come here over bug 1895301 "XrandR does not propose 3440x1440 21:9 resolution". In bug 1895301 sombody wrote "We just need one person experiencing the bug to open a bug with the relevant system details automatically attached." - so I did. I have a similar problem with a 21:9 monitor with a resolution of 2560x1080. It's a LG 25UB55-B on a HP docking station A7E32A, DVI output with adapter to HDMI, HDMI cable and input to the monitor via
[Desktop-packages] [Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore
** Summary changed: - Weather forecast and info is not available any more + (Update libgweather to 3.36.2) Weather forecast and info is not available anymore -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Confirmed Status in libgweather package in Ubuntu: Confirmed Status in gnome-weather package in Fedora: New Bug description: The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://developer.yr.no/doc/guides/getting-started-from-forecast-xml/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309535] Re: Running without pam-kwallet installed issues a warning in auth.log
The correct way to fix this issue is not to comment out the lines mentioning kwallet, but to make the modules silent by prepending a '-' (dash) to each line. Example: # /etc/pam.d/lightdm -authoptionalpam_kwallet.so -authoptionalpam_kwallet5.so -session optionalpam_kwallet.so auto_start -session optionalpam_kwallet5.so auto_start Same in /etc/pam.d/lightdm-greeter. This feature is mentioned in the pam.conf(5) manpage: If the type value from the list above is prepended with a - character the PAM library will not log to the system log if it is not possible to load the module because it is missing in the system. This can be useful especially for modules which are not always installed on the system and are not required for correct authentication and authorization of the login session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1309535 Title: Running without pam-kwallet installed issues a warning in auth.log Status in lightdm package in Ubuntu: Won't Fix Status in pam package in Ubuntu: Won't Fix Bug description: After upgrading to lightdm 1.10.0-0ubuntu2 I started to see this error in auth.log: Apr 10 14:34:54 simon-laptop lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Apr 10 14:34:54 simon-laptop lightdm: PAM adding faulty module: pam_kwallet.so This seems like a regression because with lightdm 1.10.0-0ubuntu1 or before I didn't have this error showing. FYI, I don't have the pam- kwallet package installed. $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy lightdm pam-kwallet lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 18 09:12:37 2014 InstallationDate: Installed on 2014-01-26 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1309535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
@Hui Wang, the alsa-info.txt for Yoga C930 is here http://alsa-project.org/db/?f=1ffb1551a46965865ee272cef105769e879397c7 -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918044] Re: Weather forecast and info is not available any more
"libgweather 3.36.2 is published" Seems this is fixed in the latest 3.36 release https://gitlab.gnome.org/GNOME/libgweather/-/blob/a18ae04879704e65c0ac858cbbfa451a22e8745c/NEWS -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1918044 Title: Weather forecast and info is not available any more Status in libgweather: Unknown Status in gnome-weather package in Ubuntu: Confirmed Status in libgweather package in Ubuntu: Confirmed Status in gnome-weather package in Fedora: New Bug description: The weather forecast is not available since one week now. Also, the weather info is gone from gnome-shell. The weather service provider retired their old API. https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/ https://developer.yr.no/doc/guides/getting-started-from-forecast-xml/ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Mar 7 09:54:52 2021 InstallationDate: Installed on 2020-04-26 (314 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1918044/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929343] Re: Alt-Shift-Tab to Switch Windows in reverse direction not working
So this seems to be a duplicate of this one: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/36812 -- 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/1929343 Title: Alt-Shift-Tab to Switch Windows in reverse direction not working Status in gnome-shell package in Ubuntu: Incomplete Bug description: I remember back in Ubuntu 14 (or 16) I was able to press Alt-Tab and then hold Shift to move across the windows in reverse direction. Now in Ubuntu 20.10 this no longer works. However, moving between applications (Super-Tab) does work in forward as well as reverse direction (while holding Shift). This is annoying when moving across many windows quickly, I sometimes "overshoot" by one, and then have to cycle all the way around again. So hereby a request to implement Alt-Shift-Tab for work similarly to Super-Shift-Tab. Release: Ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929343/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929343] Re: Alt-Shift-Tab to Switch Windows in reverse direction not working
I have no custom extensions installed. Found it - in Gnome Tweaks I configured keyboard layout switching using the Alt+Shift key combination. Changing it to another one "fixes" Alt- Shift-Tab. That sounds strange - why would that have an effect on Alt-Tab? In Windows Alt+Shift is the standard layout switch key combination *and* Alt-Shift-Tab also works somehow. -- 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/1929343 Title: Alt-Shift-Tab to Switch Windows in reverse direction not working Status in gnome-shell package in Ubuntu: Incomplete Bug description: I remember back in Ubuntu 14 (or 16) I was able to press Alt-Tab and then hold Shift to move across the windows in reverse direction. Now in Ubuntu 20.10 this no longer works. However, moving between applications (Super-Tab) does work in forward as well as reverse direction (while holding Shift). This is annoying when moving across many windows quickly, I sometimes "overshoot" by one, and then have to cycle all the way around again. So hereby a request to implement Alt-Shift-Tab for work similarly to Super-Shift-Tab. Release: Ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1929343/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879183] Re: Cheese does not show preferences/options/menus to non-GNOME Users
After 9 months, the patch has finally been accepted in the upstream repo. https://gitlab.gnome.org/GNOME/cheese/-/commit/e42a3e55d4d82984779ce8a86aaa805897c9e438 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1879183 Title: Cheese does not show preferences/options/menus to non-GNOME Users Status in cheese package in Ubuntu: Fix Released Status in cheese source package in Focal: Fix Released Status in cheese package in Debian: New Bug description: [Impact] Cheese no longer displays its menu button on non-GNOME desktop environments. https://gitlab.gnome.org/GNOME/cheese/-/issues/62 Xubuntu uses cheese as its default camera program. Advanced users can still change these settings through dconf-editor, but this is neither convenient nor intuitive. [Test Case] Use the cheese program in Xubuntu/xfce, Kubuntu/KDE or other non-GNOME desktop environments. Notice missing menu in titlebar. [Regression Potential] The most likely regression would be if the patch disabled the menu in GNOME. Testing has not shown this to be an issue. [ORIGINAL REPORT] Cheese has removed the GUI method of accessing preferences for non-GNOME users. https://github.com/GNOME/cheese/commit/48882da6a6dc4fc1c19e15f5210c9e10feb67ff5#diff-b2b45275b16940829b5f6f068943108d I'm not sure if upstream cheese devs care enough to fix it: https://gitlab.gnome.org/GNOME/cheese/-/issues/62 https://gitlab.gnome.org/GNOME/cheese/-/issues/52 Should Xubuntu default to a different camera program, such as guvcview? (Partial?) WORKAROUND is to use dconf-editor: dconf-editor /org/gnome/cheese To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1879183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767817] Re: Full text search does not work
I am on Ubuntu 20.04 and it worked right after the release. I also thought that it stopped working but it is an selection option in the search bar from Nautilus: Click on the arrow on the right of the serach bar and then you can choose for search "Full text" or "File name". Full text search is working for me in Ubuntu 20.04. -- 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/1767817 Title: Full text search does not work Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Bionic: Fix Released Status in nautilus source package in Cosmic: Fix Released Bug description: * Impact The text search feature, which is depending on tracker, is not working even when the service is installed * Test case - install tracker and restart your session - echo 'Nautilus is great' > ~/txt - open nautilus and type 'great' in the search entry -> the file should be listed * Regression potential That's changing the search provider logic, make sure that searching for file without tracker still works (that only look at filenames) and there is no extra logging/cpu usage --- Background: I have installed Tracker. It has finished indexing. I can also use Tracker's command line interface to search by content. 1. Description: Ubuntu 18.04 LTS Release: 18.04 2. nautilus: Installed: 1:3.26.3-0ubuntu4 Candidate: 1:3.26.3-0ubuntu4 Version table: *** 1:3.26.3-0ubuntu4 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. I expect to be able to search files by content from Nautilus, because this feature worked in 17.10. 4. I get no results from full text search unless the search matches file names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926047] Update Released
The verification of the Stable Release Update for fonts-noto-color-emoji has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1926047 Title: [SRU 缾] Update to 20200916 (to support missing emojis from unicode 13.1) Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Focal: Fix Released Bug description: [ Impact ] Many new emoji supported by various social platforms are not currently visible in Ubuntu 20.04, because of old font (even though the shipped ICU supports this version). here's a list for Unicode 13.0 and 13.1: - https://emojipedia.org/emoji-13.0/ - https://emojipedia.org/emoji-13.1/ [ Test Plan ] 1. After installing the update, visit https://unicode.org/emoji/charts/full-emoji-list.html The browser column should match the Google column 2. You can also use the Characters app shipped by default to verify that the emoji seem to work ok. This sentence should end asking "what do you want?" in the Italian way: 奈 [ Regression potential ] Emoji using a different composition not supported by 20.04 may show as multiple icons instead than as a single emoji. No emoji are shown when they used to be visible. This is easily comparable using https://unicode.org/emoji/charts/full- emoji-list.html where "Google" should match "Browser". python3-nototools has no rdepends and the only one Build-Depend is fonts-noto-color-emoji itself, so updating it has no effect either. Even though in this case is not needed. The design of some icons has been updated (compare browser with google columns at https://i.imgur.com/HkA3kOz.jpg), overall the look is consistent though and given that these are not part of any documentation or relevant component it's not something that needs an UFe. -- Note: Building the package with focal version of nototools is fine because fonts-noto-color-emoji depends on newer version only for tests and metadata checks which is not needed by our builds. This can be easily checked by diffing the resulting ttf extracting the data with ttx, which is in fact matching (for what it concerns real data). PPA for testing: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4534 A previous discussion on this was also done as part of bug #1870794 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1926047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926047] Re: [SRU 缾] Update to 20200916 (to support missing emojis from unicode 13.1)
This bug was fixed in the package fonts-noto-color-emoji - 0~20200916-1~ubuntu20.04.1 --- fonts-noto-color-emoji (0~20200916-1~ubuntu20.04.1) focal; urgency=medium * Backport to focal (LP: #1926047): Take advantage of ICU 66 supporting Unicode 13 to update the emoji font to the latest version, supporting various new characters. * debian/control: Downgrade build dependency on nototools 0.2.0 It is not needed for the pure ttf generation from PNGs, while the version already available in focal is good enough for that. In fact using a more recent version of nototools (that contains the latest unicode data) would be needed only for a full build of the emoji package (that includes medatada such as html pages) or if the sequence check was enabled. This is not the case for us as we already explicitly disabled it in debian/rules. * debian/control: Switch maintainer to ubuntu fonts-noto-color-emoji (0~20200916-1) unstable; urgency=medium * New upstream release - This major update introduces support for the Unicode 13.1 standard https://emojipedia.org/google/android-11.0/ https://blog.emojipedia.org/217-new-emojis-in-final-list-for-2021/ * Bump minimum python3-nototools to 0.2.13 * Set required VIRTUAL_ENV variable when building the font * Bypass sequence checks when building * Add patch to make build more verbose (Closes: #923621) -- Marco Trevisan (Treviño) Sun, 25 Apr 2021 06:46:50 +0200 ** Changed in: fonts-noto-color-emoji (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto-color-emoji in Ubuntu. https://bugs.launchpad.net/bugs/1926047 Title: [SRU 缾] Update to 20200916 (to support missing emojis from unicode 13.1) Status in fonts-noto-color-emoji package in Ubuntu: Fix Released Status in fonts-noto-color-emoji source package in Focal: Fix Released Bug description: [ Impact ] Many new emoji supported by various social platforms are not currently visible in Ubuntu 20.04, because of old font (even though the shipped ICU supports this version). here's a list for Unicode 13.0 and 13.1: - https://emojipedia.org/emoji-13.0/ - https://emojipedia.org/emoji-13.1/ [ Test Plan ] 1. After installing the update, visit https://unicode.org/emoji/charts/full-emoji-list.html The browser column should match the Google column 2. You can also use the Characters app shipped by default to verify that the emoji seem to work ok. This sentence should end asking "what do you want?" in the Italian way: 奈 [ Regression potential ] Emoji using a different composition not supported by 20.04 may show as multiple icons instead than as a single emoji. No emoji are shown when they used to be visible. This is easily comparable using https://unicode.org/emoji/charts/full- emoji-list.html where "Google" should match "Browser". python3-nototools has no rdepends and the only one Build-Depend is fonts-noto-color-emoji itself, so updating it has no effect either. Even though in this case is not needed. The design of some icons has been updated (compare browser with google columns at https://i.imgur.com/HkA3kOz.jpg), overall the look is consistent though and given that these are not part of any documentation or relevant component it's not something that needs an UFe. -- Note: Building the package with focal version of nototools is fine because fonts-noto-color-emoji depends on newer version only for tests and metadata checks which is not needed by our builds. This can be easily checked by diffing the resulting ttf extracting the data with ttx, which is in fact matching (for what it concerns real data). PPA for testing: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4534 A previous discussion on this was also done as part of bug #1870794 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-color-emoji/+bug/1926047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902898] Update Released
The verification of the Stable Release Update for ubuntu-settings has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1902898 Title: power-button action inconsistent between user session and greeter Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Focal: Fix Released Status in ubuntu-settings source package in Hirsute: Fix Released Bug description: [Impact] When a user is logged in to the Ubuntu desktop, a power button event will cause the user to be prompted to choose if they'd like to proceed with a shutdown. However, if the system is sitting at a greeter screen, a power button event will instead attempt a suspend w/o prompting. This is due to a different set of defaults for the greeter and the user. This is a fix for this, aligning all power actions between the greeter behaviour and the user session one on the user session. [Test Plan] 1. Install new package and reboot 2. On the greeter screen (gdm), press the physical power button of your machine. 3. You should be now prompted about what to do, like shutdown. You can dismiss it. 4. Clicking on the physical suspend button should suspend the machine immediatly. [Where problems could occur] We change the scope of when we applied those settings: we were only applying them to the GNOME session ran by the user, and it will now be applied as default to the GNOME session ran by gdm. Impacts is thus limited to the greeter screen. Diff is available on this commit: https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu-settings/commit/?h=focal=ca2f9aa9b03862ff044b64d7ef9506ca87e3dd89 -- Original report content: For a logged-in desktop user, they see: $ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'interactive' But the gdm user sees: $ sudo machinectl shell gdm@ /bin/bash Connected to the local host. Press ^] three times within 1s to exit session. gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'suspend' Changing the gdm user's setting to "interactive" using gsettings causes the greeter to begin prompting, consistent with the logged in user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter
This bug was fixed in the package ubuntu-settings - 20.04.6 --- ubuntu-settings (20.04.6) focal; urgency=medium * debian/ubuntu-settings.gsettings-override: - use the same power options between session and greeter. (LP: #1902898) -- Didier Roche Fri, 30 Apr 2021 09:01:06 +0200 ** Changed in: ubuntu-settings (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1902898 Title: power-button action inconsistent between user session and greeter Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Focal: Fix Released Status in ubuntu-settings source package in Hirsute: Fix Released Bug description: [Impact] When a user is logged in to the Ubuntu desktop, a power button event will cause the user to be prompted to choose if they'd like to proceed with a shutdown. However, if the system is sitting at a greeter screen, a power button event will instead attempt a suspend w/o prompting. This is due to a different set of defaults for the greeter and the user. This is a fix for this, aligning all power actions between the greeter behaviour and the user session one on the user session. [Test Plan] 1. Install new package and reboot 2. On the greeter screen (gdm), press the physical power button of your machine. 3. You should be now prompted about what to do, like shutdown. You can dismiss it. 4. Clicking on the physical suspend button should suspend the machine immediatly. [Where problems could occur] We change the scope of when we applied those settings: we were only applying them to the GNOME session ran by the user, and it will now be applied as default to the GNOME session ran by gdm. Impacts is thus limited to the greeter screen. Diff is available on this commit: https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu-settings/commit/?h=focal=ca2f9aa9b03862ff044b64d7ef9506ca87e3dd89 -- Original report content: For a logged-in desktop user, they see: $ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'interactive' But the gdm user sees: $ sudo machinectl shell gdm@ /bin/bash Connected to the local host. Press ^] three times within 1s to exit session. gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'suspend' Changing the gdm user's setting to "interactive" using gsettings causes the greeter to begin prompting, consistent with the logged in user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922731] Update Released
The verification of the Stable Release Update for gnome-disk-utility has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1922731 Title: SRU the current 3.36.3 stable update Status in gnome-disk-utility package in Ubuntu: Fix Released Status in gnome-disk-utility source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including a bugfix and some translation updates https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Use the disks utility to write an ISO to an usb stick, create and change some partitions. * Regression potential There is a fix to the partition creating code so special verification should go to this feature To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1922731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter
Dann, please be sure to always include the version number of the package you have tested next time! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1902898 Title: power-button action inconsistent between user session and greeter Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-settings source package in Focal: Fix Released Status in ubuntu-settings source package in Hirsute: Fix Released Bug description: [Impact] When a user is logged in to the Ubuntu desktop, a power button event will cause the user to be prompted to choose if they'd like to proceed with a shutdown. However, if the system is sitting at a greeter screen, a power button event will instead attempt a suspend w/o prompting. This is due to a different set of defaults for the greeter and the user. This is a fix for this, aligning all power actions between the greeter behaviour and the user session one on the user session. [Test Plan] 1. Install new package and reboot 2. On the greeter screen (gdm), press the physical power button of your machine. 3. You should be now prompted about what to do, like shutdown. You can dismiss it. 4. Clicking on the physical suspend button should suspend the machine immediatly. [Where problems could occur] We change the scope of when we applied those settings: we were only applying them to the GNOME session ran by the user, and it will now be applied as default to the GNOME session ran by gdm. Impacts is thus limited to the greeter screen. Diff is available on this commit: https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu-settings/commit/?h=focal=ca2f9aa9b03862ff044b64d7ef9506ca87e3dd89 -- Original report content: For a logged-in desktop user, they see: $ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'interactive' But the gdm user sees: $ sudo machinectl shell gdm@ /bin/bash Connected to the local host. Press ^] three times within 1s to exit session. gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power power-button-action 'suspend' Changing the gdm user's setting to "interactive" using gsettings causes the greeter to begin prompting, consistent with the logged in user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1902898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922731] Re: SRU the current 3.36.3 stable update
This bug was fixed in the package gnome-disk-utility - 3.36.3-0ubuntu1 --- gnome-disk-utility (3.36.3-0ubuntu1) focal; urgency=medium * New stable version (lp: #1922731) -- Sebastien Bacher Tue, 06 Apr 2021 15:36:32 +0200 ** Changed in: gnome-disk-utility (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1922731 Title: SRU the current 3.36.3 stable update Status in gnome-disk-utility package in Ubuntu: Fix Released Status in gnome-disk-utility source package in Focal: Fix Released Bug description: * Impact That's the current GNOME stable update, including a bugfix and some translation updates https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/blob/gnome-3-36/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Use the disks utility to write an ISO to an usb stick, create and change some partitions. * Regression potential There is a fix to the partition creating code so special verification should go to this feature To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1922731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924888] Re: gnome-disks can't create exfat partitions on Hirsute with the Samsung provided tools.
This bug was fixed in the package udisks2 - 2.9.2-1ubuntu1 --- udisks2 (2.9.2-1ubuntu1) hirsute; urgency=medium * debian/patches/git_dosfstools_4.2.patch: * debian/patches/git_dosfstools_4.2-reread_part.patch: - cherrypick commits to improve the compatibility with dosfstools 4.2 fix the formatting of vfat devices (lp: #1925822) * debian/patches/git_exfatprogs_compat.patch: - create exfat filesystems in a way that is compatible with exfatprogs (lp: #1924888) -- Sebastien Bacher Tue, 27 Apr 2021 10:16:27 +0200 ** Changed in: udisks2 (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1924888 Title: gnome-disks can't create exfat partitions on Hirsute with the Samsung provided tools. Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Hirsute: Fix Released Bug description: * Impact When on Hirsute with the new Samsung provided exfat support, gnome-disks can't create new exfat partitions due to being hardcoded to use the old mkexfatfs program from the exfat-utils package. The solution is to use mkfs.exfat which is provided by the old exfat-utils as well as the new exfatprogs. * Test Case - connect a device to format of your choice - $ apt install exfatprogs - start gnome-disks - select the device or partition to format - select other -> exfat as filesystem type - confirm the format -> the device should get formatted without error * Impact The change is in the section defining the commands to use for exfat so limited to this filesystem. Check that changing label or formatting is working with exfatprogs but also keeps working with exfat-utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1924888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1924888] Update Released
The verification of the Stable Release Update for udisks2 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1924888 Title: gnome-disks can't create exfat partitions on Hirsute with the Samsung provided tools. Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Hirsute: Fix Released Bug description: * Impact When on Hirsute with the new Samsung provided exfat support, gnome-disks can't create new exfat partitions due to being hardcoded to use the old mkexfatfs program from the exfat-utils package. The solution is to use mkfs.exfat which is provided by the old exfat-utils as well as the new exfatprogs. * Test Case - connect a device to format of your choice - $ apt install exfatprogs - start gnome-disks - select the device or partition to format - select other -> exfat as filesystem type - confirm the format -> the device should get formatted without error * Impact The change is in the section defining the commands to use for exfat so limited to this filesystem. Check that changing label or formatting is working with exfatprogs but also keeps working with exfat-utils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1924888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925822] Update Released
The verification of the Stable Release Update for udisks2 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1925822
Title:
[21.04 regression] formatting vfat times out
Status in udisks2 package in Ubuntu:
Fix Released
Status in udisks2 source package in Hirsute:
Fix Released
Bug description:
* Impact
Formatting devices to vfat fails in some cases due to an
incompatibility with the new dosfstools version
* Test case
see comment #5
or
- $ sudo modprobe scsi_debug
- check what device is assigned
- $ sudo busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/DEVNAME org.freedesktop.UDisks2.Block
Format 'sa{sv}' vfat 0
(replace DEVNAME by the actual device name, 'sdc' for example)
the formatting should work which you can verify by
- $ blkid -p /dev/DEVNAME
* Regression potential
The changes is specific to vfat handling so that's the feature to
focus on while testing, make sure than creating, deleting, renaming
vfat partitions from gnome-disks is working.
[racb] An upstream "precautionary" partprobe is being added following
the mkfs for vfat, when it didn't do this before. This is a change in
behaviour that might expose a problem elsewhere.
There is a regression somewhere between udisks, udev, and dosfstools.
Formatting a device with vfat hangs and fails:
# blkid -p /dev/sda
(nothing)
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
'sa{sv}' vfat 0
(long pause)
Call failed: Error synchronizing after formatting with type `vfat': Timed out
waiting for object
# blkid -p /dev/sda
/dev/sda: PTUUID="3690494f" PTTYPE="dos"
OTOH, formatting as ext4 works fine:
# wipefs -a /dev/sda; wipefs -a /dev/sda
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
'sa{sv}' ext4 0
(immediately succeeds)
# blkid -p /dev/sda
/dev/sda: UUID="8bea7475-6af5-4835-86d0-0e5b2cb5500e" VERSION="1.0"
BLOCK_SIZE="4096" TYPE="ext4" USAGE="filesystem"
I tested this to a QEMU emulated disk, but it reproduces equally well
against a `modprobe scsi_debug` device.
Package: udisks2 2.9.2-1
DistroRelease: Ubuntu 21.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1925822/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925822] Re: [21.04 regression] formatting vfat times out
This bug was fixed in the package udisks2 - 2.9.2-1ubuntu1
---
udisks2 (2.9.2-1ubuntu1) hirsute; urgency=medium
* debian/patches/git_dosfstools_4.2.patch:
* debian/patches/git_dosfstools_4.2-reread_part.patch:
- cherrypick commits to improve the compatibility with dosfstools 4.2
fix the formatting of vfat devices (lp: #1925822)
* debian/patches/git_exfatprogs_compat.patch:
- create exfat filesystems in a way that is compatible with exfatprogs
(lp: #1924888)
-- Sebastien Bacher Tue, 27 Apr 2021 10:16:27
+0200
** Changed in: udisks2 (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1925822
Title:
[21.04 regression] formatting vfat times out
Status in udisks2 package in Ubuntu:
Fix Released
Status in udisks2 source package in Hirsute:
Fix Released
Bug description:
* Impact
Formatting devices to vfat fails in some cases due to an
incompatibility with the new dosfstools version
* Test case
see comment #5
or
- $ sudo modprobe scsi_debug
- check what device is assigned
- $ sudo busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/DEVNAME org.freedesktop.UDisks2.Block
Format 'sa{sv}' vfat 0
(replace DEVNAME by the actual device name, 'sdc' for example)
the formatting should work which you can verify by
- $ blkid -p /dev/DEVNAME
* Regression potential
The changes is specific to vfat handling so that's the feature to
focus on while testing, make sure than creating, deleting, renaming
vfat partitions from gnome-disks is working.
[racb] An upstream "precautionary" partprobe is being added following
the mkfs for vfat, when it didn't do this before. This is a change in
behaviour that might expose a problem elsewhere.
There is a regression somewhere between udisks, udev, and dosfstools.
Formatting a device with vfat hangs and fails:
# blkid -p /dev/sda
(nothing)
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
'sa{sv}' vfat 0
(long pause)
Call failed: Error synchronizing after formatting with type `vfat': Timed out
waiting for object
# blkid -p /dev/sda
/dev/sda: PTUUID="3690494f" PTTYPE="dos"
OTOH, formatting as ext4 works fine:
# wipefs -a /dev/sda; wipefs -a /dev/sda
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
'sa{sv}' ext4 0
(immediately succeeds)
# blkid -p /dev/sda
/dev/sda: UUID="8bea7475-6af5-4835-86d0-0e5b2cb5500e" VERSION="1.0"
BLOCK_SIZE="4096" TYPE="ext4" USAGE="filesystem"
I tested this to a QEMU emulated disk, but it reproduces equally well
against a `modprobe scsi_debug` device.
Package: udisks2 2.9.2-1
DistroRelease: Ubuntu 21.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1925822/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926942] Update Released
The verification of the Stable Release Update for gnome-disk-utility has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1926942 Title: SRU the current 40.1 stable update Status in gnome-disk-utility package in Ubuntu: Fix Released Status in gnome-disk-utility source package in Hirsute: Fix Released Bug description: * Impact That's the current GNOME stable update, including a bugfix and some translation updates https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/blob/gnome-40/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Use the disks utility to write an ISO to an usb stick, create and change some partitions. * Regression potential There is a fix to the image restoring feature, check that it's working as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1926942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926941] Re: SRU the current 40.1 stable update
This bug was fixed in the package gnome-calculator - 1:40.1-0ubuntu1 --- gnome-calculator (1:40.1-0ubuntu1) hirsute; urgency=medium * New stable version (lp: #1926941) -- Sebastien Bacher Mon, 03 May 2021 10:40:10 +0200 ** Changed in: gnome-calculator (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1926941 Title: SRU the current 40.1 stable update Status in gnome-calculator package in Ubuntu: Fix Released Status in gnome-calculator source package in Hirsute: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-calculator/-/blob/gnome-40/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the different calculator mode still behave as expected * Regression potential There is a fix around currency conversion so verify that the feature still works correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1926941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926942] Re: SRU the current 40.1 stable update
This bug was fixed in the package gnome-disk-utility - 40.1-0ubuntu1 --- gnome-disk-utility (40.1-0ubuntu1) hirsute; urgency=medium * New stable version (lp: #1926942) -- Sebastien Bacher Mon, 03 May 2021 10:56:07 +0200 ** Changed in: gnome-disk-utility (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1926942 Title: SRU the current 40.1 stable update Status in gnome-disk-utility package in Ubuntu: Fix Released Status in gnome-disk-utility source package in Hirsute: Fix Released Bug description: * Impact That's the current GNOME stable update, including a bugfix and some translation updates https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/blob/gnome-40/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Use the disks utility to write an ISO to an usb stick, create and change some partitions. * Regression potential There is a fix to the image restoring feature, check that it's working as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1926942/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926941] Update Released
The verification of the Stable Release Update for gnome-calculator has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1926941 Title: SRU the current 40.1 stable update Status in gnome-calculator package in Ubuntu: Fix Released Status in gnome-calculator source package in Hirsute: Fix Released Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-calculator/-/blob/gnome-40/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the different calculator mode still behave as expected * Regression potential There is a fix around currency conversion so verify that the feature still works correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1926941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846790]
(In reply to Michael Warner from comment #6) > https://www.libreoffice.org/download/appimage/ Ah. How'd I miss that? For some reason I only found the PortableApps.com thing, which is Windows-only. Alrighty ... Appimage from the above URL, Basic-Fresh flavour, which gives the following version info Version: 7.1.3.2 / LibreOffice Community Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1 CPU threads: 24; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_UK); UI: en-US Calc: threaded is STILL AFFECTED by this bug, the behaviour is unchanged. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1846790 Title: [upstream] Saving files with a '#' in the name silently(!) fails on GVFS smb:// paths (Samba share) Status in LibreOffice: New Status in libreoffice package in Ubuntu: Confirmed Bug description: [Reported via ubuntu-bug, I'm assuming it has gathered all relevant system info. More, especially on the Samba server, if required, is available on request.] What I'm trying to do: Save a file whose name contains a '#' character to a Samba share accessed via a GVFS smb:// path. Ex. 1: Open a blank Writer (ODT) document, save that under the name "Test #1.odt" on a Samba share mounted via Nautilus. Ex. 2: Open a pre-existing file "Test #2.odt", either via Nautilus or File-Open, make some changes, save it & quit. What I'm expecting to happen: The file shows up under the assigned name on both the client and the Samba server (in case of a new file); or the existing file now contains the changes made (in case of an existing file being modified). Ex. 1: I'd expect to see "Test #1.odt" in the relevant directory. Ex. 2: I'd expect "Test #2.odt" to contain my changes. What happens instead: Ex. 1: LibreOffice actually saves the data in a file named "TFNZPF~F" as seen from the client, "Test " [note the space at the end] on the server. Ex. 2: The original file remains untouched, but a new file "TFNZPF~F" (client), or "Test " (server) is created with the saved data. Effectively, the save operation does not succeed -- without any error message. Analysis: This is based on experiments with more complex filenames. Somehow, when LibreOffice saves a file in this constellation, the filename gets truncated at the first '#', inclusive, first, suffix and all. (This in turn leaves a filename ending in a space, which isn't legal under Windows, so Samba's name mangling kicks in.) The problem does not occur with local files or on a sshfs-mount. Gedit has no problem even on smb://. It's unclear whether '#' is the only character affected. Some kind of URL handling/escaping bug in LibreOffice's GIO support? In any case, this cost me a day of work. (By the time I realised my changes hadn't actually been lost but landed in a new, cryptically- named file, I'd already recreated it to meet the deadline.) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-gnome 1:6.0.7-0ubuntu0.18.04.10 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 4 17:12:21 2019 InstallationDate: Installed on 2019-09-23 (10 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1846790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928932] Re: external monitor disabled upon editing file with vim
I see it: https://gitlab.gnome.org/GNOME/mutter/-/issues/1819 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1819 https://gitlab.gnome.org/GNOME/mutter/-/issues/1819 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1819 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: Incomplete => New -- 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/1928932 Title: external monitor disabled upon editing file with vim Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: This is the strangest bug I've encountered in my 20+ years of linux use. See a video of the bug at: https://drive.google.com/file/d/1StYD5kbL5pLRBOc6V-TXuE5DgymTdM0R/view?usp=sharing Using an external monitor I am editing a Snakefile with vim and syntax highlighting. Under certain condition the monitor will go to sleep. 0. download the Snakefile, vimrc, and the colorscheme that are the attached archive 1. move the colorscheme to ~/.vim/colors/ 1. `vim -u vimrc Snakefile` 2. delete one of the quotes, and see the external monitor go into sleep mode. Pertinent points: - If I disable the custom colorscheme or disable syntax highlighting there is no problem. - If I move the gnome-terminal onto the builtin display, then the external monitor reactivates. I wouldn't normally report this bug because it seems so specific to my setup. What is alarming is that a vim session in a gnome-terminal, under certain conditions, can cause the monitor to go to sleep! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libwayland-client0 1.18.0-2~exp1.1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Wed May 19 12:14:23 2021 DistUpgraded: 2021-04-27 09:44:28,765 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.11.0-16-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.11.0-17-generic, x86_64: installed facetimehd, 0.1, 5.11.0-16-generic, x86_64: installed facetimehd, 0.1, 5.11.0-17-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011b] InstallationDate: Installed on 2021-01-19 (119 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Apple Inc. MacBookAir6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=418e02d0-7fe0-4fe3-a1c4-ac2167ada4fe ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: Upgraded to hirsute on 2021-04-27 (22 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 02/22/2021 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 431.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvr431.0.0.0.0:bd02/22/2021:br0.1:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.family: MacBook Air dmi.product.name: MacBookAir6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1928001] Re: [SRU] New stable release 2.68.1
This bug was fixed in the package glib2.0 - 2.68.1-1~ubuntu21.04.1
---
glib2.0 (2.68.1-1~ubuntu21.04.1) hirsute; urgency=medium
* debian/{control,gbp.conf}: Update branch refs for hirsute
* Backport from Debian to hirsute for SRU (LP: #1928001)
glib2.0 (2.68.1-1) experimental; urgency=medium
* New upstream stable release
* d/tests/run-with-locales: Avoid FTBFS with locales-all installed
-- Iain Lane Mon, 10 May 2021 18:14:07 +0100
** Changed in: glib2.0 (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1928001
Title:
[SRU] New stable release 2.68.1
Status in glib2.0 package in Ubuntu:
Fix Released
Status in glib2.0 source package in Hirsute:
Fix Released
Bug description:
[ Description ]
Take this new upstream stable release.
* Fix a crash in `GKeyFile` when parsing a file which contains translations
using a `GKeyFile` instance which has loaded another file previously (#2361)
* Pin GIO DLL in memory on Windows (!2016)
* Bugs fixed:
- #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
- !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to
glib-2-68
- !2016 GIO W32: Pin gio DLL
- !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
- !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
- !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
- !2035 Backport !2026 “Split g_test_log() messages that contain multiple
lines” to glib-2-68
[ QA ]
Upstream release, so QA already performed by maintainers
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
This upload will trigger many autopkgtests that we expect to not be
regressed by this upload.
[ What could go wrong ]
This update contains fixes in multiple places so multiple apps could
be affected. The consequences of a broken GLib can range from some
functions returning bad results sometimes, which have minimal runtime
implications, up to the system simply crashing all the time.
Pretty much all parts of GNOME use GLib, so test anything in the
desktop that you can. If you reboot the machine and can get to the
desktop, that's already tested GLib extensively. But also run
applications like GNOME terminal, Files and Epiphany.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928001] Update Released
The verification of the Stable Release Update for glib2.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: Fix Released Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928001] Re: [SRU] New stable release 2.68.1
Hints committed, thanks for looking into that! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: Fix Released Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925095] Re: GNOME Desktop selection is misaligned with the mouse on 21.04-dev
This bug was fixed in the package gnome-shell-extension-desktop-icons-ng - 0.15.0-0ubuntu4.1 --- gnome-shell-extension-desktop-icons-ng (0.15.0-0ubuntu4.1) hirsute; urgency=medium [ Daniel van Vugt ] * Drop optimization desktopGrid_Get_the_latest_cursor_positon_on_motion.patch due to regressions (LP: #1925095, LP: #1923347) [ Gunnar Hjalmarsson ] * Fix typo in debian/watch. -- Daniel van Vugt Tue, 11 May 2021 14:08:42 +0800 ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1925095 Title: GNOME Desktop selection is misaligned with the mouse on 21.04-dev Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Fix Released Bug description: [Impact] When dragging the mouse while selected on the Desktop, the selection box is misaligned with the mouse pointer. The issue only started happening on 21.04 after upgrading from 20.04 to the dev version of the OS. [Test Plan] Drag the mouse on the desktop and ensure the corner of the selection box matches the mouse pointer position. [Where problems could occur] Anywhere in the desktop icons selection behaviour. Unlikely given all that is changing is the removal of an optional optimization. [Other Info] ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 19 22:00:22 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-12-28 (112 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-13 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1925095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923347] Re: Selecting an area on the desktop is broken on multi-monitor setups in X11
This bug was fixed in the package gnome-shell-extension-desktop-icons-ng - 0.15.0-0ubuntu4.1 --- gnome-shell-extension-desktop-icons-ng (0.15.0-0ubuntu4.1) hirsute; urgency=medium [ Daniel van Vugt ] * Drop optimization desktopGrid_Get_the_latest_cursor_positon_on_motion.patch due to regressions (LP: #1925095, LP: #1923347) [ Gunnar Hjalmarsson ] * Fix typo in debian/watch. -- Daniel van Vugt Tue, 11 May 2021 14:08:42 +0800 ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1923347 Title: Selecting an area on the desktop is broken on multi-monitor setups in X11 Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Fix Released Bug description: [Impact] This is a new bug as of yesterday or the day before. If I select an area on the desktop on my rightmost monitor, the origin point of the selection is placed correctly at the cursor position, but other point is offset by the width of the leftmost monitor (see attached screenshot). Basically, the origin point is correctly at (cursor X, cursor Y), but the other point is at (cursor X + monitor offset X, cursor Y + monitor offset Y). [Test Plan] Set up two monitors side-by-side and log into 'Ubuntu on Xorg'. Now on the rightmost monitor select an area of the desktop. Ensure the corner of the selection always matches the current cursor position. [Where problems could occur] Anywhere in the desktop icons selection behaviour. Unlikely given all that is changing is the removal of an optional optimization. [Other Info] ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 14:04:05 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-14 (574 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-01-07 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1923347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
This bug was fixed in the package gtk+3.0 - 3.24.25-1ubuntu4.1 --- gtk+3.0 (3.24.25-1ubuntu4.1) hirsute; urgency=medium * debian/patches/git_imcontext.patch: - cherry pick imcontext fixes until 3.24.29 (LP: #1925379) -- Rico Tzschichholz Sat, 01 May 2021 10:01:31 +0200 ** Changed in: gtk+3.0 (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Hirsute: Fix Released Bug description: * Impact The auto-correction in libreoffice is not action as it should * Test case see comment 9 * Regression potential The changes are in the input handling so check that standard input, keyboard layouts, compose and keybinding as worked as expected on different layout and language type, include ibus and chinese. I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
Thanks everyone. I can reproduce it now, even without ubuntu-dock. Looks like it is: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3969 but there are two flavours: - This is "normal" when opening the overview May 24 16:15:02 kab gnome-shell[5789]: value "nan" of type 'gfloat' is invalid or out of range for property 'x' of type 'gfloat' May 24 16:15:02 kab gnome-shell[5789]: value "nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat' May 24 16:15:02 kab gnome-shell[5789]: JS ERROR: Exception in callback for signal: shown: Error: Wrong type number; float expected. But it's out of range: -Infinity _init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16 _easeActor@resource:///org/gnome/shell/ui/environment.js:155:15 init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19 _syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21 _init/this._overviewShownId<@resource:///org/gnome/shell/ui/workspacesView.js:396:18 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 _showDone@resource:///org/gnome/shell/ui/overview.js:604:14 onComplete@resource:///org/gnome/shell/ui/overview.js:589:36 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64 - This appears to be the bug(?) - May 24 16:15:07 kab gnome-shell[5789]: value "nan" of type 'gfloat' is invalid or out of range for property 'x' of type 'gfloat' May 24 16:15:07 kab gnome-shell[5789]: value "nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat' May 24 16:15:07 kab gnome-shell[5789]: JS ERROR: Error: Wrong type number; float expected. But it's out of range: -Infinity _init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16 _easeActor@resource:///org/gnome/shell/ui/environment.js:155:15 init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19 _syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21 animateToOverview@resource:///org/gnome/shell/ui/workspacesView.js:577:18 animateToOverview@resource:///org/gnome/shell/ui/viewSelector.js:278:33 _animateVisible@resource:///org/gnome/shell/ui/overview.js:582:27 show@resource:///org/gnome/shell/ui/overview.js:568:14 toggle@resource:///org/gnome/shell/ui/overview.js:691:18 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:238:22 ** No longer affects: gnome-shell (Ubuntu) ** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => gnome- shell (Ubuntu) ** No longer affects: gnome-shell-extension-dash-to-panel (Ubuntu) ** Summary changed: - Overview sometimes fails to appear or disappear in 21.04 + Overview sometimes fails to appear or disappear in gnome-shell 3.38.4 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3969 Importance: Unknown Status: Unknown ** Also affects: gnome-shell (Ubuntu Impish) Importance: High Assignee: Daniel van Vugt (vanvugt) Status: In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38.4 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Hirsute: Confirmed Status in gnome-shell source package in Impish: In Progress Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not
[Desktop-packages] [Bug 1926100] Re: Hotspot (access point) is not working properly on two different wifi adapters.
Yes, both Wifi NICs support AP mode. So it's not a kernel bug. ** Package changed: linux (Ubuntu) => gnome-control-center (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1926100 Title: Hotspot (access point) is not working properly on two different wifi adapters. Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Wifi adapters: RALINK RT 5370 (RT5370) and RALINK RT 2070 (RT2070). Ubuntu 20.04.2 LTS. Kernel 5.8.0-50-generic. Motherboard GA78LMT. Expected behavior: that it would be possible to share the internet through the access point (hotspot) without any problems, through any of the adapters. Real behavior: The adapters work fine with good wifi signal, and sometimes the hotpost is possible. But most of the time the hotspot option is neither clickable nor selectable (gray). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: poe1877 F pulseaudio /dev/snd/controlC1: poe1877 F pulseaudio /dev/snd/pcmC1D0p: poe1877 F...m pulseaudio /dev/snd/controlC2: poe1877 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-04 (52 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal wayland-session Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-03-25 (31 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1926100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926620] Re: Gnome-Shell freezes when touchscreen is used in Wayland sessions
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3969 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3969 -- 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/1926620 Title: Gnome-Shell freezes when touchscreen is used in Wayland sessions Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: Gnome-Shell freezes when touchscreen is used on Dell Inspiron 2-in-1 running 21.04, the dock and the upper bar stop responding, while the windows keep running. The problem was notice after upgrade (do- release-upgrade -c) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Apr 29 15:58:43 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-03-01 (58 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-22 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1926620/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926100] [NEW] Hotspot (access point) is not working properly on two different wifi adapters.
You have been subscribed to a public bug: Wifi adapters: RALINK RT 5370 (RT5370) and RALINK RT 2070 (RT2070). Ubuntu 20.04.2 LTS. Kernel 5.8.0-50-generic. Motherboard GA78LMT. Expected behavior: that it would be possible to share the internet through the access point (hotspot) without any problems, through any of the adapters. Real behavior: The adapters work fine with good wifi signal, and sometimes the hotpost is possible. But most of the time the hotspot option is neither clickable nor selectable (gray). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: poe1877 F pulseaudio /dev/snd/controlC1: poe1877 F pulseaudio /dev/snd/pcmC1D0p: poe1877 F...m pulseaudio /dev/snd/controlC2: poe1877 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-04 (52 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal wayland-session Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-03-25 (31 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 20.04 access ap apport-collected focal ga78lmt hotspot internet lts point ralink rt2070 rt5370 share ubuntu wayland-session wifi wireless -- Hotspot (access point) is not working properly on two different wifi adapters. https://bugs.launchpad.net/bugs/1926100 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute) Status: Incomplete => Confirmed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Confirmed ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-dash-to-panel package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock source package in Hirsute: Confirmed Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
That's very good bad news. I can reproduce it now, thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell-extension-dash-to-panel package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Hirsute: Incomplete Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dash-to-panel/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
With downgraded version of ubuntu-dock the issue persists. I've found a way to reproduce it: 1) log in 2) press Super + A 3) select an App (Firefox, Files, Editor...) 4) press Super if I start same Apps from the dock, then no issue. I've tested it under Wayland. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell-extension-dash-to-panel package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Hirsute: Incomplete Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dash-to-panel/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1525477] Re: X server crash when pasting selection using middle button in Chromium
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1525477 Title: X server crash when pasting selection using middle button in Chromium Status in xorg package in Ubuntu: Won't Fix Bug description: Description: Ubuntu 14.04.3 LTS Release: 14.04 xorg 1:7.7+1ubuntu8.1 Select any text; use middle button to paste selection in Chromium (I observed it pasting in URL bar or in any form text input field, including previous attempt to report this bug :) ). Session crashes. It does not happen, when either pasting into different application (like terminal) or wen use Copy - Paste instead of middle button. I noticed it about a week ago, so it must be some recent change; I use selection paste often enough to notice something like this before. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-19.23~14.04.1-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 12 11:09:22 2015 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:062b] InstallationDate: Installed on 2015-07-02 (162 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. Latitude E5450 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-:128M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 06J17N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/19/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5450 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Dec 12 11:08:11 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1525477/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1541082] Re: [PowerMac3, 1] Blotchy GUI graphics for images
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1541082 Title: [PowerMac3,1] Blotchy GUI graphics for images Status in xorg package in Ubuntu: Won't Fix Bug description: The background image and other image files are blotchy. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: powerpc BootLog: fsck from util-linux 2.27.1 /dev/sda13: clean, 182266/1458176 files, 1099215/5826607 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rage 128 PRO AGP 4x TMDS [1002:5046] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-01-31 (154 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha powerpc (20160123) Lsusb: Bus 002 Device 004: ID 047d:1029 Kensington Mouse*in*a*Box Optical Elite Bus 002 Device 003: ID 05ac:0220 Apple, Inc. Aluminum Keyboard (ANSI) Bus 002 Device 002: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: powerpc ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=UUID=4eb514e5-48d7-4e99-a402-5294c80e78cc ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-24.43-powerpc-smp 4.4.10 Renderer: Software Tags: xenial ubuntu Uname: Linux 4.4.0-24-powerpc-smp ppc UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1541082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1570653] Re: LG 31MU97-B Black 31" 4K Monitor not detected properly
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1570653 Title: LG 31MU97-B Black 31" 4K Monitor not detected properly Status in xorg package in Ubuntu: Won't Fix Bug description: 4K monitor is not properly detected. using xfce desktop "Display" utility, my monitor is detected as "Goldstar Company Ltd 27" with a resolution of 3840x2160 and 60.0Hz The actual monitor is an LG 31MU97-B Black 31" with a resolution of 4096x2160. I'm pretty sure the Monitor's resolution was properly detected in 15.10 (4096x2160). It was called "Goldstar Company Ltd" but I do not recall which size was detected. (27" or 31") I remember seeing a 4K youtube video in 15.10 and noting the black bands on each side of the display, due to the difference between 3840 and 4096. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: 2016-04-14 20:11:08,467 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [1002:6811] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Curacao PRO [Radeon R7 370 / R9 270/370 OEM] [174b:e271] InstallationDate: Installed on 2015-11-24 (204 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) LightdmGreeterLog: upstart: indicator-application main process (2191) killed by TERM signal Invalid MIT-MAGIC-COOKIE-1 key LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (1802) killed by TERM signal MachineType: To be filled by O.E.M. To be filled by O.E.M. Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-lowlatency root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.40-lowlatency 4.4.8 Tags: xenial ubuntu Uname: Linux 4.4.0-22-lowlatency x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-15 (62 days ago) UserGroups: adm audio cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/08/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1529932] Re: X session crashes with EQ overflowing
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1529932 Title: X session crashes with EQ overflowing Status in X.Org X server: Unknown Status in xorg package in Ubuntu: Won't Fix Bug description: On my very old laptop, that is equipped with an Ati Mobility Radeon X700, sometimes (and, sadly, I have to use this word, because I found no regularity pattern for the occurrence of this bug) randomly the desktop session locks, that is I can only move the mouse pointer, but I cannot interact anymore with the desktop session. I am forced to login trough ssh from another pc and to restart the laptop. In Xorg.0.log I found these lines that are, in my opinion, related to the crash: (EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x5608e56a768e] (EE) 1: /usr/bin/X (mieqEnqueue+0x253) [0x5608e5689373] (EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x5608e5563152] (EE) 3: /usr/bin/X (xf86PostMotionEvent+0xd6) [0x5608e559a026] (EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x5322) [0x7f5e497b8322] (EE) 5: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x73d2) [0x7f5e497ba3d2] (EE) 6: /usr/bin/X (0x5608e54f3000+0x96ac8) [0x5608e5589ac8] (EE) 7: /usr/bin/X (0x5608e54f3000+0xbfc92) [0x5608e55b2c92] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e522c9000+0x352f0) [0x7f5e522fe2f0] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f5e523c60b7] (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f5e536ada08] (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f5e536b06cb] (EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x19c9) [0x7f5e4e3ae9c9] (EE) 13: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x1c0c) [0x7f5e4e3aec0c] (EE) 14: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f5e4e5b9000+0x26236) [0x7f5e4e5df236] (EE) 15: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x569b) [0x7f5e4d97869b] (EE) 16: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x7e8f) [0x7f5e4d97ae8f] (EE) 17: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x11953) [0x7f5e4d984953] (EE) 18: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xe770) [0x7f5e4d981770] (EE) 19: /usr/bin/X (0x5608e54f3000+0x13ca51) [0x5608e562fa51] (EE) 20: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0xf74f) [0x7f5e4d98274f] (EE) 21: /usr/bin/X (0x5608e54f3000+0x1332a2) [0x5608e56262a2] (EE) 22: /usr/bin/X (0x5608e54f3000+0x5818f) [0x5608e554b18f] (EE) 23: /usr/bin/X (0x5608e54f3000+0x5c34b) [0x5608e554f34b] (EE) 24: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f5e522e9a40] (EE) 25: /usr/bin/X (_start+0x29) [0x5608e55396c9] (EE) (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack. (EE) [mi] mieq is *NOT* the cause. It is a victim. (EE) [mi] EQ overflow continuing. 100 events have been dropped. (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x4e) [0x5608e56a768e] (EE) 1: /usr/bin/X (QueuePointerEvents+0x52) [0x5608e5563152] (EE) 2: /usr/bin/X (xf86PostMotionEvent+0xd6) [0x5608e559a026] (EE) 3: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x5322) [0x7f5e497b8322] (EE) 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f5e497b3000+0x73d2) [0x7f5e497ba3d2] (EE) 5: /usr/bin/X (0x5608e54f3000+0x96ac8) [0x5608e5589ac8] (EE) 6: /usr/bin/X (0x5608e54f3000+0xbfc92) [0x5608e55b2c92] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f5e522c9000+0x352f0) [0x7f5e522fe2f0] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (ioctl+0x7) [0x7f5e523c60b7] (EE) 9: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmIoctl+0x28) [0x7f5e536ada08] (EE) 10: /usr/lib/x86_64-linux-gnu/libdrm.so.2 (drmCommandWrite+0x1b) [0x7f5e536b06cb] (EE) 11: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x19c9) [0x7f5e4e3ae9c9] (EE) 12: /usr/lib/x86_64-linux-gnu/libdrm_radeon.so.1 (0x7f5e4e3ad000+0x1c0c) [0x7f5e4e3aec0c] (EE) 13: /usr/lib/xorg/modules/drivers/radeon_drv.so (0x7f5e4e5b9000+0x26236) [0x7f5e4e5df236] (EE) 14: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x569b) [0x7f5e4d97869b] (EE) 15: /usr/lib/xorg/modules/libexa.so (0x7f5e4d973000+0x7e8f) [0x7f5e4d97ae8f] (EE) 16:
[Desktop-packages] [Bug 1576784] Re: MatchIsTouchscreen also matches touchpads in 16.04
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1576784 Title: MatchIsTouchscreen also matches touchpads in 16.04 Status in xorg package in Ubuntu: Won't Fix Bug description: Previously in 15.10 I had the following rule in /usr/share/X11/xorg.conf.d/99-no-touchscreen.conf: Section "InputClass" Identifier "Touchscreen disable" MatchIsTouchscreen "on" Option "Ignore" "on" EndSection This worked in disabling the touchpad on my lenovo T440s After the upgrade to 16.04 I noticed that my touchpad would not work. And I found the following lines in the log: [ 3107.956] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event6) [ 3107.956] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "Touchscreen disable" [ 3107.956] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0) [ 3107.956] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "Touchscreen disable" So I had to disable the rule in order to be able to use the touchpad, and now I can't disable the touchscreen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Apr 29 09:39:23 2016 InstallationDate: Installed on 2015-03-18 (407 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-28 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1576784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1581270] Re: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1581270 Title: Hybrid Graphics: [drm:si_resume [radeon]] *ERROR* si startup failed on resume Status in xorg package in Ubuntu: Won't Fix Bug description: dmesg shows issues with being able to use the discrete graphics card (relevant dmesg lines attached). Grub does pass "radeon.modeset=1" but it doesn't seem to make a difference. If I pass both "radeon.modeset=1" and "radeon.startpm=1"to the kernel, then it does not error (except for the VCE error -110, which is probably harmless). Running `DRI_PRIME=1 glxgears`: - with "radeon.modeset=1" and "radeon.startpm=1", no error but only a black window with a visible top bar. - with just "radeon.modeset=1", error (attached as 'glxgears'). Results are similar on Ubuntu GNOME 16.04, except with "radeon.modeset=1" and "radeon.startpm=1" set. It works, but lots of screen tearing. Attached are relevant dmesg lines, grep'd with 'drm'. I'll also be attaching entire contents of dmesg, /var/log/syslog, etc., but TLDR: [ 22.916285] [drm] ring test on 0 succeeded in 2 usecs [ 22.916289] [drm] ring test on 1 succeeded in 1 usecs [ 22.916292] [drm] ring test on 2 succeeded in 1 usecs [ 22.916299] [drm] ring test on 3 succeeded in 3 usecs [ 22.916304] [drm] ring test on 4 succeeded in 3 usecs [ 23.092271] [drm] ring test on 5 succeeded in 2 usecs [ 23.092276] [drm] UVD initialized successfully. [ 23.092311] [drm] ib test on ring 0 succeeded in 0 usecs [ 23.092349] [drm] ib test on ring 1 succeeded in 0 usecs [ 23.092375] [drm] ib test on ring 2 succeeded in 0 usecs [ 23.092392] [drm] ib test on ring 3 succeeded in 0 usecs [ 23.092407] [drm] ib test on ring 4 succeeded in 0 usecs [ 33.241928] [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence wait failed (-35). [ 33.241948] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed testing IB on ring 5 (-35). lsb_release -rd: Description: Ubuntu 16.04 LTS Release: 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 12 20:43:03 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics Controller [144d:c0e6] Subsystem: Samsung Electronics Co Ltd Mars [Radeon HD 8670A/8670M/8750M] [144d:c0e6] InstallationDate: Installed on 2016-05-13 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: SAMSUNG ELECTRONICS CO., LTD. 870Z5E/880Z5E/680Z5E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=644ba363-51c7-419c-8544-2ff7be960f21 ro quiet splash radeon.modeset=1 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADH.017.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP680Z5E-X01US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADH.017.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn870Z5E/880Z5E/680Z5E:pvrP05ADH:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP680Z5E-X01US:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 870Z5E/880Z5E/680Z5E dmi.product.version: P05ADH dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A
[Desktop-packages] [Bug 1610666] Re: Mouse cursor moves choppy/doesn't update its position as it should
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end of standard support in April 2021: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 16.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1610666 Title: Mouse cursor moves choppy/doesn't update its position as it should Status in xorg package in Ubuntu: Won't Fix Bug description: Q. What I expected to happen? A. The mouse would run smoothly as it does run in windows. Q. What happened instead? A. The mouse lags moves choppy/doesn't update its position as it should Additional Information: Output of "xinput --list --short" ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ E-Signal USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ E-Signal USB Gaming Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Microsoft® LifeCam HD-3000 id=9[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] Output of "xinput --list-props 11" Device 'E-Signal USB Gaming Mouse': Device Enabled (133):1 Coordinate Transformation Matrix (135): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (259): 0 Device Accel Constant Deceleration (260):1.00 Device Accel Adaptive Deceleration (261):1.00 Device Accel Velocity Scaling (262): 10.00 Device Product ID (251): 1241, 41132 Device Node (252): "/dev/input/event4" Evdev Axis Inversion (263): 0, 0 Evdev Axes Swap (265): 0 Axis Labels (266): "Rel X" (143), "Rel Y" (144), "Rel Horiz Wheel" (257), "Rel Vert Wheel" (258) Button Labels (267): "Button Left" (136), "Button Middle" (137), "Button Right" (138), "Button Wheel Up" (139), "Button Wheel Down" (140), "Button Horiz Wheel Left" (141), "Button Horiz Wheel Right" (142), "Button Side" (255), "Button Extra" (256), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254), "Button Unknown" (254) Evdev Scrolling Distance (268): 1, 1, 1 Evdev Middle Button Emulation (269): 0 Evdev Middle Button Timeout (270): 50 Evdev Third Button Emulation (271): 0 Evdev Third Button Emulation Timeout (272): 1000 Evdev Third Button Emulation Button (273): 3 Evdev Third Button Emulation Threshold (274):20 Evdev Wheel Emulation (275): 0 Evdev Wheel Emulation Axes (276):0, 0, 4, 5 Evdev Wheel Emulation Inertia (277): 10 Evdev Wheel Emulation Timeout (278): 200 Evdev Wheel Emulation Button (279): 4 Evdev Drag Lock Buttons (280): 0 Output of "lsusb" Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 0bc2:3321 Seagate RSS LLC Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 04d9:a0ac Holtek Semiconductor, Inc. Bus 001 Device 003: ID 045e:0779 Microsoft Corp. LifeCam HD-3000 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Note : Holtek Semiconductor, Inc. is my mouse Also found this in dmesg : [ 292.597380] usb 1-1.4: new full-speed USB device number 5 using ehci-pci [ 293.941408] usb 1-1.4: New USB device found, idVendor=04d9, idProduct=a0ac [ 293.941413] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 293.941416] usb 1-1.4: Product: USB Gaming Mouse [ 293.941418] usb 1-1.4: Manufacturer: E-Signal [ 294.241702] input: E-Signal USB Gaming Mouse as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:04D9:A0AC.0004/input/input16 [ 294.242160] hid-generic 0003:04D9:A0AC.0004:
[Desktop-packages] [Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
We just need one person experiencing the bug to open a bug with the relevant system details automatically attached. That should be done by running: ubuntu-bug xorg or if you really want to reuse this bug then: apport-collect 1895301 Sorry, it seems no one at Canonical is affected. ** Changed in: xorg-server (Ubuntu) Status: Invalid => Incomplete -- 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/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Incomplete Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908341] Re: gnome-shell crashed with SIGSEGV in get_application_proxy() from g_task_return_now() from g_task_return() from init_second_async_cb() from g_task_return_now()
Dropping xenial; no longer supported (for free): https://wiki.ubuntu.com/Releases ** Tags removed: xenial -- 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/1908341 Title: gnome-shell crashed with SIGSEGV in get_application_proxy() from g_task_return_now() from g_task_return() from init_second_async_cb() from g_task_return_now() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.1-1ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/1614f6f99fae747f6d3291c5cdbc46a816cc5025 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
I wonder if this is cause by the fix for bug 1919972. Please try installing: https://launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/68ubuntu20.10.1/+build/19931028/+files/gnome-shell-extension- ubuntu-dock_68ubuntu20.10.1_all.deb (which is a downgrade) and then log in again. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell-extension-dash-to-panel package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Hirsute: Incomplete Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dash-to-panel/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
Please give a little help here , all my clients have this bug, and no one at canonical can help to confirm it ? That is not serious ? -- 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/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Invalid Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
I'm now convinced this is not a gnome-shell or gjs bug, but more likely an ubuntu-dock bug. Comments #14 and #9 also confirm it, and that dash- to-panel is affected. ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-dash- to-panel (Ubuntu) ** No longer affects: gnome-shell-extension-dash-to-panel (Ubuntu Hirsute) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute) Status: Incomplete => Confirmed ** Changed in: gnome-shell-extension-dash-to-panel (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-shell-extension-dash-to-panel (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell-extension-dash-to-panel package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Hirsute: Incomplete Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dash-to-panel/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1577198] Re: Imported gpg keys do not show up in Seahorse 3.18.0
I am Experiencing Same issue !! When I import a GPG key in Seahorse it does not appears in Seahorse but when I list all gpg keys using `gpg --list-keys` command I can see my new key in output. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1577198 Title: Imported gpg keys do not show up in Seahorse 3.18.0 Status in seahorse: New Status in seahorse package in Ubuntu: Triaged Bug description: After clean install of Ubuntu-Gnome 16.04 LTS I tried to import all my previous exported gpg keys. Although it seems the keys are imported, they do not show up in seahorse (Passwords and Keys). Also Evolution did not find to proper keys to decrypt messages. It seems however that the keys have been imported under gpg1 in stead of gpg2. This can also be confirmed with the list command (gpg --list- key and gpg2 -- list-keys). Importing all keys by command (gpg2 --import Multiple_Keys.asc) seems to work. See also the same problem already reported by Andreas Happe on: https://www.snikt.net/blog/2016/02/27/evolution-seahorse-gpg-gpg2-woes/ To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/1577198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
Thanks again. When it comes to bugs "lower latency" methods of communication are not appropriate. Because we need a single permanent record of the discussion, which is here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell-extension-dash-to-panel package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock source package in Hirsute: Confirmed Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dash-to-panel/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
Anyone with monitor problems should open their own bug, thanks. ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Invalid -- 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/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Invalid Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
Incomplete due to blank Bug Description. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in pulseaudio package in Ubuntu: Incomplete Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895301] Re: XrandR does not propose 3440x1440 21:9 resolution
Anyone with a 21:9 monitor could apport this ? ** Changed in: xorg-server (Ubuntu) Status: Expired => Confirmed -- 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/1895301 Title: XrandR does not propose 3440x1440 21:9 resolution Status in xorg-server package in Ubuntu: Confirmed Bug description: XrandR does not propose 3440x1440 21:9 resolution on Ubuntu 20.04 : How to reproduce : - Connect on HDMI 1.4 Intel HD 630 mobile a UWUHD 3440x1440 monitor - Only 16:9 are proposed by xrandR - XrandR should propose all supported resolutions WorkAround : manually add the mode xrandr --newmode "3440x1440_30.00" 196.90 3440 3600 3960 4480 1440 1441 1444 1465 -HSync +Vsync xrandr --addmode HDMI-2 3440x1440_30.00 xrandr --output HDMI-2 --mode 3440x1440_30.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1895301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929376] [NEW] freezes on 'searching for drivers'
Public bug reported: change [printer] driver selected. then 'select printer from data base' clicked. freezes on 'searching for drivers'. choice to 'force quit' or 'wait' appears but 'searching for drivers ' message freezes over the 'force quit/wait' message. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: cups 2.3.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-54.61-generic 5.8.18 Uname: Linux 5.8.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 24 17:48:25 2021 InstallationDate: Installed on 2018-05-10 (1110 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) KernLog: Lpstat: device for HP_OfficeJet_8010_series_747033_: implicitclass://HP_OfficeJet_8010_series_747033_/ device for HP_OfficeJet_Pro_6970_C04CF1_USB_: hp:/usb/OfficeJet_Pro_6970?serial=TH6C753105 device for MG5400-series: usb://Canon/MG5400%20series?serial=30D4AD=1 MachineType: Hewlett-Packard 220-1010a Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MG5400-series.ppd', '/etc/cups/ppd/HP_OfficeJet_8010_series_747033_.ppd', '/etc/cups/ppd/HP_OfficeJet_Pro_6970_C04CF1_USB_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MG5400-series.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_8010_series_747033_.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_Pro_6970_C04CF1_USB_.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-54-generic root=UUID=3675aa14-c77b-4e55-9fe8-fb9631834d4b ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to groovy on 2021-02-26 (86 days ago) dmi.bios.date: 07/21/2011 dmi.bios.release: 7.2 dmi.bios.vendor: AMI dmi.bios.version: 7.02 dmi.board.asset.tag: 3CR1351T4R dmi.board.name: 2AC3 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02A dmi.chassis.asset.tag: 3CR1351T4R dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr7.02:bd07/21/2011:br7.2:svnHewlett-Packard:pn220-1010a:pvr1.02A:rvnPEGATRONCORPORATION:rn2AC3:rvr1.02A:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 220-1010a dmi.product.sku: QU221AA#ABG dmi.product.version: 1.02A dmi.sys.vendor: Hewlett-Packard ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1929376 Title: freezes on 'searching for drivers' Status in cups package in Ubuntu: New Bug description: change [printer] driver selected. then 'select printer from data base' clicked. freezes on 'searching for drivers'. choice to 'force quit' or 'wait' appears but 'searching for drivers ' message freezes over the 'force quit/wait' message. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: cups 2.3.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-54.61-generic 5.8.18 Uname: Linux 5.8.0-54-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 24 17:48:25 2021 InstallationDate: Installed on 2018-05-10 (1110 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) KernLog: Lpstat: device for HP_OfficeJet_8010_series_747033_: implicitclass://HP_OfficeJet_8010_series_747033_/ device for HP_OfficeJet_Pro_6970_C04CF1_USB_: hp:/usb/OfficeJet_Pro_6970?serial=TH6C753105 device for MG5400-series: usb://Canon/MG5400%20series?serial=30D4AD=1 MachineType: Hewlett-Packard 220-1010a Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MG5400-series.ppd', '/etc/cups/ppd/HP_OfficeJet_8010_series_747033_.ppd', '/etc/cups/ppd/HP_OfficeJet_Pro_6970_C04CF1_USB_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MG5400-series.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_8010_series_747033_.ppd: Permission denied grep: /etc/cups/ppd/HP_OfficeJet_Pro_6970_C04CF1_USB_.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-54-generic root=UUID=3675aa14-c77b-4e55-9fe8-fb9631834d4b ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to groovy on 2021-02-26 (86 days ago) dmi.bios.date: 07/21/2011 dmi.bios.release: 7.2 dmi.bios.vendor: AMI dmi.bios.version: 7.02 dmi.board.asset.tag: 3CR1351T4R dmi.board.name: 2AC3 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02A dmi.chassis.asset.tag: 3CR1351T4R dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard
