[Bug 1964839] [NEW] software-properties-gtk crashes if APT::Periodic::Upgrade-Package-Lists="3"
Public bug reported:
Changing `APT::Periodic::Update-Package-Lists` to a value not in the
data model `model_updates_interval` in `/usr/share/software-
properties/gtkbuilder/main.ui` calls an invalid method, crashing the
program.
```
$ cat /etc/apt/apt.conf.d/10periodic
APT::Periodic::Update-Package-Lists "3";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::AutocleanInterval "0";
APT::Periodic::Unattended-Upgrade "0";
$ software-properties-gtk
Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options,
file=file)
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 231, in __init__
self.init_auto_update()
File
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
line 310, in init_auto_update
self.combobox_update_interval.append_text(_("Every %s days")
AttributeError: 'ComboBox' object has no attribute 'append_text'
```
Occurs in:
```
$ lsb_release -rd
Description:Ubuntu 21.04
Release:21.04
$ apt-cache policy software-properties-gtk
software-properties-gtk:
Installed: 0.99.10.2
Candidate: 0.99.10.2
Version table:
*** 0.99.10.2 500
500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main amd64
Packages
500 http://us.archive.ubuntu.com/ubuntu hirsute-updates/main i386
Packages
100 /var/lib/dpkg/status
0.99.10 500
500 http://us.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu hirsute/main i386 Packages
** Affects: software-properties (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/1964839
Title:
software-properties-gtk crashes if APT::Periodic::Upgrade-Package-
Lists="3"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1964839/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931176] [NEW] Crashed while installing with ZFS on 6TB disk
Public bug reported: Very early in the installation process. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckMismatches: ./casper/initrd CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Mon Jun 7 16:52:13 2021 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931176 Title: Crashed while installing with ZFS on 6TB disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1931176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Kernel 5.4.0-71 has finally fixed the problem. Having just installed it, I have not run extensive test on it, but it appears to be stable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Still screwed up after reinstall. At this point I'd just recommend installing the 5.11.3 kernel from the ppa and be done with it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
While 5.10.0-1017 did fix the ir-keytable problem it introduced other problems which I couldn't live with. After deleting my 5.11.3 kernel I have since reinstalled it and am running it.Maybe I'll try to reinstall the 5.10.0-1017 kernel later and see if I just got a bad install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
I'm happy to report that the following dist kernel has fixed the problem. wes@mythfe0:~$ uname -a Linux mythfe0 5.10.0-1017-oem #18-Ubuntu SMP Fri Mar 5 18:33:48 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux It's in the repos. And it also supports my nvme drive status which was why I was running later ppa kernels to begin with. Now if they could only get the 5.4 kernels fixed it would be complete. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Well, I run newer kernels from the ppa as my main kernel. Currently running 5.11.3, so it's not a problem for me. As long as whomever does the distribution kernels keep using old base kernels, the problem will never be fixed. If you want to run a distribution kernel, then you should go back to 5.4.0-48. It works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Kernel 5.4.0-67 is still broken. Can anyone explain this to me. A patch that fixed it was done in Dec. 2020. And it was implemented in ppa kernels compiled after 01/28/2021. So why is it that this has not made it into any of the distribution kernels yet. Kernels 5.10 has shown up in the repos, yet it is still based on the broken kernel versions. What the heck is going on with this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917771] Re: Icon location not updating in chromium_chromium.desktop
Did I miss something? It looks like you may have referenced 3 commands but I only see 2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917771 Title: Icon location not updating in chromium_chromium.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917771] Re: Icon location not updating in chromium_chromium.desktop
echo $XDG_DATA_DIRS: /usr/share/ubuntu:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917771 Title: Icon location not updating in chromium_chromium.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917771] Re: Icon location not updating in chromium_chromium.desktop
gsettings get org.gnome.shell favorite-apps: ['chromium_chromium.desktop', 'nemo.desktop', 'org.gnome.gedit.desktop', 'org.gnome.Terminal.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'shotwell.desktop', 'slack_slack.desktop', 'simple-scan.desktop', 'Zoom.desktop', 'gnome-system-monitor.desktop', 'flameshot.desktop', 'brackets_brackets.desktop', 'org.gnome.Calculator.desktop'] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917771 Title: Icon location not updating in chromium_chromium.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917771] Re: Icon location not updating in chromium_chromium.desktop
This has been going on for a while. I found an article that suggested a solution for the disappearing icon be to add the .desktop file. I would certainly be interested in a better solution. Changing to "current" seems to have worked but I sense you hinting there is a larger problem in having to accomplish this in this manner. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917771 Title: Icon location not updating in chromium_chromium.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917771] Re: Icon location not updating in chromium_chromium.desktop
I should have mentioned - I can go in and update chromium_chromium.desktop with the new location, the icon appears and everything works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917771 Title: Icon location not updating in chromium_chromium.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917771] [NEW] Icon location not updating in chromium_chromium.desktop
Public bug reported: I am having to constantly edit ~/.local/share/applications/chromium_chromium.desktop and update the location of the icon. I think this is something happening when an update happens. For instance Icon location: Icon=/snap/chromium/1444/chromium.png changed to Icon location: Icon=/snap/chromium/1479/chromium.png but the line in chromium_chromium.desktop did not get updated with the new location. What ends up happening is the spot in my favorites bar is blank however you can still click on the blank spot and launch chromium. ProblemType: Bug DistroRelease: Ubuntu 20.04 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Mar 4 07:43:49 2021 InstallationDate: Installed on 2021-01-19 (43 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Snap: chromium 89.0.4389.72 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal snap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917771 Title: Icon location not updating in chromium_chromium.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
last kernel upgrade to 5.4.0-66 is still broken. ** 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/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Patch was added into kernel builds on 01-31-21. Working later kernels. Linux mythfe0 5.10.13-051013-generic #202102032337 SMP Thu Feb 4 00:17:21 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
After a system upgrade last night, the patched version 5.4.0-59 that works was replaced by an older version of 5.4.0-59 dated Dec 10. So anyone that installed the patched version will likely find their remote not working again if they do a system upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Just curious how long that takes. 5.10.3 was just released today and doesn't look like it made it into it going by the changes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Yes! That fixed it for me. Glad someone here could compile it. I was lost. What happens now to all the other kernels. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
After enabling sources and reverting to ubuntu kernel 5.4.0-58 installed first part. Will continue tomorrow or later tonight. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Well, that didn't work. wes@mythfe0:~$ sudo apt-get build-dep linux linux-image-$(uname -r) [sudo] password for wes: Reading package lists... Done E: You must put some 'deb-src' URIs in your sources.list wes@mythfe0:~$ uname -r 5.10.2-051002-generic wes@mythfe0:~$ Last time I compiled a kernel was ~20 years ago. Can I assume I need to be running a current ubuntu dist. kernel to do this following those instructions? Might it not be easier to just dl current sources and manually edit rc-main.c and then recompile. i might be able to get that done. i know how to dl the sources. or maybe have someone more familiar with the process to do it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
As you can see there's no reference to ir-keytable running in that kernel. Ran the same on good kernel 5.8.7 and here's a snippet from the output of it. Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: /usr/lib/udev/rules.d/60-ir-keytable.rules:5 RUN '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s $name' Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: Running command "/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3" Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: Starting '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3' Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: Successfully forked off '(spawn)' as PID 1477. Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: wakeup39: Processing device (SEQNUM=4086, ACTION=add) Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To Be Filled By O.E.M.' Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To Be Filled By O.E.M.' Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: wakeup39: Device (SEQNUM=4086, ACTION=add) processed Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: wakeup39: sd-device-monitor: Passed 194 byte to netlink monitor Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3'(err) '/etc/rc_keymaps/rc6_mce.toml: error: cannot open: No such file or directory' Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3'(err) 'Old keytable cleared' Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3'(err) 'Wrote 163 keycode(s) to driver' Dec 21 14:04:20 mythfe0 systemd-udevd[308]: ir_nec_decoder: Device (SEQNUM=4089, ACTION=add) is queued Dec 21 14:04:20 mythfe0 systemd-udevd[308]: ir_nec_decoder: sd-device-monitor: Passed 138 byte to netlink monitor Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: ir_nec_decoder: Processing device (SEQNUM=4089, ACTION=add) Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To Be FDec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: /usr/lib/udev/rules.d/60-ir-keytable.rules:5 RUN '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s $name' Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: Running command "/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3" Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: Starting '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3' Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: Successfully forked off '(spawn)' as PID 1477. Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: wakeup39: Processing device (SEQNUM=4086, ACTION=add) Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To Be Filled By O.E.M.' Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To Be Filled By O.E.M.' Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: wakeup39: Device (SEQNUM=4086, ACTION=add) processed Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: wakeup39: sd-device-monitor: Passed 194 byte to netlink monitor Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3'(err) '/etc/rc_keymaps/rc6_mce.toml: error: cannot open: No such file or directory' Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3'(err) 'Old keytable cleared' Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3'(err) 'Wrote 163 keycode(s) to driver' Dec 21 14:04:20 mythfe0 systemd-udevd[308]: ir_nec_decoder: Device (SEQNUM=4089, ACTION=add) is queued Dec 21 14:04:20 mythfe0 systemd-udevd[308]: ir_nec_decoder: sd-device-monitor: Passed 138 byte to netlink monitor Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: ir_nec_decoder: Processing device (SEQNUM=4089, ACTION=add) Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To Be Filled By O.E.M.' Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To Be Filled By O.E.M.' Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: ir_nec_decoder: Device (SEQNUM=4089, ACTION=add) processed Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: ir_nec_decoder: sd-device-monitor: Passed 138 byte to netlink monitor Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3'(err) 'Protocols changed to nec rc-6 ' Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: Process '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3' succeeded. Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: Device (SEQNUM=4082, ACTION=add) processedilled By O.E.M.' Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: value '[dmi/id]sys_vendor' is 'To Be Filled By O.E.M.' Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: ir_nec_decoder: Device (SEQNUM=4089, ACTION=add) processed Dec 21 14:04:20 mythfe0 systemd-udevd[1464]: ir_nec_decoder: sd-device-monitor: Passed 138 byte to netlink monitor Dec 21 14:04:20 mythfe0 systemd-udevd[1458]: rc3: '/usr/bin/ir-keytable -a /etc/rc_maps.cfg -s rc3'(err) 'Protocols
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
here goes. root@mythfe0:/home/wes# journalctl -u systemd-udevd.service -f -- Logs begin at Thu 2020-09-24 22:03:46 CDT. -- Dec 21 06:58:08 mythfe0 systemd-udevd[1702]: value '[dmi/id]sys_vendor' is 'To Be Filled By O.E.M.' Dec 21 06:58:08 mythfe0 systemd-udevd[1702]: 1-8: Device (SEQNUM=4105, ACTION=remove) processed Dec 21 06:58:08 mythfe0 systemd-udevd[1702]: 1-8: sd-device-monitor: Passed 355 byte to netlink monitor Dec 21 06:58:12 mythfe0 systemd-udevd[310]: Cleanup idle workers Dec 21 06:58:12 mythfe0 systemd-udevd[1702]: Unload module index Dec 21 06:58:12 mythfe0 systemd-udevd[1701]: Unload module index Dec 21 06:58:12 mythfe0 systemd-udevd[1701]: Unloaded link configuration context. Dec 21 06:58:12 mythfe0 systemd-udevd[1702]: Unloaded link configuration context. Dec 21 06:58:12 mythfe0 systemd-udevd[310]: Worker [1701] exited Dec 21 06:58:12 mythfe0 systemd-udevd[310]: Worker [1702] exited Dec 21 06:58:29 mythfe0 systemd-udevd[310]: 1-8: Device (SEQNUM=4106, ACTION=add) is queued Dec 21 06:58:29 mythfe0 systemd-udevd[310]: Validate module index Dec 21 06:58:29 mythfe0 systemd-udevd[310]: Check if link configuration needs reloading. Dec 21 06:58:29 mythfe0 systemd-udevd[310]: Successfully forked off 'n/a' as PID 1710. Dec 21 06:58:29 mythfe0 systemd-udevd[310]: 1-8: Worker [1710] is forked for processing SEQNUM=4106. Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Processing device (SEQNUM=4106, ACTION=add) Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: value '[dmi/id]sys_vendor' is 'To Be Filled By O.E.M.' Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: value '[dmi/id]sys_vendor' is 'To Be Filled By O.E.M.' Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: /usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from results of builtin command 'usb_id' Dec 21 06:58:29 mythfe0 systemd-udevd[310]: 1-8:1.0: Device (SEQNUM=4107, ACTION=add) is queued Dec 21 06:58:29 mythfe0 systemd-udevd[310]: lirc0: Device (SEQNUM=4108, ACTION=add) is queued Dec 21 06:58:29 mythfe0 systemd-udevd[310]: input20: Device (SEQNUM=4109, ACTION=add) is queued Dec 21 06:58:29 mythfe0 systemd-udevd[310]: event8: Device (SEQNUM=4110, ACTION=add) is queued Dec 21 06:58:29 mythfe0 systemd-udevd[310]: wakeup39: Device (SEQNUM=4111, ACTION=add) is queued Dec 21 06:58:29 mythfe0 systemd-udevd[310]: 1-8:1.0: Device (SEQNUM=4112, ACTION=bind) is queued Dec 21 06:58:29 mythfe0 systemd-udevd[310]: 1-8: Device (SEQNUM=4113, ACTION=bind) is queued Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: /usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from results of builtin command 'hwdb --subsystem=usb' Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: /usr/lib/udev/rules.d/50-udev-default.rules:48 MODE 0664 Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: /usr/lib/udev/rules.d/60-drm.rules:3 Importing properties from results of builtin command 'path_id' Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: /usr/lib/udev/rules.d/69-libmtp.rules:2685 Running PROGRAM 'mtp-probe /sys/devices/pci:00/:00:01.2/:01:00.0/usb1/1-8 1 5' Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Starting 'mtp-probe /sys/devices/pci:00/:00:01.2/:01:00.0/usb1/1-8 1 5' Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: Successfully forked off '(spawn)' as PID 1712. Dec 21 06:58:29 mythfe0 mtp-probe[1712]: checking bus 1, device 5: "/sys/devices/pci:00/:00:01.2/:01:00.0/usb1/1-8" Dec 21 06:58:29 mythfe0 mtp-probe[1712]: bus: 1, device: 5 was not an MTP device Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: 'mtp-probe /sys/devices/pci:00/:00:01.2/:01:00.0/usb1/1-8 1 5'(out) '0' Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Process 'mtp-probe /sys/devices/pci:00/:00:01.2/:01:00.0/usb1/1-8 1 5' succeeded. Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Handling device node '/dev/bus/usb/001/005', devnum=c189:4 Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Setting permissions /dev/bus/usb/001/005, uid=0, gid=0, mode=0664 Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Creating symlink '/dev/char/189:4' to '../bus/usb/001/005' Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: sd-device: Created db file '/run/udev/data/c189:4' for '/devices/pci:00/:00:01.2/:01:00.0/usb1/1-8' Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: Device (SEQNUM=4106, ACTION=add) processed Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8: sd-device-monitor: Passed 744 byte to netlink monitor Dec 21 06:58:29 mythfe0 systemd-udevd[310]: 1-8:1.0: sd-device-monitor: Passed 307 byte to netlink monitor Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8:1.0: Processing device (SEQNUM=4107, ACTION=add) Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: value '[dmi/id]sys_vendor' is 'To Be Filled By O.E.M.' Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: value '[dmi/id]sys_vendor' is 'To Be Filled By O.E.M.' Dec 21 06:58:29 mythfe0 systemd-udevd[1710]: 1-8:
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Ccofigs for both kernels attached. ** Attachment added: "config-5.8.8-050808-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+attachment/5445250/+files/config-5.8.8-050808-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Oops. here's the other. ** Attachment added: "config-5.8.7-050807-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+attachment/5445251/+files/config-5.8.7-050807-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
This is with kernel 5.8.8 which doesn't work. Found /sys/class/rc/rc0/ with: Name: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) Driver: mceusb Default keymap: rc-rc6-mce Input device: /dev/input/event7 LIRC device: /dev/lirc0 Attached BPF protocols: Operation not supported Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm Enabled kernel protocols: lirc rc-6 bus: 3, vendor/product: 0471:0815, version: 0x Repeat delay = 500 ms, repeat period = 125 ms root@mythfe0:/home/wes# evtest /dev/input/event7 Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x471 product 0x815 version 0x0 Input device name: "Media Center Ed. eHome Infrared Remote Transceiver (0471:0815)" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 28 (KEY_ENTER) Event code 103 (KEY_UP) Event code 105 (KEY_LEFT) Event code 106 (KEY_RIGHT) Event code 108 (KEY_DOWN) Event code 111 (KEY_DELETE) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 119 (KEY_PAUSE) Event code 128 (KEY_STOP) Event code 142 (KEY_SLEEP) Event code 161 (KEY_EJECTCD) Event code 164 (KEY_PLAYPAUSE) Event code 167 (KEY_RECORD) Event code 168 (KEY_REWIND) Event code 174 (KEY_EXIT) Event code 207 (KEY_PLAY) Event code 208 (KEY_FASTFORWARD) Event code 210 (KEY_PRINT) Event code 212 (KEY_CAMERA) Event code 224 (KEY_BRIGHTNESSDOWN) Event code 225 (KEY_BRIGHTNESSUP) Event code 226 (KEY_MEDIA) Event code 352 (KEY_OK) Event code 356 (KEY_POWER2) Event code 358 (KEY_INFO) Event code 365 (KEY_EPG) Event code 366 (KEY_PVR) Event code 368 (KEY_LANGUAGE) Event code 369 (KEY_TITLE) Event code 370 (KEY_SUBTITLE) Event code 372 (KEY_ZOOM) Event code 373 (KEY_MODE) Event code 377 (KEY_TV) Event code 385 (KEY_RADIO) Event code 386 (KEY_TUNER) Event code 387 (KEY_PLAYER) Event code 389 (KEY_DVD) Event code 392 (KEY_AUDIO) Event code 393 (KEY_VIDEO) Event code 398 (KEY_RED) Event code 399 (KEY_GREEN) Event code 400 (KEY_YELLOW) Event code 401 (KEY_BLUE) Event code 402 (KEY_CHANNELUP) Event code 403 (KEY_CHANNELDOWN) Event code 407 (KEY_NEXT) Event code 412 (KEY_PREVIOUS) Event code 425 (KEY_PRESENTATION) Event code 430 (KEY_MESSENGER) Event code 512 (KEY_NUMERIC_0) Event code 513 (KEY_NUMERIC_1) Event code 514 (KEY_NUMERIC_2) Event code 515 (KEY_NUMERIC_3) Event code 516 (KEY_NUMERIC_4) Event code 517 (KEY_NUMERIC_5) Event code 518 (KEY_NUMERIC_6) Event code 519 (KEY_NUMERIC_7) Event code 520 (KEY_NUMERIC_8) Event code 521 (KEY_NUMERIC_9) Event code 522 (KEY_NUMERIC_STAR) Event code 523 (KEY_NUMERIC_POUND) Event type 2 (EV_REL) Event code 0 (REL_X) Event code 1 (REL_Y) Found /sys/class/rc/rc0/ with: Name: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) Driver: mceusb Default keymap: rc-rc6-mce Input device: /dev/input/event7 LIRC device: /dev/lirc0 Attached BPF protocols: Operation not supported Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm Enabled kernel protocols: lirc rc-6 bus: 3, vendor/product: 0471:0815, version: 0x Repeat delay = 500 ms, repeat period = 125 ms root@mythfe0:/home/wes# evtest /dev/input/event7 Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x471 product 0x815 version 0x0 Input device name: "Media Center Ed. eHome Infrared Remote Transceiver (0471:0815)" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 28 (KEY_ENTER) Event code 103 (KEY_UP) Event code 105 (KEY_LEFT) Event code 106 (KEY_RIGHT) Event code 108 (KEY_DOWN) Event code 111 (KEY_DELETE) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 119 (KEY_PAUSE) Event code 128 (KEY_STOP) Event code 142 (KEY_SLEEP) Event code 161 (KEY_EJECTCD) Event code 164 (KEY_PLAYPAUSE) Event code 167 (KEY_RECORD) Event code 168 (KEY_REWIND) Event code 174 (KEY_EXIT) Event code 207 (KEY_PLAY) Event code 208 (KEY_FASTFORWARD) Event code 210 (KEY_PRINT) Event code 212 (KEY_CAMERA) Event code 224 (KEY_BRIGHTNESSDOWN) Event code 225 (KEY_BRIGHTNESSUP) Event code 226 (KEY_MEDIA) Event code 352 (KEY_OK) Event code 356 (KEY_POWER2) Event code 358 (KEY_INFO) Event code 365 (KEY_EPG) Event code 366 (KEY_PVR) Event code 368 (KEY_LANGUAGE) Event code 369 (KEY_TITLE) Event code 370 (KEY_SUBTITLE) Event code 372 (KEY_ZOOM) Event code 373 (KEY_MODE) Ev
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
This is with working kernel 5.8.7. root@mythfe0:/home/wes# ir-keytable Found /sys/class/rc/rc3/ with: Name: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) Driver: mceusb Default keymap: rc-rc6-mce Input device: /dev/input/event19 LIRC device: /dev/lirc3 Attached BPF protocols: Operation not supported Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm Enabled kernel protocols: lirc nec rc-6 bus: 3, vendor/product: 0471:0815, version: 0x Repeat delay = 500 ms, repeat period = 125 ms root@mythfe0:/home/wes# evtest /dev/input/event19 Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x471 product 0x815 version 0x0 Input device name: "Media Center Ed. eHome Infrared Remote Transceiver (0471:0815)" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 1 (KEY_ESC) Event code 2 (KEY_1) Event code 3 (KEY_2) Event code 4 (KEY_3) Event code 5 (KEY_4) Event code 6 (KEY_5) Event code 7 (KEY_6) Event code 8 (KEY_7) Event code 9 (KEY_8) Event code 10 (KEY_9) Event code 11 (KEY_0) Event code 16 (KEY_Q) Event code 17 (KEY_W) Event code 18 (KEY_E) Event code 19 (KEY_R) Event code 20 (KEY_T) Event code 21 (KEY_Y) Event code 22 (KEY_U) Event code 23 (KEY_I) Event code 24 (KEY_O) Event code 25 (KEY_P) Event code 28 (KEY_ENTER) Event code 30 (KEY_A) Event code 31 (KEY_S) Event code 32 (KEY_D) Event code 33 (KEY_F) Event code 34 (KEY_G) Event code 35 (KEY_H) Event code 36 (KEY_J) Event code 37 (KEY_K) Event code 38 (KEY_L) Event code 39 (KEY_SEMICOLON) Event code 44 (KEY_Z) Event code 45 (KEY_X) Event code 46 (KEY_C) Event code 47 (KEY_V) Event code 48 (KEY_B) Event code 49 (KEY_N) Event code 50 (KEY_M) Event code 51 (KEY_COMMA) Event code 52 (KEY_DOT) Event code 53 (KEY_SLASH) Event code 67 (KEY_F9) Event code 68 (KEY_F10) Event code 87 (KEY_F11) Event code 88 (KEY_F12) Event code 102 (KEY_HOME) Event code 103 (KEY_UP) Event code 104 (KEY_PAGEUP) Event code 105 (KEY_LEFT) Event code 106 (KEY_RIGHT) Event code 107 (KEY_END) Event code 108 (KEY_DOWN) Event code 109 (KEY_PAGEDOWN) Event code 111 (KEY_DELETE) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 116 (KEY_POWER) Event code 119 (KEY_PAUSE) Event code 128 (KEY_STOP) Event code 142 (KEY_SLEEP) Event code 161 (KEY_EJECTCD) Event code 164 (KEY_PLAYPAUSE) Event code 167 (KEY_RECORD) Event code 168 (KEY_REWIND) Event code 174 (KEY_EXIT) Event code 207 (KEY_PLAY) Event code 208 (KEY_FASTFORWARD) Event code 210 (KEY_PRINT) Event code 212 (KEY_CAMERA) Event code 224 (KEY_BRIGHTNESSDOWN) Event code 225 (KEY_BRIGHTNESSUP) Event code 226 (KEY_MEDIA) Event code 352 (KEY_OK) Event code 356 (KEY_POWER2) Event code 358 (KEY_INFO) Event code 365 (KEY_EPG) Event code 366 (KEY_PVR) Event code 368 (KEY_LANGUAGE) Event code 369 (KEY_TITLE) Event code 370 (KEY_SUBTITLE) Event code 372 (KEY_ZOOM) Event code 373 (KEY_MODE) Event code 377 (KEY_TV) Event code 385 (KEY_RADIO) Event code 386 (KEY_TUNER) Event code 387 (KEY_PLAYER) Event code 389 (KEY_DVD) Event code 392 (KEY_AUDIO) Event code 393 (KEY_VIDEO) Event code 398 (KEY_RED) Event code 399 (KEY_GREEN) Event code 400 (KEY_YELLOW) Event code 401 (KEY_BLUE) Event code 402 (KEY_CHANNELUP) Event code 403 (KEY_CHANNELDOWN) Event code 407 (KEY_NEXT) Event code 412 (KEY_PREVIOUS) Event code 425 (KEY_PRESENTATION) Event code 430 (KEY_MESSENGER) Event code 512 (KEY_NUMERIC_0) Event code 513 (KEY_NUMERIC_1) Event code 514 (KEY_NUMERIC_2) Event code 515 (KEY_NUMERIC_3) Event code 516 (KEY_NUMERIC_4) Event code 517 (KEY_NUMERIC_5) Event code 518 (KEY_NUMERIC_6) Event code 519 (KEY_NUMERIC_7) Event code 520 (KEY_NUMERIC_8) Event code 521 (KEY_NUMERIC_9) Event code 522 (KEY_NUMERIC_STAR) Event code 523 (KEY_NUMERIC_POUND) Event type 2 (EV_REL) Event code 0 (REL_X) Event code 1 (REL_Y) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Key repeat handling: Repeat type 20 (EV_REP) Repeat code 0 (REP_DELAY) Value500 Repeat code 1 (REP_PERIOD) Value125 Properties: Property type 5 (INPUT_PROP_POINTING_STICK) Testing ... (interrupt to exit) Event: time 1608477381.651705, type 4 (EV_MSC), code 4 (MSC_SCAN), value 02 Event: time 1608477381.651705, type 1 (EV_KEY), code 3 (KEY_2), value 1 Event: time 1608477381.651705, -- SYN_REPORT 2Event: time 1608477381.703235, type 4 (EV_MSC), code 4 (MSC_SCAN), value 02 E
Re: [Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
On 12/19/20 5:09 PM, Sean Young wrote: > Hello, the author of those commits here. It's not clear to me how those > commits broke things. Either something else changed, or there is > something subtle going on. > > The following bits of information would be very useful. > > 1. Is the issue intermittent or consistent, i.e. does booting with a new > kernel always cause some keys to fail and an older kernel all the keys always > work fine? > 2. What keymap are you loading? > 3. Are you using a streamzap device? > 3. How are you loading the keymap; i.e. how is ir-keytable run, and with what > command line. > 4. Once the system is booted, it would be useful to know what the output of > the evtest command line tool is (after you select the device) > > Ideally it would also be useful to know what happens if you revert those > commits. > > Thank you 1. It's consistent. older kernels always work. never ones never work. 2. I'm using a custom keymap. I'll attach my keymap file and config file. Don't know what the original reporter uses. 3. No. I'm using a JP1 remote with my own custom nec protocol. 4. You lost me on this one. Don't know what evtest you mean. Nor do I select the device. It just works after boot. I'm not a kernel guy and don't know how to revert the commits. Here's my ir-keytable output on kernel 5.8.7. wes@mythfe0:~$ ir-keytable Found /sys/class/rc/rc3/ with: Name: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) Driver: mceusb Default keymap: rc-rc6-mce Input device: /dev/input/event19 LIRC device: /dev/lirc3 Attached BPF protocols: Permission denied Supported kernel protocols: lirc rc-5 rc-5-sz jvc sony nec sanyo mce_kbd rc-6 sharp xmp imon rc-mm Enabled kernel protocols: lirc nec rc-6 Newer kernels ir-keytable output does not enable the nec protocol. I have removed them from my system. Currently running 5.8.7. It was the last one that worked. All after that don't work. The last ubuntu kernel that worked was 5.4.0-48. None after that work either. I have no clue if those commits have anything to do with this. It was someone else's comment in the bug report. If I'm barking up the wrong tree I'm sorry to have bothered you. -- https://github.com/wesnewell/Functionality http://wesnewell.ddns.net ** Attachment added: "rc_maps.cfg" https://bugs.launchpad.net/bugs/1901089/+attachment/5445176/+files/rc_maps.cfg ** Attachment added: "myremotes.toml" https://bugs.launchpad.net/bugs/1901089/+attachment/5445177/+files/myremotes.toml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
I've emailed the person that commited them. With luck. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
I have no idea how to do that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
** 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/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
5.8.7-050807-generic #202009051031 SMP Sat Sep 5 10:34:16 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux WORKS. kernel 5.8.8 does not. Looks like any kernel built after Sep 5 2020 will be bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Last ubuntu kernel that worked was 5.4.0-48. First that doesn't is 5.4.0-51. And there isn't a 5.4.0 dir list here. https://kernel.ubuntu.com/~kernel-ppa/mainline/ It works in some later kernels from mainline but quit working sometime after 5.4.53, and doesn't work in 5.9 or 5.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
AFAICT, it affects all later kernels starting after 5.4.0-48 somewhere. that includes 5.9 and 5.10 which i just installed a couple of days ago. If you think it would help I can reboot to whichever kernel you want and post dmesg output.Wondering if this should be posted as a kernel bug too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Interesting, but doesn't seem to be a proper fix. Been running ir- keytable for years and was never able to use ir-krytable -t as a regular user. had to redo keymap file going from xubuntu 18.04lts to 20.04lts. Having to load after boot is not a viable option as this is a frontend my wife uses that boots staight to mythtv frontend and if the remote doesn't work on boot, to her it's broke. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901089] Re: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading
Just upgraded to -58 kernel and it broke my remote too. Going back to -42 kernel fixed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901089 Title: Ubuntu kernels 5.4.0-51 and 5.4.0-52 break ir-keytable loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901089/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901959] Re: Default Profile is called "default-release", programs like Slack open links with different "default" profile
if someone has a good contact at Slack, please reach out to them about this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901959 Title: Default Profile is called "default-release", programs like Slack open links with different "default" profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1901959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901959] Re: Default Profile is called "default-release", programs like Slack open links with different "default" profile
I'm reporting that it opens the wrong profile. I'm not sure how Slack does this but I'm guessing Oliver is right, they call it directly with -profile or something Marking invalid since this is a FF/Slack issue. ** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901959 Title: Default Profile is called "default-release", programs like Slack open links with different "default" profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1901959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901959] [NEW] Default Profile is called "default-release", programs like Slack open links with different "default" profile
Public bug reported: Firefox 82.0 Ubuntu 20.04 The default profile in the Ubuntu Firefox package is called "default- release", while the typical profile name for Firefox is "default". Slack opens links using the default profile when Firefox is the browser, causing links to open in a different profile than normal without the extensions , history, etc. from the normal browsing profile. To reproduce: - Set up Firefox in Ubuntu , run session to generate profile, install extensions - Install Slack from snap : snap install slack - Firefox as default browser in Ubuntu - Open link in Slack Slack opens the "default" profile of Firefox, which is different than the "default-release" that the Ubuntu firefox package defaults to. Expected: Ubuntu Firefox uses the normal "default" profile as default. Cheers, ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: focal ** Summary changed: - Default Profile is called "default-release", causing unexpected behavior in programs like Slack that expect "default" profile + Default Profile is called "default-release", programs like Slack open links with "default" profile ** Summary changed: - Default Profile is called "default-release", programs like Slack open links with "default" profile + Default Profile is called "default-release", programs like Slack open links with different "default" profile -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901959 Title: Default Profile is called "default-release", programs like Slack open links with different "default" profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1901959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04
Sigh indeed. The ignoring of this bug report (and many other bad, bad decisions for that matter) has now lead us to just abandon Ubuntu entirely. Even for non-server desktop use cases. I have no idea if the original reported issue has ever actually been dealt with, and I guess I never will. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771236 Title: forced use of systemd-networkd interferes with ifupdown in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1771236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872122] Re: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] [8086:9df0] (rev 30) Subsystem [8086:0034] Kernel 4.19+: Bluetooth not working; Ubuntu 20.04
> In kernel v < 4.19 the "normal" BLE commands work. > In kernel v > 4.19 only the BLE extended (BT 5.0) commands work. .. > So it doesn't seem to be an issue in kernel What? That indicates it is a problem with the kernel, doesn't it? The desired behaviour exists in previous versions but is broken in current versions where the only component changing is the kernel version. I too am seeing this and specifically with the AC 9560's Bluetooth's BLE on a 4.19 kernel - I am unable to scan or query any BLE devices with this hw and kernel now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872122 Title: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] [8086:9df0] (rev 30) Subsystem [8086:0034] Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876157] Re: memtest86+ freeze on 4 different PCs
memtest86+ freezes on my am4 ryzen 3 2200G and 3200G systems. Runs fine on all my older systems. And Theirs nothing wrong with the memory on the amd system. Multiple passes with another tester. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876157 Title: memtest86+ freeze on 4 different PCs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1876157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808951] Re: python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object
** Changed in: tripleo Milestone: ussuri-rc3 => victoria-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808951 Title: python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1808951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808951] Re: python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object
** Changed in: tripleo Milestone: ussuri-3 => ussuri-rc3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808951 Title: python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1808951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808951] Re: python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object
** Changed in: tripleo Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808951 Title: python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1808951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869878] [NEW] Space in username breaks wsl integration cache
Public bug reported: * What you're doing and what's happening: launching bash from a user whose name includes a space breaks /etc/profile.d/wsl-integration.sh * What's wrong / what should be happening instead: > PS C:\Users\Jack Troughton\git\dcp-jason> bash > -bash: [: /mnt/c/Users/Jack: binary operator expected > mkdir: cannot create directory ë/mnt/c/Users/Jackí: Permission denied > -bash: $WSL_INTEGRATION_CACHE: ambiguous redirect > > The reason it breaks is due to incorrect quoting around $HOME and things derived from it. It looks like you have parallel issues as well which could break pulse audio on a machine with a space in its hostname (is that legal in windows-land?) I have created a zip file containing a fix, both the complete script and a unified context diff. I hereby place my changes in the public domain, free for use by anybody for anything. The fix is at http://people.kingsds.network/wesgarland/wsl-integration- fix.zip Windows build number: Microsoft Windows [Version 10.0.18362.720] My WSL is the Ubuntu flavour of Linux version 4.4.0-18362-Microsoft (micros...@microsoft.com) (gcc version 5.4.0 (GCC) ) #476-Microsoft Fri Nov 01 16:53:00 PST 2019 lsb_release -rd says Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy wslu says wslu: Installed: (none) Candidate: 2.3.2-0ubuntu2~18.04.3 Version table: 2.3.2-0ubuntu2~18.04.3 500 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages ** Affects: wslu (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/1869878 Title: Space in username breaks wsl integration cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1869878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808951] Re: python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object
** Changed in: tripleo Milestone: ussuri-2 => ussuri-3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808951 Title: python3 + Fedora + SSL + wsgi nova deployment, nova api returns RecursionError: maximum recursion depth exceeded while calling a Python object To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1808951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858293] Re: Missing repeated characters
Hello, Hello and than you for the assistance and your time. For sure I thought this was a bug because it appeared platform dependent and only associated with nano. The first thing I did was I checked my version of PuTTy which was .70 and then checked the PuTTy site and updated to PuTTy .73 and this "bug" is gone. Updating PuTTy to .73 resolved my issue. Probably the first thing I should have done, but we never quit learning. Nano is my favorite terminal editor. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858293 Title: Missing repeated characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1858293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858293] Re: Missing repeated characters
Question Answers: 1. Windows 10 laptop core i7 Microsoft Windows [Version 10.0.17763.914] 2. TERM=xterm 3. write(1, "\33[?1049h\33[22;0;0t\33[1;47r\33(B\33[m\33[4l\33[?7h\33[39;49m\33[?1h\33=", 54) = 54 write(1, "\33[?1h\33=", 7) = 7 write(1, "\33[?1h\33=", 7) = 7 write(1, "\33[?25l", 6) = 6 write(1, "\33[39;49m\33(B\33[m\33[H\33[2J", 21) = 21 write(1, "\33(B\33[0;7m GNU nano 2.9.3 \33[53bNew Buffer \33[63b \33[1;144H", 56) = 56 write(1, "\33(B\33[m", 6) = 6 write(1, "\r\33[46d", 6)= 6 write(1, "\33(B\33[0;7m^G\33(B\33[m Get Help \33(B\33[0;7m^O\33(B\33[m Write Out\33(B\33[0;7m^W\33(B\33[m Where Is \33(B\33[0;7m^K\33(B\33[m Cut Text \33(B\33[0;7m^J\33(B\33[m Justify\33[81G", 154) = 154 write(1, "\33(B\33[0;7m^C\33(B\33[m Cur Pos\33[97G", 30) = 30 write(1, "\33(B\33[0;7mM-U\33(B\33[m Undo\33[46;113H", 32) = 32 write(1, "\33(B\33[0;7mM-A\33(B\33[m Mark Text \33(B\33[0;7mM-]\33(B\33[m To Bracket\r\33[47d", 66) = 66 write(1, "\33(B\33[0;7m^X\33(B\33[m Exit\33[47;17H", 30) = 30 write(1, "\33(B\33[0;7m^R\33(B\33[m Read File\33(B\33[0;7m^\\\33(B\33[m Replace\33[49G", 61) = 61 write(1, "\33(B\33[0;7m^U\33(B\33[m Uncut Text \33(B\33[0;7m^T\33(B\33[m To Spell \33(B\33[0;7m^_\33(B\33[m Go To Line \33(B\33[0;7mM-E\33(B\33[m Redo\33[47;113H", 125) = 125 write(1, "\33(B\33[0;7mM-6\33(B\33[m Copy Text \33(B\33[0;7mM-W\33(B\33[m WhereIs Next\r\33[45d", 68) = 68 write(1, "\33[3d", 4) = 4 write(1, "\33[39;49m\33(B\33[m", 14)= 14 write(1, "\33[?12l\33[?25h", 12)= 12 write(1, "\33[?25l", 6) = 6 write(1, "\33[1;136H", 8) = 8 write(1, "\33(B\33[0;7mModified", 17) = 17 write(1, "\33(B\33[m", 6) = 6 write(1, "\r\33[3d", 5) = 5 write(1, "#\33[9G", 5) = 5 write(1, "+-\33[7b+\33[25G", 12)= 12 write(1, "+-\33[7b+\33[41G", 12)= 12 write(1, "+-\33[7b+\33[57G", 12)= 12 write(1, "+-\33[7b+\r\33[4d", 12) = 12 write(1, "#\33[9G", 5) = 5 write(1, "|\33[4;18H", 8) = 8 write(1, "|\33[25G", 6) = 6 write(1, "|\33[4;34H", 8) = 8 write(1, "|\33[41G", 6) = 6 write(1, "|\33[4;50H", 8) = 8 write(1, "|\33[57G", 6) = 6 write(1, "|\33[4;66H", 8) = 8 write(1, "|\r\33[5d", 6)= 6 write(1, "# >CLK->|\33[5;18H", 16) = 16 write(1, "|>CLK->|\33[5;34H", 15) = 15 write(1, "|>CLK->|\33[5;50H", 15) = 15 write(1, "|>CLK->|\33[5;66H", 15) = 15 write(1, "|>CLK->\r\33[6d", 12) = 12 write(1, "# >CS ->|\33[6;18H", 16) = 16 write(1, "|>CS ->|\33[6;34H", 15) = 15 write(1, "|>CS ->|\33[6;50H", 15) = 15 write(1, "|>CS ->|\33[6;66H", 15) = 15 write(1, "|>CS ->\r\33[7d", 12) = 12 write(1, "# >DIN->|\33[7;18H", 16) = 16 write(1, "|>DIN->|\33[7;34H", 15) = 15 write(1, "|>DIN->|\33[7;50H", 15) = 15 write(1, "|>DIN->|\33[7;66H", 15) = 15 write(1, "|>DIN->\r\33[8d", 12) = 12 write(1, "#\33[9G", 5) = 5 write(1, "|\33[8;18H", 8) = 8 write(1, "|\33[25G", 6) = 6 write(1, "|\33[8;34H", 8) = 8 write(1, "|\33[41G", 6) = 6 write(1, "|\33[8;50H", 8) = 8 write(1, "|\33[57G", 6) = 6 write(1, "|\33[8;66H", 8) = 8 write(1, "|\r\33[9d", 6)= 6 write(1, "#\33[9G", 5) = 5 write(1, "+-\33[7b+\33[25G", 12)= 12 write(1, "+-\33[7b+\33[41G", 12)= 12 write(1, "+-\33[7b+\33[57G", 12)= 12 write(1, "+-\33[7b+", 7)= 7 write(1, "\33[?12l\33[?25h", 12)= 12 write(1, "\33[?25l", 6) = 6 write(1, "\r\33[45d", 6)= 6 write(1, "\33(B\33[0;7mSave modified buffer? (Answering \"No\" will DISCARD changes.) \33[82b \33[46;1H", 84) = 84 write(1, " Y\33(B\33[m Yes\33[K\r\33[47d", 21) = 21 write(1, "\33(B\33[0;7m N\33(B\33[m No \33[47;18H", 30) = 30 write(1, "\33(B\33[0;7mC\33(B\33[m Cancel\33[K\33[45;63H", 34) = 34 write(1, "\33[?12l\33[?25h", 12)= 12 write(1, "\33[?25l", 6) = 6 write(1, "\r", 1) = 1 write(1, "\33[J\33[47;145H", 12)= 12 write(1, "\33[?12l\33[?25h", 12)= 12 write(1, "\33[47;1H\33[?1049l\33[23;0;0t\r\33[?1l\33>", 32) = 32 +++ exited with 0 +++ 4. I am putty'd in on machine 1 and ssh into machine 2, open nano, paste the example and issue is still there. 5. I have not "built" a nano4-7 on the machine. But I can try tomorrow if you still need me to do so. Just let me know. 6. I do not have access to a 19.10 machine Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858293 Title: Missing repeated characters To manage
[Bug 1858293] [NEW] Missing repeated characters
Public bug reported: Nano 2.9.3 Ubuntu 18.04.3 LTS - Linux 4.14.157-171 armv7l ARMv7 Processor rev 3 (v7l) Ubuntu 18.04.3 LTS - Linux 4.9.196-63 aarch64 Amlogic S922X rev a (4 A73 + 2 A53) This issue is repeatable on more than 6 each different machines of the above configurations. I am using ssh via Putty to log in via terminal screen. I am using nano defaults. I have not changed anything nor do I open with any arguments. I use nano and it's not associated with any extension. It behaves the same for all files, even no extension files. Nano is not changing the file, it's just not displaying correctly. The characters are there and they save properly, they're just not visible on the terminal screen. Using WinSCP presents no issues as I am using my local Windows text editor. If I use vi to view the file there are no problems. If I use cat to view the file there are no problems. If I use tail to view the file there are no problems I do not experience this issue on: Nano 2.5.3 Ubuntu 16.04.6 LTS - Linux 4.14.5-92 armv7l ARMv7 Processor rev 3 (v7l) If I take any file that has repeat characters such as: - ||| Nano 2.9.3 will not display all of the continuous repeat characters in the row. For example: Copy and paste is displayed as: # <-- But end of line is correct If I copy that line from the file in nano editor and paste it into another non nano editor I get: # as the paste result This is the same for all different repeated characters. If I keyboard type ## nano will display it until nano is closed and then the same file is reopened. Then it's same as above, one # but end of line is correct. Pasting: # ++ ++ ++ ++ # || || || || # >CLK->||>CLK->||>CLK->||>CLK->||>CLK-> # >CS ->||>CS ->||>CS ->||>CS ->||>CS -> # >DIN->||>DIN->||>DIN->||>DIN->||>DIN-> # || || || || # ++ ++ ++ ++ into nano results in displayed: # +-+ +-+ +-+ +-+ # | | | | | | | | # >CLK->| |>CLK->| |>CLK->| |>CLK->| |>CLK-> # >CS ->| |>CS ->| |>CS ->| |>CS ->| |>CS -> # >DIN->| |>DIN->| |>DIN->| |>DIN->| |>DIN-> # | | | | | | | | # +-+ +-+ +-+ +-+ while nano is still open. Close the file and view in cat, vi or tail and it is show properly.. Pasting: # ++ ++ ++ ++ # || || || || # >CLK->||>CLK->||>CLK->||>CLK->||>CLK-> # >CS ->||>CS ->||>CS ->||>CS ->||>CS -> # >DIN->||>DIN->||>DIN->||>DIN->||>DIN-> # || || || || # ++ ++ ++ ++ using vi editor then save file and open file in nano results in: # +-+ +-+ +-+ +-+ # | | | | | | | | # >CLK->| |>CLK->| |>CLK->| |>CLK->| |>CLK-> # >CS ->| |>CS ->| |>CS ->| |>CS ->| |>CS -> # >DIN->| |>DIN->| |>DIN->| |>DIN->| |>DIN-> # | | | | | | | | # +-+ +-+ +-+ +-+ ** Affects: nano (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/1858293 Title: Missing repeated characters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nano/+bug/1858293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819074] Re: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd-networkd
Medium? I've had this take a few prod clusters offline at highly inconvenient times, it effectively makes keepalived on 18.04 unfit for purpose. We've had to build our own keepalived packages to keep things running - I think you need to give this a bit more priority please -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819074 Title: Keepalived < 2.0.x in Ubuntu 18.04 LTS not compatible with systemd- networkd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/1819074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839174] Re: Xorg crashes in stdio functions under pci_device_vgaarb_set_target() from VGAGet() from VGAarbiterSpriteMoveCursor()
installing the HWE packages resolved the issue for Linux Mint 19.2, thank you. Command: apt install --install-recommends xserver-xorg-hwe-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/1839174 Title: Xorg crashes in stdio functions under pci_device_vgaarb_set_target() from VGAGet() from VGAarbiterSpriteMoveCursor() To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1839174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839174] [NEW] Xorg crashes - segfault error 6 in libc-2.27.so
Public bug reported: Issue xorg crashes, there doesn't seem to be any repeatable cause, it'll happen just watching hulu or youtube, it'll happen when using citrix, or when playing steam games. Steps to reproduce use xorg for a while Expected behaviour not crashing Other information issue only happens when using pci-e passthrough to qemu virtual machines Has been an issue since setting up pci-e passthrough, have reinstalled Linux Mint (from XFCE version) but error persists, have changed numerous bios settings without having an impact Upgraded bios to most recent version, also reset bios to factory defaults, didn't make a difference Tried latest Linux 5.x kernels from uuku, same issue The virtual machine doesn't have any problems, it never crashes and stays running when the host os xorg crashes. System:Host: drac Kernel: 4.15.0-55-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Cinnamon 4.2.3 Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic Machine: Type: Server System: Supermicro product: Super Server v: 0123456789 serial: Mobo: Supermicro model: X10SRL-F v: 1.01B serial: UEFI: American Megatrends v: 3.1c date: 05/02/2019 Graphics: Device-1: NVIDIA GP104 [GeForce GTX 1070] vendor: Micro-Star MSI driver: nvidia v: 430.34 bus ID: 03:00.0 Device-2: NVIDIA GK104 [GeForce GTX 770] vendor: eVga.com. driver: vfio-pci v: 0.2 bus ID: 04:00.0 Device-3: ASPEED Graphics Family vendor: Super Micro driver: ast v: kernel bus ID: 0b:00.0 Display: x11 server: X.Org 1.19.6 driver: nvidia resolution: 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: GeForce GTX 1070/PCIe/SSE2 v: 4.6.0 NVIDIA 430.34 direct render: Yes CPU: Topology: 6-Core model: Intel Xeon E5-1650 v4 bits: 64 type: MT MCP arch: Broadwell rev: 1 L2 cache: 15.0 MiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 86397 Speed: 1203 MHz min/max: N/A Core speeds (MHz): 1: 1203 2: 1206 3: 1330 4: 1200 5: 1201 6: 1201 7: 1200 8: 1200 9: 2046 10: 1202 11: 1202 12: 1201 Not using PPA builds Linux Mint 19.2 (Upgraded from 19.1) 64bit root@drac:/vms# apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu7.1 Candidate: 1:7.7+19ubuntu7.1 Version table: *** 1:7.7+19ubuntu7.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:7.7+19ubuntu7 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 1070GTX - NVIDIA-Linux-x86_64-430.34.run Left screen is a 60hz monitor, right screen is a 120hz monitor Also have a 770GTX bound to vfio for virtual machine passthrough Previously used the PPA from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa, but changed to Nvidia's .run to see if it made a different - it did not. [xsession-errors.old.upload.txt](https://github.com/linuxmint/cinnamon/files/3471789/xsession-errors.old.upload.txt) [xsession-errors.upload.txt](https://github.com/linuxmint/cinnamon/files/3471791/xsession-errors.upload.txt) [lspci.txt](https://github.com/linuxmint/cinnamon/files/3471859/lspci.txt) Syslog: [kernel.log.txt](https://github.com/linuxmint/cinnamon/files/3471804/kernel.log.txt) Grub: having mitigations on or off makes no difference GRUB_CMDLINE_LINUX_DEFAULT="intel_idle.max_cstate=1 drm.debug=14 log_buf_len=16M mitigations=on intel_iommu=on vfio-pci.ids=8086:8d26,10de:1184,10de:0e0a modprobe.blacklist=snd_hda_intel,snd_hda_core,snd_hda_codec,snd_hda_codec_hdmi,nouveau" Xorg crashdump traces: /var/crash/usr_lib_xorg_Xorg.0.crash Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -noliste'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f34b8f87432 in __GI__IO_default_xsputn (f=0x7f34b0427610, data=0x7f34b90b5030 , n=3) at genops.c:389 389 genops.c: No such file or directory. [Current thread is 1 (Thread 0x7f34b0c26700 (LWP 1320))] (gdb) thread 2 [Switching to thread 2 (Thread 0x7f34bbc10600 (LWP 1196))] #0 0x7f34b92fb2b7 in __libc_write (fd=14, buf=0x7fffd039b2c0, nbytes=23) at ../sysdeps/unix/sysv/linux/write.c:27 27 ../sysdeps/unix/sysv/linux/write.c: No such file or directory. Thread 1 backtrace: #0 0x7f34b8f87432 in __GI__IO_default_xsputn (f=0x7f34b0427610, data=0x7f34b90b5030 , n=3) at genops.c:389 #1 0x7f34b8f7937e in __GI__IO_padn (fp=fp@entry=0x7f34b0427610, pad=pad@entry=48, count=count@entry=3) at iopadn.c:64 #2 0x7f34b8f55f20 in _IO_vfprintf_internal (s=s@entry=0x7f34b0427610, format=format@entry=0x7f34bac5f55c "target PCI:%04x:%02x:%02x.%x", ap=ap@entry=0x7f34b0427790) at vfprintf.c:1642 #3 0x7f34b902b169 in ___vsnprintf_chk (s=0x7f34b0427890 "target PCI:\020\200y\360.0\323\b3\330U", maxlen=, flags=1, slen=, format=0x7f34bac5f55c "target
[Bug 1838176] Re: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login screen with cursor
Same here. Reported to https://bugzilla.kernel.org/show_bug.cgi?id=204325 Covers all 5.2.x kernels up to 5.2.5. No video, no KB response. But system runs. Can ssh into it. Runs fine on kernels up to 5.1.21. Ryzen 3 2200G using internal video. ** Bug watch added: Linux Kernel Bug Tracker #204325 https://bugzilla.kernel.org/show_bug.cgi?id=204325 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838176 Title: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login screen with cursor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1838176/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314988] Re: Missing tray icon
This is not a bug only a very weird ubuntu not having a system tray issue. the fact is that this program was intended to be used just like (example. When you click on the Wi-Fi status icon, and then a small menu pops up. Thats it.) If your like me and you saw a picture of the settings GUI. And then you install software. Made sure you had all the dependencies. And then after you click on icon nothing happends.. Well Look No More. All you have to do is open terminal. And type. qjoypad --notray Then the enter key.. And it might come back with one line of code. But a GUI window will pop up. Keep terminal open click on GUI of controller icon. And thank disco dingo for trying to be like win10.and then win10 for trying to be like an ipad interface. Then use qjoypadthats it took me hours to figure this crap out. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314988 Title: Missing tray icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qjoypad/+bug/1314988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807743] Re: QEMU timerfd_create support on PowerPC
I have tested this package and it fixes the bug without causing any regressions in my tests. To test the update I re-performed the test case procedure to verify the updated package fixed the bug and then used the updated package to run the unit tests for an internal application compiled for ppc64. Is that enough to move this from verification-needed to verification- done? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807743 Title: QEMU timerfd_create support on PowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1807743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
RE: [Bug 1807743] Re: QEMU timerfd_create support on PowerPC
When I try to edit the description I'm getting timeout errors (maybe because I'm behind a corporate proxy?). I've written the test case below. Please add it to the bug description. [Test Case] * Compile the attached source code using your host C compiler. * Run the resulting binary. > It should run for 3 seconds and print timer information. (sanity test) * Compile the attached source code using a PowerPC cross compiler with static linking enabled (to make the remaining steps simpler). * Run the resulting binary using the unpatched qemu-user or qemu-user-static executable for your selected PowerPC architecture. > It should exit immediately complaining about an unsupported syscall. * Run the same binary using the patched qemu-user or qemu-user-static executable for your selected PowerPC architecture. > It should behave as the host version did. > If you chose a big-endian PowerPC architecture, the "timer expirations" output may be "72057594037927936" instead of "1" because the bytes read were in host byte order instead of target byte order. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807743 Title: QEMU timerfd_create support on PowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1807743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807743] Re: QEMU timerfd_create support on PowerPC
I've attached source code to use for the test case. I tested it using the Ubuntu standard compiler (gcc package), the Ubuntu standard powerpc64 cross compiler (gcc-powerpc64-linux-gnu package), and a custom GCC 4.9.2 targeting PowerPC64 on an embedded board. ** Attachment added: "C source code to exercise timerfd support" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1807743/+attachment/5221438/+files/timerfd_support_test.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807743 Title: QEMU timerfd_create support on PowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1807743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807743] [NEW] QEMU timerfd_create support on PowerPC
Public bug reported: QEMU erroneously fails to detect support for the timerfd_create syscall when running user-mode emulation of PowerPC targets. QEMU supports the timerfd_create syscall, but because the PowerPC target syscall header has it named "timerfd" instead of "timerfd_create", support is erroneously not enabled. This notably affects anything that uses Boost.Asio with deadline timers because it uses timerfds under the hood. I have attached a patch to fix the problem. For now I have a custom- built qemu-user-static.deb file with this fix implemented, but I would appreciate it if you could officially backport this patch to 16.04 LTS (Xenial) so our developers can use the official package repositories. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Patch added: "Add an extra define to enable timerfd_create support." https://bugs.launchpad.net/bugs/1807743/+attachment/5220929/+files/fix-timerfd-support-on-ppc.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807743 Title: QEMU timerfd_create support on PowerPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1807743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778569] Re: ir-keytable -c -w /etc/rc_keymaps/file
** Summary changed: - vlc liblirc-client0 depends breaks kernel lirc + ir-keytable -c -w /etc/rc_keymaps/file ** Description changed: - Subject pretty much says it all. Installing vlc also installs liblirc- - client0. This hoses up kernel lirc by not allowing some key codes to be - passed to apps. ir-keytable -t shows it is working fine. Removing - liblirc-client0 fixes the problem but also removes vlc. + Subject pretty much says it all. Installing vlc also installs liblirc-client0. This hoses up kernel lirc by not allowing some key codes to be passed to apps. ir-keytable -t shows it is working fine. Removing liblirc-client0 fixes the problem but also removes vlc. + See mt last post for more details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778569 Title: ir-keytable -c -w /etc/rc_keymaps/file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1778569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783631] Re: Dual boot install - Grub install failed.
Problem resolved. I changed to BIOS to allow booting from the CDROM in EFI mode. Once that was done it worked correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783631 Title: Dual boot install - Grub install failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1783631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783631] [NEW] Dual boot install - Grub install failed.
Public bug reported: Trying a dual boot install. /dev/sda is a Windows SSD and boots normally. /dev/sdb is supposed to be the Ubuntu SSD, but grub will not install from the graphical install program. Command line install "sudo grub-install /dev/sdb" returns an error "failed to get canonical path of `cow'." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 Date: Wed Jul 25 14:50:19 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783631 Title: Dual boot install - Grub install failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1783631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Has to be the right shift key on my 18.04lts system, but I've always just used tapping the Esc key immediately after post until the grub menu comes up. I explained earlier how to remove the .24 kernel. But don't try to remove the one you are running at the time. Not sure what would happen then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Easiest thing to do is just delete the .24 kernel. During boot, start tapping the esc key repeatedly. You should get the grub menu. Select the advanced option, and then load the last good kernel, which should be the .23 one if you've kept the system up to date. Once it boots and everything is working right, you can use your package manager to remove the offending .24 kernel or do it manually with sudo apt remove . Once you've removed it, grub will automatically be updated so it will boot to the .23 kernel. FWIW, the .24 kernel was removed from the repo as to not to infect people that do updates now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
I only had the slow boot problem on 2 out of 3 systems with the .24 kernel. Both systems that had problems had single ssd drives in them. One was an ECS GF8200A mb and the other was a jetway GF8200 based mb. The system that didn't have a problem was also an ECS GF8200A mb, but does not have a ssd drive in it. All work fine so far with the .26 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
I had already installed everything from the proposed mirror using software updater, but it didn't install the new .26 kernel on the 2 affected machines. So I installed the image, headers, module-extra packages using apt-get install /bioic-proposed. that worked and everything worked fine afterwards afaik. I then removed the developer check from the software updater. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
Don't know why the new kernel didn't install from the software updater, but after manually installing it, it works fine. Now to do the same on other machine. Funny it all installed fine with the software updater on my main machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic
After turning on developer options for pre-release upgrades and installing a lot of stuff, I still have the same problem with the slow boot on the 2 machines I updated. uname-a shows same as before.Is that normal? I turned off developer stuff afterwards. Since 4.15.0-23 works fine, should I just delete the -24 til this gets straightened out? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779827 Title: failure to boot with linux-image-4.15.0-24-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780108] [NEW] kernel 4.15.0.24.26 gets fails to load right on systems with ssd drives
Public bug reported: Last software update with kernel 4.15.0.24.26 causes systems with sata ssd drives to take 5-10 minutes to init. All previous kernels booted quick. Going back to 4.15.0.23.25 works fine. Didn't see any different Failed commands in kern.log Don't know if this will help as i get them with the older kernel too, but it doesn't hang the system. lori@mythfe2:~$ cat /var/log/kern.log|grep fail Jul 3 13:24:52 mythfe2 kernel: [0.065940] acpi PNP0A03:00: _OSC failed (AE_SUPPORT); disabling ASPM Jul 3 13:24:52 mythfe2 kernel: [1.513900] ACPI: \_SB_.PCI0.IXVE.IGPU: failed to evaluate _DSM Jul 3 13:24:52 mythfe2 kernel: [2.172040] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 13:24:52 mythfe2 kernel: [2.980044] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 17:19:29 mythfe2 kernel: [0.065702] acpi PNP0A03:00: _OSC failed (AE_SUPPORT); disabling ASPM Jul 3 17:19:29 mythfe2 kernel: [1.523356] ACPI: \_SB_.PCI0.IXVE.IGPU: failed to evaluate _DSM Jul 3 17:19:29 mythfe2 kernel: [2.167996] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 17:19:29 mythfe2 kernel: [3.008000] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 17:19:29 mythfe2 kernel: [4.852022] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 17:28:37 mythfe2 kernel: [0.065742] acpi PNP0A03:00: _OSC failed (AE_SUPPORT); disabling ASPM Jul 3 17:28:37 mythfe2 kernel: [1.525808] ACPI: \_SB_.PCI0.IXVE.IGPU: failed to evaluate _DSM Jul 3 17:28:37 mythfe2 kernel: [2.136112] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 17:28:37 mythfe2 kernel: [2.968070] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 17:28:37 mythfe2 kernel: [4.592055] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 17:31:51 mythfe2 kernel: [0.065786] acpi PNP0A03:00: _OSC failed (AE_SUPPORT); disabling ASPM Jul 3 17:31:51 mythfe2 kernel: [1.520433] ACPI: \_SB_.PCI0.IXVE.IGPU: failed to evaluate _DSM Jul 3 17:31:51 mythfe2 kernel: [2.072087] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 17:31:51 mythfe2 kernel: [2.940072] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 21:15:51 mythfe2 kernel: [0.065793] acpi PNP0A03:00: _OSC failed (AE_SUPPORT); disabling ASPM Jul 3 21:15:51 mythfe2 kernel: [1.514930] ACPI: \_SB_.PCI0.IXVE.IGPU: failed to evaluate _DSM Jul 3 21:15:51 mythfe2 kernel: [2.096048] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 21:15:51 mythfe2 kernel: [2.956042] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 21:23:11 mythfe2 kernel: [0.065698] acpi PNP0A03:00: _OSC failed (AE_SUPPORT); disabling ASPM Jul 3 21:23:11 mythfe2 kernel: [1.508642] ACPI: \_SB_.PCI0.IXVE.IGPU: failed to evaluate _DSM Jul 3 21:23:11 mythfe2 kernel: [2.167987] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 21:23:11 mythfe2 kernel: [2.975948] ata2.00: failed command: IDENTIFY PACKET DEVICE Jul 3 23:22:38 mythfe2 kernel: [0.062144] acpi PNP0A03:00: _OSC failed (AE_SUPPORT); disabling ASPM Jul 3 23:22:38 mythfe2 kernel: [1.504871] ACPI: \_SB_.PCI0.IXVE.IGPU: failed to evaluate _DSM ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wes1410 F pulseaudio /dev/snd/controlC1: wes1410 F pulseaudio CurrentDesktop: XFCE Date: Wed Jul 4 09:35:14 2018 HibernationDevice: RESUME=UUID=24a36ad2-b58c-4870-87e8-2d33e9889c43 InstallationDate: Installed on 2018-05-02 (62 days ago) InstallationMedia: Mythbuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) IwConfig: enp6s0no wireless extensions. lono wireless extensions. MachineType: ECS GeForce 8000 series ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=359009ee-bb5e-4def-b7e5-0475dde40840 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-05-06 (58 days ago) dmi.bios.date: 05/12/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.name: GeForce 8000 series dmi.board.vendor: ECS dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: ECS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/12/2010:svnECS:pnGeForce8000series:pvr1.0:rvnECS:rnGeForce8000series:rvr1.0:cvnECS:ct3:cvr: dmi.product.name: GeForce 8000 series dmi.product.version: 1.0 dmi.sys.vendor: ECS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- Yo
[Bug 1778569] Re: vlc liblirc-client0 depends breaks kernel lirc
OK, I changed one key code and then issued this command; root@mythfe0:/home/wes# ir-keytable -c -w /etc/rc_keymaps/myremotes Then tested that it worked like this] root@mythfe0:/home/wes# ir-keytable -t Testing events. Please, press CTRL-C to abort. 555.460958: event type EV_MSC(0x04): scancode = 0x28 555.460958: event type EV_KEY(0x01) key_down: KEY_SEMICOLON(0x0027) 555.460958: event type EV_SYN(0x00). ;555.566930: event type EV_MSC(0x04): scancode = 0x28 555.566930: event type EV_SYN(0x00). 555.836028: event type EV_KEY(0x01) key_up: KEY_SEMICOLON(0x0027) 555.836028: event type EV_SYN(0x00). Then tried it in notes clipboard and it didn't work. Then rebooted and it worked. So I guess it takes a reboot, meaning the ir-keytable -c -w /etc/rc_keymaps/myremotes command doesn't fully support all changes that need to happen for the rc keymap file to work right in other apps. BTW, this was all with vlc installed along with liblirc-client0. With them removed, the changes worked without a reboot iirc. Might want to close this out. I don't know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778569 Title: vlc liblirc-client0 depends breaks kernel lirc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1778569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778569] Re: vlc liblirc-client0 depends breaks kernel lirc
having got ir-keytable the way I want it and all key codes working with vlc and liblic-client0 removed, I then reinstalled vlc and all the key codes still worked, even after a reboot. So now I'm guessing that liblirc-client0 prevents proper setup of the key codes if it is installed, but after it's already been setup, it has no effect on them. Maybe someone else can figure out what is going on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778569 Title: vlc liblirc-client0 depends breaks kernel lirc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1778569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778569] Re: vlc liblirc-client0 depends breaks kernel lirc
** Description changed: - Subject pretty says it all. Installing vlc also installs liblirc- + Subject pretty much says it all. Installing vlc also installs liblirc- client0. This hoses up kernel lirc by not allowing some key codes to be - passed to apps. ir-table -t shows it is working fine. Removing liblirc- - client0 fixes the problem but also removes vlc. + passed to apps. ir-keytable -t shows it is working fine. Removing + liblirc-client0 fixes the problem but also removes vlc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778569 Title: vlc liblirc-client0 depends breaks kernel lirc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/1778569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778569] [NEW] vlc liblirc-client0 depends breaks kernel lirc
Public bug reported: Subject pretty says it all. Installing vlc also installs liblirc- client0. This hoses up kernel lirc by not allowing some key codes to be passed to apps. ir-table -t shows it is working fine. Removing liblirc- client0 fixes the problem but also removes vlc. ** Affects: vlc (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/1778569 Title: vlc liblirc-client0 depends breaks kernel lirc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1778569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
I compiled (from a make oldconfig) 4.13.16 w/ CONFIG_RCU_NOCB_CPU=y and rcu_nocbs=0-15 as a boot parameter. I've been almost 60 hours, which is a first since buying this machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
These symptoms definitely still happen to me on 18.04 w/ 4.15.0-22-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04
> A simple "apt install ifupdown" will not undo everything that installer has done to setup the system, nor redo it for the alternative networking management tool. Where do you expect ifupdown configs to materialize from? Well that's kind of my point - your documentation is deficient around that. And we expect the ifupdown configuration to 'materialize' from the sysadmin writing them, that's the point of ifupdown isn't it? I'd wager that anyone reverting to ifupdown is doing so specifically because they don't want something managing configuration for them - they want to do it themselves. > Given that the system is sensitive to all configs present on disk. This is > similar situation to how on the desktop one cannot simply "remove > network-manager & install ifupdown" to switch to ifupdown. That's why we tried disabling systemd-networkd, which came back as enabled on subsequent boots. Apparently netplan adds some hooks that aren't clearly documented (at least when I looked on netplan.io, maybe I missed them?). I guess netplan needs to be actively purged, but that breaks the dep on it in ubuntu-minimal which may not be desirable to purge if its dep list changes in the future and people want to pull in those deps (apart from netplan). > can you please give the examples that you have experienced, specifically? the > ubuntu developers have gone extensive amount of porting, and integration > testing to ensure that as many things as possible are fixed to work, both on > new installs and upgrades. We run gateways and firewalls with multiple providers and so forth. The need for pre-up, and more importantly post-up, comes up frequently in all sorts of situations. 'We need to (re)start openvpn after this vlan interface is configured, but both need to happen only after this pppoe interface is (re)configured' (yeah some of our ISPs still use ppp.. even on fibre links. it's terrible). This is why systemd-networkd implements such a facility, and why ifupdown does too. I feel it's near-sighted of netplan to pretend the need doesn't exist when the things it's configuring do see the need and do implement such facilities. If Ubuntu devs tested netplan extensively' I'd wager they never tested beyond basic use cases otherwise the deficiency would have been obvious. There are other, complex configurations out in the wild and netplan can't even begin to accommodate them in its current form. Which is fine... we remove it. But removing it appears to be problematic, or not permanent. So what's the correct method? Remove the initial config the installer makes? Does that let systemd-networkd remain disabled or does it get re-enabled anyway? Can you put this somewhere in the documentation and /etc/network/interfaces comments beyond the mere 'apt install ifupdown' that is there currently? As a side note we found an issue yesterday where DHCP via systemd-networkd in 18.04 wasn't working against an isc-dhcpd running on an early ubuntu version. The apparent inability to prevent systemd-networkd from trying to run and conflicting with other mechanisms was causing enough grief for my employer to decide to just give 18.04 a miss entirely. :( I could have put more time in to diagnosing it, or testing netplan with no config and purging the previous config from systemd-networkd and rebooting and hoping networkd didn't come back but it had already cost enough time by then and he made the call. > Please provide the contents of /etc/netplan on the affected systems, and > please let me know, if removing files in said directory makes networkd ignore > interfaces. I'll test this when I have a spare minute and report back soon Thanks, Wes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771236 Title: forced use of systemd-networkd interferes with ifupdown in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1771236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04
** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771236 Title: forced use of systemd-networkd interferes with ifupdown in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04
There are plenty of examples, some of them bespoke 3rd party things. An equally large issue though are legacy technicians who aren't familiar with systemd's way of doing things yet (I've been trying to get them up to speed though). But the crux is if returning to ifupdown is offered as an option, then it needs to work as expected. If there's more to reverting to the old way than merely 'apt install ifupdown' then the documentation and config file comments referring to this needs to be updated to outline these steps. If a sysadmin disables systemd-networkd, it should stay disabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771236 Title: forced use of systemd-networkd interferes with ifupdown in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771393] Re: 18.04 Server "Whole Disk" option does not allow LVM
Actually, it appears this installer variant won't install to LVM at all, even if you precreate the LV. ** Package changed: debian-installer (Ubuntu) => subiquity ** Changed in: subiquity Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771393 Title: 18.04 Server "Whole Disk" option does not allow LVM To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1771393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771393] [NEW] 18.04 Server "Whole Disk" option does not allow LVM
Public bug reported:
This is a feature request/WISHLIST item.
It's pretty common (at least here) for us to format VM images with full-
disk ("whole disk") LVM. Normally we have to drop to a shell and
preconfigure that beforehand so I was super excited to see the new
"Whole Disk" option in the new-style installer.
However, it doesn't have "LVM Physical Partition" as an option. I'm
genuinely puzzled by this because I would think it's an extremely common
pattern. I must be wrong.
We would really appreciate it if the default installer supported whole-
disk LVM physical partition. Also, considering how different the
interface is, this might not even be a d-i request any more but it seems
likely.
To clarify, this is the installer equivalent of a 'pvcreate /dev/sdb',
whereas the current workflow only supports a 'pvcreate /dev/sdb1'.
Using full disk LVM PV's makes expansion of disk (either iSCSI, VMDK,
etc) trivial.
** Affects: debian-installer (Ubuntu)
Importance: Undecided
Status: Confirmed
** Attachment added: "Screenshot_20180515_125208.png"
https://bugs.launchpad.net/bugs/1771393/+attachment/5139889/+files/Screenshot_20180515_125208.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771393
Title:
18.04 Server "Whole Disk" option does not allow LVM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1771393/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771236] Re: forced use of systemd-networkd interferes with ifupdown in 18.04
Well I think it pertains to ubuntu's architecture in general not just systemd but whatever. ** Package changed: ubuntu => systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771236 Title: forced use of systemd-networkd interferes with ifupdown in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771236] [NEW] forced use of systemd-networkd interferes with ifupdown in 18.04
Public bug reported: For several reasons, we are not able to use netplan nor systemd-networkd due to legacy applications that expect ifupdown's pre-up and post-up script mechanism. The documentation around 18.04's (premature, I feel) wholesale adoption of netplan claims that one can revert to old behaviour by merely installing ifupdown (amongst assertions that netplan will never offer a mechanism for configuring pre-up and post-up actions even for network managers that support them). However when ifupdown is installed, systemd-networkd still tries to manage interfaces. If you 'systemctl disable systemd-networkd', upon next reboot it is automatically re-enabled. We tried disabling any systemd units even remotely related to networking and yet systemd- networkd still runs. If it hasn't been configured, it tries to DHCP. On networks that don't provide DHCP this results in a stupendously long stall during boot. Currently it appears to be impossible to tell systemd-networkd not to run in a clean manner that won't get reverted on package upgrades. I sincerely hope this is is a bug/oversight and not intentional. We need to be able to disable systemd-networkd properly. Thanks ** Affects: ubuntu Importance: Undecided Status: New ** Summary changed: - forced use of systemd-networkd interferes with ifupdown + forced use of systemd-networkd interferes with ifupdown 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/1771236 Title: forced use of systemd-networkd interferes with ifupdown in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1771236/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1290310] Re: nautilus does not start
After trying to start Nautilus from Unity and failing, I tried invoking it from the terminal. $ nautilus . (nautilus:20662): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed (nautilus:20662): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed Could not register the application: Timeout was reached (nautilus:20662): Gtk-CRITICAL **: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed (nautilus:20662): GLib-GObject-WARNING **: invalid (NULL) pointer instance (nautilus:20662): GLib-GObject-CRITICAL **: g_signal_connect_object: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290310 Title: nautilus does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1290310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713995] [NEW] Grub will not install
Public bug reported: have disabled secure boot, removed bitlocker and reformatted drive. Also, removed Windows 10 hibernation ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.4 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 Date: Wed Aug 30 07:04:21 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.4 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713995 Title: Grub will not install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1713995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713890] [NEW] Unable to GRUB in /dev/sda during initial installation
Public bug reported: During initial installation buntu 16.04.3 on Dell Inspiron 3000 Unable to install GRUB in /dev/sda Executing 'grub-install /dev/sda' failed. This is a fatal error. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.4 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 Date: Tue Aug 29 21:03:43 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.4 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713890 Title: Unable to GRUB in /dev/sda during initial installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1713890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703840] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: Just said I needed to report a bug on reboot. I had just tried to run Synaptic to install Skype and it said that it coulldn't run because apt- get or apt something was already running. Of course no button to end the conflicting process, no help to find it, etc. Not a very helpful system. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.4 AptOrdering: gconf2-common:amd64: Install libgconf-2-4:amd64: Install gconf-service-backend:amd64: Install gconf-service:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Wed Jul 12 09:37:20 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-22 (19 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703840 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1703840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673583] Re: dar_split not included in package.
Hans, Thank you for following up! Best, Wes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673583 Title: dar_split not included in package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dar/+bug/1673583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673583] Re: dar_split not included in package.
Further investigation: looks like it's as simple as a missing rule in ~/debian/dar.install for usr/bin/dar_split. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1673583 Title: dar_split not included in package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dar/+bug/1673583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1673583] [NEW] dar_split not included in package.
Public bug reported: Neither the Ubuntu version (any release, it appears) nor the Debian packages have dar_split in the package. https://packages.debian.org/search?searchon=contents=dar_split=exactfilename=unstable=any Using 16.04/AMD64 w/ ii dar 2.5.3-1ubuntu1 amd64Disk ARchive: Backup directory tree and files ** Affects: dar (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/1673583 Title: dar_split not included in package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dar/+bug/1673583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1542262] [NEW] npm not installable from backport PPA
Public bug reported: Because of the dependency "node-ansi (>= 0.3.0-2)", you cannot backport npm to a PPA for trusty et al, as the ppa prefix is incompatible with the depends: The following packages have unmet dependencies: npm : Depends: node-ansi (>= 0.3.0-2) but 0.3.0-2~ubuntu14.04.1~ppa1 is to be installed This needs ideally to be "node-ansi (>= 0.3.0-2~)" to allow backport packages as well. ** Affects: npm (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/1542262 Title: npm not installable from backport PPA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/npm/+bug/1542262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307445] Re: openstack: instances with multiple nics on the same network don't have deterministic private-addresses
** Changed in: juju-core Milestone: None = 1.25.0 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1307445 Title: openstack: instances with multiple nics on the same network don't have deterministic private-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307445/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1307445] Re: openstack: instances with multiple nics on the same network don't have deterministic private-addresses
** Changed in: juju-core Milestone: None = 1.25.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307445 Title: openstack: instances with multiple nics on the same network don't have deterministic private-addresses To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1466130] Re: Intel Graphics 5500
HP Pavillion 15-P214DX Notebook intel core i7-5500U CPU @ 2.40 GHz 6.00GB 64-bit Operating System, x64-based processor On Thu, Jun 25, 2015 at 7:48 AM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Wes, thank you for reporting this and helping make Ubuntu better. Could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)? ** Tags added: needs-full-computer-model ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1466130 Title: Intel Graphics 5500 Status in xorg package in Ubuntu: Incomplete Bug description: There are missing letters, some of the background display is black, etc. Everything only works properly when I resume boot from the recovery mode. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jun 17 11:19:56 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2293] InstallationDate: Installed on 2015-06-16 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-41-generic.efi.signed root=UUID=5adf5fb3-6806-4214-bfcc-610afee5d200 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2293 dmi.board.vendor: Hewlett-Packard dmi.board.version: 78.21 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd02/02/2015:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr0971120002405F1620180:rvnHewlett-Packard:rn2293:rvr78.21:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 0971120002405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jun 17 11:18:34 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1466130/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466130 Title: Intel Graphics 5500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1466130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466130] [NEW] Intel Graphics 5500
Public bug reported: There are missing letters, some of the background display is black, etc. Everything only works properly when I resume boot from the recovery mode. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-41.55~14.04.1-generic 3.16.7-ckt11 Uname: Linux 3.16.0-41-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jun 17 11:19:56 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2293] InstallationDate: Installed on 2015-06-16 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-41-generic.efi.signed root=UUID=5adf5fb3-6806-4214-bfcc-610afee5d200 ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2293 dmi.board.vendor: Hewlett-Packard dmi.board.version: 78.21 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd02/02/2015:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr0971120002405F1620180:rvnHewlett-Packard:rn2293:rvr78.21:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 0971120002405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jun 17 11:18:34 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466130 Title: Intel Graphics 5500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1466130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422892] [NEW] Exception for Juju 1.23 (systemd)
Public bug reported: We would like to create an exception to allow for Juju 1.23 to be included in the package which would provide support for systemd. Our intent is to land on 23 Mar with systemd features. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: update-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422892 Title: Exception for Juju 1.23 (systemd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1422892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422892] [NEW] Exception for Juju 1.23 (systemd)
Public bug reported: We would like to create an exception to allow for Juju 1.23 to be included in the package which would provide support for systemd. Our intent is to land on 23 Mar with systemd features. ** Affects: juju-core (Ubuntu) Importance: Undecided Status: New ** Tags: update-software-version -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1422892 Title: Exception for Juju 1.23 (systemd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1422892/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1350432] Re: Changelogs fail to download (403)
I also needed to add NEWS\.Debian to VfilePattern to get ubuntu changelogs to download. VfilePattern = (^|.*/)(Index|Packages(\.gz|\.bz2|\.lzma|\.xz)?|NEWS\.Debian|InRelease|Release|Release\.gpg |Sources(\.gz|\.bz2|\.lzma|\.xz)?|release|index\.db-.*\.gz|Contents-[^/]*(\.gz|\.bz2|\.lzma|\.xz)?|pkglist [^/]*\.bz2|rclist[^/]*\.bz2|meta-release[^/]*|Translation[^/]*(\.gz|\.bz2|\.lzma|\.xz)?|MD5SUMS|SHA1SUMS|( (setup|setup-legacy)(\.ini|\.bz2|\.hint)(\.sig)?)|mirrors\.lst|repo(index|md)\.xml(\.asc|\.key)?|directory \.yast|products|content(\.asc|\.key)?|media|filelists\.xml\.gz|filelists\.sqlite\.bz2|repomd\.xml|packages \.[a-zA-Z][a-zA-Z]\.gz|info\.txt|license\.tar\.gz|license\.zip|.*\.(db|files|abs)(\.tar(\.gz|\.bz2|\.lzma| \.xz))?|metalink\?repo|.*prestodelta\.xml\.gz|repodata/.*\.(xml|sqlite)(\.gz|\.bz2|\.lzma|\.xz))$|/dists/. */installer-[^/]+/[^0-9][^/]+/images/.* # PfilePattern = .*(\.d?deb|\.rpm|\.drpm|\.dsc|\.tar(\.gz|\.bz2|\.lzma|\.xz)(\.gpg)?|\.diff(\.gz|\.bz2|\.l zma|\.xz)|\.jigdo|\.template|changelog|copyright|\.udeb|\.debdelta|\.diff/.*\.gz|(Devel)?ReleaseAnnounceme nt(\?.*)?|[a-f0-9]+-(susedata|updateinfo|primary|deltainfo).xml.gz|fonts/(final/)?[a-z]+32.exe(\?download. *)?|/dists/.*/installer-[^/]+/[0-9][^/]+/images/.*)$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1350432 Title: Changelogs fail to download (403) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1350432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1350432] [NEW] Changelogs fail to download (403)
Public bug reported: Bug: Changelogs fail to download in update-manager with apt-cacher-ng in the default configuration. Solutions: 1. Enable ForwardBtSoap in /etc/apt-cacher-ng/acng.conf and cross fingers # Experimental feature for apt-listbugs: pass-through SOAP requests and # responses to/from bugs.debian.org. If not set, default is true if # ForceManaged is enabled and false otherwise. #ForwardBtsSoap: 0 ForwardBtsSoap: 1 2. Remap and update PassThroughPattern ## docker Remap-docker: get.docker.io ; https://get.docker.io #PassThroughPattern: get\.docker\.io:443$ ## changelogs Remap-changelogs: changelogs.ubuntu.com ; http://changelogs.ubuntu.com #PassThroughPattern: changelogs\.ubuntu\.com$ ## passthrough PassThroughPattern: (get\.docker\.io:443|changelogs\.ubuntu\.com)$ It may be helpful to add Remap-changelogs and PassThroughPattern to the default Ubuntu configuration with instructions for how to add an additional pattern (e.g. get.docker.io:443). ** Affects: apt-cacher-ng (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/1350432 Title: Changelogs fail to download (403) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1350432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1340923] Re: virtualbox-guest-dkms 4.3.12-dfsg-1: virtualbox-guest kernel module failed to build
Encountered this this morning when installing a fresh install of 14.10 in Virtualbox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1340923 Title: virtualbox-guest-dkms 4.3.12-dfsg-1: virtualbox-guest kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1340923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1281250] Re: VNC accessible from non-linux machines only with encryption disabled
FYI Solution for Android users - use bVNC Free It accepts this encryption type -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1281250 Title: VNC accessible from non-linux machines only with encryption disabled To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/1281250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
