[Bug 1861327] Re: [needs-packaging] Can't run npm because of outdated nodejs in repos
There's something deeply wrong with the way Ubuntu packages Node. Here's the NodeJS project's release timeline: https://nodejs.org/en/about/releases/ Node LTS releases are even-numbered and supported for 30 months. Node 10 isn't even on there anymore. Node 12 is the oldest currently available, in maintenance mode, until it goes fully EOL at the end of April 2022. It's also the Node packaged in Ubuntu 21.10, released last month, which isn't EOL until July 2022. So for the last 3 months of 21.10's life, we've arranged for it to be running a dead NodeJS with no security updates. Presumably the Ubuntu NodeJS packagers have volunteered to backport them? But they can't backport the modules, which is what NodeJS exists to run. Unless 22.04 skips right ahead to Node 16, it's going to once again ship a NodeJS that's scheduled to go out of support and be left behind by the module ecosystem an entire year before the next Ubuntu LTS is ready. And since the LTS support timeline extends beyond that, if the package isn't bumped during the release lifecycle, it will spend a lot of its life being terminally out of date relative to what people need it for (running modules). We ought to have a plan to provide an in-support Node for the full life of the LTS release. We do this with other packages like Firefox, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861327 Title: [needs-packaging] Can't run npm because of outdated nodejs in repos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1861327/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1901742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901742 Title: systemd-modules-load.service fails to start because it can't understand
Re: [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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870430] Re: snap-store does not start when the user's home directory is not /home/$USER
I'm not quite sure how to mark this on Launchpad as a general 20.04 system integration problem, rather than really quite being snap-store's fault/responsibility. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870430 Title: snap-store does not start when the user's home directory is not /home/$USER To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1870430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870430] [NEW] snap-store does not start when the user's home directory is not /home/$USER
Public bug reported: When I set my home directory to e.g. /alt/home/$USER, I cannot open `snap-store`, the new default package manager for 20.04. When starting it from Gnome, I just get nothing. When starting it from the command line, I get: $ snap-store Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. How is 20.04 going to deal with home directories outside of /home if critical parts of the system (such as the package manager) are now Snaps? Is that configuration just not allowed anymore? Is the upgrade smart enough to see if some users on the system can't run Snaps and not transition the old Software Center to the Snap Store in those cases? ** Affects: snap-store Importance: Undecided Status: New ** Affects: ubuntu Importance: Undecided Status: New ** Also affects: snap-store Importance: Undecided Status: New ** No longer affects: usd-importer ** Also affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870430 Title: snap-store does not start when the user's home directory is not /home/$USER To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1870430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861082 Title: ubuntu-bug doesn't know how to file bugs against snaps To manage notifications about this bug go to: https://bugs.launchpad.net/snapcraft/+bug/1861082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870428 Title: ubuntu-bug cannot report a problem with the preinstalled snap-store To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1870428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS SFTP mounts in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS SFTP mounts in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS SFTP mounts in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1852927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS SFTP mounts in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1813679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1852927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to 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" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1852927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844443] Re: Version check wrapper scripts for e.g. perf packaged in linux-tools-common prevent usage in a Docker container e.g. on Kubernetes
There's not really an applicable Ubuntu kernel to collect logs for; the problem is only apparent in a container on top of a host that doesn't run a recognized kernel. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/183 Title: Version check wrapper scripts for e.g. perf packaged in linux-tools- common prevent usage in a Docker container e.g. on Kubernetes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844443] Re: Version check wrapper scripts for e.g. perf packaged in linux-tools-common prevent usage in a Docker container e.g. on Kubernetes
I reported this bug from this container running on an Ubuntu-based host where I built it. When I tried to run ubuntu-bug in the container on the host where I actually encountered the problem, it refused to report the bug due to... a non-Ubuntu kernel! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/183 Title: Version check wrapper scripts for e.g. perf packaged in linux-tools- common prevent usage in a Docker container e.g. on Kubernetes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844443] [NEW] Version check wrapper scripts for e.g. perf packaged in linux-tools-common prevent usage in a Docker container e.g. on Kubernetes
Public bug reported: The `perf` profiling tool, and a few other tools, are part of the Linux project. Ubuntu gets them from a package specific to the running kernel version, and uses wrapper scripts installed as e.g. /usr/bin/perf to dispatch to the appropriate version for the running kernel. This appears to involve not only checking the actual kernel version number (e.g. 4.15.0) but also the patch level/build number and flavor that Ubuntu adds (e.g. 4.15.0-62-generic) if found in the kernel version. This is perfectly fine on a real system, where Ubuntu's package manager is actually in control of the kernel. But Ubuntu is also fantastically popular as a base for Docker images, and in a Docker container you have to take your lumps and run on whatever kernel version the host happens to be using, even if the host isn't using an official Ubuntu kernel, or running Ubuntu at all. As currently designed, the linux-tools-common wrapper scripts cannot work reliably in a Docker environment. When running in my particular Kubernetes environment (where the host is some kind of Red Hat Enterprise Linux derivative), this problem manifests as the following exchange: root@adamnovak-pod:/vg# perf record ls WARNING: perf not found for kernel 3.10.0 You may need to install the following packages for this specific kernel: linux-tools-3.10.0 You may also want to install one of the following packages to keep up to date: linux-tools root@adamnovak-pod:/vg# apt install linux-tools-3.10.0 Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package linux-tools-3.10.0 E: Couldn't find any package by glob 'linux-tools-3.10.0' E: Couldn't find any package by regex 'linux-tools-3.10.0' However, the perf binary I happen to have installed, when I get it to try to run, at least appears to work, despite the kernel version mismatch. In larger tests, I've gotten perfectly fine profiling data. root@adamnovak-pod:/vg# /usr/lib/linux-tools/4.15.0-62-generic/perf record ls bin deps perf.data scripts [ perf record: Woken up 2 times to write data ] [ perf record: Captured and wrote 0.002 MB perf.data (10 samples) ] root@adamnovak-pod:/vg# So it is not clear that the level of specificity enforced by the wrapper scripts is actually necessary. There are a few potential solutions I can see to this problem: 1. Modify the scripts to treat the lack of the exact right tool version being installed as a warning instead of an error, and have them select the closest version to run instead. 2. Create linux-tools-3.10.0 ish through linux-tools-5.x.x packages, containing builds of perf and co. derived from those official mainline kernels, and a metapackage to install all of them. Then the package that you get prompted to install when running in a container will exist, and you will be able to install it to have a toolset that has a high probability of being compatible with the kernel you are running on. A container that needs to be portable between different hosts can install the metapackage. 3. Create a package that conflicts with linux-tools-common and provides some arbitrary version of the tools. People who want a toolset that can run in a container can install that package instead, and bear the responsibility for what happens if the tools provided don't work with the kernel that happens to be running. 4. Hook into the alternatives system; allow the user to switch between packages providing the tools for different kernel versions, with the default being the dispatch script. The workaround I am currently using is running this as soon as I get inside the container, to clobber the wrapper script with whatever actual binary I have installed: cp /usr/lib/linux-tools/*/perf /usr/bin/perf However, this is a pretty terrible hack. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-tools-common 4.15.0-62.69 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic x86_64 AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser': 'fuser' CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Sep 17 19:20:29 2019 Lspci: Error: [Errno 2] No such file or directory: 'lspci': 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb': 'lsusb' MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-62-generic root=/dev/mapper/hex--vg-root ro splash quiet vt.handoff=1
Re: [Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
Do I have to downgrade my system from Dingo to Cosmic in order to test this in Cosmic, to keep my bug from being closed? May 20, 2019 7:02 AM, "Ubuntu Kernel Bot" wrote: > This bug is awaiting verification that the kernel in -proposed solves > the problem. Please test the kernel and update this bug with the > results. If the problem is solved, change the tag 'verification-needed- > cosmic' to 'verification-done-cosmic'. If the problem still exists, > change the tag 'verification-needed-cosmic' to 'verification-failed- > cosmic'. > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > ** Tags added: verification-needed-cosmic > > -- > You received this bug notification because you are subscribed to the bug > report. > 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: > Fix Committed > Status in linux source package in Bionic: > Fix Committed > Status in linux source package in Cosmic: > Fix Committed > Status in linux source package in Disco: > Fix Committed > > Bug description: > [Impact] > On the LattePanda board, the headphone detection signal is not correct, it is > inverted: plugging in headphones disables headphone output > > [Fix] > In the codec driver, there already is a fixup, just set the inv_jd1_1 to true. > > [Test Case] > It is tested by the bug reporter, please refer to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/comments/23 > > [Regression Risk] > Low. This fix is specific to a board which is defined by DMI strings. > > 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: >
[Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
OK, this second deb seems to solve my problem! The headphone jack state is detected correctly without the quirk! Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
Here's the whole `sudo dmidecode` output (attached). ** Attachment added: "Output of sudo dmidecode for the LattePanda" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+attachment/5258402/+files/dmidecode.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
Hello, Thank you for looking into this. I installed the DKMS module deb (which built itself against kernel 5.0.0-13, which is what the system is now updated to), commented out the quirk-setting line in my module config file, and rebooted. I now have no sound; list-cards in pacmd shows me that it thinks the headphone output is unavailable when plugged in, again. 1 card(s) available. index: 0 name: driver: owner module: 7 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: Built-in Audio Headset Microphone + Internal Analog Microphone ports: [Out] Headphones: Headphones (priority 100, latency offset 0 usec, available: no) properties: [Out] Speaker: Speaker (priority 100, latency offset 0 usec, available: unknown) properties: [In] HSMic: Headset Microphone (priority 100, latency offset 0 usec, available: no) properties: [In] Mic: Internal Analog Microphone (priority 150, latency offset 0 usec, available: unknown) properties: I'm going to put it back the way I had it (remove the deb and reinstate the quirk). Is there anything else I can test? Or any more DMI info you would like? Is there something special I can do to make sure the module override actually loaded? Thanks, -Adam -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255466/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255460/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255458/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255463/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255467/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255461/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
I set the bug to Confirmed, despite being the original reporter, because the bot told me to. The Apport logs I posted are form the system with my workaround enabled. I also blacklisted the HDMI audio module, since I don't use HDMI audio, and I thought it might help. It didn't seem to, but I never unblacklisted it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] Re: Headphone jack switch sense is inverted: plugging in headphones disables headphone output
apport information ** Tags added: apport-collected ** Description changed: 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
[Bug 1824259] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255459/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255464/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255465/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824259] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1824259/+attachment/5255462/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824259
Title:
Headphone jack switch sense is inverted: plugging in headphones
disables headphone output
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824259/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824259 Title: Headphone jack switch sense is inverted: plugging in headphones disables headphone output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1824259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824259
Title:
Headphone jack switch sense is inverted: plugging in headphones
disables headphone output
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1824259/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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:
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813679 Title: vim-gtk can no longer save to GVFS STFP mounts in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1813679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810207] [NEW] r8152 Ethernet adapter disconnects with a transmit queue timeout
Public bug reported: The r8152 Ethernet device in my Lattepanda board just disconnected from my network while I was uploading some files over the LAN. dmesg reported this: [1036155.155084] [ cut here ] [1036155.155099] NETDEV WATCHDOG: enx00e04c368b17 (r8152): transmit queue 0 timed out [1036155.155201] WARNING: CPU: 0 PID: 0 at /build/linux-vxxS7y/linux-4.15.0/net/sched/sch_generic.c:323 dev_watchdog+0x221/0x230 [1036155.155207] Modules linked in: xt_nat xt_tcpudp veth ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge stp llc overlay aufs nls_iso8859_1 snd_soc_sst_cht_bsw_rt5645 axp288_fuel_gauge axp288_adc axp288_charger industrialio axp20x_pek extcon_axp288 gpio_keys intel_rapl intel_powerclamp coretemp kvm_intel kvm irqbypass punit_atom_debug crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cdc_ether cryptd usbnet intel_cstate r8152 mii cdc_acm snd_intel_sst_acpi snd_intel_sst_core mei_txe snd_soc_sst_atom_hifi2_platform snd_soc_acpi mei snd_seq_midi snd_soc_acpi_intel_match [1036155.14] snd_seq_midi_event processor_thermal_device snd_rawmidi intel_soc_dts_iosf lpc_ich snd_hdmi_lpe_audio snd_seq snd_soc_rt5645 snd_soc_rl6231 snd_soc_core intel_hid snd_compress sparse_keymap snd_seq_device axp20x_i2c ac97_bus dw_dmac snd_pcm_dmaengine goodix axp20x snd_pcm dw_dmac_core snd_timer pwm_lpss_platform snd pwm_lpss soundcore spi_pxa2xx_platform 8250_dw int3400_thermal int3406_thermal acpi_thermal_rel int3403_thermal mac_hid int340x_thermal_zone soc_button_array intel_int0002_vgpio acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid mmc_block i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm video sdhci_acpi sdhci [1036155.155901] CPU: 0 PID: 0 Comm: swapper/0 Tainted: GW 4.15.0-43-generic #46-Ubuntu [1036155.155907] Hardware name: Default string Default string/Cherry Trail CR, BIOS DF-BI-7-S70CR200-CC55F-022-B 05/15/2018 [1036155.155920] RIP: 0010:dev_watchdog+0x221/0x230 [1036155.155929] RSP: 0018:9b977fc03e58 EFLAGS: 00010286 [1036155.155941] RAX: RBX: RCX: 0006 [1036155.155948] RDX: 0007 RSI: 0092 RDI: 9b977fc16490 [1036155.155955] RBP: 9b977fc03e88 R08: 0001 R09: 043e [1036155.155963] R10: 9b977fc03ee0 R11: R12: 0001 [1036155.155969] R13: 9b97725c1000 R14: 9b97725c1478 R15: 9b976d4ede80 [1036155.155981] FS: () GS:9b977fc0() knlGS: [1036155.155988] CS: 0010 DS: ES: CR0: 80050033 [1036155.155995] CR2: 7ffe98d7e008 CR3: 00017540a000 CR4: 001006f0 [1036155.156003] Call Trace: [1036155.156014] [1036155.156039] ? dev_deactivate_queue.constprop.33+0x60/0x60 [1036155.156055] call_timer_fn+0x30/0x130 [1036155.156069] run_timer_softirq+0x3fb/0x450 [1036155.156081] ? ktime_get+0x43/0xa0 [1036155.156094] ? lapic_next_deadline+0x26/0x30 [1036155.156108] __do_softirq+0xe4/0x2bb [1036155.156124] irq_exit+0xb8/0xc0 [1036155.156135] smp_apic_timer_interrupt+0x79/0x130 [1036155.156147] apic_timer_interrupt+0x84/0x90 [1036155.156153] [1036155.156169] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 [1036155.156175] RSP: 0018:ad803e10 EFLAGS: 0246 ORIG_RAX: ff11 [1036155.156187] RAX: 9b977fc22880 RBX: 0003ae60abf28410 RCX: 001f [1036155.156193] RDX: 0003ae60abf28410 RSI: fff7e3411b99 RDI: [1036155.156200] RBP: ad803e50 R08: 0001 R09: 027c [1036155.156206] R10: ad803de0 R11: 1e6e R12: 9b977fc2c400 [1036155.156213] R13: 0003 R14: ad971cb8 R15: [1036155.156234] cpuidle_enter+0x17/0x20 [1036155.156248] call_cpuidle+0x23/0x40 [1036155.156259] do_idle+0x18c/0x1f0 [1036155.156272] cpu_startup_entry+0x73/0x80 [1036155.156287] rest_init+0xae/0xb0 [1036155.156302] start_kernel+0x4dc/0x4fd [1036155.156314] x86_64_start_reservations+0x24/0x26 [1036155.156324] x86_64_start_kernel+0x74/0x77 [1036155.156339] secondary_startup_64+0xa5/0xb0 [1036155.156348] Code: 38 00 49 63 4e e8 eb 92 4c 89 ef c6 05 f9 d7 d8 00 01 e8 83 35 fd ff 89 d9 48 89 c2 4c 89 ee 48 c7 c7 30 99 59 ad e8 df 95 80 ff <0f> 0b eb c0 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 [1036155.156580] ---[ end trace 5a05a48c7e597e05 ]--- [1036155.156645] r8152 1-4:1.0 enx00e04c368b17: Tx timeout [1036157.235268] r8152 1-4:1.0 enx00e04c368b17: Tx status -2 [1036157.235353] r8152 1-4:1.0 enx00e04c368b17: Tx status -2 [1036157.235431] r8152 1-4:1.0 enx00e04c368b17: Tx status -2
[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 Bugs, which is subscribed to 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1793920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
I don't seem to have access to change the tag, but I can confirm that 4.15.0-34-generic from -proposed solves the problem. So the tag should be verification-done-bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
OK, I have tested the provided kernel and it works for me under Xen. Thank you for fixing the bug! I look forward to seeing this in the real releases. [anovak@octagon ~]$ uname -a Linux octagon 4.15.0-31-generic #34~lp1777338 SMP Tue Aug 7 14:57:12 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux On Mon, Aug 13, 2018 at 8:48 AM, Joseph Salisbury wrote: > The hashes are: > > 63d7e9ca7710792e1603953b0ec14337 linux-image- > unsigned-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb > > 8cca692f07f9edbb56dec15375bc9979 linux- > modules-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb > > df24a98ec4769f33a9831a5aaeb9f437 linux-modules- > extra-4.15.0-31-generic_4.15.0-31.34~lp1777338_amd64.deb > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 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: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
Thanks for preparing this kernel; I am downloading it now. What are the expected hashes of the files, so that I can verify the insecure downloads? On Tue, Aug 7, 2018 at 8:49 AM, Joseph Salisbury wrote: > I built a test kernel with commit 74899d92e3dc7671a8017b3146dcd4735f3b. > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1777338 > > Can you test this kernel and see if it resolves this bug? > > If this kernel also fixes the bug, I'll submit an SRU request. > > > Note about installing test kernels: > • If the test kernel is prior to 4.15(Bionic) you need to install the > linux-image and linux-image-extra .deb packages. > • If the test kernel is 4.15(Bionic) or newer, you need to install the > linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. > > Thanks in advance! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 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: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
OK, I grabbed commit 74899d92e3dc7671a8017b3146dcd4735f3b "x86/xen: Add call of speculative_store_bypass_ht_init() to PV paths" from g...@github.com:torvalds/linux.git and cherry-picked it on top of the tag Ubuntu-4.15.0-29.31, and built the kernel, and now it boots fine as dom0! I think that that patch fixes this bug. How can I get this commit to be pulled into the main Ubuntu kernel development branch, to be released in the official kernel builds? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
I've been advised by Juergen Gross that not having "x86/xen: Add call of speculative_store_bypass_ht_init() to PV paths" from the mainline kernel might contribute to this problem. I am trying to pull that in now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
I'm not finding any kernel packages in bionic-proposed; maybe they were released already? I've installed and tested 4.15.0-29 from the normal repos; it has the same null pointer dereference at address 8 issue. On Tue, Jul 24, 2018, 09:17 Joseph Salisbury wrote: > Thanks for finishing up the bisect! > > Would it be possible for you to test the proposed kernel and post back if > it resolves this bug? > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. > > Thank you in advance! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 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: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
OK, I have finished the bisect. 3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c is the first bad commit. I tested it and it displays the problem, and I tested abd39ac1da07b433fc570332ee9ad938b5071760 right before it and that one boots fine. On Sat, Jul 21, 2018 at 9:42 AM, Adam Novak wrote: > That one works. On to 5856293c78e552c012835e667d66775bba20b4f7. > > I suspect 3f6a3b035f91 and abd39ac1da07 may be the real problem, since > the CPU I am using is an AMD Ryzen chip, and those are tinkering > specifically with how the kernel handles those. > > On Fri, Jul 20, 2018 at 10:23 PM, Adam Novak wrote: >> OK, I tried that one and it still exhibited the issue. I'm going to >> try 91762b4035d9da8c266e2cb3dbc552052434bbf0 next. >> >> On Fri, Jul 20, 2018 at 9:08 PM, Adam Novak wrote: >>> Thanks! >>> >>> I have tested this kernel; it doesn't work, so the problem is between >>> fc8704280f2ada9f61f08a2d5adc0dab169cc207 and >>> 8eca6add0defde203282476d7969a7c13bbd7d91. >>> >>> I've gotten set up with a kernel build environment; I think I can >>> finish the git bisect myself, but looking at the commits in that >>> range, I have no hope of actually fixing the underlying bug myself. >>> I'm building 3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c now. >>> >>> On Tue, Jul 17, 2018 at 11:24 AM, Joseph Salisbury >>> wrote: >>>> I built the next test kernel, up to the following commit: >>>> fc8704280f2ada9f61f08a2d5adc0dab169cc207 >>>> >>>> The test kernel can be downloaded from: >>>> http://kernel.ubuntu.com/~jsalisbury/lp1777338 >>>> >>>> Can you test that kernel and report back if it has the bug or not? I >>>> will build the next test kernel based on your test results. >>>> >>>> Thanks in advance >>>> >>>> >>>> MD5SUM of files: >>>> d76993d34e1203375090a47c4de8ebfe >>>> linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >>>> >>>> 5b89b2341b858bbe2bcae88e3efaf8c8 linux- >>>> modules-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >>>> >>>> 6928b4ad5f2a861ad674ff88a4745471 linux-modules- >>>> extra-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >>>> >>>> -- >>>> You received this bug notification because you are subscribed to the bug >>>> report. >>>> https://bugs.launchpad.net/bugs/1777338 >>>> >>>> Title: >>>> Linux 4.15.0-23 crashes during the boot process with a "Unable to >>>> handle kernel NULL pointer dereference" message >>>> >>>> Status in linux package in Ubuntu: >>>> In Progress >>>> Status in linux source package in Bionic: >>>> In Progress >>>> >>>> Bug description: >>>> I went to boot my computer today and it wouldn't boot. >>>> >>>> I get an "Unable to handle kernel NULL pointer dereference" message >>>> during the boot process, and, a bit after that, a message from the >>>> kernel watchdog about CPU #0 being stuck. Then the boot process stops >>>> completely. >>>> >>>> I was able to boot the system by telling Grub to load 4.15.0-22, which >>>> works perfectly fine, so there has been a regression. >>>> >>>> I am running Ubuntu as a Xen dom0, if that matters. I haven't tried >>>> booting the offending kernel version without Xen. >>>> >>>> I'm not sure where, if anywhere, these messages go on disk, for >>>> posting. >>>> >>>> ProblemType: Bug >>>> DistroRelease: Ubuntu 18.04 >>>> Package: linux-image-4.15.0-23-generic 4.15.0-23.25 >>>> ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 >>>> Uname: Linux 4.15.0-22-generic x86_64 >>>> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair >>>> ApportVersion: 2.20.9-0ubuntu7.1 >>>> Architecture: amd64 >>>> CurrentDesktop: ubuntu:GNOME >>>> Date: Sun Jun 17 10:12:58 2018 >>>> InstallationDate: Installed on 2017-08-06 (314 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: linux-signed >>>> UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) >>>> >>>> To manage notifications about this bug go to: >>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
That one works. On to 5856293c78e552c012835e667d66775bba20b4f7. I suspect 3f6a3b035f91 and abd39ac1da07 may be the real problem, since the CPU I am using is an AMD Ryzen chip, and those are tinkering specifically with how the kernel handles those. On Fri, Jul 20, 2018 at 10:23 PM, Adam Novak wrote: > OK, I tried that one and it still exhibited the issue. I'm going to > try 91762b4035d9da8c266e2cb3dbc552052434bbf0 next. > > On Fri, Jul 20, 2018 at 9:08 PM, Adam Novak wrote: >> Thanks! >> >> I have tested this kernel; it doesn't work, so the problem is between >> fc8704280f2ada9f61f08a2d5adc0dab169cc207 and >> 8eca6add0defde203282476d7969a7c13bbd7d91. >> >> I've gotten set up with a kernel build environment; I think I can >> finish the git bisect myself, but looking at the commits in that >> range, I have no hope of actually fixing the underlying bug myself. >> I'm building 3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c now. >> >> On Tue, Jul 17, 2018 at 11:24 AM, Joseph Salisbury >> wrote: >>> I built the next test kernel, up to the following commit: >>> fc8704280f2ada9f61f08a2d5adc0dab169cc207 >>> >>> The test kernel can be downloaded from: >>> http://kernel.ubuntu.com/~jsalisbury/lp1777338 >>> >>> Can you test that kernel and report back if it has the bug or not? I >>> will build the next test kernel based on your test results. >>> >>> Thanks in advance >>> >>> >>> MD5SUM of files: >>> d76993d34e1203375090a47c4de8ebfe >>> linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >>> >>> 5b89b2341b858bbe2bcae88e3efaf8c8 linux- >>> modules-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >>> >>> 6928b4ad5f2a861ad674ff88a4745471 linux-modules- >>> extra-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >>> >>> -- >>> You received this bug notification because you are subscribed to the bug >>> report. >>> https://bugs.launchpad.net/bugs/1777338 >>> >>> Title: >>> Linux 4.15.0-23 crashes during the boot process with a "Unable to >>> handle kernel NULL pointer dereference" message >>> >>> Status in linux package in Ubuntu: >>> In Progress >>> Status in linux source package in Bionic: >>> In Progress >>> >>> Bug description: >>> I went to boot my computer today and it wouldn't boot. >>> >>> I get an "Unable to handle kernel NULL pointer dereference" message >>> during the boot process, and, a bit after that, a message from the >>> kernel watchdog about CPU #0 being stuck. Then the boot process stops >>> completely. >>> >>> I was able to boot the system by telling Grub to load 4.15.0-22, which >>> works perfectly fine, so there has been a regression. >>> >>> I am running Ubuntu as a Xen dom0, if that matters. I haven't tried >>> booting the offending kernel version without Xen. >>> >>> I'm not sure where, if anywhere, these messages go on disk, for >>> posting. >>> >>> ProblemType: Bug >>> DistroRelease: Ubuntu 18.04 >>> Package: linux-image-4.15.0-23-generic 4.15.0-23.25 >>> ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 >>> Uname: Linux 4.15.0-22-generic x86_64 >>> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair >>> ApportVersion: 2.20.9-0ubuntu7.1 >>> Architecture: amd64 >>> CurrentDesktop: ubuntu:GNOME >>> Date: Sun Jun 17 10:12:58 2018 >>> InstallationDate: Installed on 2017-08-06 (314 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: linux-signed >>> UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) >>> >>> To manage notifications about this bug go to: >>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
OK, I tried that one and it still exhibited the issue. I'm going to try 91762b4035d9da8c266e2cb3dbc552052434bbf0 next. On Fri, Jul 20, 2018 at 9:08 PM, Adam Novak wrote: > Thanks! > > I have tested this kernel; it doesn't work, so the problem is between > fc8704280f2ada9f61f08a2d5adc0dab169cc207 and > 8eca6add0defde203282476d7969a7c13bbd7d91. > > I've gotten set up with a kernel build environment; I think I can > finish the git bisect myself, but looking at the commits in that > range, I have no hope of actually fixing the underlying bug myself. > I'm building 3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c now. > > On Tue, Jul 17, 2018 at 11:24 AM, Joseph Salisbury > wrote: >> I built the next test kernel, up to the following commit: >> fc8704280f2ada9f61f08a2d5adc0dab169cc207 >> >> The test kernel can be downloaded from: >> http://kernel.ubuntu.com/~jsalisbury/lp1777338 >> >> Can you test that kernel and report back if it has the bug or not? I >> will build the next test kernel based on your test results. >> >> Thanks in advance >> >> >> MD5SUM of files: >> d76993d34e1203375090a47c4de8ebfe >> linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >> >> 5b89b2341b858bbe2bcae88e3efaf8c8 linux- >> modules-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >> >> 6928b4ad5f2a861ad674ff88a4745471 linux-modules- >> extra-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1777338 >> >> Title: >> Linux 4.15.0-23 crashes during the boot process with a "Unable to >> handle kernel NULL pointer dereference" message >> >> Status in linux package in Ubuntu: >> In Progress >> Status in linux source package in Bionic: >> In Progress >> >> Bug description: >> I went to boot my computer today and it wouldn't boot. >> >> I get an "Unable to handle kernel NULL pointer dereference" message >> during the boot process, and, a bit after that, a message from the >> kernel watchdog about CPU #0 being stuck. Then the boot process stops >> completely. >> >> I was able to boot the system by telling Grub to load 4.15.0-22, which >> works perfectly fine, so there has been a regression. >> >> I am running Ubuntu as a Xen dom0, if that matters. I haven't tried >> booting the offending kernel version without Xen. >> >> I'm not sure where, if anywhere, these messages go on disk, for >> posting. >> >> ProblemType: Bug >> DistroRelease: Ubuntu 18.04 >> Package: linux-image-4.15.0-23-generic 4.15.0-23.25 >> ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 >> Uname: Linux 4.15.0-22-generic x86_64 >> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair >> ApportVersion: 2.20.9-0ubuntu7.1 >> Architecture: amd64 >> CurrentDesktop: ubuntu:GNOME >> Date: Sun Jun 17 10:12:58 2018 >> InstallationDate: Installed on 2017-08-06 (314 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: linux-signed >> UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
Thanks! I have tested this kernel; it doesn't work, so the problem is between fc8704280f2ada9f61f08a2d5adc0dab169cc207 and 8eca6add0defde203282476d7969a7c13bbd7d91. I've gotten set up with a kernel build environment; I think I can finish the git bisect myself, but looking at the commits in that range, I have no hope of actually fixing the underlying bug myself. I'm building 3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c now. On Tue, Jul 17, 2018 at 11:24 AM, Joseph Salisbury wrote: > I built the next test kernel, up to the following commit: > fc8704280f2ada9f61f08a2d5adc0dab169cc207 > > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1777338 > > Can you test that kernel and report back if it has the bug or not? I > will build the next test kernel based on your test results. > > Thanks in advance > > > MD5SUM of files: > d76993d34e1203375090a47c4de8ebfe > linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb > > 5b89b2341b858bbe2bcae88e3efaf8c8 linux- > modules-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb > > 6928b4ad5f2a861ad674ff88a4745471 linux-modules- > extra-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 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: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
OK, I've tested this kernel, and it works just fine under Xen, from what I can tell. The system comes up just fine: Linux octagon 4.15.0-23-generic #26~lp1777338Commit8eca6add0 SMP Wed Jun 27 15:50:08 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux The offending commit must be later. On Thu, Jul 5, 2018 at 8:32 AM, Joseph Salisbury wrote: > Here are the md5sum hashes of the files needed to install the test > kernel: > > d5f16dcf0080db1268d3b3477c911cd7 linux-image- > unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commit8eca6add0_amd64.deb > > 1d7504d8e691ba64d552a2d507179882 linux- > modules-4.15.0-23-generic_4.15.0-23.26~lp1777338Commit8eca6add0_amd64.deb > > b004fa6244e3e038b0d67c86e0218536 linux-modules- > extra-4.15.0-23-generic_4.15.0-23.26~lp1777338Commit8eca6add0_amd64.deb > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 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: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
Hello, Thanks for putting this together. I tried to get the kernels you built, but I'm having trouble establishing a secure (https) connection to kernel.ubuntu.com. It looks like the server might not offer https. Can you give me the expected hashes of the files so I can verify the downloads? Thanks, -Adam On Wed, Jun 27, 2018 at 10:34 AM, Joseph Salisbury wrote: > I started a kernel bisect between v4.15.0-22 and v4.15.0-23. The kernel > bisect will require testing of about 7-10 test kernels. > > I built the first test kernel, up to the following commit: > 8eca6add0defde203282476d7969a7c13bbd7d91 > > The test kernel can be downloaded from: > http://kernel.ubuntu.com/~jsalisbury/lp1777338 > > Can you test that kernel and report back if it has the bug or not? I > will build the next test kernel based on your test results. > > > Thanks in advance > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 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: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
I updated my BIOS and tested the -24 kernel, as was recommended. It definitely doesn't work any better. It still has the null dereference problem, and then it prints a bunch of smp_call_function_too_many errors, apparently forever. On Tue, Jun 19, 2018, 08:11 Joseph Salisbury wrote: > Can you see if this issue exists in the 4.15.0-24 kernel: > > https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/15010188 > > Note about installing test kernels: > • If the test kernel is prior to 4.15(Bionic) you need to install the > linux-image and linux-image-extra .deb packages. > • If the test kernel is 4.15(Bionic) or newer, you need to install the > linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. > > Thanks in advance! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1777338 > > Title: > Linux 4.15.0-23 crashes during the boot process with a "Unable to > handle kernel NULL pointer dereference" message > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Bionic: > In Progress > > Bug description: > I went to boot my computer today and it wouldn't boot. > > I get an "Unable to handle kernel NULL pointer dereference" message > during the boot process, and, a bit after that, a message from the > kernel watchdog about CPU #0 being stuck. Then the boot process stops > completely. > > I was able to boot the system by telling Grub to load 4.15.0-22, which > works perfectly fine, so there has been a regression. > > I am running Ubuntu as a Xen dom0, if that matters. I haven't tried > booting the offending kernel version without Xen. > > I'm not sure where, if anywhere, these messages go on disk, for > posting. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: linux-image-4.15.0-23-generic 4.15.0-23.25 > ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 > Uname: Linux 4.15.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.9-0ubuntu7.1 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Jun 17 10:12:58 2018 > InstallationDate: Installed on 2017-08-06 (314 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: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
This also affects the mainline kernel build 4.17.0-041700.201806041953 that I was testing for another bug. I've attached a photo of the screen with the issue occurring, in that version. Booting not under Xen seems to work around the issue, and the system comes up, but that's not useful for me because I need Xen. ** Attachment added: "Screenshot of the null pointer dereference message" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1777338/+attachment/5153715/+files/Screenshot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069780] Re: [needs-packaging] Doesn't work under 12.10
With the demise of Grooveshark, this bug is no longer relevant and should be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069780 Title: [needs-packaging] Doesn't work under 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-webapps-grooveshark/+bug/1069780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775487] Re: Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports
The drive that was giving me this problem failed. I got a replacement (which is notionally the same model, with the same USB ID 0781:5581), and, on kernel 4.15-22, under Xen, the new drive seems to work fine in USB 3 ports. However, I also tested with the latest v4.17 kernel from the given link (4.17.0-041700.201806041953) That kernel does not boot under Xen where I run my system (it seems to suffer from https://bugs.launchpad.net/ubuntu/+source/linux- signed/+bug/1777338). When I load it outside of Xen, it does not mount my home directory, because it is on a ZFS disk and the provided builds do not seem to include ZFS support. It also does seem to work fine with the drive, but it has other substantial problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775487 Title: Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777338] [NEW] Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
Public bug reported: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 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: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1777338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775487] [NEW] Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports
Public bug reported: I have a 128 GB Sandisk Ultra USB Flash Drive. It works when I plug it into a USB 2.0 port, or if I partially insert it into a USB 3.0 port (so the USB 3 pins don't make contact). Here's what lsusb says about it: Bus 001 Device 005: ID 0781:5581 SanDisk Corp. Ultra And dmesg from a successful connection: [ 1269.667097] usb 3-1.4: new high-speed USB device number 6 using xhci_hcd [ 1269.779871] usb 3-1.4: New USB device found, idVendor=0781, idProduct=5581 [ 1269.779875] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1269.779878] usb 3-1.4: Product: Ultra [ 1269.779880] usb 3-1.4: Manufacturer: SanDisk [ 1269.779883] usb 3-1.4: SerialNumber: 4C530001080228105161 [ 1269.780937] usb-storage 3-1.4:1.0: USB Mass Storage device detected [ 1269.781346] scsi host10: usb-storage 3-1.4:1.0 [ 1270.800187] scsi 10:0:0:0: Direct-Access SanDisk Ultra1.00 PQ: 0 ANSI: 6 [ 1270.800733] sd 10:0:0:0: Attached scsi generic sg3 type 0 [ 1270.800919] sd 10:0:0:0: [sdd] 240254976 512-byte logical blocks: (123 GB/115 GiB) [ 1270.801887] sd 10:0:0:0: [sdd] Write Protect is off [ 1270.801891] sd 10:0:0:0: [sdd] Mode Sense: 43 00 00 00 [ 1270.802269] sd 10:0:0:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 1270.811703] sdd: sdd1 [ 1270.813869] sd 10:0:0:0: [sdd] Attached SCSI removable disk But if I insert the drive all the way into a USB 3.0 port on a hub, I get nothing. And on a USB 3.0 port on the machine directly, I get this in dmesg: [ 1395.230629] xhci_hcd :03:00.0: Cannot set link state. [ 1395.230641] usb usb2-port4: cannot disable (err = -32) [ 1396.966273] xhci_hcd :03:00.0: Cannot set link state. [ 1396.966285] usb usb2-port4: cannot disable (err = -32) [ 1398.706493] xhci_hcd :03:00.0: Cannot set link state. [ 1398.706505] usb usb2-port4: cannot disable (err = -32) [ 1400.446161] xhci_hcd :03:00.0: Cannot set link state. [ 1400.446172] usb usb2-port4: cannot disable (err = -32) [ 1402.182073] xhci_hcd :03:00.0: Cannot set link state. [ 1402.182085] usb usb2-port4: cannot disable (err = -32) ...repeats until unplugged... It doesn't show up in lsusb in the USB 3.0 port. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:22:35 2018 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2017-08-06 (304 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: linux-signed Symptom: storage UpgradeStatus: Upgraded to bionic on 2018-05-29 (8 days ago) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775487 Title: Sandisk Ultra USB 3.0 Flash Drive doesn't work in USB 3 ports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1775487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04
It looks like the drive is replying with an ILLEGAL REQUEST/INVALID FIELD IN CDB error to all the interesting SCSI commands, and to pretty much anything hdparm sends it. I've also tried throwing sdparm at it. The only page sdparm can get out of it is the basic identification page: [anovak@octagon hdparm-9.54]$ sudo sdparm -i /dev/sdg /dev/sdg: Seagate Backup+ Hub BKD781 Device identification VPD page: Addressed logical unit: designator type: NAA, code set: Binary 0x5001 But this has convinced me that I am actually communicating with the disk itself. Is there any way the kernel/driver could be tinkering with the commands that hdparm used to send that worked and which now fail? Or is there some kind of initialization that isn't being done that would put the disk in a mode where it is willing to do more things? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774569 Title: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsmartcontrol/+bug/1774569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04
I pulled the hdparm binary from Artful, and it can't spin down the drive with -y either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774569 Title: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsmartcontrol/+bug/1774569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04
Even after rebooting with the drive for the zpool physically removed from the system, I still had a zpool I couldn't destroy, export, or otherwise remove from the listing. Using "sudo zpool status -Pv" I worked out that my ZFS was actually expecting to find the data on partition 1 of the drive: errors: No known data errors pool: hub state: UNAVAIL status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://zfsonlinux.org/msg/ZFS-8000-5E scan: none requested config: NAME STATE READ WRITE CKSUM hub UNAVAIL 0 0 0 insufficient replicas /dev/disk/by-id/ata-ST6000DM003-2CY186_ZF200PC8-part1 UNAVAIL 0 0 0 I'd previously tried symlinking the old device name to the new one, but I was inspired to try it with just the partition: [anovak@octagon ~]$ cd /dev/disk/by-id/ [anovak@octagon by-id]$ sudo ln -s 'usb-Seagate_Backup+_Hub_BK_NA8TQC87-0:0-part1' ata-ST6000DM003-2CY186_ZF200PC8-part1 When I did that, the pool immediately came back online, and I was able to export it to make it go away. Then I managed to import it under a more stable name with "sudo zpool import -a -d /dev/disk/by-partuuid/". I still can't see the drive data in gsmartcontrol, and I still can't spin it down, but at least I can now use it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774569 Title: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsmartcontrol/+bug/1774569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04
Nope, my speculation is definitely wrong. The disk shows up in lsscsi: [anovak@octagon ~]$ lsscsi ... [9:0:0:0]diskSeagate Backup+ Hub BK D781 /dev/sdb Also, it shows up in lsusb -t with a "uas" driver. Maybe the problem is the uas driver itself? Here's the full description of the USB device, if that helps: [anovak@octagon ~]$ sudo lsusb -v -d 0bc2:ab38 Bus 001 Device 008: ID 0bc2:ab38 Seagate RSS LLC Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0bc2 Seagate RSS LLC idProduct 0xab38 bcdDevice1.00 iManufacturer 2 Seagate iProduct3 Backup+ Hub BK iSerial 1 NA8TQC87 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 85 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 1 bNumEndpoints 4 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 98 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Data-in pipe (0x03) Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Data-out pipe (0x04) Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Status pipe (0x02) Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x04 EP 4 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Command pipe (0x01) Binary Object Store Descriptor: bLength 5 bDescriptorType15 wTotalLength 22 bNumDeviceCaps 2 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType16 bDevCapabilityType 2 bmAttributes 0xf41e Link Power Management (LPM) Supported SuperSpeed USB Device Capability: bLength10 bDescriptorType16 bDevCapabilityType 3 bmAttributes 0x00 wSpeedsSupported 0x000e Device can operate at Full Speed (12Mbps) Device can operate at High Speed (480Mbps) Device can operate at SuperSpeed (5Gbps) bFunctionalitySupport 1 Lowest fully-functional device speed is Full
[Bug 1774569] [NEW] gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04
Public bug reported: I recently upgraded from 17.10 to 18.04. After the upgrade, I noticed that my Seagate Backup+ Hub external drive was displaying a series of puzzling symptoms: 1. gsmartcontrol can't get SMART data from the drive. I am pretty sure it used to report SMART data? Here's a log of it not working: [hz] Warning: exit: Command line did not parse. [app] execute_smartctl(): Smartctl binary did not execute cleanly. [app] StorageDevice::execute_device_smartctl(): Smartctl binary did not execute cleanly. [app] SmartctlParser::parse_section_info_property(): Unknown property "Physical block size" [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id" [app] SmartctlParser::parse_section_info_property(): Unknown property "Temperature Warning" [app] SmartctlParser::parse_section_data(): Unknown Data subsection encountered. [hz] Warning: exit: Some SMART command to the disk failed, or there was a checksum error in a SMART data structure [app] SmartctlParser::parse_section_info_property(): Unknown property "Physical block size" [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical Unit id" [app] SmartctlParser::parse_section_info_property(): Unknown property "Temperature Warning" [app] SmartctlParser::parse_section_data(): Unknown Data subsection encountered. 2. hdparm used to be able to spin down the drive. I had it configured to spin it down after a few minutes of inactivity, in the hdparm config file. Now that no longer happens, and hdparm can't seem to talk to the drive meaningfully at all: [anovak@octagon ~]$ sudo hdparm -I /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ATA device, with non-removable media Standards: Likely used: 1 Configuration: Logical max current cylinders 0 0 heads 0 0 sectors/track 0 0 -- Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 0 MBytes device size with M = 1000*1000: 0 MBytes cache/buffer size = unknown Capabilities: IORDY not likely Cannot perform double-word IO R/W multiple sector transfer: not supported DMA: not supported PIO: pio0 [anovak@octagon ~]$ sudo hdparm -y /dev/sdb /dev/sdb: issuing standby command SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 0a 00 00 00 00 24 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I think this may be related to https://askubuntu.com/questions/1037997 /upgraded-to-18-04-usb-harddrive-doesn-t-idle-anymore which is someone else having the same problem. 3. The ZFS tools think the drive is hosed: [anovak@octagon ~]$ sudo zpool status hub pool: hub state: UNAVAIL status: One or more devices could not be used because the label is missing or invalid. There are insufficient replicas for the pool to continue functioning. action: Destroy and re-create the pool from a backup source. see: http://zfsonlinux.org/msg/ZFS-8000-5E scan: none requested config: NAME STATE READ WRITE CKSUM hubUNAVAIL 0 0 0 insufficient replicas ata-ST6000DM003-2CY186_ZF200PC8 UNAVAIL 0 0 0 This may be related to the drive having adopted a new /dev/disk/by-id name during the upgrade? I think it was "ata- ST6000DM003-2CY186_ZF200PC8" when I added it to my zpool by its symlink under /dev/disks/by-id, but now it is "usb- Seagate_Backup+_Hub_BK_NA8TQC87-0:0": [anovak@octagon ~]$ ls -lah /dev/disk/by-id/usb-Seagate_Backup+_Hub_BK_NA8TQC87-0\:0 lrwxrwxrwx 1 root root 9 May 31 20:52 /dev/disk/by-id/usb-Seagate_Backup+_Hub_BK_NA8TQC87-0:0 -> ../../sdb This *shouldn't* cause trouble; you should be able to export the zpool and re-import it under the new name. But zpool import shows nothing to import: [anovak@octagon ~]$ sudo zpool import no pools available to import And I also can't export or even destroy the busted zpool, because zpool doesn't think it exists for exporting or destroying purposes: [anovak@octagon ~]$ sudo zpool export hub cannot export 'hub': no such pool or dataset [anovak@octagon ~]$ sudo zpool destroy hub cannot destroy 'hub': no such pool or dataset 4. The weirdest thing is that the drive itself seems to be working correctly. I see /dev/sdb1 and /dev/sdb9, as expected for a ZFS drive. I can `cat /dev/sdb1 | xxd | less` and see the data stored on the drive, including what I think is the ZFS label (at 0x4000, with a bunch of ZFS-y strings in it) that zpool is upset about not seeing. I see the partitions in `gparted` just fine, too; there's no indication that there's anything wrong with the partition table. Even the device's integrated USB hub
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772747 Title: Package is missing several dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1772747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772742 Title: libglib2.0-dev needs a dependency on libffi-dev because its pkg-config file specifies -lffi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1772742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772711] [NEW] Static library for libyajl is "libyajl_s.a" and pkg-config lies about it
Public bug reported: The static library for libyajl-dev is installed as /usr/lib/x86_64 -linux-gnu/libyajl_s.a and not /usr/lib/x86_64-linux-gnu/libyajl.a. This means that static linking with "-lyajl" will not find it; you need to use "-lyajl_s". This has not been explained to pkg-config (and I suspect the pkg-config file format can't express it). So when you do "pkg-config --static --libs yajl", you get back "-lyajl" and not "-lyajl_s". You also get the erroneous "-lyajl" when you ask pkg-config about anything that *depends* on yajl, such as raptor2: $ pkg-config --libs --static raptor2 -lraptor2 -lcurl -lxml2 -lxslt -lxml2 -lyajl This makes pkg-config not work for linking statically against any library that depends on yajl. The Debian bug for this problem is at https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=877285 and has been sitting idel for several months. I've also opened an upstream bug at https://github.com/lloyd/yajl/issues/209 but the upstream project seems suspiciously quiet, and I think the upstream maintainer may have quit. I believe the actual problem with the upstream code is at https://github.com/lloyd/yajl/blob/5e3a7856e643b4d6410ddc3f84bc2f38174f2872/src/CMakeLists.txt#L38-L40 where CMake is told to build a static library and a dynamic library with different names. (This might be necessary on Windows, but nobody knows how to deal with it in Linux.) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libyajl-dev 2.1.0-2 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 12:37:28 2018 Dependencies: gcc-6-base 6.2.0-3ubuntu11~12.04 [origin: unknown] libc6 2.23-0ubuntu10 libgcc1 1:6.2.0-3ubuntu11~12.04 [origin: unknown] libyajl2 2.1.0-2 multiarch-support 2.23-0ubuntu10 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-18 (1859 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: yajl UpgradeStatus: Upgraded to xenial on 2018-02-26 (85 days ago) ** Affects: yajl (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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772711 Title: Static library for libyajl is "libyajl_s.a" and pkg-config lies about it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yajl/+bug/1772711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 888847] Re: rhythmbox can't find ID3 tag muxer for MP3 support
You need gstreamer1.0-plugins-ugly and/or gstreamer1.0-plugins-bad. Not the 0.10 versions. I installed them both and it started working for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/47 Title: rhythmbox can't find ID3 tag muxer for MP3 support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-codec-install/+bug/47/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253638 Title: dynamic linker does not use DT_RUNPATH for transitive dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1253638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481536] Re: "cryptsetup: unknown fstype, bad password or options?" error unlocking / decrypting LUKS volume at boot
This also occurs on Ubuntu MATE 15.04 running cryptsetup 1.6.6-5ubuntu2 (versus the ubuntu1 in the original report). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481536 Title: "cryptsetup: unknown fstype, bad password or options?" error unlocking / decrypting LUKS volume at boot To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1481536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011446] Re: UML drawing tools' comment fields are too small to be usable
I can confirm that the patch to /usr/bin/dia works on 12.04 as well. Can we get the maintainer to update the package to include the patch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011446 Title: UML drawing tools' comment fields are too small to be usable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dia/+bug/1011446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1375430 Title: ping6 output too wide To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1375430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309785] Re: blurry font as document is longer than one page and scroll bars appear
I can confirm that the workaround works! You can add the environment variable to the launcher with the alacarte menu editor, if you want a GUI for it. I can now read my gedit again. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1309785 Title: blurry font as document is longer than one page and scroll bars appear To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1309785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1069780] Re: Doesn't work under 12.10
Now how do we get this from an attachment back into the official repositories? On Feb 11, 2013 2:48 PM, Marcin Jakubowski 1069...@bugs.launchpad.net wrote: I have the Untitled icon as well but only when launching the webapp through its own launcher icon. But the webapp will also come up if it detects Grooveshark open in a tab, at least in Chromium. So I have Grooveshark as a pinned tab in my normal session instead of launching it separately. I modified latest version posted by Alex Stefan Kaye to show a notification when a new track is played, it's attached. ** Attachment added: unity-webapps-grooveshark.tar.gz https://bugs.launchpad.net/ubuntu/+source/unity-webapps-grooveshark/+bug/1069780/+attachment/3524596/+files/unity-webapps-grooveshark.tar.gz -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1069780 Title: Doesn't work under 12.10 Status in “unity-webapps-grooveshark” package in Ubuntu: Confirmed Bug description: Firefox asked to install the webapp , it shows like installed but it doesn't do nothing ... no dash , launcher or sound menu entry . I'm using Ubuntu 12.10 32bit version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-webapps-grooveshark/+bug/1069780/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069780 Title: Doesn't work under 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-webapps-grooveshark/+bug/1069780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1084298] [NEW] blastn crashes when using XML output format with infinite max E-value
Public bug reported: I can run blastn with the option -evalue +inf and, with the default output format, the program runs fine and prints out everything it finds with e-values infinity. However, with XML output (-outfmt 5), it crashes because it refuses to represent an infinite double in its XML format. It should either output infinity for the parameter in the XML file, or say explicitly that an infinite e-value can't be used in combination with XML output. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ncbi-blast+ (not installed) ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Wed Nov 28 15:56:14 2012 InstallationMedia: Ubuntu-Server 11.04 Natty Narwhal - Release amd64 (20110426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ncbi-blast+ UpgradeStatus: Upgraded to precise on 2012-05-31 (181 days ago) ** Affects: ncbi-blast+ (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1084298 Title: blastn crashes when using XML output format with infinite max E-value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncbi-blast+/+bug/1084298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069780] Re: Doesn't work under 12.10
GMail is working for me (it wasn't initially, but after a few minutes I got prompted to install it), but Grooveshark isn't. No prompt from the site, no icon or search results from the installed application. Could it be related to Grooveshark's new UI? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069780 Title: Doesn't work under 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-webapps-grooveshark/+bug/1069780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045640] [NEW] Menu not showing up for some Qt apps
Public bug reported: For some Qt apps from PPAs (I have noticed this with Retroshare 0.5.3.5503 from ppa:csoler-users/retroshare-snapshots and Bitcoin v0.6.3.0-g6e0c5e3-beta from ppa:bitcoin/bitcoin), no menus appear in the global menu bar (just the application's title). However, the application also does not display its own menu bar, and the menu options are still accessible via the Alt-invoked HUD. Bitcoin's tray icon is also missing, although Retroshare's icons still display properly; I am not sure if those go through this package as well. Menu options from Qt Creator (in the official Ubuntu repositories) are showing up just fine in the global menu bar. I am guessing that the flaw lies somewhere in appmenu-qt, since it's responsible for taking an arbitrary Qt app and making its menu options show up in the global menu bar. It's possible that the applications I'm observing this issue with are somehow not well-behaved, but it would be good to know what sort of bad behavior is responsible for this breakage. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: appmenu-qt 0.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Mon Sep 3 21:10:26 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: appmenu-qt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: appmenu-qt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045640 Title: Menu not showing up for some Qt apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt/+bug/1045640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1045640] Re: Menu not showing up for some Qt apps
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1045640 Title: Menu not showing up for some Qt apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt/+bug/1045640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 957668] Re: Opening this file causes gedit to segfault
** Attachment added: The file causing the segfault https://bugs.launchpad.net/bugs/957668/+attachment/2884434/+files/gedit-segfault.dat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/957668 Title: Opening this file causes gedit to segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/957668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 957668] [NEW] Opening this file causes gedit to segfault
Public bug reported: I found this (binary) file inside of an app called RetroShare. I tried to open it in my running gedit window by drag-and-drop, and my gedit disappeared. I then tried to gedit filename from the command line. The gedit window opened, was blank for a little bit, and then disapeared, and I got Segmentation fault in my terminal. The offending file is attached. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gedit 3.2.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Mar 16 22:40:20 2012 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to oneiric on 2011-10-16 (152 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/957668 Title: Opening this file causes gedit to segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/957668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954577] Re: Mercurial configuration difficult
Yes, it's my opinion that this is a failure of UI design, and that's a bug. Has anybody responsible for the package had a look at this? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qtcreator in Ubuntu. https://bugs.launchpad.net/bugs/954577 Title: Mercurial configuration difficult To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/954577/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 954577] [NEW] Mercurial configuration difficult
Public bug reported: Creating a new project and specifying that it shuld be put under version control with Mercurial produces very unhelpful error messages unless the Mercurial binary path and default user name and e-mail are set in the Mercurial version control settings tab. The application should complain that the user needs to set these before using Mercurial version control, instead of just saying it couldn't create the repository. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: qtcreator 2.2.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Tue Mar 13 18:23:26 2012 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qtcreator UpgradeStatus: Upgraded to oneiric on 2011-10-16 (149 days ago) ** Affects: qtcreator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954577 Title: Mercurial configuration difficult To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/954577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954577] Re: Mercurial configuration difficult
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954577 Title: Mercurial configuration difficult To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator/+bug/954577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 662009] Re: [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky
Yes, works fine in 11.04 with model=auto. Great job, devs. On Sat, Apr 30, 2011 at 1:03 PM, Jayendra Rakesh jayendra.rak...@gmail.com wrote: just for conformation ... Has this problem been rectified in 11.04 ?? I would like to upgrade from 10.04 sequentially.. -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/662009 Title: [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky Status in ALSA driver: New Status in “linux” package in Ubuntu: Fix Committed Bug description: The Lenovo Y530 has a set of speakers, all of which need to be working to get adequate sound. On both 10.04 and 10.10, the default configuration only uses 2 speakers, which is unbearably tinny. In 10.04, following instructions at http://www.linlap.com/wiki/lenovo+ideapad+y530, I could enable all speakers with the line: options snd_hda_intel model=lenovo-sky added to alsa-base.conf. Unfortunately, in 10.10 doing this breaks all sound. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: alsa-base 1.0.23+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: slauzon 2095 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd420 irq 43' Mixer name : 'Intel Cantiga HDMI' Components : 'HDA:10ec0888,17aa3d78,00100202 HDA:10573055,17aa3d7d,00100700 HDA:80862802,80860101,0010' Controls : 44 Simple ctrls : 25 Date: Sat Oct 16 23:41:06 2010 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1) PackageArchitecture: all ProcEnviron: LANG=C SHELL=/bin/bash SelectedCard: 0 Intel HDA-Intel - HDA Intel SourcePackage: alsa-driver Symptom: audio Title: [Realtek ALC888] ALSA test tone not correctly played back dmi.bios.date: 09/23/2008 dmi.bios.vendor: Lenovo dmi.bios.version: 10CN37WW dmi.board.asset.tag: Lenovo Assert TAG dmi.board.name: INVALID dmi.board.vendor: Lenovo dmi.board.version: 10CN36WW dmi.chassis.asset.tag: Lenovo Assert TAG dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: 10CN37WW dmi.modalias: dmi:bvnLenovo:bvr10CN37WW:bd09/23/2008:svnLenovo:pnINVALID:pvrLenovoIdeaPadY530:rvnLenovo:rnINVALID:rvr10CN36WW:cvnLenovo:ct10:cvr10CN37WW: dmi.product.name: INVALID dmi.product.version: Lenovo IdeaPad Y530 dmi.sys.vendor: Lenovo To unsubscribe from this bug, go to: https://bugs.launchpad.net/alsa-driver/+bug/662009/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662009 Title: [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 662009] Re: [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky
Yeah, how do we open an upstream bug for this? On Sat, Dec 18, 2010 at 5:43 PM, Stephanie Duverge sduve...@gmail.com wrote: No good, will go back to 2.6.33 or 34. -- You received this bug notification because you are a direct subscriber of the bug. https://bugs.launchpad.net/bugs/662009 Title: [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky Status in ALSA driver: New Status in “alsa-driver” package in Ubuntu: Triaged Bug description: The Lenovo Y530 has a set of speakers, all of which need to be working to get adequate sound. On both 10.04 and 10.10, the default configuration only uses 2 speakers, which is unbearably tinny. In 10.04, following instructions at http://www.linlap.com/wiki/lenovo+ideapad+y530, I could enable all speakers with the line: options snd_hda_intel model=lenovo-sky added to alsa-base.conf. Unfortunately, in 10.10 doing this breaks all sound. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: alsa-base 1.0.23+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: slauzon 2095 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd420 irq 43' Mixer name : 'Intel Cantiga HDMI' Components : 'HDA:10ec0888,17aa3d78,00100202 HDA:10573055,17aa3d7d,00100700 HDA:80862802,80860101,0010' Controls : 44 Simple ctrls : 25 Date: Sat Oct 16 23:41:06 2010 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1) PackageArchitecture: all ProcEnviron: LANG=C SHELL=/bin/bash SelectedCard: 0 Intel HDA-Intel - HDA Intel SourcePackage: alsa-driver Symptom: audio Title: [Realtek ALC888] ALSA test tone not correctly played back dmi.bios.date: 09/23/2008 dmi.bios.vendor: Lenovo dmi.bios.version: 10CN37WW dmi.board.asset.tag: Lenovo Assert TAG dmi.board.name: INVALID dmi.board.vendor: Lenovo dmi.board.version: 10CN36WW dmi.chassis.asset.tag: Lenovo Assert TAG dmi.chassis.type: 10 dmi.chassis.vendor: Lenovo dmi.chassis.version: 10CN37WW dmi.modalias: dmi:bvnLenovo:bvr10CN37WW:bd09/23/2008:svnLenovo:pnINVALID:pvrLenovoIdeaPadY530:rvnLenovo:rnINVALID:rvr10CN36WW:cvnLenovo:ct10:cvr10CN37WW: dmi.product.name: INVALID dmi.product.version: Lenovo IdeaPad Y530 dmi.sys.vendor: Lenovo To unsubscribe from this bug, go to: https://bugs.launchpad.net/alsa-driver/+bug/662009/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/662009 Title: [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662009] Re: [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky
I have a workaround! The 2.6.33-02063307-generic kernel from http://kernel.ubuntu.com /~kernel-ppa/mainline works with the module=lenovo-sky trick. So the breaking patch is between it and .35. -- [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky https://bugs.launchpad.net/bugs/662009 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662009] Re: [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky
I also have this problem. Lenovo y530, installed 10.10 today without checking the known issues, and now I'm stuck with this bug. Any ideas? Anyone know how to build/install a kernel with the older ALSA? -- [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky https://bugs.launchpad.net/bugs/662009 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662009] Re: [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky
Here's my ALSA info: http://www.alsa- project.org/db/?f=d5f25b384ea24d6bcf5014d9098a6cb28c828b2a Would anything else be useful? -- [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky https://bugs.launchpad.net/bugs/662009 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 662009] Re: [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky
The .33 kernel seems OK, but I need to build the nVidia beta driver to run CUDA applications, and those kernels were built with GCC 4.2. Maverick has GCC 4.4, and 4.2 doesn't seem to be available anywhere, so I can't build the nVidia module, so I can't run X. I'll try making some test sounds with mplayer or something, but if anyone has a link for GCC 4.2 for Maverick or a mainline kernel built with 4.4, it would be very helpful. I have tried booting the .32 kernel left over from Karmic, and the machine doesn't start X or give me a login prompt. -- [Lenovo Y530 - Realtek ALC888] Regression from 10.04: No sound with snd_hda_intel model=lenovo-sky https://bugs.launchpad.net/bugs/662009 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
