[Touch-packages] [Bug 1901742] Re: systemd-modules-load.service fails to start because it can't understand module arguments in /etc/modules, which it shouldn't even be reading
This is an interaction between a symlink that systemd ships (as mentioned in https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=627949#10) and the kmod package (which ships the now-inaccurate /usr/share/man/man5/modules.5.gz). ** Also affects: kmod (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #627949 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627949 -- 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/1901742 Title: systemd-modules-load.service fails to start because it can't understand module arguments in /etc/modules, which it shouldn't even be reading Status in kmod package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: My systemd-modules-load.service fails to start like this: ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-10-27 10:24:52 PDT; 4s ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 23683 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 23683 (code=exited, status=1/FAILURE) Oct 27 10:24:52 octagon systemd[1]: Starting Load Kernel Modules... Oct 27 10:24:52 octagon systemd-modules-load[23683]: Failed to find module 'vfio vfio_iommu_type1 vfio_pci vfio_virqfd' Oct 27 10:24:52 octagon systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Oct 27 10:24:52 octagon systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. Oct 27 10:24:52 octagon systemd[1]: Failed to start Load Kernel Modules. It looks like it's trying to interpret a whole module-and-arguments string as just a module name, and failing to load this. By recursive grep of /etc, the only place it can be getting that string is /etc/modules: $ sudo ag vfio_iommu_type1 [sudo] password for anovak: modules 5:vfio vfio_iommu_type1 vfio_pci vfio_virqfd The manpage for /etc/modules clearly says that the file may contain module names *and* arguments: [anovak@octagon ~]$ man modules | grep Arguments The /etc/modules file contains the names of kernel modules that are to be loaded at boot time, one per line. Arguments can be given in the same line as the module name. Lines beginning with a The manpage for systemd-modules-load.service doesn't mention /etc/modules, and says to see the manpage for modules-load.d(5). That manpage says that it only reads files from specific directories: SYNOPSIS /etc/modules-load.d/*.conf /run/modules-load.d/*.conf /usr/lib/modules-load.d/*.conf The manpage is clearly lying, and systemd-modules-load.service is clearly also reading /etc/modules. Moreover, it's misreading it, and not interpreting it according to the documented semantics of /etc/modules. I was induced to create an /etc/modules like this by https://mathiashueber.com/windows-virtual-machine-gpu-passthrough- ubuntu/ but I'm not sure that it's actually getting used by anything, because lsmod shows some but not all of the options I specified. [anovak@octagon etc]$ lsmod | grep "^vfio " vfio 28672 2 vfio_iommu_type1,vfio_pci Can systemd be made to stop reading /etc/modules so that it doesn't report failure when it doesn't understand lines with options? And is that file being read by something else in the system, or should I just remove it as a workaround to stop upsetting systemd? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.42 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 10:33:50 2020 InstallationDate: Installed on 2017-08-06 (1177 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic root=UUID=5219a3ae-e14c-4f63-8f62-17cebc1af57a ro modprobe.blacklist=amdgpu usb_storage.quirks=0bc2:ab38: amd_iommu=on vfio-pci.ids=1002:67df SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-05-29 (882 days ago) dmi.bios.date: 12/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x
[Touch-packages] [Bug 1901742] [NEW] systemd-modules-load.service fails to start because it can't understand module arguments in /etc/modules, which it shouldn't even be reading
Public bug reported: My systemd-modules-load.service fails to start like this: ● systemd-modules-load.service - Load Kernel Modules Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-10-27 10:24:52 PDT; 4s ago Docs: man:systemd-modules-load.service(8) man:modules-load.d(5) Process: 23683 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE) Main PID: 23683 (code=exited, status=1/FAILURE) Oct 27 10:24:52 octagon systemd[1]: Starting Load Kernel Modules... Oct 27 10:24:52 octagon systemd-modules-load[23683]: Failed to find module 'vfio vfio_iommu_type1 vfio_pci vfio_virqfd' Oct 27 10:24:52 octagon systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Oct 27 10:24:52 octagon systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. Oct 27 10:24:52 octagon systemd[1]: Failed to start Load Kernel Modules. It looks like it's trying to interpret a whole module-and-arguments string as just a module name, and failing to load this. By recursive grep of /etc, the only place it can be getting that string is /etc/modules: $ sudo ag vfio_iommu_type1 [sudo] password for anovak: modules 5:vfio vfio_iommu_type1 vfio_pci vfio_virqfd The manpage for /etc/modules clearly says that the file may contain module names *and* arguments: [anovak@octagon ~]$ man modules | grep Arguments The /etc/modules file contains the names of kernel modules that are to be loaded at boot time, one per line. Arguments can be given in the same line as the module name. Lines beginning with a The manpage for systemd-modules-load.service doesn't mention /etc/modules, and says to see the manpage for modules-load.d(5). That manpage says that it only reads files from specific directories: SYNOPSIS /etc/modules-load.d/*.conf /run/modules-load.d/*.conf /usr/lib/modules-load.d/*.conf The manpage is clearly lying, and systemd-modules-load.service is clearly also reading /etc/modules. Moreover, it's misreading it, and not interpreting it according to the documented semantics of /etc/modules. I was induced to create an /etc/modules like this by https://mathiashueber.com/windows-virtual-machine-gpu-passthrough- ubuntu/ but I'm not sure that it's actually getting used by anything, because lsmod shows some but not all of the options I specified. [anovak@octagon etc]$ lsmod | grep "^vfio " vfio 28672 2 vfio_iommu_type1,vfio_pci Can systemd be made to stop reading /etc/modules so that it doesn't report failure when it doesn't understand lines with options? And is that file being read by something else in the system, or should I just remove it as a workaround to stop upsetting systemd? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.42 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 10:33:50 2020 InstallationDate: Installed on 2017-08-06 (1177 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic root=UUID=5219a3ae-e14c-4f63-8f62-17cebc1af57a ro modprobe.blacklist=amdgpu usb_storage.quirks=0bc2:ab38: amd_iommu=on vfio-pci.ids=1002:67df SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-05-29 (882 days ago) dmi.bios.date: 12/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4207 dmi.board.asset.tag: Default string dmi.board.name: PRIME X370-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4207:bd12/08/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.systemd.journald.conf: 2018-05-28T15:25:25.223494 mtime.conffile..etc.systemd.resolved.conf: 2017-09-24T15:57:22.768472 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1901742 Title: systemd-modules-load.service fails to start because
Re: [Touch-packages] [Bug 1813679] Re: vim-gtk can no longer save to non-group-writable files in GVFS SFTP mounts in 18.04
I haven't upgraded to Focal yet, but it's still an open issue upstream: https://github.com/vim/vim/issues/5237 May 20, 2020 5:49 AM, "Sebastien Bacher" wrote: > Is that still an issue in focal? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1813679 > > Title: > vim-gtk can no longer save to non-group-writable files in GVFS SFTP > mounts in 18.04 > > Status in gvfs package in Ubuntu: > Invalid > Status in nautilus package in Ubuntu: > Invalid > Status in vim package in Ubuntu: > New > > Bug description: > In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH > mounts (by going to `ssh://wherever` in the address bar in the file > browser and double-clicking on the file), edit them, and save them. > > In Ubuntu 18.04, when I install `vim-gtk` and try to do the same > thing, I can open the files just fine, but when I try to save them I > get a message that Vim "Can't open file for writing". > > If I check out the Vim source tree and build and install vim > v7.4.1689, which is what Xenial is shipping now, and use *that* gvim > on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from > gedit. > > Something is wrong with the gvim shipping with 18.04. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: vim-gtk (not installed) > ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 > Uname: Linux 4.15.0-44-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Mon Jan 28 15:55:56 2019 > ProcEnviron: > TERM=xterm-256color > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: vim > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to non-group-writable files in GVFS SFTP mounts in 18.04 Status in gvfs package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Invalid Status in vim package in Ubuntu: New Bug description: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+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 1861082] Re: ubuntu-bug doesn't know how to file bugs against snaps
I encountered this when trying to report a bug in the snap-store, which as far as I can tell is the new default package manager. It looks pretty silly to see Apport disclaiming responsibility for the package manager. It knows the snap is published by "canonical". Maybe everything published by "canonical" should be special-cased. -- 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/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps Status in Snapcraft: New Status in snapd: Triaged Status in Snap Store: New Status in apport package in Ubuntu: Incomplete Bug description: Hello, I had problems with subiquity in the focal live server install image. I tried to use 'ubuntu-bug subiquity' to report the bug, but ubuntu-bug apparently cannot file bug reports against snaps. This is frustrating that users need to know which portions of Ubuntu are delivered via debs, which portions are delivered by snaps, and try to find a way to report bugs correctly. ubuntu-bug should know how to report bugs for Canonical software. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+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 1870428] [NEW] ubuntu-bug cannot report a problem with the preinstalled snap-store
*** This bug is a duplicate of bug 1861082 *** https://bugs.launchpad.net/bugs/1861082 Public bug reported: With the move to package the software center as a Snap in 20.04, I decided to go fishing for bugs that might manifest on my 18.04 machine (with a home directory outside of /home), which has trouble with snaps, when I get around to upgrading. I set up this 20.04 VM, moved the home directory for the user, and tried to run `snap-store`. It didn't work. So I went to report a bug with it: ubuntu-bug snap-store This didn't work. Instead of the normal Apport report interface, I got a dialog that says: The problem cannot be reported: This report is about a snap published by canonical. No contact address has been provided; visit the forum at https://forum.snapcraft.io/ for help. If the snap-store is part of the base system, and is indeed the recommended package manager in 20.04, and Canonical published it, ubuntu-bug ought to work on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu21 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 13:41:49 2020 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** This bug has been marked a duplicate of bug 1861082 ubuntu-bug doesn't know how to file bugs against snaps -- 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/1870428 Title: ubuntu-bug cannot report a problem with the preinstalled snap-store Status in apport package in Ubuntu: New Bug description: With the move to package the software center as a Snap in 20.04, I decided to go fishing for bugs that might manifest on my 18.04 machine (with a home directory outside of /home), which has trouble with snaps, when I get around to upgrading. I set up this 20.04 VM, moved the home directory for the user, and tried to run `snap-store`. It didn't work. So I went to report a bug with it: ubuntu-bug snap-store This didn't work. Instead of the normal Apport report interface, I got a dialog that says: The problem cannot be reported: This report is about a snap published by canonical. No contact address has been provided; visit the forum at https://forum.snapcraft.io/ for help. If the snap-store is part of the base system, and is indeed the recommended package manager in 20.04, and Canonical published it, ubuntu-bug ought to work on it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu21 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 13:41:49 2020 InstallationDate: Installed on 2020-04-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870428/+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 1813679] Re: vim-gtk can no longer save to non-group-writable files in GVFS SFTP mounts in 18.04
I did a bisect as asked in the upstream issue I reported at https://github.com/vim/vim/issues/5237 and I think that https://github.com/vim/vim/commit/cd142e3369db163a511dbe9907bcd138829c is the offending commit. ** Summary changed: - vim-gtk can no longer save to GVFS SFTP mounts in 18.04 + vim-gtk can no longer save to non-group-writable files in GVFS SFTP mounts in 18.04 ** Bug watch added: github.com/vim/vim/issues #5237 https://github.com/vim/vim/issues/5237 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to non-group-writable files in GVFS SFTP mounts in 18.04 Status in gvfs package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Status in vim package in Ubuntu: New Bug description: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+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 1813679] Re: vim-gtk can no longer save to GVFS SFTP mounts in 18.04
Sorry, I misremembered my results from yesterday. I just checked again. The permissions are in fact different: the Nautilus-created files are 644 (because my "New Text Document.txt" template in ~/Templates is 644), while files created with e.g. touch are 664. Since both allow me, the owning user, to write the file, vim still shouldn't have problems, but it does seem like that is the underlying cause, rather than Nautilus having been used to create the file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS SFTP mounts in 18.04 Status in gvfs package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Status in vim package in Ubuntu: New Bug description: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+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 1813679] Re: vim-gtk can no longer save to GVFS SFTP mounts in 18.04
The permissions and ownership are the same. It seems to persist across ejecting and remounting the SSH mount. I can see if it persists across a reboot or magically spreads from one SSH mount to a different mount (via a different hostname/ip for the same machine), but I suspect it won't. November 18, 2019 12:37 PM, "Sebastien Bacher" wrote: > Thank you for your bug report. Does it only happen directly after > creating the file or is it still an issue for those files after e.G a > reboot? > > Could you see if there is anything different in permission/ownership > between the files created by nautilus and from the commandline? > > ** Changed in: nautilus (Ubuntu) > Importance: Undecided => Low > > ** Changed in: nautilus (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1813679 > > Title: > vim-gtk can no longer save to GVFS SFTP mounts in 18.04 > > Status in gvfs package in Ubuntu: > New > Status in nautilus package in Ubuntu: > Incomplete > Status in vim package in Ubuntu: > New > > Bug description: > In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH > mounts (by going to `ssh://wherever` in the address bar in the file > browser and double-clicking on the file), edit them, and save them. > > In Ubuntu 18.04, when I install `vim-gtk` and try to do the same > thing, I can open the files just fine, but when I try to save them I > get a message that Vim "Can't open file for writing". > > If I check out the Vim source tree and build and install vim > v7.4.1689, which is what Xenial is shipping now, and use *that* gvim > on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from > gedit. > > Something is wrong with the gvim shipping with 18.04. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: vim-gtk (not installed) > ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 > Uname: Linux 4.15.0-44-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Mon Jan 28 15:55:56 2019 > ProcEnviron: > TERM=xterm-256color > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: vim > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS SFTP mounts in 18.04 Status in gvfs package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Status in vim package in Ubuntu: New Bug description: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+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 1813679] Re: vim-gtk can no longer save to GVFS SFTP mounts in 18.04
I can actually only get this to manifest *for files created by Nautilus*. Files that are created from an ssh session or by cd-ing into the /run/user/1000/... directory are unaffected. So I guess this also affects Nautilus? ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS SFTP mounts in 18.04 Status in gvfs package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in vim package in Ubuntu: New Bug description: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+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 1852927] Re: Trying to save a file over SSH with GVim doesn't work; fails with "cannot open file for writing"
*** This bug is a duplicate of bug 1813679 *** https://bugs.launchpad.net/bugs/1813679 ** Description changed: To reproduce: 1. Have an SSH server you have access to. It could even be localhost. 2. Open "Files" (Nautilus), hit Ctrl+L to get the URL bar, and type in "ssh://your.server", and hit enter. 3. Authenticate to the server if necessary. It should now be mounted. 4. Create a new text file with Nautilus on the server. 5. Open that file in GVim. If GVim is not your default editor you need to right-click and choose it in "Open With Other Application". 6. Add some content to the file. 7. Try to save the file. Expected Behavior: The file should save successfully. Observed behavior: The file is not saved. Instead, GVim reports an error: - "/run/user/1000/gvfs/host=your.server/path/to/your/file.txt: E212: Can't - open file for writing" + "/run/user/1000/gvfs/sftp:host=your.server/path/to/your/file.txt: E212: + Can't open file for writing" If I navigate to that local mount directory in Bash, the file is there, with writable permissions, and I can edit it with e.g. nano. I also have no trouble wditing it with gedit. Trying to edit it with CLI "vim" produces the same E212 error. This problem started fro me with Ubuntu 18.04 and Vim 8. If I build Vim 7 from source, I don't have the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 11:11:55 2019 InstallationDate: Installed on 2017-08-06 (832 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-05-29 (537 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1852927 Title: Trying to save a file over SSH with GVim doesn't work; fails with "cannot open file for writing" Status in vim package in Ubuntu: New Bug description: To reproduce: 1. Have an SSH server you have access to. It could even be localhost. 2. Open "Files" (Nautilus), hit Ctrl+L to get the URL bar, and type in "ssh://your.server", and hit enter. 3. Authenticate to the server if necessary. It should now be mounted. 4. Create a new text file with Nautilus on the server. 5. Open that file in GVim. If GVim is not your default editor you need to right-click and choose it in "Open With Other Application". 6. Add some content to the file. 7. Try to save the file. Expected Behavior: The file should save successfully. Observed behavior: The file is not saved. Instead, GVim reports an error: "/run/user/1000/gvfs/sftp:host=your.server/path/to/your/file.txt: E212: Can't open file for writing" If I navigate to that local mount directory in Bash, the file is there, with writable permissions, and I can edit it with e.g. nano. I also have no trouble wditing it with gedit. Trying to edit it with CLI "vim" produces the same E212 error. This problem started fro me with Ubuntu 18.04 and Vim 8. If I build Vim 7 from source, I don't have the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 11:11:55 2019 InstallationDate: Installed on 2017-08-06 (832 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-05-29 (537 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1852927/+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 1852927] Re: Trying to save a file over SSH with GVim doesn't work; fails with "cannot open file for writing"
*** This bug is a duplicate of bug 1813679 *** https://bugs.launchpad.net/bugs/1813679 Looks like I reported this already ages ago, but as far as I can tell nobody noticed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1852927 Title: Trying to save a file over SSH with GVim doesn't work; fails with "cannot open file for writing" Status in vim package in Ubuntu: New Bug description: To reproduce: 1. Have an SSH server you have access to. It could even be localhost. 2. Open "Files" (Nautilus), hit Ctrl+L to get the URL bar, and type in "ssh://your.server", and hit enter. 3. Authenticate to the server if necessary. It should now be mounted. 4. Create a new text file with Nautilus on the server. 5. Open that file in GVim. If GVim is not your default editor you need to right-click and choose it in "Open With Other Application". 6. Add some content to the file. 7. Try to save the file. Expected Behavior: The file should save successfully. Observed behavior: The file is not saved. Instead, GVim reports an error: "/run/user/1000/gvfs/host=your.server/path/to/your/file.txt: E212: Can't open file for writing" If I navigate to that local mount directory in Bash, the file is there, with writable permissions, and I can edit it with e.g. nano. I also have no trouble wditing it with gedit. Trying to edit it with CLI "vim" produces the same E212 error. This problem started fro me with Ubuntu 18.04 and Vim 8. If I build Vim 7 from source, I don't have the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 11:11:55 2019 InstallationDate: Installed on 2017-08-06 (832 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-05-29 (537 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1852927/+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 1813679] Re: vim-gtk can no longer save to GVFS STFP mounts in 18.04
This is an interaction between vim and GVFS, so I've added GVFS as affected. ** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Summary changed: - vim-gtk can no longer save to GVFS STFP mounts in 18.04 + vim-gtk can no longer save to GVFS SFTP mounts in 18.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS SFTP mounts in 18.04 Status in gvfs package in Ubuntu: New Status in vim package in Ubuntu: New Bug description: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+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 1852927] [NEW] Trying to save a file over SSH with GVim doesn't work; fails with "cannot open file for writing"
*** This bug is a duplicate of bug 1813679 *** https://bugs.launchpad.net/bugs/1813679 Public bug reported: To reproduce: 1. Have an SSH server you have access to. It could even be localhost. 2. Open "Files" (Nautilus), hit Ctrl+L to get the URL bar, and type in "ssh://your.server", and hit enter. 3. Authenticate to the server if necessary. It should now be mounted. 4. Create a new text file with Nautilus on the server. 5. Open that file in GVim. If GVim is not your default editor you need to right-click and choose it in "Open With Other Application". 6. Add some content to the file. 7. Try to save the file. Expected Behavior: The file should save successfully. Observed behavior: The file is not saved. Instead, GVim reports an error: "/run/user/1000/gvfs/host=your.server/path/to/your/file.txt: E212: Can't open file for writing" If I navigate to that local mount directory in Bash, the file is there, with writable permissions, and I can edit it with e.g. nano. I also have no trouble wditing it with gedit. Trying to edit it with CLI "vim" produces the same E212 error. This problem started fro me with Ubuntu 18.04 and Vim 8. If I build Vim 7 from source, I don't have the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 11:11:55 2019 InstallationDate: Installed on 2017-08-06 (832 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-05-29 (537 days ago) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** This bug has been marked a duplicate of bug 1813679 vim-gtk can no longer save to GVFS STFP mounts in 18.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1852927 Title: Trying to save a file over SSH with GVim doesn't work; fails with "cannot open file for writing" Status in vim package in Ubuntu: New Bug description: To reproduce: 1. Have an SSH server you have access to. It could even be localhost. 2. Open "Files" (Nautilus), hit Ctrl+L to get the URL bar, and type in "ssh://your.server", and hit enter. 3. Authenticate to the server if necessary. It should now be mounted. 4. Create a new text file with Nautilus on the server. 5. Open that file in GVim. If GVim is not your default editor you need to right-click and choose it in "Open With Other Application". 6. Add some content to the file. 7. Try to save the file. Expected Behavior: The file should save successfully. Observed behavior: The file is not saved. Instead, GVim reports an error: "/run/user/1000/gvfs/host=your.server/path/to/your/file.txt: E212: Can't open file for writing" If I navigate to that local mount directory in Bash, the file is there, with writable permissions, and I can edit it with e.g. nano. I also have no trouble wditing it with gedit. Trying to edit it with CLI "vim" produces the same E212 error. This problem started fro me with Ubuntu 18.04 and Vim 8. If I build Vim 7 from source, I don't have the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim 2:8.0.1453-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 11:11:55 2019 InstallationDate: Installed on 2017-08-06 (832 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to bionic on 2018-05-29 (537 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1852927/+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 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
This is actually a kernel bug, in Linux. The issue is the absence of
platform data for this particular board in the snd_soc_rt5645 module.
The issue can be worked around by creating
/etc/modprobe.d/hacksound.conf with the following contents:
# Invert jack detection (1) and use detection mode 2 (2).
options snd_soc_rt5645 quirk=0x21
This takes advantage of the "quirk" option for the module, added in
https://github.com/torvalds/linux/commit/4999b0214b05a08b42bbafcb29a0b9c413002d3f,
which allows overriding the platform data it usually just has built into
it about how audio jacks are hooked up on particular systems.
It looks like this board needs special system info added to
sound/soc/codecs/rt5645.c, keyed on DMI data. The platform data would
look something like:
static const struct rt5645_platform_data lattepanda_platform_data = {
.jd_mode = 2,
.inv_jd1_1 = true
};
Here's the DMI data for the motherboard; it's a bit generic. I can
provide other DMI data to match on if needed.
Base Board Information
Manufacturer: AMI Corporation
Product Name: Cherry Trail CR
Version: Default string
Serial Number: Default string
Asset Tag: Default string
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Default string
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0
** Package changed: alsa-lib (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1824259
Title:
Headphone jack switch sense is inverted: plugging in headphones
disables headphone output
Status in linux package in Ubuntu:
Incomplete
Bug description:
My machine is a LattePanda board, which uses a "chtrt5645" device as a
sound card. It has a single headphone output jack, which I think is a
TRRS jack, with a mic input, such as is normally used on phones.
When I don't have headphones plugged in, the system thinks headphones
*are* plugged in. Gnome Control Center shows my audio device as being
headphones. If I insert a headphone connector partway into the jack, I
can even get sound in the headphones.
But if I plug the headphones all the way in, the system decided that I
have *un*plugged the headphones, and switches output over to
"Speaker". The system doesn't actually have a speaker, only a
headphone jack. And when the system switches over to "Speaker", I get
no sound out of the headphones, even if I open "pavucontrol" and swap
over to "Headphones (unplugged)" on the "Output Devices" tab.
This is what "pacmd"'s "list-cards" command says with my headphones
*unplugged*:
2 card(s) available.
index: 0
name:
driver:
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path =
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2)
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2)
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3)
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3)
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile:
ports:
[Touch-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
This may be a kernel driver bug, and a regression from 4.12. See http://www.lattepanda.com/topic-p24689.html?sid=1fa88916eb19dd9d65e0abd3ecbf6210#p24689 This may be a missing piece of platform data in the kernel that would tell it to invert jack detection on this particular board. I will try testing with the functionality added to the kernel in https://github.com/torvalds/linux/commit/4999b0214b05a08b42bbafcb29a0b9c413002d3f which lets you tinker with the platform data at runtime. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output Status in alsa-lib package in Ubuntu: New Bug description: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645"
[Touch-packages] [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
If I save the ALSA state with the headphones unplugged to a file:
sudo alsactl --file=settings-out.txt store
And then plug in the headphones and restore it:
sudo alsactl --file=settings-out.txt restore
I still get no sound. But then diffing the final state against the
unplugged state did find this:
control.175 {
iface CARD
name 'Headphone Jack'
- value false
+ value true
comment {
access read
type BOOLEAN
count 1
}
}
control.176 {
iface CARD
name 'Headset Mic Jack'
- value false
+ value true
comment {
access read
type BOOLEAN
count 1
}
}
I need to convince ALSA to report/interpret those boolean jack states
the other way around.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1824259
Title:
Headphone jack switch sense is inverted: plugging in headphones
disables headphone output
Status in alsa-lib package in Ubuntu:
New
Bug description:
My machine is a LattePanda board, which uses a "chtrt5645" device as a
sound card. It has a single headphone output jack, which I think is a
TRRS jack, with a mic input, such as is normally used on phones.
When I don't have headphones plugged in, the system thinks headphones
*are* plugged in. Gnome Control Center shows my audio device as being
headphones. If I insert a headphone connector partway into the jack, I
can even get sound in the headphones.
But if I plug the headphones all the way in, the system decided that I
have *un*plugged the headphones, and switches output over to
"Speaker". The system doesn't actually have a speaker, only a
headphone jack. And when the system switches over to "Speaker", I get
no sound out of the headphones, even if I open "pavucontrol" and swap
over to "Headphones (unplugged)" on the "Output Devices" tab.
This is what "pacmd"'s "list-cards" command says with my headphones
*unplugged*:
2 card(s) available.
index: 0
name:
driver:
owner module: 7
properties:
alsa.card = "1"
alsa.card_name = "Intel HDMI/DP LPE Audio"
alsa.long_card_name = "Intel HDMI/DP LPE Audio"
alsa.driver_name = "snd_hdmi_lpe_audio"
device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio"
sysfs.path =
"/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "22b0"
device.product.name = "Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
device.string = "1"
device.description = "Atom/Celeron/Pentium Processor
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
output:hdmi-stereo: Digital Stereo (HDMI) Output (priority
5900, available: no)
output:hdmi-surround: Digital Surround 5.1 (HDMI) Output
(priority 800, available: no)
output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output
(priority 800, available: no)
output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output
(priority 5700, available: no)
output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2)
Output (priority 600, available: no)
output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2)
Output (priority 600, available: no)
output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output
(priority 5700, available: no)
output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3)
Output (priority 600, available: no)
output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3)
Output (priority 600, available: no)
off: Off (priority 0, available: unknown)
active profile:
ports:
hdmi-output-0: HDMI / DisplayPort (priority 5900, latency
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency
offset 0 usec, available: no)
properties:
device.icon_name = "video-display"
hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency
offset 0 usec, available: no)
[Touch-packages] [Bug 1824259] [NEW] Headphone jack switch sense is inverted: plugging in headphones disables headphone output
Public bug reported: My machine is a LattePanda board, which uses a "chtrt5645" device as a sound card. It has a single headphone output jack, which I think is a TRRS jack, with a mic input, such as is normally used on phones. When I don't have headphones plugged in, the system thinks headphones *are* plugged in. Gnome Control Center shows my audio device as being headphones. If I insert a headphone connector partway into the jack, I can even get sound in the headphones. But if I plug the headphones all the way in, the system decided that I have *un*plugged the headphones, and switches output over to "Speaker". The system doesn't actually have a speaker, only a headphone jack. And when the system switches over to "Speaker", I get no sound out of the headphones, even if I open "pavucontrol" and swap over to "Headphones (unplugged)" on the "Output Devices" tab. This is what "pacmd"'s "list-cards" command says with my headphones *unplugged*: 2 card(s) available. index: 0 name: driver: owner module: 7 properties: alsa.card = "1" alsa.card_name = "Intel HDMI/DP LPE Audio" alsa.long_card_name = "Intel HDMI/DP LPE Audio" alsa.driver_name = "snd_hdmi_lpe_audio" device.bus_path = "pci-:00:02.0-platform-hdmi-lpe-audio" sysfs.path = "/devices/pci:00/:00:02.0/hdmi-lpe-audio/sound/card1" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "22b0" device.product.name = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" device.string = "1" device.description = "Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" profiles: output:hdmi-stereo: Digital Stereo (HDMI) Output (priority 5900, available: no) output:hdmi-surround: Digital Surround 5.1 (HDMI) Output (priority 800, available: no) output:hdmi-surround71: Digital Surround 7.1 (HDMI) Output (priority 800, available: no) output:hdmi-stereo-extra1: Digital Stereo (HDMI 2) Output (priority 5700, available: no) output:hdmi-surround-extra1: Digital Surround 5.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-surround71-extra1: Digital Surround 7.1 (HDMI 2) Output (priority 600, available: no) output:hdmi-stereo-extra2: Digital Stereo (HDMI 3) Output (priority 5700, available: no) output:hdmi-surround-extra2: Digital Surround 5.1 (HDMI 3) Output (priority 600, available: no) output:hdmi-surround71-extra2: Digital Surround 7.1 (HDMI 3) Output (priority 600, available: no) off: Off (priority 0, available: unknown) active profile: ports: hdmi-output-0: HDMI / DisplayPort (priority 5900, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-1: HDMI / DisplayPort 2 (priority 5800, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" hdmi-output-2: HDMI / DisplayPort 3 (priority 5700, latency offset 0 usec, available: no) properties: device.icon_name = "video-display" index: 1 name: driver: owner module: 8 properties: alsa.card = "0" alsa.card_name = "chtrt5645" alsa.long_card_name = "AMICorporation-Defaultstring-Defaultstring-CherryTrailCR" alsa.driver_name = "snd_soc_sst_cht_bsw_rt5645" device.bus_path = "platform-cht-bsw-rt5645" sysfs.path = "/devices/pci:00/808622A8:00/cht-bsw-rt5645/sound/card0" device.form_factor = "internal" device.string = "0" device.description = "Built-in Audio" module-udev-detect.discovered = "1" device.icon_name = "audio-card" profiles: HiFi: Default (priority 8000, available: unknown) off: Off (priority 0, available: unknown) active profile: sinks: alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink/#0: Built-in Audio Headphones + Speaker sources: alsa_output.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__sink.monitor/#0: Monitor of Built-in Audio Headphones + Speaker alsa_input.platform-cht-bsw-rt5645.HiFi__hw_chtrt5645__source/#1:
[Touch-packages] [Bug 1813679] [NEW] vim-gtk can no longer save to GVFS STFP mounts in 18.04
Public bug reported: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vim (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS STFP mounts in 18.04 Status in vim package in Ubuntu: New Bug description: In Ubuntu 16.04, with gvim 7.4.1689, I can open files over GVFS SSH mounts (by going to `ssh://wherever` in the address bar in the file browser and double-clicking on the file), edit them, and save them. In Ubuntu 18.04, when I install `vim-gtk` and try to do the same thing, I can open the files just fine, but when I try to save them I get a message that Vim "Can't open file for writing". If I check out the Vim source tree and build and install vim v7.4.1689, which is what Xenial is shipping now, and use *that* gvim on Ubuntu 18.04, I can save over SSH mounts. I can also save fine from gedit. Something is wrong with the gvim shipping with 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vim-gtk (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 28 15:55:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1813679/+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 1793920] [NEW] software-properties-gtk prompts me to install the nVidia proprietary drivers on a system using Xen, leading to no video on the next boot
Public bug reported: nVidia's proprietary drivers don't work when the kernel is running under the Xen hypervisor; nVidia knows this and has chosen not to implement Xen support. However, I did not know this. On my Ubuntu Xen dom0 system, I went into Ubuntu's "Software & Updates", on the "Additional Drivers" tab, and selected "Using NVIDIA driver metapackage from nvidia-driver-390" as my GPU driver. The driver was available, with no warning associated with it, and it seemed to install correctly. However, upon rebooting, I had no video output. I had to mess about in Grub to boot the system without Xen, and now I'm going to have to uninstall the nVidia proprietary drivers. The "Additional Drivers" UI should not present the option to install the proprietary nVidia drivers if the system is running under Xen, because doing so renders the system unusable in that configuration until the drivers are removed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 22 15:09:38 2018 InstallationDate: Installed on 2017-08-06 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-05-29 (116 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1793920 Title: software-properties-gtk prompts me to install the nVidia proprietary drivers on a system using Xen, leading to no video on the next boot Status in software-properties package in Ubuntu: New Bug description: nVidia's proprietary drivers don't work when the kernel is running under the Xen hypervisor; nVidia knows this and has chosen not to implement Xen support. However, I did not know this. On my Ubuntu Xen dom0 system, I went into Ubuntu's "Software & Updates", on the "Additional Drivers" tab, and selected "Using NVIDIA driver metapackage from nvidia-driver-390" as my GPU driver. The driver was available, with no warning associated with it, and it seemed to install correctly. However, upon rebooting, I had no video output. I had to mess about in Grub to boot the system without Xen, and now I'm going to have to uninstall the nVidia proprietary drivers. The "Additional Drivers" UI should not present the option to install the proprietary nVidia drivers if the system is running under Xen, because doing so renders the system unusable in that configuration until the drivers are removed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.5 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 22 15:09:38 2018 InstallationDate: Installed on 2017-08-06 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to bionic on 2018-05-29 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1793920/+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 1772747] [NEW] Package is missing several dependencies
Public bug reported: libcurl4-gnutls-dev provides my /usr/bin/curl-config and the static library (symlink) /usr/lib/x86_64-linux-gnu/libcurl.a -> libcurl- gnutls.a. I am trying to link statically against that static library. The right way to do this seems to be to run "curl-config --static-libs" and forward the result along to my linker. But doing that causes the linker to complain about several missing libraries. The flags I get are: -Wl,-Bstatic -lcurl -Wl,-Bdynamic -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -lnghttp2 -lidn2 -lrtmp -lpsl -lnettle -lgnutls -llber -lldap -llber -lz And the (unique) missing libraries are: /usr/bin/x86_64-linux-gnu-ld: cannot find -lnghttp2 /usr/bin/x86_64-linux-gnu-ld: cannot find -lidn2 /usr/bin/x86_64-linux-gnu-ld: cannot find -lrtmp /usr/bin/x86_64-linux-gnu-ld: cannot find -lpsl /usr/bin/x86_64-linux-gnu-ld: cannot find -lnettle /usr/bin/x86_64-linux-gnu-ld: cannot find -lgnutls /usr/bin/x86_64-linux-gnu-ld: cannot find -llber /usr/bin/x86_64-linux-gnu-ld: cannot find -lldap So pretty much all the interesting libraries are missing. The packages that provide these are: libnghttp2-dev provides libnghttp2.a libidn2-dev provides libidn2.a librtmp-dev provides librtmp.a libpsl-dev provides libpsl.a nettle-dev provides libnettle.a libgnutls28-dev (in Bionic) and other packages in older releases provide libgnutls.a libldap2-dev provides liblber.a and libldap.a All of these packages need to be dependencies of libcurl4-gnutls-dev, so that libcurl.a can be used. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcurl4-gnutls-dev 7.58.0-2ubuntu3.1 ProcVersionSignature: User Name 4.15.0-1009.9-azure 4.15.17 Uname: Linux 4.15.0-1009-azure x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Tue May 22 20:41:00 2018 SourcePackage: curl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- 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/1772747 Title: Package is missing several dependencies Status in curl package in Ubuntu: New Bug description: libcurl4-gnutls-dev provides my /usr/bin/curl-config and the static library (symlink) /usr/lib/x86_64-linux-gnu/libcurl.a -> libcurl- gnutls.a. I am trying to link statically against that static library. The right way to do this seems to be to run "curl-config --static- libs" and forward the result along to my linker. But doing that causes the linker to complain about several missing libraries. The flags I get are: -Wl,-Bstatic -lcurl -Wl,-Bdynamic -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -lnghttp2 -lidn2 -lrtmp -lpsl -lnettle -lgnutls -llber -lldap -llber -lz And the (unique) missing libraries are: /usr/bin/x86_64-linux-gnu-ld: cannot find -lnghttp2 /usr/bin/x86_64-linux-gnu-ld: cannot find -lidn2 /usr/bin/x86_64-linux-gnu-ld: cannot find -lrtmp /usr/bin/x86_64-linux-gnu-ld: cannot find -lpsl /usr/bin/x86_64-linux-gnu-ld: cannot find -lnettle /usr/bin/x86_64-linux-gnu-ld: cannot find -lgnutls /usr/bin/x86_64-linux-gnu-ld: cannot find -llber /usr/bin/x86_64-linux-gnu-ld: cannot find -lldap So pretty much all the interesting libraries are missing. The packages that provide these are: libnghttp2-dev provides libnghttp2.a libidn2-dev provides libidn2.a librtmp-dev provides librtmp.a libpsl-dev provides libpsl.a nettle-dev provides libnettle.a libgnutls28-dev (in Bionic) and other packages in older releases provide libgnutls.a libldap2-dev provides liblber.a and libldap.a All of these packages need to be dependencies of libcurl4-gnutls-dev, so that libcurl.a can be used. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcurl4-gnutls-dev 7.58.0-2ubuntu3.1 ProcVersionSignature: User Name 4.15.0-1009.9-azure 4.15.17 Uname: Linux 4.15.0-1009-azure x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Tue May 22 20:41:00 2018 SourcePackage: curl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1772747/+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 1772742] [NEW] libglib2.0-dev needs a dependency on libffi-dev because its pkg-config file specifies -lffi
Public bug reported: The pkg-config file at /usr/lib/x86_64-linux- gnu/pkgconfig/gobject-2.0.pc has "-lffi" in its "Libs.private". This means that when you ask pkg-config how to link statically against gobject-2.0, with "pkg-config --libs --static gobject-2.0", you get a series of linker flags that say you need to link against, among other things, libffi with "-lffi". But the static library for libffi is in package libffi-dev, which libglib2.0-dev doesn't depend on. So if you actually try to use those linker flags and libffi-dev doesn't happen to be installed, your build will crash. I think that libglib2.0-dev needs to be made to depend on libffi-dev (so that the library is always available). Alternately, if -lffi isn't actually needed to link against the static /usr/lib/x86_64-linux- gnu/libgobject-2.0.a, then -lffi needs to be removed from the pkg-config file so that builds don't go looking for it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libglib2.0-dev 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 22 13:09:39 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-18 (1859 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: glib2.0 UpgradeStatus: Upgraded to xenial on 2018-02-26 (85 days ago) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- 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/1772742 Title: libglib2.0-dev needs a dependency on libffi-dev because its pkg-config file specifies -lffi Status in glib2.0 package in Ubuntu: New Bug description: The pkg-config file at /usr/lib/x86_64-linux- gnu/pkgconfig/gobject-2.0.pc has "-lffi" in its "Libs.private". This means that when you ask pkg-config how to link statically against gobject-2.0, with "pkg-config --libs --static gobject-2.0", you get a series of linker flags that say you need to link against, among other things, libffi with "-lffi". But the static library for libffi is in package libffi-dev, which libglib2.0-dev doesn't depend on. So if you actually try to use those linker flags and libffi-dev doesn't happen to be installed, your build will crash. I think that libglib2.0-dev needs to be made to depend on libffi-dev (so that the library is always available). Alternately, if -lffi isn't actually needed to link against the static /usr/lib/x86_64-linux- gnu/libgobject-2.0.a, then -lffi needs to be removed from the pkg- config file so that builds don't go looking for it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libglib2.0-dev 2.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: XFCE Date: Tue May 22 13:09:39 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-18 (1859 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: glib2.0 UpgradeStatus: Upgraded to xenial on 2018-02-26 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1772742/+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 1253638] Re: dynamic linker does not use DT_RUNPATH for transitive dependencies
I don't know if this is expected behavior, but it's certainly annoying behavior. I'm writing an app that depends on libtcodxx.so, which in turn depends on libtcod.so. I want to ship them both in the lib directory next to my app. With RUNPATH as "$ORIGIN/lib", it finds the direct dependency (libtcodxx.so) and then doesn't look in the same directory for its dependency. To get it to search there for both, I have to set RPATH to "$ORIGIN/lib", and I suspect that RPATH may not technically be supposed to support the $ORIGIN syntax. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1253638 Title: dynamic linker does not use DT_RUNPATH for transitive dependencies Status in eglibc package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 $ uname -a Linux mhassert 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $gcc -dumpversion 4.8 $ ld -v GNU ld (GNU Binutils for Ubuntu) 2.23.52.20130913 $ LC_ALL=C apt-cache policy libc-bin libc-bin: Installed: 2.17-93ubuntu4 * What you expected to happen Binaries with DT_RPATH or DT_RUNPATH behaving identical in the absence of LD_LIBRARY_PATH * What happened instead DT_RUNPATH not searched for transitive dependencies. When running a binary that depends on custom libraries which in turn depend on custom libraries, hard-coded search paths in DT_RUNPATH behave differently from those in DT_RPATH. Paths in DT_RPATH are being considered for everything that is dynamically loaded, even dependencies of dependencies. Paths in DT_RUNPATH seem being considered only for direct dependencies of the binary. Searching the web I think that the one and only difference between DT_RPATH and DT_RUNPATH should be that DT_RPATH is considered _before_ LD_LIBRARY_PATH and DT_RUNPATH _afterwards_. In the absence of LD_LIBRARY_PATH there should be no difference at all. I stumbled upon this problem when switching from "ld" to "gold" for the linker. The default for ld on Ubuntu 13.10 is "--disable-new- dtags" while the default for gold is "--enable-new-dtags". Therefore ld produces binaries with DT_RPATH and gold ones with DT_RUNPATH. In the attached minimal example - the binaries rpath and runpath both depend on libb but not directly on liba. - libb depends on liba. - liba and libb are linked without any hard-coded library paths. - rpath and runpath are linked with hard-coded library paths for both liba and libb - rpath is linked with --disable-new-dtags (producing DT_RPATH) - rpath is linked with --enable-new-dtags (producing DT_RUNPATH) To test, please run make all and observe how "rpath" works while "runpath" fails to find liba at runtime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1253638/+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 1375430] [NEW] ping6 output too wide
Public bug reported: A fully-filled-in IPv6 address is 8 groups of 4 characters each, with 7 colons, for a total of 39 characters. This is much longer than the 4 * 4 + 3 = 19 characters maximum required to represent an IPv4 address, which is what the output format that ping6 inherits from ping was designed around. When asked to ping a full IPv6 address, ping6's output wraps just a few characters onto the next 80-character line: anovak@hex:~$ ping6 fc19:fcfd:28e4:29a8:6ccd:04c2:e736:9c95 PING fc19:fcfd:28e4:29a8:6ccd:04c2:e736:9c95(fc19:fcfd:28e4:29a8:6ccd:4c2:e736:9 c95) 56 data bytes 64 bytes from fc19:fcfd:28e4:29a8:6ccd:4c2:e736:9c95: icmp_seq=1 ttl=42 time=89. 6 ms 64 bytes from fc19:fcfd:28e4:29a8:6ccd:4c2:e736:9c95: icmp_seq=2 ttl=42 time=111 ms If something could be cut from the output format (maybe the icmp_ in icmp_seq, or the from?), the output for pinging a full IPv6 address could fit on one 80-character terminal line, just like that from pinging an IPv4 address. This would make the ping6 tool much more useable, as the round trip times would not be constantly split over two lines, and it would then be much easier to take in latency at a glance. Please reduce the number of characters in the output format so that a ping to an IPv6 address produces =80 characters of output per ping in this common use case. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: iputils-ping 3:20101006-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-69.103-generic 3.2.62 Uname: Linux 3.2.0-69-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.7 Architecture: amd64 Date: Mon Sep 29 12:02:49 2014 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iputils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1375430 Title: ping6 output too wide Status in “iputils” package in Ubuntu: New Bug description: A fully-filled-in IPv6 address is 8 groups of 4 characters each, with 7 colons, for a total of 39 characters. This is much longer than the 4 * 4 + 3 = 19 characters maximum required to represent an IPv4 address, which is what the output format that ping6 inherits from ping was designed around. When asked to ping a full IPv6 address, ping6's output wraps just a few characters onto the next 80-character line: anovak@hex:~$ ping6 fc19:fcfd:28e4:29a8:6ccd:04c2:e736:9c95 PING fc19:fcfd:28e4:29a8:6ccd:04c2:e736:9c95(fc19:fcfd:28e4:29a8:6ccd:4c2:e736:9 c95) 56 data bytes 64 bytes from fc19:fcfd:28e4:29a8:6ccd:4c2:e736:9c95: icmp_seq=1 ttl=42 time=89. 6 ms 64 bytes from fc19:fcfd:28e4:29a8:6ccd:4c2:e736:9c95: icmp_seq=2 ttl=42 time=111 ms If something could be cut from the output format (maybe the icmp_ in icmp_seq, or the from?), the output for pinging a full IPv6 address could fit on one 80-character terminal line, just like that from pinging an IPv4 address. This would make the ping6 tool much more useable, as the round trip times would not be constantly split over two lines, and it would then be much easier to take in latency at a glance. Please reduce the number of characters in the output format so that a ping to an IPv6 address produces =80 characters of output per ping in this common use case. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: iputils-ping 3:20101006-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-69.103-generic 3.2.62 Uname: Linux 3.2.0-69-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.7 Architecture: amd64 Date: Mon Sep 29 12:02:49 2014 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1375430/+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
