[Touch-packages] [Bug 1737614] Re: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop
The issues persist on Ubuntu 18.04.1 with Linux Kernel 4.20. -- 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/1737614 Title: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop Status in alsa-driver package in Ubuntu: Won't Fix Bug description: I have a new laptop HP-15-BS576TX which has this Intel Corporation Sunrise Point-LP HD Audio. 00:1f.3 Audio device [0403]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) The laptop sound works perfectly fine in Windows 10 with realtek drivers. However, in Ubuntu 17.10, the volume is significantly low, that I've to scroll the volume slider above 100% mark in pulseaudio to the maximum to get acceptable level of sound. I suspect the sound quality also is low (mono-like), may be not coming from all speakers (perhaps subwoofer exist for this model). Also alsamixer shows the speaker volume at the maximum. Details about the audio hardware are below: :~$ sudo lspci -vvv | grep -A 40 -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Hewlett-Packard Company Device 832b Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- /proc/asound/card0/codec#0 <== Codec: Realtek ALC3227 ==> /proc/asound/card0/codec#2 <== Codec: Intel Kabylake HDMI :~$ aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3227 Analog [ALC3227 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 I have gone through Linux kernel sources ALSA and Snd-HDA lists and unable to find any optimizations for this laptop. Here is the relevant dmesg details: [ 15.502856] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 16.310503] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3227: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 16.310506] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 16.310507] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 16.310508] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [ 16.310509] snd_hda_codec_realtek hdaudioC0D0:inputs: [ 16.310510] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 [ 16.310512] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 [ 16.451397] input: HDA Intel PCH Mic as /devices/pci:00/:00:1f.3/sound/card0/input9 [ 16.451451] input: HDA Intel PCH Headphone as /devices/pci:00/:00:1f.3/sound/card0/input10 [ 16.451496] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1f.3/sound/card0/input11 [ 16.451538] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1f.3/sound/card0/input12 [ 16.451581] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1f.3/sound/card0/input13 [ 16.451624] input: HDA Intel PCH HDMI/DP,pcm=9 as /devices/pci:00/:00:1f.3/sound/card0/input14 [ 16.451687] input: HDA Intel PCH HDMI/DP,pcm=10 as /devices/pci:00/:00:1f.3/sound/card0/input15 Any further information needed, please let me know. Thank you. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 [modified: usr/share/alsa-base/alsa-info.sh] ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: ndiswrapper ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: admin2018 1246 F pulseaudio CurrentDesktop: GNOME Date: Tue Dec 12 00:46:12 2017 InstallationDate: Installed on 2017-11-22 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832B dmi.board.vendor: HP dmi.board.version: 23.40 dmi.chassis.asset.tag:
[Touch-packages] [Bug 1810474] [NEW] package libcupscgi1:amd64 2.2.7-1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting confi
Public bug reported: maybe behind program unable to load ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libcupscgi1:amd64 2.2.7-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CupsErrorLog: E [04/Jan/2019:12:09:14 +1300] [cups-deviced] PID 2947 (gutenprint52+usb) stopped with status 1! E [05/Jan/2019:05:52:25 +1300] [cups-deviced] PID 1133 (gutenprint52+usb) stopped with status 1! Date: Fri Jan 4 18:20:16 2019 DuplicateSignature: package:libcupscgi1:amd64:2.2.7-1ubuntu2.2 Setting up cups-client (2.2.7-1ubuntu2.2) ... dpkg: error processing package libcupscgi1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2019-01-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for OfficeJet-Pro-6960: hp:/usb/OfficeJet_Pro_6960?serial=TH74J6N067 device for OfficeJet-Pro-6960-Fax-4: hpfax:/usb/OfficeJet_Pro_6960?serial=TH74J6N067 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Papersize: a4 PpdFiles: OfficeJet-Pro-6960-Fax-4: HP Fax4 hpcups OfficeJet-Pro-6960: HP Officejet Pro 6960, hpcups 3.17.10 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=e0823691-5f97-41e9-bd50-df1a2814e3d1 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=e0823691-5f97-41e9-bd50-df1a2814e3d1 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: cups Title: package libcupscgi1:amd64 2.2.7-1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: A320M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd06/12/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1810474 Title: package libcupscgi1:amd64 2.2.7-1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in cups package in Ubuntu: New Bug description: maybe behind program unable to load ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libcupscgi1:amd64 2.2.7-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CupsErrorLog: E [04/Jan/2019:12:09:14 +1300] [cups-deviced] PID 2947 (gutenprint52+usb) stopped with status 1! E [05/Jan/2019:05:52:25 +1300] [cups-deviced] PID 1133 (gutenprint52+usb) stopped with status 1! Date: Fri Jan 4 18:20:16 2019 DuplicateSignature: package:libcupscgi1:amd64:2.2.7-1ubuntu2.2 Setting up cups-client (2.2.7-1ubuntu2.2) ... dpkg: error processing package libcupscgi1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2019-01-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for OfficeJet-Pro-6960: hp:/usb/OfficeJet_Pro_6960?serial=TH74J6N067 device for OfficeJet-Pro-6960-Fax-4: hpfax:/usb/OfficeJet_Pro_6960?serial=TH74J6N067 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Papersize: a4 PpdFiles: OfficeJet-Pro-6960-Fax-4: HP Fax4 hpcups OfficeJet-Pro-6960: HP Officejet Pro 6960, hpcups 3.17.10 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=e0823691-5f97-41e9-bd50-df1a2814e3d1 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic
[Touch-packages] [Bug 1810474] Re: package libcupscgi1:amd64 2.2.7-1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1810474 Title: package libcupscgi1:amd64 2.2.7-1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in cups package in Ubuntu: New Bug description: maybe behind program unable to load ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libcupscgi1:amd64 2.2.7-1ubuntu2.2 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CupsErrorLog: E [04/Jan/2019:12:09:14 +1300] [cups-deviced] PID 2947 (gutenprint52+usb) stopped with status 1! E [05/Jan/2019:05:52:25 +1300] [cups-deviced] PID 1133 (gutenprint52+usb) stopped with status 1! Date: Fri Jan 4 18:20:16 2019 DuplicateSignature: package:libcupscgi1:amd64:2.2.7-1ubuntu2.2 Setting up cups-client (2.2.7-1ubuntu2.2) ... dpkg: error processing package libcupscgi1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2019-01-02 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: device for OfficeJet-Pro-6960: hp:/usb/OfficeJet_Pro_6960?serial=TH74J6N067 device for OfficeJet-Pro-6960-Fax-4: hpfax:/usb/OfficeJet_Pro_6960?serial=TH74J6N067 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Papersize: a4 PpdFiles: OfficeJet-Pro-6960-Fax-4: HP Fax4 hpcups OfficeJet-Pro-6960: HP Officejet Pro 6960, hpcups 3.17.10 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=e0823691-5f97-41e9-bd50-df1a2814e3d1 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=e0823691-5f97-41e9-bd50-df1a2814e3d1 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: cups Title: package libcupscgi1:amd64 2.2.7-1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/12/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.50 dmi.board.name: A320M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd06/12/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1810474/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I'm in 18.10 Adding my volume to the resume file with RESUME=/dev/mapper/ubuntu-swap doesn't work. Something to add to my story, /etc/initramfs-tools/conf.d/resume did not exist until I created it after reading this. Also, I had started using /var/swap/swap.img file for swap, could that have anything to do with it? My booting time is far greater than 30seconds. It just takes about 3 to 4 minutes if not more. Any help is greatly appreciated. -- 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/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Confirmed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1810471] Re: Styled-output incorrectly uses double-underline attribute
Launchpad has imported 4 comments from the remote bug at https://bugzilla.suse.com/show_bug.cgi?id=1105624. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2018-08-22T12:19:33+00:00 Kbabioch-b wrote: Created attachment 780410 Screenshot of messed up terminal While using curl I've stumbled upon a bug, which messes up my terminal. The end result is that the characters are bold and double underlined (see attached screenshot for details). This stays even after the invocation of curl, so I have to actively reset the terminal after invoking curl. I have the following version of curl installed: kbabioch@aquarius:~> rpm -qi curl Name: curl Version : 7.61.0 It has something to do with "styled-output", i.e. it works fine with the option "no-styled-output". stracing this, shows the following: kbabioch@aquarius:~> strace -e write -s 120 curl -I registry.opensuse.org write(1, "HTTP/1.1 301 Moved Permanently\r\n", 32HTTP/1.1 301 Moved Permanently ) = 32 write(1, "\33[1mContent-length\33[21m: 0\r\n", 28Content-length: 0 ) = 28 write(1, "\33[1mLocation\33[21m: https://registry.opensuse.org/\r\n;, 51Location: https://registry.opensuse.org/ ) = 51 write(1, "\r\n", 2 ) = 2 +++ exited with 0 +++ I'm using GNOME's terminal: kbabioch@aquarius:~> rpm -qi gnome-terminal Name: gnome-terminal Version : 3.28.2 Reply at: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1810471/comments/0 On 2018-08-22T12:24:34+00:00 Matthias-gerstner wrote: This seems to be the upstream fix: https://github.com/curl/curl/commit/a82372e0fb3aa3ce9ab27687c4d4a738a6ec9064 Reply at: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1810471/comments/1 On 2018-08-22T12:35:19+00:00 Kbabioch-b wrote: This fixes the problem, I've prepared a submission: https://build.opensuse.org/request/show/630909 Reply at: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1810471/comments/2 On 2018-08-22T14:07:45+00:00 Vcizek-l wrote: Another problem that fixed itself :-) Thanks for the report and the submission. Closing, as the bug affects Tumbleweed only. Reply at: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1810471/comments/3 ** Changed in: curl (openSUSE) Status: Unknown => Fix Released ** Changed in: curl (openSUSE) Importance: Unknown => Medium -- 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/1810471 Title: Styled-output incorrectly uses double-underline attribute Status in curl package in Ubuntu: New Status in curl package in openSUSE: Fix Released Bug description: Using --styled-output (which is the default running cURL interactive terminal) results in the double-underline text attribute being set incorrectly and remaining on after cURL exits. For example, running this in xfce4-terminal: curl -I google.com Results in double-underlined text starting from the ":" after "Location", and running into the shell prompt after cURL has exited. The intended behaviour of this feature is HTTP header names to be bold, and header values to be normal. While I noticed the problem in xfce4-terminal on Xubuntu, others have reported the issue on other terminal emulators, so I don't think this is specific to xfce4-terminal. Man page for --styled-output doesn't mention setting double underline either: Enables the automatic use of bold font styles when writing HTTP headers to the terminal. Use --no-styled-output to switch them off. Added in 7.61.0. This has already been fixed upstream by using the correct font attribute control code. Upstream cURL bug report: https://github.com/curl/curl/issues/2736 Fixed upstream in: https://github.com/curl/curl/pull/2738 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1810471/+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 1810471] [NEW] Styled-output incorrectly uses double-underline attribute
Public bug reported: Using --styled-output (which is the default running cURL interactive terminal) results in the double-underline text attribute being set incorrectly and remaining on after cURL exits. For example, running this in xfce4-terminal: curl -I google.com Results in double-underlined text starting from the ":" after "Location", and running into the shell prompt after cURL has exited. The intended behaviour of this feature is HTTP header names to be bold, and header values to be normal. While I noticed the problem in xfce4-terminal on Xubuntu, others have reported the issue on other terminal emulators, so I don't think this is specific to xfce4-terminal. Man page for --styled-output doesn't mention setting double underline either: Enables the automatic use of bold font styles when writing HTTP headers to the terminal. Use --no-styled-output to switch them off. Added in 7.61.0. This has already been fixed upstream by using the correct font attribute control code. Upstream cURL bug report: https://github.com/curl/curl/issues/2736 Fixed upstream in: https://github.com/curl/curl/pull/2738 ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Affects: curl (openSUSE) Importance: Medium Status: Fix Released ** Attachment added: "Screenshot of problem" https://bugs.launchpad.net/bugs/1810471/+attachment/5226802/+files/curl-double-underline.png ** Bug watch added: bugzilla.suse.com/ #1105624 https://bugzilla.suse.com/show_bug.cgi?id=1105624 ** Also affects: curl (openSUSE) via https://bugzilla.suse.com/show_bug.cgi?id=1105624 Importance: Unknown Status: Unknown -- 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/1810471 Title: Styled-output incorrectly uses double-underline attribute Status in curl package in Ubuntu: New Status in curl package in openSUSE: Fix Released Bug description: Using --styled-output (which is the default running cURL interactive terminal) results in the double-underline text attribute being set incorrectly and remaining on after cURL exits. For example, running this in xfce4-terminal: curl -I google.com Results in double-underlined text starting from the ":" after "Location", and running into the shell prompt after cURL has exited. The intended behaviour of this feature is HTTP header names to be bold, and header values to be normal. While I noticed the problem in xfce4-terminal on Xubuntu, others have reported the issue on other terminal emulators, so I don't think this is specific to xfce4-terminal. Man page for --styled-output doesn't mention setting double underline either: Enables the automatic use of bold font styles when writing HTTP headers to the terminal. Use --no-styled-output to switch them off. Added in 7.61.0. This has already been fixed upstream by using the correct font attribute control code. Upstream cURL bug report: https://github.com/curl/curl/issues/2736 Fixed upstream in: https://github.com/curl/curl/pull/2738 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1810471/+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 1771185] Re: Secondary monitor not connecting in 18.04 LTS
Same here. Lenovo T460s (Intel only). Cannot use HDMI to Display Port. HDMI to VGA works though on the same port!! The below is with HDMI->VGA. With HDMI->DP it just doesn't recognise the display. Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 8192 x 8192 eDP-1 connected primary 1920x1080+1233+1080 (normal left inverted right x axis y axis) 309mm x 174mm 1920x1080 60.02*+ 60.0159.9759.9659.9350.02 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 509mm x 286mm 1920x1080 60.00*+ 1600x900 60.00 1280x1024 75.0260.02 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 640x480 75.0059.94 720x400 70.08 HDMI-1 disconnected (normal left inverted right x axis y axis) 1920x1080 60.02 DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 509mm x 286mm 1920x1080 60.00*+ 60.02 1600x900 60.00 1280x1024 75.0260.02 1152x864 75.00 1280x720 60.00 1024x768 75.0360.00 800x600 75.0060.32 640x480 75.0059.94 720x400 70.08 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxrandr in Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS Status in libxrandr package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V Nitro VN7-592G-709V with Nvidia Geforce 960M (nvidia driver v390) and a Benq W1070 projector. I have upgraded from Ubuntu 16.04 to 18.04 and my projector connects for a split second and then gets disconnected. In Ubuntu 16.04 projector was working fine as a mirror display and extended desktop. Here's what I already tried: - enable the nouveau driver instead of the nvidia driver -> no result - enable the on-board intel board with sudo prime-select intel -> no result - apt purge nvidia* & reinstall nvidia driver 390 (stable) or 396 (beta) -> no result - disable nouveau driver, disable nvidia driver from the repository and install nvidia driver from nvidia website (both 390 and 396) -> no result - installed CCSM (CompizConfig Settings Manager) and disabled display auto-detection -> no result - played around with the refresh rate (some forums say that the two outputs have to be in sync -> no result - deleted the whole Ubuntu 18.04 upgrade and installed a fresh 18.04 -> still the same issue - tried to manually enable the output with xrandr --output HDMI-1-2 --mode 1920x1920 -> nothing - under settings -> devices -> displays I don't see a secondary display (just the main one) I have the latest libxrandr2, 2:1.5.1-1 under Ubuntu 18.04 (updated to day) Here is the output of xrandr the very second when I connect the projector (then HDMI-1-2 goes disconnected and no modes are displayed): ~$ xrandr Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 345mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024
[Touch-packages] [Bug 1563110]
(In reply to Jacek Jagosz from comment #105) > (In reply to marcin19883 from comment #104) > > https://github.com/conexant/codec_drivers/commits/rpi-4.4.y > > > > Autor adding support linux kernel 4.18. > > Sorry for bothering, but did he try to merge it to the main kernel? Or do we > have to compile it ourselves from this branch? I have no idea. I'm a beginning linux user. I am currently using Arch Linux and the cx2072x kernel from AUR. It works great. Everything works, even better than on ubuntu 18.04. -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~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 1810458] [NEW] do-release-upgrade fails with "No such file or directory: 'gpg'"
Public bug reported: > + do-release-upgrade Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,263 kB] Fetched 1,264 kB in 0s (0 B/s) authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' Traceback (most recent call last): File "/usr/bin/do-release-upgrade", line 200, in fetcher.run() File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 282, in run if not self.authenticate(): File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 76, in authenticate if self.gpgauthenticate(f, sig): File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 108, in gpgauthenticate close_fds=False, universal_newlines=True) File "/usr/lib/python3.5/subprocess.py", line 947, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.5/subprocess.py", line 1551, in _execute_child raise child_exception_type(errno_num, err_msg) FileNotFoundError: [Errno 2] No such file or directory: 'gpg' > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.5 LTS Release:16.04 Codename: xenial > + apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > which gpg gpg: Command not found. > which gpg2 /usr/bin/gpg2 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1810458 Title: do-release-upgrade fails with "No such file or directory: 'gpg'" Status in apparmor package in Ubuntu: New Bug description: > + do-release-upgrade Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,263 kB] Fetched 1,264 kB in 0s (0 B/s) authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' Traceback (most recent call last): File "/usr/bin/do-release-upgrade", line 200, in fetcher.run() File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 282, in run if not self.authenticate(): File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 76, in authenticate if self.gpgauthenticate(f, sig): File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeFetcherCore.py", line 108, in gpgauthenticate close_fds=False, universal_newlines=True) File "/usr/lib/python3.5/subprocess.py", line 947, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.5/subprocess.py", line 1551, in _execute_child raise child_exception_type(errno_num, err_msg) FileNotFoundError: [Errno 2] No such file or directory: 'gpg' > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial > + apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > which gpg gpg: Command not found. > which gpg2 /usr/bin/gpg2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1810458/+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 1801540]
Actually this workaround adds another problem, in games the sound is delayed... -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1801540]
A partial workaround which doesn't completely fix the issue but improves things is the following: Adding to /etc/pulse/default.pa, use_ucm=0 tsched=0 right after module- udev-detect and /etc/pulse/daemon resample-method = src-sinc-best-quality default-sample-format = s16le default-fragment-size-msec=80 default-sample-rate = 48000 Don't know which what specific parameter improved this, because when I test each one of those singularly doesn't totally fix the problem. The best results I can obtain are with all those combined -- 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/1801540 Title: Microphone distorted sound on ALC892 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+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 1810351] Re: journalctl fails to work inside systemd service
Part of the mystery is solved and part not. SOLVED: The problem was that journal entries were not being stored on disk and journalctl was not showing entries from memory. The default Ubuntu config has settings Storage=auto SplitMode=uid Also, the directory /var/log/journal does not exist by default and does not get created in Storage=auto mode. Creating the /var/log/journal directory and restarting journald so that entries get stored to disk fixes the problem. NOT SOLVED: It is still unclear why journalctl would display output when run from the shell but not when run from systemd. It would seem that in a systemd --user unit it could not access the in-memory logs. I would suggest that the default Ubuntu install should have the /var/log/journal directory in place so that journalctl will work correctly out-of-the-box. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1810351 Title: journalctl fails to work inside systemd service Status in systemd package in Ubuntu: New Bug description: Using Ubuntu 16.04.4 LTS and Package: systemd Architecture: amd64 Version: 229-4ubuntu21.10 Multi-Arch: foreign Priority: required Section: admin Origin: Ubuntu The journalctl(1) command cannot be used in a systemd OnFailure service to get error logs. To replicate the issue 1) Create a service unit [Unit] Description=%n [Service] #ExecStart=/bin/sh -xv -c 'systemctl --user status -o cat -n 20 | mail -s "Unit failed" ' ExecStart=/bin/sh -c 'journalctl --user-unit= -o verbose -q -n 20 | mail -s "Unit failed" ' 2) enable the unit 3) start the unit You will get a failure message from journalctl and mail of sh[28225]: No journal files were opened due to insufficient permissions. sh[28225]: mail: Null message body; hope that's ok 4) switch the comment # to the journalctl ExecStart and uncomment the systemctl ExecStart line From systemctl you will get journal output in the email. The man page for systemctl states "In addition, journalctl --unit=NAME or journalctl --user-unit=NAME use a similar filter for messages and might be more convenient." and indeed it would if it worked properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810351/+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 1810444] [NEW] possible gpsim fault
Public bug reported: I was trying unsuccessfully to load gpsim at the time the bug came to my attention ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jan 3 23:19:47 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:7270] InstallationDate: Installed on 2018-12-20 (14 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: ADSC Z140C ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2100f5b6-e85f-4f6c-8fd0-da01ce01659d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.version: WH-BI-14-Y116CR210-CC341-037-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvn:bvrWH-BI-14-Y116CR210-CC341-037-C:bd06/05/2017:svnADSC:pnZ140C:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z140C dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: ADSC version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Jan 3 23:17:35 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1810444 Title: possible gpsim fault Status in xorg package in Ubuntu: New Bug description: I was trying unsuccessfully to load gpsim at the time the bug came to my attention ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jan 3 23:19:47 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:7270] InstallationDate: Installed on 2018-12-20 (14 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: ADSC Z140C ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=2100f5b6-e85f-4f6c-8fd0-da01ce01659d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.version: WH-BI-14-Y116CR210-CC341-037-C dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.version: To be filled by O.E.M.
[Touch-packages] [Bug 1810439] Re: DNS/systemd-resolve: host1.foo.local cannot resolve host2.bar.local
Why isn't systemd-resolved forwarding my query for mirror1.eng.local to the configured upstream DNS server? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1810439 Title: DNS/systemd-resolve: host1.foo.local cannot resolve host2.bar.local Status in systemd package in Ubuntu: New Bug description: This is a fresh install of Ubuntu 18.04 (using the latest maas.io image). The system is in a DNS domain of "maas.local". There are other systems in this data center that are in the DNS domain "eng.local". Attempting to resolve the name of a system in the eng.local domain fails when run from the maas.local system (and vice versa, but we'll focus on the details of the former case). Details: ubuntu@kvm7246-vm009:~$ grep '^[^#]' /etc/resolv.conf nameserver 127.0.0.53 search maas.local tc82.local ubuntu@kvm7246-vm009:~$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (ens6) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.23.4.4 DNS Domain: maas.local tc82.local ubuntu@kvm7246-vm009:~$ host maas1.maas.local maas1.maas.local has address 172.23.4.4 ubuntu@kvm7246-vm009:~$ systemd-resolve maas1.maas.local maas1.maas.local: 172.23.4.4 -- Information acquired via protocol DNS in 2.3ms. -- Data is authenticated: no ubuntu@kvm7246-vm009:~$ host mirror1.eng.local Host mirror1.eng.local not found: 2(SERVFAIL) ubuntu@kvm7246-vm009:~$ systemd-resolve mirror1.eng.local mirror1.eng.local: resolve call failed: No appropriate name servers or networks for name found ubuntu@kvm7246-vm009:~$ host mirror1.eng.local 172.23.4.4 Using domain server: Name: 172.23.4.4 Address: 172.23.4.4#53 Aliases: mirror1.eng.local has address 172.21.0.66 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1810439/+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 1810439] [NEW] DNS/systemd-resolve: host1.foo.local cannot resolve host2.bar.local
Public bug reported: This is a fresh install of Ubuntu 18.04 (using the latest maas.io image). The system is in a DNS domain of "maas.local". There are other systems in this data center that are in the DNS domain "eng.local". Attempting to resolve the name of a system in the eng.local domain fails when run from the maas.local system (and vice versa, but we'll focus on the details of the former case). Details: ubuntu@kvm7246-vm009:~$ grep '^[^#]' /etc/resolv.conf nameserver 127.0.0.53 search maas.local tc82.local ubuntu@kvm7246-vm009:~$ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 2 (ens6) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 172.23.4.4 DNS Domain: maas.local tc82.local ubuntu@kvm7246-vm009:~$ host maas1.maas.local maas1.maas.local has address 172.23.4.4 ubuntu@kvm7246-vm009:~$ systemd-resolve maas1.maas.local maas1.maas.local: 172.23.4.4 -- Information acquired via protocol DNS in 2.3ms. -- Data is authenticated: no ubuntu@kvm7246-vm009:~$ host mirror1.eng.local Host mirror1.eng.local not found: 2(SERVFAIL) ubuntu@kvm7246-vm009:~$ systemd-resolve mirror1.eng.local mirror1.eng.local: resolve call failed: No appropriate name servers or networks for name found ubuntu@kvm7246-vm009:~$ host mirror1.eng.local 172.23.4.4 Using domain server: Name: 172.23.4.4 Address: 172.23.4.4#53 Aliases: mirror1.eng.local has address 172.21.0.66 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Description changed: This is a fresh install of Ubuntu 18.04 (using the latest maas.io image). The system is in a DNS domain of "maas.local". There are other systems in this data center that are in the DNS domain "eng.local". Attempting to resolve the name of a system in the eng.local domain fails when run from the maas.local system (and vice versa, but we'll focus on the details of the former case). Details: - ubuntu@kvm7246-vm009:~$ grep '^[^#]' /etc/resolv.conf + ubuntu@kvm7246-vm009:~$ grep '^[^#]' /etc/resolv.conf nameserver 127.0.0.53 search maas.local tc82.local ubuntu@kvm7246-vm009:~$ systemd-resolve --status Global - DNSSEC NTA: 10.in-addr.arpa - 16.172.in-addr.arpa - 168.192.in-addr.arpa - 17.172.in-addr.arpa - 18.172.in-addr.arpa - 19.172.in-addr.arpa - 20.172.in-addr.arpa - 21.172.in-addr.arpa - 22.172.in-addr.arpa - 23.172.in-addr.arpa - 24.172.in-addr.arpa - 25.172.in-addr.arpa - 26.172.in-addr.arpa - 27.172.in-addr.arpa - 28.172.in-addr.arpa - 29.172.in-addr.arpa - 30.172.in-addr.arpa - 31.172.in-addr.arpa - corp - d.f.ip6.arpa - home - internal - intranet - lan - local - private - test + DNSSEC NTA: 10.in-addr.arpa + 16.172.in-addr.arpa + 168.192.in-addr.arpa + 17.172.in-addr.arpa + 18.172.in-addr.arpa + 19.172.in-addr.arpa + 20.172.in-addr.arpa + 21.172.in-addr.arpa + 22.172.in-addr.arpa + 23.172.in-addr.arpa + 24.172.in-addr.arpa + 25.172.in-addr.arpa + 26.172.in-addr.arpa + 27.172.in-addr.arpa + 28.172.in-addr.arpa +
[Touch-packages] [Bug 1776475] Re: Unlocking existing session often requires several attempts.
I have a question for people experiencing this bug (yes, you included :-). Please: * open xfce4-settings-manager, * click icon "power manager", * click tab "security", * report what settings are there for when to "automatically lock the session", "delay locking after screensaver for...", "lock screen when system is going to sleep" * if the bug affects you, * and your exact distribution version. Also, since you have to login to launchpad to comment here, please answer to "does this bug affect you?" question on top of this page. This will help me figure out a proper fix. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1776475 Title: Unlocking existing session often requires several attempts. Status in lightdm package in Ubuntu: Confirmed Bug description: # Context * Computer with several X sessions opened. * Users switching from one opened session to another. * Lightdm opens new greeter, wait for typing password. * User types password. * Password is accepted. * System closes the current greeter (screen gets black for an instant). # Expected * User gets back to their already opened session. # Observed * System immediately opens another greeter. * User has to type password again. # Reproducible * Not always. At times, often, at other times, rare. # Additional information Users switch session via dm-tool switch-to-user $OTHERUSER but I guess bug appears with other means (like menu item like "lock screen", etc). # Information requested lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 LC_ALL=C apt-cache policy lightdm lightdm: Installed: 1.26.0-0ubuntu1 Candidate: 1.26.0-0ubuntu1 Version table: *** 1.26.0-0ubuntu1 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jun 12 14:14:52 2018 ExecutablePath: /usr/sbin/lightdm InstallationDate: Installed on 2018-05-25 (18 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.logrotate.d.lightdm: [modified] mtime.conffile..etc.logrotate.d.lightdm: 2018-05-25T06:19:22.081830 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1776475/+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
Re: [Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files
THANKS FOR YOUR REPLIED. IT WAS FIXED Jarno Suni <798...@bugs.launchpad.net> 于2019年1月1日周二 下午8:39写道： > cwdruf, luckily, there are some ways. > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/798414 > > Title: > update-initramfs should produce a more helpful error message when > there isn't enough free space--or provide an automatic tool for > removal of old files > > Status in initramfs-tools: > New > Status in Ubuntu Software Center: > Invalid > Status in Ubuntu: > Fix Released > Status in dpkg package in Ubuntu: > Invalid > Status in initramfs-tools package in Ubuntu: > Fix Released > > Bug description: > Binary package hint: initramfs-tools > > When installing a kernel, /boot may become full during execution of > post-installation script typically when update-initramfs is creating > or updating an initrd.img file. This is resulting in kernel > installation error. For example: > > Setting up initramfs-tools (0.98.8ubuntu3) ... > update-initramfs: deferring update (trigger activated) > Processing triggers for initramfs-tools ... > update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic > > gzip: stdout: No space left on device > E: mkinitramfs failure cpio 141 gzip 1 > update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic > dpkg: error processing initramfs-tools (--configure): >subprocess installed post-installation script returned error exit > status 1 > > Ideal behavior: > > Give a more helpful error message when this unfortunate situation > occurs so that user can fix the broken system and keep it going. > > Workaround: > > As the bug reporting system forwards user to this bug report, such > instructions can be given here: > https://help.ubuntu.com/community/RemoveOldKernels > > To manage notifications about this bug go to: > https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions > -- 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/798414 Title: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files Status in initramfs-tools: New Status in Ubuntu Software Center: Invalid Status in Ubuntu: Fix Released Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Bug description: Binary package hint: initramfs-tools When installing a kernel, /boot may become full during execution of post-installation script typically when update-initramfs is creating or updating an initrd.img file. This is resulting in kernel installation error. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Ideal behavior: Give a more helpful error message when this unfortunate situation occurs so that user can fix the broken system and keep it going. Workaround: As the bug reporting system forwards user to this bug report, such instructions can be given here: https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 319376] Re: No Dvorak layout for multilingual keyboards
Hebrew Dvorak can be found at the following address: http://mikladot.com/dvorak/hebdvork-linux.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/319376 Title: No Dvorak layout for multilingual keyboards Status in xkeyboard-config: Unknown Status in xkeyboard-config package in Ubuntu: Triaged Bug description: I use three languages in my keyboard, so after physically moving keys to dvorak, It created obvious problem. I made a fix for it, "dvorak - compatible" layouts for phonetic russian & hebrew. Hope It will be usefull to somebody. Attached files ru & il go to /etc/X11/xkb/symbols Activating them in xorg.conf: Option "XkbLayout" "ru,il,il" Option "XKbVariant""phonetic_dvorak,phonetic_dvorak,dvorak" To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/319376/+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 1810388] [NEW] syslog filled with drm messages 40 times per second
Public bug reported: Hi all, I don't really know when it exactly began. >From /var/log/syslog : Jan 3 09:42:42 localhost kernel: [32659.271016] [drm:drm_mode_addfb2 [drm]] [FB:74] Jan 3 09:42:42 localhost kernel: [32659.300800] [drm:drm_mode_addfb2 [drm]] [FB:89] There are similar bugs that have been already noticed, but none of them helped me. Changing desktop environment to a non-gnome desktop stops messages. My environment (export cmd) : declare -x XDG_CONFIG_DIRS="/etc/xdg/xdg-ubuntu:/etc/xdg" declare -x XDG_CURRENT_DESKTOP="ubuntu:GNOME" declare -x XDG_DATA_DIRS="/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop" declare -x XDG_GREETER_DATA_DIR="/var/lib/lightdm-data/userprofile" declare -x XDG_MENU_PREFIX="gnome-" declare -x XDG_RUNTIME_DIR="/run/user/1000" declare -x XDG_SEAT="seat0" declare -x XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" declare -x XDG_SESSION_DESKTOP="ubuntu" declare -x XDG_SESSION_ID="c2" declare -x XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session0" declare -x XDG_SESSION_TYPE="x11" declare -x XDG_VTNR="7" My kernel : 4.15.0-43-generic Ubuntu 18.04.01 LTS Graphic : Intel Haswell Mobile Any help is appreciated Thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jan 3 09:38:35 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-42-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed virtualbox, 5.2.18, 4.19.0-041900-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a] InstallationDate: Installed on 2016-12-20 (743 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. XPS13 9333 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=19d7298f-74c8-4a78-9f17-88b9f04bbc3a ro net.ifnames=0 biosdevname=0 acpi=force plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd08/31/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay System dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1810388 Title: syslog filled with drm messages 40 times per second Status in xorg package in Ubuntu: New Bug description: Hi all, I don't really know when it exactly began. From /var/log/syslog : Jan 3 09:42:42 localhost kernel: [32659.271016] [drm:drm_mode_addfb2 [drm]] [FB:74] Jan 3 09:42:42 localhost kernel: [32659.300800] [drm:drm_mode_addfb2 [drm]] [FB:89] There are similar bugs that have been already noticed, but none of them helped me. Changing desktop environment to a non-gnome desktop stops messages. My environment (export cmd) : declare -x XDG_CONFIG_DIRS="/etc/xdg/xdg-ubuntu:/etc/xdg" declare -x XDG_CURRENT_DESKTOP="ubuntu:GNOME" declare -x XDG_DATA_DIRS="/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop" declare -x XDG_GREETER_DATA_DIR="/var/lib/lightdm-data/userprofile" declare -x XDG_MENU_PREFIX="gnome-" declare -x XDG_RUNTIME_DIR="/run/user/1000" declare -x XDG_SEAT="seat0" declare -x
