[Touch-packages] [Bug 1964349] [NEW] package linux-firmware 1.187.27 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Public bug reported: This is 16.04 updated to 20.04 with some Debian repositories glued on (for a non-Snap Chromium); I've come to expect the odd issue, but still reporting, in case. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.27 ProcVersionSignature: Ubuntu 5.4.0-97.110-generic 5.4.162 Uname: Linux 5.4.0-97-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1783 F pulseaudio /dev/snd/pcmC0D0p: pete 1783 F...m pulseaudio CasperMD5CheckResult: skip Date: Wed Mar 9 13:15:55 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=25544052-705f-413e-8821-a612310589eb InstallationDate: Installed on 2018-02-25 (1473 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 4291AB3 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-97-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.27 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET59WW (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291AB3 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: LTL0011096 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET59WW(1.29):bd04/02/2012:svnLENOVO:pn4291AB3:pvrThinkPadX220:rvnLENOVO:rn4291AB3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 dmi.product.name: 4291AB3 dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1964349 Title: package linux-firmware 1.187.27 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: This is 16.04 updated to 20.04 with some Debian repositories glued on (for a non-Snap Chromium); I've come to expect the odd issue, but still reporting, in case. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.27 ProcVersionSignature: Ubuntu 5.4.0-97.110-generic 5.4.162 Uname: Linux 5.4.0-97-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pete 1783 F pulseaudio /dev/snd/pcmC0D0p: pete 1783 F...m pulseaudio CasperMD5CheckResult: skip Date: Wed Mar 9 13:15:55 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=25544052-705f-413e-8821-a612310589eb InstallationDate: Installed on 2018-02-25 (1473 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 4291AB3 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-97-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.27 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET59WW (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 4291AB3 dmi.board.vendor: LENOVO dmi.board.version: Not Available
[Touch-packages] [Bug 1944404] [NEW] [HDA-Intel - HDA NVidia, playback] No sound at all
Public bug reported: Hi...my problem is that I am using the nVidia GTX card connected by HDMI cable to a widescreen Samsung monitor that doesn't have speakers. Ubuntu assumes I can use that to play audio. In reality I'm using stereo speakers connected to the "center" output from the rear of the computer. This works fine in windows, but not in Ubuntu 20.04. I've tried several fixes to similar looking issues on line, but still I don't get sound. The only option I have under settings is for the HDMI/DisplayPort 2 - GM107 High Definition audio controller [GE Force 940 MX]. I've tried an old solution by adding hdajackretask and I've tried adjusting volume levels using alsamixer, but those solutions didn't help. Anyone have any other ideas? Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: larry 11338 F pulseaudio /dev/snd/controlC2: larry 11338 F pulseaudio /dev/snd/controlC1: larry 11338 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 23:05:52 2021 PackageArchitecture: all ProcEnviron: 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:NVidia failed Symptom_Card: GM107 High Definition Audio Controller [GeForce 940MX] - HDA NVidia Symptom_Type: No sound at all Title: [HDA-Intel - HDA NVidia, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2019 dmi.bios.release: 64.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd05/31/2019:br64.14:svnDellInc.:pnXPS8700:pvr:sku0x05B7:rvnDellInc.:rn0KWVT8:rvrA03:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.product.sku: 0x05B7 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1944404 Title: [HDA-Intel - HDA NVidia, playback] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hi...my problem is that I am using the nVidia GTX card connected by HDMI cable to a widescreen Samsung monitor that doesn't have speakers. Ubuntu assumes I can use that to play audio. In reality I'm using stereo speakers connected to the "center" output from the rear of the computer. This works fine in windows, but not in Ubuntu 20.04. I've tried several fixes to similar looking issues on line, but still I don't get sound. The only option I have under settings is for the HDMI/DisplayPort 2 - GM107 High Definition audio controller [GE Force 940 MX]. I've tried an old solution by adding hdajackretask and I've tried adjusting volume levels using alsamixer, but those solutions didn't help. Anyone have any other ideas? Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: larry 11338 F pulseaudio /dev/snd/controlC2: larry 11338 F pulseaudio /dev/snd/controlC1: larry 11338 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Sep 20 23:05:52 2021 PackageArchitecture: all ProcEnviron: 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:NVidia failed Symptom_Card: GM107 High Definition Audio Controller [GeForce 940MX] - HDA NVidia Symptom_Type: No sound at all Title: [HDA-Intel - HDA NVidia, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/31/2019 dmi.bios.release: 64.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1886493] Re: Galaxy Book Ion, sof-hda-dsp detected but no soound (ubuntu 20.04)
Same issue. Any fix yet? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1886493 Title: Galaxy Book Ion, sof-hda-dsp detected but no soound (ubuntu 20.04) Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu Release : ubuntu 20.04 LTS release 20.04 Driver : alsa-base : 1.0.25+dfsg-0ubuntu5 On Galaxy Book Ion (model NP950XCJ-X01, from 2020) The audio device (AKG Stereo Speakers) is detected as : sof-hda-dsp Profile : Play HiFi quality music But I get no sound either from the speakers of headphone jack. Guessing a driver issue, hardware not properly detected. Note : Laptop was provided with windows10, sound is ok on windows (so it's not an hardware issue). Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1886493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
I face a similar issue that I posted on ubuntu forum: https://ubuntuforums.org/showthread.php?t=2452881 PPA solves my issue and interestingly changes the Bluetooth controller address -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 Status in bluez package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: Incomplete Status in pi-bluetooth package in Ubuntu: Confirmed Status in bluez source package in Groovy: Incomplete Status in linux-raspi source package in Groovy: Incomplete Status in pi-bluetooth source package in Groovy: New Bug description: Raspberry pi 4 4Gb ram Ubuntu desktop 20.10 64 bit After reboot no Bluetooth devices connect, scanning Bluetooth devices works, results with same device name (duplicated and with not set up status). Sometimes after several reboots it works. If I use power off and cycle power then it works fine each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Confirmed Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831388] [NEW] Wrong Scrolling Direction in Wi-Fi Networks Box
Public bug reported: To reproduce the bug: Natural scrolling is turned on for trackpad scrolling. 1. Go the arrow in the top right corner pointing down 2. Click "Wi-Fi Not Connected" to expand the wifi info 3. Click "Select Network" 4. Scroll in the box titled "Wi-Fi Networks" subtitled "Select a Network" using a trackpad Rather than scrolling up on trackpad causing the list of networks to scroll down it scrolls in the direction of motion on the trackpad, violating the selected natural scrolling setting Expected Behavior: Scroll Track-Pad Up Makes Screen Scroll Down & Scroll Track-Pad Down Makes Screen Scroll Up Current Behavior: Scroll Track-Pad Up Makes Screen Scroll Up & Scroll Track-Pad Down Makes Screen Scroll Down ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 16:49:35 2019 DistUpgraded: 2019-05-04 00:48:40,509 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: disco DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 5.0.0-13-generic, x86_64: installed nvidia, 390.116, 5.0.0-15-generic, x86_64: installed openrazer-driver, 2.5.0, 5.0.0-13-generic, x86_64: installed openrazer-driver, 2.5.0, 5.0.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. UHD Graphics 630 (Mobile) [1a58:2001] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:2001] InstallationDate: Installed on 2018-12-28 (156 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Razer Blade ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=eca2d1f1-3f0e-4dd4-aa0c-3ae11c838d59 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-05-04 (29 days ago) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.sku: RZ09-02705E76 dmi.product.version: 1.04 dmi.sys.vendor: Razer version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Dec 28 15:02:58 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.1-3ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1831388 Title: Wrong Scrolling Direction in Wi-Fi Networks Box Status in xorg package in Ubuntu: New Bug description: To reproduce the bug: Natural scrolling is turned on for trackpad scrolling. 1. Go the arrow in the top right corner pointing down 2. Click "Wi-Fi Not Connected" to expand the wifi info 3. Click "Select Network" 4. Scroll in the box titled "Wi-Fi Networks" subtitled "Select a Network" using a trackpad Rather than scrolling up on trackpad causing the list of networks to scroll down it scrolls in the direction of motion on the trackpad, violating the selected natural scrolling setting Expected Behavior: Scroll Track-Pad Up Makes Screen Scroll Down & Scroll Track-Pad Down Makes Screen Scroll Up Current Behavior: Scroll Track-Pad Up Makes Screen Scroll Up & Scroll Track-Pad Down Makes Screen Scroll Down ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
This also breaks Shibboleth since libapache2-mod-shib2 has a dependency on libxmltooling7 which depends on libcurl3. sudo apt install libapache2-mod-shib2 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libapache2-mod-shib2 : Depends: libshibsp-plugins (= 2.6.1+dfsg1-2) but it is not going to be installed Depends: shibboleth-sp2-utils (>= 2.6) Depends: libshibsp7 but it is not going to be installed Depends: libxmltooling7 (>= 1.6.0-5) but it is not going to be installed E: Unable to correct problems, you have held broken packages. If installing libcurl3 alongside libcurl4 was possible this wouldn't be an issue. Why is this not a high priority? It makes 18.04 unstable at best. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load
Same problem. x1 carbon gen6 like Thorsten, Ubuntu 18.04. Kernel 4.15. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1728238 Title: update-initramfs not adding i915 GuC firmware, firmware fails to load Status in initramfs-tools: New Status in initramfs-tools package in Ubuntu: Confirmed Bug description: The i915 Kabylake GuC firmware is failing to load on boot, and generating dmesg errors. The Kabylake HuC firmware succeeds. All files exist. I've also verified the Kabylake GuC firmware matches the correct file size and md5 listed on 01.org. I then ran update-initramfs verbosely, and see that only /lib/firmware/i915/skl_guc_ver6_1.bin is being added. /lib/firmware/i915/bxt_guc_ver8_7.bin and /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored. I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and initramfs-tools 0.125ubuntu12. Perhaps Broxton systems might have the same issue? Output and logs: - ls -al /lib/firmware/i915/kbl_* -rw-r--r-- 1 root root 8616 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1_01.bin lrwxrwxrwx 1 root root 19 Aug 17 11:08 /lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin -rw-r--r-- 1 root root 142656 Oct 20 21:12 /lib/firmware/i915/kbl_guc_ver9_14.bin -rw-r--r-- 1 root root 218688 Aug 17 11:09 /lib/firmware/i915/kbl_huc_ver02_00_1810.bin sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status GuC firmware status: path: i915/kbl_guc_ver9_14.bin fetch: FAIL load: NONE version wanted: 9.14 version found: 0.0 header: offset is 0; size = 0 uCode: offset is 0; size = 0 RSA: offset is 0; size = 0 GuC status 0x0001: Bootrom status = 0x0 uKernel status = 0x0 MIA Core status = 0x0 Scratch registers: 0: 0x0 1: 0x0 2: 0x0 3: 0x0 4: 0x0 5: 0x0 6: 0x0 7: 0x0 8: 0x0 9: 0x0 10: 0x0 11: 0x0 12: 0x0 13: 0x0 14: 0x0 15: 0x0 sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status HuC firmware status: path: i915/kbl_huc_ver02_00_1810.bin fetch: SUCCESS load: SUCCESS version wanted: 2.0 version found: 2.0 header: offset is 0; size = 128 uCode: offset is 128; size = 218304 RSA: offset is 218432; size = 256 HuC status 0x6000: dmesg [1.052879] hidraw: raw HID events driver (C) Jiri Kosina [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method not found [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002) [1.082308] nvme nvme0: pci function :3c:00.0 [1.095073] Setting dangerous option enable_guc_loading - tainting kernel [1.095075] Setting dangerous option enable_guc_submission - tainting kernel [1.097867] [drm] Memory usable by graphics device = 4078M [1.097869] checking generic (9000 1fb) vs hw (9000 1000) [1.097869] fb: switching to inteldrmfb from EFI VGA [1.097899] Console: switching to colour dummy device 80x25 [1.098049] [drm] Replacing VGA console driver [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.104157] [drm] Driver supports precise vblank timestamp query. [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd [1.298572] nvme0n1: p1 p2 [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1.433243] usb 1-1: Product: USB+PS2 Keyboard [1.433244] usb 1-1: Manufacturer: Generic [1.446460] usbcore: registered new interface driver usbhid [1.446461] usbhid: USB HID core driver [1.448067] input: Generic USB+PS2 Keyboard as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7 [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0 [1.508541] input: Generic USB+PS2 Keyboard as /devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8 [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd [1.568448] hid-generic 0003:0D62:001C.0002: input,hidraw1: USB HID v1.10 Device [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input1 [1.695655] usb 1-2: New USB device found, idVendor=046d, idProduct=c52b [1.695656] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1.695657] usb 1-2: Product: USB Receiver [1.695658] usb 1-2: Manufacturer: Logitech [1.702641] logitech-djreceiver 0003:046D:C52B.0005: hiddev0,hidraw2: USB HID v1.11 Device [Logitech USB
[Touch-packages] [Bug 1596344] Re: pulseaudio causes long login delay waiting for bluetooth
I guess I was mistaken about commenting out "load-module module-
bluetooth-policy" and "load-module module-bluetooth-discover", that did
not solve the problem for me.
A successful workaround though was to "sudo rm
/xdg/autostart/pulseaudio.desktop" which stops gnome-session from trying to
start start-pulseaudio-x11 (and block until it signals completion of startup,
which takes about 30 seconds).
Even without /xdg/autostart/pulseaudio.desktop pulse is being spawned by
something, as can be seen from "pgrep pulse", and I can play sounds
fine.
I am *not* recommending this as a general solution for everyone as I do
not know what ramifications there might be to not having
/xdg/autostart/pulseaudio.desktop that I just might not have noticed. I
assume that it is there for a reason.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1596344
Title:
pulseaudio causes long login delay waiting for bluetooth
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
Kubuntu 16.04 --
I was experiencing a long delay when logging in, on the order of 20+
seconds. After entering the password on the splash screen, it would
stay there before showing the desktop.
journalctl revealed a timeout form pulseaudio waiting for a bluetooth
service (I don't not use bluetooth, and it is disabled, but I believe
I saw this even when I enabled it?)
Jun 26 10:43:42 machinename org.kde.KScreen[1988]: kscreen: Primary output
changed from KScreen::Output(Id: 68 , Name: "HDMI1" ) ( "HDMI1" ) to
KScreen::Output(Id: 68 , Name: "HDMI1" ) ( "HDMI1" )
Jun 26 10:44:02 machinename dbus[982]: [system] Failed to activate service
'org.bluez': timed out
Jun 26 10:44:02 machinename pulseaudio[2121]: [pulseaudio] bluez5-util.c:
GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive
a reply. Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout expired,
or the network connection was broken.
I can fix the problem by editing /etc/pulse/default.pa and commenting
out both bluetooth lines ("load-module module-bluetooth-policy" and
"load-module module-bluetooth-discover" -- not sure if both are
actually necessary.)
I have seen other bugs relating to blocking calls to bluetooth causing
problems. Perhaps there are a few left.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1596344/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596344] Re: pulseaudio causes long login delay waiting for bluetooth
I have encountered this same bug delaying login with Ubuntu Gnome 16.04,
16.10, and 17.04. I am happy to apport-collect if that would be helpful.
I can also confirm that commenting out "load-module module-bluetooth-
policy" and "load-module module-bluetooth-discover" successfully worked
around the problem for me and also stopped the apport crash report
dialogs that I was getting at every login about pulseadio crashing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1596344
Title:
pulseaudio causes long login delay waiting for bluetooth
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
Kubuntu 16.04 --
I was experiencing a long delay when logging in, on the order of 20+
seconds. After entering the password on the splash screen, it would
stay there before showing the desktop.
journalctl revealed a timeout form pulseaudio waiting for a bluetooth
service (I don't not use bluetooth, and it is disabled, but I believe
I saw this even when I enabled it?)
Jun 26 10:43:42 machinename org.kde.KScreen[1988]: kscreen: Primary output
changed from KScreen::Output(Id: 68 , Name: "HDMI1" ) ( "HDMI1" ) to
KScreen::Output(Id: 68 , Name: "HDMI1" ) ( "HDMI1" )
Jun 26 10:44:02 machinename dbus[982]: [system] Failed to activate service
'org.bluez': timed out
Jun 26 10:44:02 machinename pulseaudio[2121]: [pulseaudio] bluez5-util.c:
GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive
a reply. Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout expired,
or the network connection was broken.
I can fix the problem by editing /etc/pulse/default.pa and commenting
out both bluetooth lines ("load-module module-bluetooth-policy" and
"load-module module-bluetooth-discover" -- not sure if both are
actually necessary.)
I have seen other bugs relating to blocking calls to bluetooth causing
problems. Perhaps there are a few left.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1596344/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675990] [NEW] package linux-image-extra-4.8.0-37-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: There is some issue with language support. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-extra-4.8.0-37-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 AptOrdering: linux-image-extra-4.8.0-37-generic:amd64: Remove linux-image-4.8.0-41-generic:amd64: Install linux-headers-4.8.0-37-generic:amd64: Remove linux-headers-4.8.0-37:amd64: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: jeremih1699 F...m pulseaudio /dev/snd/controlC1: jeremih1699 F pulseaudio /dev/snd/controlC0: jeremih1699 F pulseaudio Date: Sat Mar 18 22:51:12 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-DS3H ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic root=/dev/mapper/VG1-LV1 ro splash quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11 RfKill: SourcePackage: initramfs-tools Title: package linux-image-extra-4.8.0-37-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/03/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97M-DS3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97M-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97M-DS3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1675990 Title: package linux-image-extra-4.8.0-37-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: There is some issue with language support. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-image-extra-4.8.0-37-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 AptOrdering: linux-image-extra-4.8.0-37-generic:amd64: Remove linux-image-4.8.0-41-generic:amd64: Install linux-headers-4.8.0-37-generic:amd64: Remove linux-headers-4.8.0-37:amd64: Remove NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: jeremih1699 F...m pulseaudio /dev/snd/controlC1: jeremih1699 F pulseaudio /dev/snd/controlC0: jeremih1699 F pulseaudio Date: Sat Mar 18 22:51:12 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. Z97M-DS3H ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-34-generic root=/dev/mapper/VG1-LV1 ro splash quiet PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11 RfKill: SourcePackage: initramfs-tools Title: package linux-image-extra-4.8.0-37-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/03/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97M-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Touch-packages] [Bug 1622686] Re: double header in 16.10
Did some quick testing with the 0.6.10.1 package in -proposed, and can verify that it fixes this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1622686 Title: double header in 16.10 Status in humanity-icon-theme package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in humanity-icon-theme source package in Xenial: Fix Committed Status in ubiquity source package in Xenial: New Status in humanity-icon-theme source package in Yakkety: Fix Committed Status in ubiquity source package in Yakkety: New Bug description: [Impact] During install and oem-firstboot, the header bar at the top of the screen in Ubiquity is twice as tall as it should be on hidpi screens (looking like two normal sized header bars stacked on top of each other), and the blue a11y icon is double sized. This looks obviously incorrect and ugly and makes a bad first impression on users installing Ubuntu on a hidpi laptop or customers of Ubuntu OEMs booting new machines for the first time. Arstechnica commented negatively on this in their review of Dell's XPS 13: http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still- delivers-linux-now-embraces-svelte-hardware/ Users of the Dell XPS 13 are affected as well as users of other brands of laptops with hidpi screens. System76 is temporarily carrying a patched version of Humanity to work around this bug. The a11y icon is double-sized because the version of Humanity shipping in Ubuntu doesn't support @2 hidpi scaling, which results in the header bar doubling its height. Because the header bar is drawn with CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars stacked one on top of the other. The fix to the Humanity icon theme adds @2 hidpi support, which shrinks the icon and restores the header bar to its normal height. [Test Case] ISO install: 1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer with a hidpi screen. 2. Note the double-sized header and icon during install. - Using an iso with a fixed version of Humanity, the header and icon should look normal. OEM-Firstboot: 1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi screen. 2. After installing, click the launcher icon to "Prepare for shipping to the end user" and reboot. 3. During oem-firstboot, note the double-sized header and icon during install. - To test the fix, install a fixed version of humanity before preparing the system for the end user. [Regression Potential] This patch affects the look of anything using the Humanity icon set. The look of Nautilus, and many other GTK apps will be affected. This is not a regression but fixes another bug and resolves a discrepancy between rendering of icons on hidpi screens vs lowdpi screens. The biggest risk for regression comes from the off chance that there is an error or omission in the index.theme files. Comparing icons on a broad range of applications and systems should catch this class of issues. If any issues with icons are found, check there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens
Did some quick testing with the 0.6.10.1 package in -proposed, and can verify that it fixes this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens Status in humanity-icon-theme package in Ubuntu: Fix Released Status in humanity-icon-theme source package in Xenial: Fix Committed Status in humanity-icon-theme source package in Yakkety: Fix Committed Bug description: [Impact] Humanity icons are sometimes displayed too big on hidpi screens in 16.04. On both 16.04 and 16.10, different icons are used on hidpi screens than non-hidpi screens. Sometimes the icons look similar but with much thinner strokes, while other times an icon with a different metaphor is used. Users on hidpi screens will notice that icons in applications like Nautilus, Transmission, etc. look different (not just clearer) on hidpi screens. The fix here is to add support for @2 icons to the Humanity theme by adding symbolic links for @2 icons and updating the index.theme files accordingly. We should backport the fix to 16.04 and 16.10, so Humanity icons look the same on hidpi screens as non-hidpi screens. [Test Case] Here are a few test cases: 1) Using a computer with hidpi screen and a computer with a lowdpi screen both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi screen are much larger. (This applies to icons on the desktop as well.) -The fix should result in icons being the same size on both hidpi and lowdpi. 2) Using a computer with a hidpi screen and one with a lowdpi screen running Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the toolbar uses an icon with a different metaphor on hidpi screens (an up arrow emerging from a folder) than on lowdpi screens (a sheet of paper emerging from a folder). - The fix should result in the "sheet of paper emerging from a folder" icon being used here on both hidpi and lowdpi screens. 3) Using a computer with hidpi screen and a computer with a lowdpi screen both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons look sutbly different. The strokes in icons on the hidpi screen will be visibly thinner on the hidpi screen because icons for bigger scale are used (say 48 on hidpi instead of 24) rather than rendering the original size icon at a larger resolution. - The fix should result in icons that have the same stroke width on hidpi and lowdpi screens. The icons will still be sharper on the hidpi screen, but the lines won't be thinner. [Regression Potential] The patch is designed for compatibility where @2 support is not available by listing the @2 directories under "ScaledDirectories=" rather than "Directories=". However it's possible there could be other kinds of issues not found in testing. If there are any omissions or errors in the index.theme, this could cause rendering issues for some categories of icons. Comparing icons on a broad range of applications and systems should catch this class of issues. Hidpi users may find that their machine looks different after the update than it did before. This is not a regression, but a fix to a bug that's been present all along. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens
Did some quick testing with the 0.6.11.1 package in -proposed, and can verify that it fixes this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens Status in humanity-icon-theme package in Ubuntu: Fix Released Status in humanity-icon-theme source package in Xenial: Fix Committed Status in humanity-icon-theme source package in Yakkety: Fix Committed Bug description: [Impact] Humanity icons are sometimes displayed too big on hidpi screens in 16.04. On both 16.04 and 16.10, different icons are used on hidpi screens than non-hidpi screens. Sometimes the icons look similar but with much thinner strokes, while other times an icon with a different metaphor is used. Users on hidpi screens will notice that icons in applications like Nautilus, Transmission, etc. look different (not just clearer) on hidpi screens. The fix here is to add support for @2 icons to the Humanity theme by adding symbolic links for @2 icons and updating the index.theme files accordingly. We should backport the fix to 16.04 and 16.10, so Humanity icons look the same on hidpi screens as non-hidpi screens. [Test Case] Here are a few test cases: 1) Using a computer with hidpi screen and a computer with a lowdpi screen both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi screen are much larger. (This applies to icons on the desktop as well.) -The fix should result in icons being the same size on both hidpi and lowdpi. 2) Using a computer with a hidpi screen and one with a lowdpi screen running Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the toolbar uses an icon with a different metaphor on hidpi screens (an up arrow emerging from a folder) than on lowdpi screens (a sheet of paper emerging from a folder). - The fix should result in the "sheet of paper emerging from a folder" icon being used here on both hidpi and lowdpi screens. 3) Using a computer with hidpi screen and a computer with a lowdpi screen both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons look sutbly different. The strokes in icons on the hidpi screen will be visibly thinner on the hidpi screen because icons for bigger scale are used (say 48 on hidpi instead of 24) rather than rendering the original size icon at a larger resolution. - The fix should result in icons that have the same stroke width on hidpi and lowdpi screens. The icons will still be sharper on the hidpi screen, but the lines won't be thinner. [Regression Potential] The patch is designed for compatibility where @2 support is not available by listing the @2 directories under "ScaledDirectories=" rather than "Directories=". However it's possible there could be other kinds of issues not found in testing. If there are any omissions or errors in the index.theme, this could cause rendering issues for some categories of icons. Comparing icons on a broad range of applications and systems should catch this class of issues. Hidpi users may find that their machine looks different after the update than it did before. This is not a regression, but a fix to a bug that's been present all along. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622686] Re: double header in 16.10
Did some quick testing with the 0.6.11.1 package in -proposed, and can verify that it fixes this bug. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1622686 Title: double header in 16.10 Status in humanity-icon-theme package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in humanity-icon-theme source package in Xenial: Fix Committed Status in ubiquity source package in Xenial: New Status in humanity-icon-theme source package in Yakkety: Fix Committed Status in ubiquity source package in Yakkety: New Bug description: [Impact] During install and oem-firstboot, the header bar at the top of the screen in Ubiquity is twice as tall as it should be on hidpi screens (looking like two normal sized header bars stacked on top of each other), and the blue a11y icon is double sized. This looks obviously incorrect and ugly and makes a bad first impression on users installing Ubuntu on a hidpi laptop or customers of Ubuntu OEMs booting new machines for the first time. Arstechnica commented negatively on this in their review of Dell's XPS 13: http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still- delivers-linux-now-embraces-svelte-hardware/ Users of the Dell XPS 13 are affected as well as users of other brands of laptops with hidpi screens. System76 is temporarily carrying a patched version of Humanity to work around this bug. The a11y icon is double-sized because the version of Humanity shipping in Ubuntu doesn't support @2 hidpi scaling, which results in the header bar doubling its height. Because the header bar is drawn with CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars stacked one on top of the other. The fix to the Humanity icon theme adds @2 hidpi support, which shrinks the icon and restores the header bar to its normal height. [Test Case] ISO install: 1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer with a hidpi screen. 2. Note the double-sized header and icon during install. - Using an iso with a fixed version of Humanity, the header and icon should look normal. OEM-Firstboot: 1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi screen. 2. After installing, click the launcher icon to "Prepare for shipping to the end user" and reboot. 3. During oem-firstboot, note the double-sized header and icon during install. - To test the fix, install a fixed version of humanity before preparing the system for the end user. [Regression Potential] This patch affects the look of anything using the Humanity icon set. The look of Nautilus, and many other GTK apps will be affected. This is not a regression but fixes another bug and resolves a discrepancy between rendering of icons on hidpi screens vs lowdpi screens. The biggest risk for regression comes from the off chance that there is an error or omission in the index.theme files. Comparing icons on a broad range of applications and systems should catch this class of issues. If any issues with icons are found, check there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1622686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens Status in humanity-icon-theme package in Ubuntu: Fix Released Status in humanity-icon-theme source package in Xenial: Fix Committed Status in humanity-icon-theme source package in Yakkety: Fix Committed Bug description: [Impact] Humanity icons are sometimes displayed too big on hidpi screens in 16.04. On both 16.04 and 16.10, different icons are used on hidpi screens than non-hidpi screens. Sometimes the icons look similar but with much thinner strokes, while other times an icon with a different metaphor is used. Users on hidpi screens will notice that icons in applications like Nautilus, Transmission, etc. look different (not just clearer) on hidpi screens. The fix here is to add support for @2 icons to the Humanity theme by adding symbolic links for @2 icons and updating the index.theme files accordingly. We should backport the fix to 16.04 and 16.10, so Humanity icons look the same on hidpi screens as non-hidpi screens. [Test Case] Here are a few test cases: 1) Using a computer with hidpi screen and a computer with a lowdpi screen both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi screen are much larger. (This applies to icons on the desktop as well.) -The fix should result in icons being the same size on both hidpi and lowdpi. 2) Using a computer with a hidpi screen and one with a lowdpi screen running Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the toolbar uses an icon with a different metaphor on hidpi screens (an up arrow emerging from a folder) than on lowdpi screens (a sheet of paper emerging from a folder). - The fix should result in the "sheet of paper emerging from a folder" icon being used here on both hidpi and lowdpi screens. 3) Using a computer with hidpi screen and a computer with a lowdpi screen both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons look sutbly different. The strokes in icons on the hidpi screen will be visibly thinner on the hidpi screen because icons for bigger scale are used (say 48 on hidpi instead of 24) rather than rendering the original size icon at a larger resolution. - The fix should result in icons that have the same stroke width on hidpi and lowdpi screens. The icons will still be sharper on the hidpi screen, but the lines won't be thinner. [Regression Potential] The patch is designed for compatibility where @2 support is not available by listing the @2 directories under "ScaledDirectories=" rather than "Directories=". However it's possible there could be other kinds of issues not found in testing. If there are any omissions or errors in the index.theme, this could cause rendering issues for some categories of icons. Comparing icons on a broad range of applications and systems should catch this class of issues. Hidpi users may find that their machine looks different after the update than it did before. This is not a regression, but a fix to a bug that's been present all along. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622686] Re: double header in 16.10
** Description changed: - STEPS: - 1. grab the latest iso - 2. Note the header during install + [Impact] - EXPECTED: - Icon on one header + During install and oem-firstboot, the header bar at the top of the + screen in Ubiquity is twice as tall as it should be on hidpi screens + (looking like two normal sized header bars stacked on top of each + other), and the blue a11y icon is double sized. - ACTUAL: - I believe the a11y icon is double sized and forces a double header. see photo + This looks obviously incorrect and ugly and makes a bad first impression + on users installing Ubuntu on a hidpi laptop or customers of Ubuntu OEMs + booting new machines for the first time. Arstechnica commented + negatively on this in their review of Dell's XPS 13: + http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still- + delivers-linux-now-embraces-svelte-hardware/ - /!\ Seem to be a hidpi only issue I see it on xps13 but not on other - installs + Users of the Dell XPS 13 are affected as well as users of other brands + of laptops with hidpi screens. System76 is temporarily carrying a + patched version of Humanity to work around this bug. + + The a11y icon is double-sized because the version of Humanity shipping + in Ubuntu doesn't support @2 hidpi scaling, which results in the header + bar doubling its height. Because the header bar is drawn with + CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars + stacked one on top of the other. The fix to the Humanity icon theme + adds @2 hidpi support, which shrinks the icon and restores the header + bar to its normal height. + + + [Test Case] + ISO install: + 1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer with a hidpi screen. + 2. Note the double-sized header and icon during install. + - Using an iso with a fixed version of Humanity, the header and icon should look normal. + + OEM-Firstboot: + 1. Grab an Ubuntu iso and do an oem-install on on a computer with a hidpi screen. + 2. After installing, click the launcher icon to "Prepare for shipping to the end user" and reboot. + 3. During oem-firstboot, note the double-sized header and icon during install. + - To test the fix, install a fixed version of humanity before preparing the system for the end user. + + + [Regression Potential] + + This patch affects the look of anything using the Humanity icon set. + The look of Nautilus, and many other GTK apps will be affected. This is + not a regression but fixes another bug and resolves a discrepancy + between rendering of icons on hidpi screens vs lowdpi screens. + + The biggest risk for regression comes from the off chance that there is + an error or omission in the index.theme files. Comparing icons on a + broad range of applications and systems should catch this class of + issues. If any issues with icons are found, check there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1622686 Title: double header in 16.10 Status in humanity-icon-theme package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in humanity-icon-theme source package in Xenial: New Status in ubiquity source package in Xenial: New Status in humanity-icon-theme source package in Yakkety: New Status in ubiquity source package in Yakkety: New Bug description: [Impact] During install and oem-firstboot, the header bar at the top of the screen in Ubiquity is twice as tall as it should be on hidpi screens (looking like two normal sized header bars stacked on top of each other), and the blue a11y icon is double sized. This looks obviously incorrect and ugly and makes a bad first impression on users installing Ubuntu on a hidpi laptop or customers of Ubuntu OEMs booting new machines for the first time. Arstechnica commented negatively on this in their review of Dell's XPS 13: http://arstechnica.com/gadgets/2017/01/dells-latest-xps-13-de-still- delivers-linux-now-embraces-svelte-hardware/ Users of the Dell XPS 13 are affected as well as users of other brands of laptops with hidpi screens. System76 is temporarily carrying a patched version of Humanity to work around this bug. The a11y icon is double-sized because the version of Humanity shipping in Ubuntu doesn't support @2 hidpi scaling, which results in the header bar doubling its height. Because the header bar is drawn with CAIRO_PAD_REPEAT, the gradient is repeated so it looks like two bars stacked one on top of the other. The fix to the Humanity icon theme adds @2 hidpi support, which shrinks the icon and restores the header bar to its normal height. [Test Case] ISO install: 1. Grab an Ubuntu iso and proceed to install (not "try") Ubuntu on a computer with a hidpi screen. 2. Note the double-sized header and icon during
[Touch-packages] [Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens
** Description changed: - Because Humanity doesn't have support for @2x icons, some icons are - displayed too big. This is a general issue, but is easily noticed in a - few examples below. + [Impact] - In Nautilus, the icons are much too big on hidpi screends in 16.04, - while in 16.10 the icons are the same size but use different icons with - much thinner strokes. The difference is also visible in icons on the - Desktop. + Humanity icons are sometimes displayed too big on hidpi screens in + 16.04. On both 16.04 and 16.10, different icons are used on hidpi + screens than non-hidpi screens. Sometimes the icons look similar but + with much thinner strokes, while other times an icon with a different + metaphor is used. Users on hidpi screens will notice that icons in + applications like Nautilus, Transmission, etc. look different (not just + clearer) on hidpi screens. - In Transmission, the "Open" button in the toolbar uses an icon with a - different metaphor on hidpi screens (an up arrow emerging from a folder) - than on lowdpi screens (a sheet of paper emerging from a folder). + The fix here is to add support for @2 icons to the Humanity theme by + adding symbolic links for @2 icons and updating the index.theme files + accordingly. - After adding symbolic links for @2x icons and updating the index.theme - files accordingly fixes these issues. + We should backport the fix to 16.04 and 16.10, so Humanity icons look + the same on hidpi screens as non-hidpi screens. + + + [Test Case] + + Here are a few test cases: + 1) Using a computer with hidpi screen and a computer with a lowdpi screen both running Ubuntu 16.04: Open Nautilus and see that the icons on the hidpi screen are much larger. (This applies to icons on the desktop as well.) + -The fix should result in icons being the same size on both hidpi and lowdpi. + + 2) Using a computer with a hidpi screen and one with a lowdpi screen running Ubuntu 16.04 or 16.10: Open Transmission and see that the "Open" button in the toolbar uses an icon with a different metaphor on hidpi screens (an up arrow emerging from a folder) than on lowdpi screens (a sheet of paper emerging from a folder). + - The fix should result in the "sheet of paper emerging from a folder" icon being used here on both hidpi and lowdpi screens. + + 3) Using a computer with hidpi screen and a computer with a lowdpi screen both running Ubuntu 16.10: Compare icons in Nautilus and see that the icons look sutbly different. The strokes in icons on the hidpi screen will be visibly thinner on the hidpi screen because icons for bigger scale are used (say 48 on hidpi instead of 24) rather than rendering the original size icon at a larger resolution. + - The fix should result in icons that have the same stroke width on hidpi and lowdpi screens. The icons will still be sharper on the hidpi screen, but the lines won't be thinner. + + + [Regression Potential] + + The patch is designed for compatibility where @2 support is not + available by listing the @2 directories under "ScaledDirectories=" + rather than "Directories=". However it's possible there could be other + kinds of issues not found in testing. If there are any omissions or + errors in the index.theme, this could cause rendering issues for some + categories of icons. Comparing icons on a broad range of applications + and systems should catch this class of issues. + + Hidpi users may find that their machine looks different after the update + than it did before. This is not a regression, but a fix to a bug that's + been present all along. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens Status in humanity-icon-theme package in Ubuntu: Fix Released Status in humanity-icon-theme source package in Xenial: New Status in humanity-icon-theme source package in Yakkety: New Bug description: [Impact] Humanity icons are sometimes displayed too big on hidpi screens in 16.04. On both 16.04 and 16.10, different icons are used on hidpi screens than non-hidpi screens. Sometimes the icons look similar but with much thinner strokes, while other times an icon with a different metaphor is used. Users on hidpi screens will notice that icons in applications like Nautilus, Transmission, etc. look different (not just clearer) on hidpi screens. The fix here is to add support for @2 icons to the Humanity theme by adding symbolic links for @2 icons and updating the index.theme files accordingly. We should backport the fix to 16.04 and 16.10, so Humanity icons look the same on hidpi screens as non-hidpi screens. [Test Case] Here are a few test cases: 1) Using a computer with hidpi screen and a computer with a lowdpi screen both running Ubuntu 16.04:
[Touch-packages] [Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens
** Branch linked: lp:~dmj726/humanity/hidpi-2x -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens Status in humanity-icon-theme package in Ubuntu: New Bug description: Because Humanity doesn't have support for @2x icons, some icons are displayed too big. This is a general issue, but is easily noticed in a few examples below. In Nautilus, the icons are much too big on hidpi screends in 16.04, while in 16.10 the icons are the same size but use different icons with much thinner strokes. The difference is also visible in icons on the Desktop. In Transmission, the "Open" button in the toolbar uses an icon with a different metaphor on hidpi screens (an up arrow emerging from a folder) than on lowdpi screens (a sheet of paper emerging from a folder). After adding symbolic links for @2x icons and updating the index.theme files accordingly fixes these issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1657863] Re: Icons are too big or the wrong icon is shown on hidpi screens
Left side: humanity without @2x support Right side: humanity with @2x support (looks just like lowdpi but crisper) ** Description changed: Because Humanity doesn't have support for @2x icons, some icons are displayed too big. This is a general issue, but is easily noticed in a few examples below. - In nautilus, the default window size only fits 4 columns of icons on a - hidpi screen, compared with 7 on a non-hidpi screen. + In Nautilus, the icons are much too big on hidpi screends in 16.04, + while in 16.10 the icons are the same size but use different icons with + much thinner strokes. The difference is also visible in icons on the + Desktop. In Transmission, the "Open" button in the toolbar uses an icon with a different metaphor on hidpi screens (an up arrow emerging from a folder) than on lowdpi screens (a sheet of paper emerging from a folder). After adding symbolic links for @2x icons and updating the index.theme files accordingly fixes these issues. ** Attachment added: "humanity hidpi xenial.png" https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+attachment/4806440/+files/humanity%20hidpi%20xenial.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens Status in humanity-icon-theme package in Ubuntu: New Bug description: Because Humanity doesn't have support for @2x icons, some icons are displayed too big. This is a general issue, but is easily noticed in a few examples below. In Nautilus, the icons are much too big on hidpi screends in 16.04, while in 16.10 the icons are the same size but use different icons with much thinner strokes. The difference is also visible in icons on the Desktop. In Transmission, the "Open" button in the toolbar uses an icon with a different metaphor on hidpi screens (an up arrow emerging from a folder) than on lowdpi screens (a sheet of paper emerging from a folder). After adding symbolic links for @2x icons and updating the index.theme files accordingly fixes these issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1657863] [NEW] Icons are too big or the wrong icon is shown on hidpi screens
Public bug reported: Because Humanity doesn't have support for @2x icons, some icons are displayed too big. This is a general issue, but is easily noticed in a few examples below. In nautilus, the default window size only fits 4 columns of icons on a hidpi screen, compared with 7 on a non-hidpi screen. In Transmission, the "Open" button in the toolbar uses an icon with a different metaphor on hidpi screens (an up arrow emerging from a folder) than on lowdpi screens (a sheet of paper emerging from a folder). After adding symbolic links for @2x icons and updating the index.theme files accordingly fixes these issues. ** Affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: hidpi humanity icons nautilus -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1657863 Title: Icons are too big or the wrong icon is shown on hidpi screens Status in humanity-icon-theme package in Ubuntu: New Bug description: Because Humanity doesn't have support for @2x icons, some icons are displayed too big. This is a general issue, but is easily noticed in a few examples below. In nautilus, the default window size only fits 4 columns of icons on a hidpi screen, compared with 7 on a non-hidpi screen. In Transmission, the "Open" button in the toolbar uses an icon with a different metaphor on hidpi screens (an up arrow emerging from a folder) than on lowdpi screens (a sheet of paper emerging from a folder). After adding symbolic links for @2x icons and updating the index.theme files accordingly fixes these issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1657863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638846] Re: Update GLib to fix a bug with Trash in Nautilus
** Bug watch added: GNOME Bug Tracker #662946 https://bugzilla.gnome.org/show_bug.cgi?id=662946 ** Also affects: glib via https://bugzilla.gnome.org/show_bug.cgi?id=662946 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1638846 Title: Update GLib to fix a bug with Trash in Nautilus Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Confirmed Bug description: As described here there is a bug in Ubuntu 16.10 with trash and external drives in Nautilus: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1633824 Seems that this has been fixed already with GLib 2.50.1 according to https://bugzilla.gnome.org/show_bug.cgi?id=773819#c3 So updating the package for Ubuntu 16.10 would fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1638846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1608622] Re: 14.04.5 drops to initramfs prompt during boot with nvme drive
** Package changed: linux (Ubuntu) => initramfs-tools (Ubuntu) ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1608622 Title: 14.04.5 drops to initramfs prompt during boot with nvme drive Status in initramfs-tools package in Ubuntu: New Bug description: So, installing 14.04.4 works fine, but systems with nvme drives don't boot after installing 14.04.5. Steps to reproduce: 1) Install Ubuntu 14.04.5 on a system with an nvme drive 2) reboot 3) instead of booting to a graphical environment, there is an initramfs prompt. Notes: This also prevents reaching any of the recovery mode tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1608622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp
Confirming this issue also with the Phillips Bluetooth speaker model BT2500B/37. Cannot set to higher quality sound in pulseaudio. Using gnome-ubuntu 16.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Confirmed Status in pulseaudio source package in Vivid: Confirmed Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1438510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1127151] Re: The system network services are not compatible with this version
I was just hit by this bug as well on 14.04LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1127151 Title: The system network services are not compatible with this version Status in network-manager package in Ubuntu: Confirmed Bug description: Network is not working after the upgrade of Ubuntu 12.04 network manager and related packages. First time happened already on June 2012, seems the problem still exists. Error message in Network manager is "The system network services are not compatible with this version" I needed to downgrade packages, Working versions below, later versions give the error libnm-glib-vpn1_0.9.4.0-0ubuntu3_i386.deb libnm-glib4_0.9.4.0-0ubuntu3_i386.deb libnm-util2_0.9.4.0-0ubuntu3_i386.deb network-manager_0.9.4.0-0ubuntu3_i386.deb network-manager-dbg_0.9.4.0-0ubuntu3_i386.deb Related thread and answer: http://ubuntuforums.org/showthread.php?t=2001421 https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/199450 System info: Description: Ubuntu 12.04.2 LTS Release: 12.04 Linux bogey 3.2.0-24-generic-pae #39-Ubuntu SMP Mon May 21 18:54:21 UTC 2012 i686 i686 i386 GNU/Linux Motherboard is gigabyte GA-E7AUM-DS2H with Nvidia Geforce 9400 chipset with integrated network. According to gigabyte website, network device is Realtek 8211CL chip (10/100/1000 Mbit) # lcpci -v 00:0a.0 Ethernet controller: NVIDIA Corporation MCP79 Ethernet (rev b1) Subsystem: Giga-byte Technology Device e000 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 41 Memory at e4187000 (32-bit, non-prefetchable) [size=4K] I/O ports at c800 [size=8] Memory at e4188000 (32-bit, non-prefetchable) [size=256] Memory at e4189000 (32-bit, non-prefetchable) [size=16] Capabilities: Kernel driver in use: forcedeth Kernel modules: forcedeth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1127151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1539513] Re: networkmanager segfaults with 3.2.21-1ubuntu1
I just run an upgrade and hit the same problem. Lots of messages in syslog like: Jan 30 21:04:14 sony ModemManager[767]: ModemManager (version 1.0.0) sta rting... Jan 30 21:04:16 sony NetworkManager[924]: NetworkManager (version 0.9.8.8 ) is starting... Jan 30 21:04:16 sony NetworkManager[924]: Read config file /etc/NetworkMa nager/NetworkManager.conf Jan 30 21:04:16 sony NetworkManager[924]: WEXT support is enabled Jan 30 21:04:16 sony kernel: [ 42.654682] init: network-manager main process ( 924) killed by SEGV signal Jan 30 21:04:16 sony kernel: [ 42.654699] init: network-manager main process e nded, respawning I restored network using the method suggested by post #7 and using the links from #28. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1539513 Title: networkmanager segfaults with 3.2.21-1ubuntu1 Status in libnl3 package in Ubuntu: Confirmed Bug description: Description:Ubuntu 14.04.3 LTS Release:14.04 After upgrading to 3.2.21-1ubuntu1 network-manager 0.9.8.8-0ubuntu7.2 segfaults: [ 21.367977] init: network-manager main process (1000) killed by SEGV signal [ 21.367989] init: network-manager main process ended, respawning [ 21.424932] init: network-manager main process (1060) killed by SEGV signal [ 21.424943] init: network-manager main process ended, respawning [ 21.451519] init: network-manager main process (1066) killed by SEGV signal [...] xxx@yyy:/tmp/bla# gdb /usr/sbin/NetworkManager CoreDump [...] Reading symbols from /usr/sbin/NetworkManager...(no debugging symbols found)...done. [New LWP 3550] [New LWP 3551] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `NetworkManager'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00469fee in nm_netlink_monitor_attach () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1539513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348954] Re: update Python3 for trusty
Bug #1499075 is another regression introduced by this SRU. A fix is available in python-botocore/trusty-proposed, so please release that fix either before/alongside this SRU to avoid reintroducing this regression. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1348954 Title: update Python3 for trusty Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions source package in Trusty: Fix Released Status in python3.4 source package in Trusty: Triaged Bug description: update Python3 for trusty. Rationale: the LTS was released with 3.4.0, the first 3.4 release which certainly had some issues. The idea is to update the python3.4 packages to the version found in 15.04 (vivid), which currently doesn't have any outstanding issues. A test rebuild of the trusty main component was done without showing any regressions during the package builds. http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150317-trusty.html http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150501-updates-trusty.html To validate this SRU, I'm proposing to use the results from the test rebuild, plus evaluating the testsuite results of the python3.4 package itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1348954/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 34629] Re: Left-click clears PRIMARY buffer selection (Copy-paste with middle-button/mouse wheel fails)
And still continues to be very annoying... Linux Mint 17.2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/34629 Title: Left-click clears PRIMARY buffer selection (Copy-paste with middle- button/mouse wheel fails) Status in GTK+: Confirmed Status in One Hundred Papercuts: Invalid Status in gtk+2.0 package in Ubuntu: Triaged Bug description: Left-click clears the visible selection *and* PRIMARY buffer contents, rather than just clearing the visible selection. This means that a user middle-click pasting finds the text has been dropped and that they can't paste what they expected to paste without going back and reselecting in the previous application again. 1) Select some text. 2) Click somewhere on the document. 3) Click mouse wheel. Using the PRIMARY mechanism, text should be pasted like it works elsewhere in X. However, nothing is pasted in gedit. Using the CLIPBOARD mechanism, Ctrl-C, ctrl-V copy-pasting seems to work within gedit, so this is unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/34629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1244176] Re: Server 13.10 Install Fails with USB Keyboard (Appears to Hang)
Note that while this particular bug, about missing ohci-pci in the initramfs, is fixed in Ubuntu 15.04 another similar bug, missing xhci- pci, is still present. The debian bug report about, and fix for, missing xhci-pci is here: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=773250 If you are experiencing these symptoms on Ubuntu 15.04 (USB keyboard working in installed and Live systems, but not debian-installer / early boot initramfs), you are probably hitting the xhci-pci bug. ** Bug watch added: Debian Bug tracker #773250 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773250 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1244176 Title: Server 13.10 Install Fails with USB Keyboard (Appears to Hang) Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in initramfs-tools source package in Saucy: Invalid Status in linux source package in Saucy: Fix Released Status in initramfs-tools source package in Trusty: Confirmed Status in linux source package in Trusty: Fix Released Status in initramfs-tools source package in Utopic: Invalid Status in linux source package in Utopic: Fix Released Bug description: A fresh install of Server 13.10 on old hardware fails when a USB keyboard is present. The installation succeeds when a PS/2 keyboard is installed. The installation appears to hang at the third screen, which is Select Language. The screen does not respond to keyboard or mouse events. The issue was experienced independently on HP/Compag dc5850 with Athlon X2 2.3 GHz dual core, 4GB RAM; and DELL Optiplex 755. See Server 13.10 Install Hangs, http://askubuntu.com/questions/364945/server-13-10-install- hangs/364949. The issue was not present on Server 12.04.3 LTS or 13.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1244176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1074792] Re: Bluetooth Mouse is laggy/sluggish/erratic behaviour in Linux but not Windows
I found that my issue was actually caused by interference. The dongle was too close to my cell phone, moving the dongle closer to the mouse and farther from the cell phone, actually solved all jitter issues for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1074792 Title: Bluetooth Mouse is laggy/sluggish/erratic behaviour in Linux but not Windows Status in bluez package in Ubuntu: Confirmed Bug description: My Prolink PMO624B Bluetooth Mouse movement is laggy/sluggish/erratic in Ubuntu 12.04 and 12.10 on a Asus EeePC 1215B. However, it works completely normal in Windows 7 on the same machine, so I believe that the issue is with Linux/BlueZ. Please advise? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1074792/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387036] [NEW] erratically reboot in low res without using nvidia card
Public bug reported: All worked fine after a brand new installation. This morning after booting, I am back to low res mode. Another reboot and I am in 1024x768 mode but without 3D acceleration. Hardware : laptop zbook 17 HP with K610M graphic card ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.5 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: Wed Oct 29 09:16:11 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.117, 3.13.0-37-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK208GLM [Quadro K610M] [10de:12b9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:197a] InstallationDate: Installed on 2014-10-17 (11 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ZBook 17 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=02b45209-d8b9-40c3-ba22-1b46544dbe7d ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.10 dmi.board.name: 190A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.51 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.10:bd06/24/2014:svnHewlett-Packard:pnHPZBook17:pvrA3008CD10003:rvnHewlett-Packard:rn190A:rvrKBCVersion94.51:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 17 dmi.product.version: A3008CD10003 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Oct 29 09:14:54 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1387036 Title: erratically reboot in low res without using nvidia card Status in “xorg” package in Ubuntu: New Bug description: All worked fine after a brand new installation. This morning after booting, I am back to low res mode. Another reboot and I am in 1024x768 mode but without 3D acceleration. Hardware : laptop zbook 17 HP with K610M graphic card ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.5 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: Wed Oct 29 09:16:11 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.117, 3.13.0-37-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK208GLM [Quadro K610M] [10de:12b9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:197a] InstallationDate: Installed on 2014-10-17 (11 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Hewlett-Packard HP ZBook 17 ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=02b45209-d8b9-40c3-ba22-1b46544dbe7d ro drm.debug=0xe plymouth:debug Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2014
[Touch-packages] [Bug 1273752] Re: Can't Copy Crash Report Details to Clipboard
guntbert, because I didn't know it existed until you pointed it out and I went and found it ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1273752 Title: Can't Copy Crash Report Details to Clipboard Status in “apport” package in Ubuntu: Confirmed Bug description: Often times, after receiving a crash report, if I click the Continue button it doesn't launch the browser for me to submit my crash to launchpad.net. Because of this, I'd always like to copy the crash report to my clipboard before clicking the continue button, so that I can manually provide this information into a bug report to launchpad.net. However, this option is not available. More over, there is absolutely *no way* to copy any text from this crash report's dialog window! 1) You cannot ctrl-a to select all. 2) Ctrl-c doesn't copy anything 3) Right-clicking doesn't produce a context menu where you can select Copy. This is an unfinished design. You should always give the user the ability to copy any text displayed in the UI. Next to the Show/Hide details button, I suggest adding a Copy to Clipboard button. If not this, please offer some way to achieve this from the GUI. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport-gtk 2.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl ApportLog: ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 28 10:21:00 2014 InstallationDate: Installed on 2013-10-07 (113 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-01-08 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1273752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
