[Bug 2069529] [NEW] Shotwell doesn't switch to dark mode
Public bug reported: After an upgrade of Ubuntu & Shotwell I am stuck in light mode. Trying to set dark mode either in Shotwell or in Gnome settings doesn't change the fact that it stays in light mode. ** Affects: shotwell (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/2069529 Title: Shotwell doesn't switch to dark mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/2069529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069529] Re: Shotwell doesn't switch to dark mode
❯ dpkg -l gnome-settings-daemon Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-=-=--== ii gnome-settings-daemon 46.0-1ubuntu1 amd64daemon handling the GNOME session settings ❯ dpkg -l shotwell* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===-===--== ii shotwell0.32.6-1ubuntu1 amd64digital photo organizer ii shotwell-common 0.32.6-1ubuntu1 all digital photo organizer - common files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069529 Title: Shotwell doesn't switch to dark mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/2069529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058228] [NEW] mkbootimg : ModuleNotFoundError: No module named 'gki'
Public bug reported: ``` Traceback (most recent call last): File "/usr/bin/mkbootimg", line 31, in from gki.generate_gki_certificate import generate_gki_certificate ModuleNotFoundError: No module named 'gki' ``` on Ubuntu Noble : ``` apt policy mkbootimg mkbootimg: Installed: 1:33.0.3-2 Candidate: 1:33.0.3-2 Version table: *** 1:33.0.3-2 500 500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu noble/universe i386 Packages 100 /var/lib/dpkg/status ``` Looks similar to https://github.com/nmeum/android-tools/issues/76 ** Affects: android-platform-tools (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/2058228 Title: mkbootimg : ModuleNotFoundError: No module named 'gki' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-platform-tools/+bug/2058228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1953613] Re: GPIO character device v1 API not enabled in kernel
Sorry but I no longer have access to the affected machine, so I cannot test the proposed fix. - Arthur On Fri, 1 Mar 2024 at 07:26, Ubuntu Kernel Bot <1953...@bugs.launchpad.net> wrote: > This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 > kernel in -proposed solves the problem. Please test the kernel and > update this bug with the results. If the problem is solved, change the > tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy- > linux-mtk'. If the problem still exists, change the tag 'verification- > needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'. > > > If verification is not done by 5 working days from today, this fix will > be dropped from the source code, and this bug will be closed. > > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how > to enable and use -proposed. Thank you! > > > ** Tags added: kernel-spammed-jammy-linux-mtk-v2 > verification-needed-jammy-linux-mtk > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1953613 > > Title: > GPIO character device v1 API not enabled in kernel > > Status in linux package in Ubuntu: > Fix Released > Status in linux-allwinner-5.17 package in Ubuntu: > Invalid > Status in linux-hwe-5.17 package in Ubuntu: > Invalid > Status in linux-starfive-5.17 package in Ubuntu: > Invalid > Status in linux source package in Jammy: > Fix Released > Status in linux-allwinner-5.17 source package in Jammy: > Fix Released > Status in linux-hwe-5.17 source package in Jammy: > Fix Committed > Status in linux-starfive-5.17 source package in Jammy: > Fix Released > > Bug description: > [Impact] > >* The libgpiod2 library and gpiod tools shipped in Jammy don't work. > >* These tools are meant to replace the old sysfs interface and be > a better and more efficient way to manipulate GPIOs from userspace. > Unfortunately the latest release is still using v1 of the character > device kernel API which is not enabled in Ubuntu kernels. > >* This is Kent Gibsons reply on the linux-gpio mailing list: > > On Tue, Jul 12, 2022 at 09:48:45AM +0200, Alexandre Ghiti wrote: > > Hi, > > > > Ubuntu kernels do not enable GPIO_CDEV_V1 as it is deprecated, but the > > libgpiod package that we ship is still based on the latest version > > 1.6.3 which does not implement the API v2. So I'd like to update > > libgpiod, do you have any recommendations about what branch/sha1 I > > should use? Do you plan to make a release that implements the API v2? > > > > Firstly, libgpiod is Bart's library so he is the authority, but this > is my understanding... > > TLDR: You should keep GPIO_CDEV_V1 enabled. > > v1 is deprecated from a development perspective, so all new feature > development will occur on v2, and new applications should target v2. > Existing apps targetting v1, be that directly or via libgpiod v1.6.3, > will require GPIO_CDEV_V1 until they migrate to v2. > The mainline kernel will continue to support v1 while userspace > transitions. > > libgpiod v2 is in active development, and should reach its first release > shortly. > Note that it is NOT a plugin replacement for v1. It has a different API, > for similar reasons to why we had to switch in the kernel, so apps will > need to be actively migrated. > > I wouldn't suggest making any effort to package libgpiod v2 until Bart > makes an official release. > > Cheers, > Kent. > > [Test Plan] > >* Run gpioinfo on a machine with exposed GPIOs and check that it lists > the GPIOs and doesn't error with > > gpioinfo: error creating line iterator: Invalid argument > > [Where problems could occur] > >* There may be code and scripts that hasn't been tested with a working > libgpiod2/gpiod tools and uncover latent bugs. > > [Other Info] > > Original bug text: > > The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) > use version 1 of the GPIO character device API. However, they cannot > work because the interface is disabled in the default kernel (tested > with 5.13.19). After rebuilding the kernel with the option > CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. > > Thanks to Marek Szuba, who reported the same bug for Gentoo > (https://bugs.gentoo.org/807334), pointing me in the right direction. > > What I expect to happen: > > $ gpiodetect > gpiochip0 [0-003c] (8 lines) > $ gpioinfo > gpiochip0 - 8 lines: >line 0: unnamed
[Bug 1937110] Re: dhcp option 121 & 249
Funny thing is that the rfc 3442 is from 2002. Thats what makes me wonder of the missing support till today... My workarround till today is to unzip the iso -> kernel+initrd, patch the initrd, and use the patched initrd. I would not recommend anyone to do it like that, only if theres no other options.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937110 Title: dhcp option 121 & 249 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968550] Re: unattended updates, missing routes
happened on jammy ** Changed in: frr (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/1968550 Title: unattended updates, missing routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/frr/+bug/1968550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968550] [NEW] unattended updates, missing routes
Public bug reported: Hello, It happened now twice for me that after a "unattended update" the linux kernel is missing routes which were announced via BGP. From my point of view, the problem is that networkd is restarted(?). Which leads to a deletion of the routes in linux kernel. # cat /var/log/unattended-upgrades/unattended-upgrades.log | grep "upgraded:" 2022-04-08 06:45:58,859 INFO Packages that will be upgraded: cloud-init dpkg libarchive13 liblzma5 libudisks2-0 libutempter0 linux-generic linux-headers-generic linux-image-generic patch tmux udisks2 update-notifier-common xz-utils 2022-04-09 06:11:51,294 INFO Packages that will be upgraded: libboost-iostreams1.74.0 libboost-thread1.74.0 libudisks2-0 libx11-6 libx11-data libx11-dev libx11-xcb1 ltrace python3-distutils python3-gdbm python3-lib2to3 udisks2 update-notifier-common 2022-04-10 06:09:12,653 INFO Packages that will be upgraded: gzip liblzma5 libnss-mymachines libnss-systemd libpam-systemd libsystemd0 libudev1 systemd systemd-container systemd-sysv systemd-timesyncd udev update-notifier-common xz-utils 2022-04-11 06:26:31,366 INFO Packages that will be upgraded: libjpeg8 update-notifier-common # systemctl status frr ● frr.service - FRRouting Loaded: loaded (/lib/systemd/system/frr.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2022-04-08 02:00:16 UTC; 3 days ago # systemctl status systemd-networkd.service ● systemd-networkd.service - Network Configuration Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2022-04-10 06:09:17 UTC; 1 day 3h ago # vtysh -c "show ip route" | grep "B>" B>* 10.3.0.0/16 [20/0] via 172.25.84.114, wg-1-dc-003, weight 1, 3d08h05m B>* 10.4.0.0/16 [20/0] via 172.25.84.122, wg-1-dc-004, weight 1, 1d15h36m B>* 172.20.0.0/16 [20/0] via 10.0.240.129, wg-1-int, weight 1, 3d08h05m # ip route | grep /16 10.1.0.0/16 dev ethGeoInternal proto kernel scope link src 10.1.254.253 As you can see 10.3.0.0/16 and 10.4.0.0/16 is missing in "ip route" ** Affects: frr (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/1968550 Title: unattended updates, missing routes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/frr/+bug/1968550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
A lot of trouble, traced it down. So basicly the fix is working. The reason was an 'old' not restarted daemon on another host. Very confusing is that even an old daemon can break itself (which is expected) AND the CLI tools on another host. Which was not expected by me and confused me hardly. Sorry for the report confusing. Thanks for solving it. Finally closed. ** Changed in: ceph (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964322 Title: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1964322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
hey @chris.macnaughton, Yes i restarted all daemons, rebooted even the whole machine. As you can see in my console logs above. Having a cluster of +10 nodes, tried it on multiple hosts. It was working at some point, but now it seems fully broken again. Which is.. weird. The mgr-daemons are broken (especially this "balancer module" for example) and the CLI tools like "ceph crash ls" / "ceph telemtry status". Wondering where this "not deterministic" factor is coming from. Some dynamic loading of python..? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964322 Title: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1964322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
even after reboot / restart.. under random circumstances this bug comes back. ~ # dpkg -l | grep ceph ii ceph-base 17.1.0-0ubuntu3 amd64common ceph daemon libraries and management tools ii ceph-common 17.1.0-0ubuntu3 amd64common utilities to mount and interact with a ceph storage cluster ii ceph-mds 17.1.0-0ubuntu3 amd64metadata server for the ceph distributed file system ii ceph-mgr 17.1.0-0ubuntu3 amd64manager for the ceph distributed file system ii ceph-mgr-modules-core 17.1.0-0ubuntu3 all ceph manager modules which are always enabled ii ceph-mon 17.1.0-0ubuntu3 amd64monitor server for the ceph storage system ii ceph-osd 17.1.0-0ubuntu3 amd64OSD server for the ceph storage system ii ceph-volume 17.1.0-0ubuntu3 all tool to facilidate OSD deployment ii libcephfs217.1.0-0ubuntu3 amd64Ceph distributed file system client library ii libsqlite3-mod-ceph 17.1.0-0ubuntu3 amd64SQLite3 VFS for Ceph ii python3-ceph-argparse 17.1.0-0ubuntu3 amd64Python 3 utility libraries for Ceph CLI ii python3-ceph-common 17.1.0-0ubuntu3 all Python 3 utility libraries for Ceph ii python3-cephfs17.1.0-0ubuntu3 amd64Python 3 libraries for the Ceph libcephfs library ~ # uptime 20:55:23 up 52 min, 2 users, load average: 0.04, 0.13, 0.22 ~ # ceph crash ls Error EINVAL: SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats ~ # ceph telemetry status Error EINVAL: SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats any idea? ** Changed in: ceph (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964322 Title: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1964322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
Uhm, interesting.. its maybe still fixed. But it needs a reconnect of ssh/reboot after installing the new packages.. ** Changed in: ceph (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964322 Title: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1964322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
~ # dpkg -l | grep ceph ii ceph-base 17.1.0-0ubuntu3 amd64common ceph daemon libraries and management tools ii ceph-common 17.1.0-0ubuntu3 amd64common utilities to mount and interact with a ceph storage cluster ii ceph-mds 17.1.0-0ubuntu3 amd64metadata server for the ceph distributed file system ii ceph-mgr 17.1.0-0ubuntu3 amd64manager for the ceph distributed file system ii ceph-mgr-modules-core 17.1.0-0ubuntu3 all ceph manager modules which are always enabled ii ceph-mon 17.1.0-0ubuntu3 amd64monitor server for the ceph storage system ii ceph-osd 17.1.0-0ubuntu3 amd64OSD server for the ceph storage system ii ceph-volume 17.1.0-0ubuntu3 all tool to facilidate OSD deployment ii libcephfs217.1.0-0ubuntu3 amd64Ceph distributed file system client library ii libsqlite3-mod-ceph 17.1.0-0ubuntu3 amd64SQLite3 VFS for Ceph ii python3-ceph-argparse 17.1.0-0ubuntu3 amd64Python 3 utility libraries for Ceph CLI ii python3-ceph-common 17.1.0-0ubuntu3 all Python 3 utility libraries for Ceph ii python3-cephfs17.1.0-0ubuntu3 amd64Python 3 libraries for the Ceph libcephfs library ~ # ceph telemetry status Error EINVAL: SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats Fix doesnt work ** Changed in: ceph (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964322 Title: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1964322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
thanks @james-page, any ETA for the fix beeing on the apt mirros? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964322 Title: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1964322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
# ceph telemetry status Error EINVAL: SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964322 Title: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1964322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964322] Re: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
Module 'balancer' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats is affected as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964322 Title: Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1964322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964322] [NEW] Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
Public bug reported: #ceph -s ... health: HEALTH_ERR Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats .. # dpkg -l | grep ceph ii ceph-base 17.1.0-0ubuntu1 amd64common ceph daemon libraries and management tools ii ceph-common 17.1.0-0ubuntu1 amd64common utilities to mount and interact with a ceph storage cluster ii ceph-mds 17.1.0-0ubuntu1 amd64metadata server for the ceph distributed file system ii ceph-mgr 17.1.0-0ubuntu1 amd64manager for the ceph distributed file system ii ceph-mgr-modules-core 17.1.0-0ubuntu1 all ceph manager modules which are always enabled ii ceph-mon 17.1.0-0ubuntu1 amd64monitor server for the ceph storage system ii ceph-osd 17.1.0-0ubuntu1 amd64OSD server for the ceph storage system ii ceph-volume 17.1.0-0ubuntu1 all tool to facilidate OSD deployment ii libcephfs217.1.0-0ubuntu1 amd64Ceph distributed file system client library ii libsqlite3-mod-ceph 17.1.0-0ubuntu1 amd64SQLite3 VFS for Ceph ii python3-ceph-argparse 17.1.0-0ubuntu1 amd64Python 3 utility libraries for Ceph CLI ii python3-ceph-common 17.1.0-0ubuntu1 all Python 3 utility libraries for Ceph ii python3-cephfs17.1.0-0ubuntu1 amd64Python 3 libraries for the Ceph libcephfs library # ls -alh /usr/bin/python3 lrwxrwxrwx 1 root root 10 Jan 13 16:58 /usr/bin/python3 -> python3.10 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 Codename: jammy 2022-03-08T17:58:18.807+ 7f7734ff9640 -1 Traceback (most recent call last): File "/usr/share/ceph/mgr/devicehealth/module.py", line 338, in serve if self.db_ready() and self.enable_monitoring: File "/usr/share/ceph/mgr/mgr_module.py", line 1189, in db_ready return self.db is not None File "/usr/share/ceph/mgr/mgr_module.py", line 1201, in db self._db = self.open_db() File "/usr/share/ceph/mgr/mgr_module.py", line 1178, in open_db self.create_mgr_pool() File "/usr/share/ceph/mgr/mgr_module.py", line 1084, in create_mgr_pool self.rename_pool(devhealth, self.MGR_POOL_NAME) File "/usr/share/ceph/mgr/mgr_module.py", line 1048, in rename_pool self.check_mon_command(c) File "/usr/share/ceph/mgr/mgr_module.py", line 1560, in check_mon_command r = HandleCommandResult(*self.mon_command(cmd_dict, inbuf)) File "/usr/share/ceph/mgr/mgr_module.py", line 1577, in mon_command self.send_command(result, "mon", "", json.dumps(cmd_dict), "", inbuf) File "/usr/share/ceph/mgr/mgr_module.py", line 1641, in send_command self._ceph_send_command(result, svc_type, svc_id, command, tag, inbuf) SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats maybe bug fix here: https://github.com/ceph/ceph/pull/44112 ** Affects: ceph (Ubuntu) Importance: Undecided Status: New ** Description changed: - health: HEALTH_ERR - Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats + #ceph -s + + ... + health: HEALTH_ERR + Module 'devicehealth' has failed: PY_SSIZE_T_CLEAN macro must be defined for '#' formats + .. # dpkg -l | grep ceph ii ceph-base 17.1.0-0ubuntu1 amd64common ceph daemon libraries and management tools ii ceph-common 17.1.0-0ubuntu1 amd64common utilities to mount and interact with a ceph storage cluster ii ceph-mds 17.1.0-0ubuntu1 amd64metadata server for the ceph distributed file system ii ceph-mgr 17.1.0-0ubuntu1 amd64manager for the ceph distributed file system ii ceph-mgr-modules-core 17.1.0-0ubuntu1 all ceph manager modules which are always enabled ii ceph-mon 17.1.0-0ubuntu1 amd64monitor server for the ceph storage system ii ceph-osd 17.1.0-0ubuntu1 amd64OSD server for the ceph storage system ii ceph-volume 17.1.0-0ubuntu1 all tool to facilidate OSD
[Bug 1879976] Re: pads revert to same workspace after loging out and back in
Hi Howard, Would you mind to specify in more detail how the issue can be reproduced? For example - Install Ubuntu 18.0.4 - Install Xpad 5.0 - Create note on workspace 1 - Switch to workspace 2 - ... Also, does the problem happen also with Xpad 5.4 or 5.5? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879976 Title: pads revert to same workspace after loging out and back in To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546278/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. + Thanks to Marek Szuba, who reported the same bug for Gentoo + (https://bugs.gentoo.org/807334), pointing me in the right direction. What I expect to happen: - $ gpiodetect + $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: - line 0: unnamed unused output active-high - line 1: unnamed unused output active-high - line 2: unnamed unused output active-high - line 3: unnamed unused output active-high - line 4: unnamed unused output active-high - line 5: unnamed unused output active-high - line 6: unnamed unused input active-high - line 7: unnamed unused input active-high + line 0: unnamed unused output active-high + line 1: unnamed unused output active-high + line 2: unnamed unused output active-high + line 3: unnamed unused output active-high + line 4: unnamed unused output active-high + line 5: unnamed unused output active-high + line 6: unnamed unused input active-high + line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument - - $ cat /proc/version_signature + $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: - Installed: 1.6.2-1 - Candidate: 1.6.2-1 - Version table: - *** 1.6.2-1 500 - 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.6.2-1 + Candidate: 1.6.2-1 + Version table: + *** 1.6.2-1 500 + 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages + 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) - DeviceName: Onboard - Other - Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller - Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- - Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546275/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546274/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546277/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546273/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546271/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546276/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546268/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546272/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546270/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546269/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546266/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546267/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546264/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546265/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1953613/+attachment/5546263/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] Re: GPIO character device API not enabled in kernel
apport information ** Tags added: apport-collected impish ** Description changed: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/1953613/+attachment/5546262/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953613] [NEW] GPIO character device API not enabled in kernel
Public bug reported: The current versions of gpiod, libgpiod-dev and libgpiod2 (1.6.2-1) use version 1 of the GPIO character device API. However, they cannot work because the interface is disabled in the default kernel (tested with 5.13.19). After rebuilding the kernel with the option CONFIG_GPIO_CDEV_V1=y, the gpiod tools work as expected. What I expect to happen: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpiochip0 - 8 lines: line 0: unnamed unused output active-high line 1: unnamed unused output active-high line 2: unnamed unused output active-high line 3: unnamed unused output active-high line 4: unnamed unused output active-high line 5: unnamed unused output active-high line 6: unnamed unused input active-high line 7: unnamed unused input active-high $ gpioget gpiochip0 0 1 What actually happens: $ gpiodetect gpiochip0 [0-003c] (8 lines) $ gpioinfo gpioinfo: error creating line iterator: Invalid argument $ gpioget gpiochip0 0 gpioget: error reading GPIO values: Invalid argument $ cat /proc/version_signature Ubuntu 5.13.0-22.22-lowlatency 5.13.19 $ apt-cache policy libgpiod2 libgpiod2: Installed: 1.6.2-1 Candidate: 1.6.2-1 Version table: *** 1.6.2-1 500 500 http://de.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 100 /var/lib/dpkg/status I am testing with the onboard PCA9554A on a Fujitsu D3641-S motherboard. $ lspci | grep -i smb 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) $ lspci -s 1f.4 -vvv 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) DeviceName: Onboard - Other Subsystem: Fujitsu Technology Solutions Cannon Lake PCH SMBus Controller Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/1953613 Title: GPIO character device API not enabled in kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943423] Re: mgr crashs in 16.2.5 / clock-skew
sadly it didnt solve the issue.. heres more infos about: https://tracker.ceph.com/issues/23460 sadly i didnt found a solution until now.. ** Bug watch added: tracker.ceph.com/issues #23460 http://tracker.ceph.com/issues/23460 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943423 Title: mgr crashs in 16.2.5 / clock-skew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1943423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943423] Re: mgr crashs in 16.2.5 / clock-skew
added following cron on top of ntpd, to see if this solves the issue: 0 * * * * /usr/sbin/hwclock -w --verbose --update-drift >> /tmp/hwclock.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943423 Title: mgr crashs in 16.2.5 / clock-skew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1943423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943238] Re: memory requirements
latest impish stable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943238 Title: memory requirements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1943238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943729] [NEW] AMD impish Libvirt7.6 nested amd-v, rbd storage broken
Public bug reported: Hello, Having issues with AMD and RBD Driver. Running on latest impish, using libvirt7.6ubuntu1. Having following setup (not sure if matters): Dedicated-Host (AMD) -> Level1-KVM (cpu-pass-through, rbd) -> "Customer- VM"=CVM ubuntu20.04 -> impish -> custom What happens? It seems Level1-KVM is struggeling with RBD storage access, breaking/preventing CVM's operating system to fully boot. Half of the booting process is going through, but later at random point in time (still booting the kernel) it seems to deadlock, letting CVM's CPU spin endless. Following tests setups i verified to isolate the issue: Dedicated-Host (Intel) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, direct storage=virtio) -> CVM = works Dedicated-Host (Intel) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) -> CVM = works Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, direct storage=virtio) -> CVM = works --- Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = stuck Out of those tests, the issue seems to be IMO located in libvirt 7.6, sadly im not able to check it against 7.4 (which was shortly available for impish, but was already removed from the repo mirror..). Any idears what could make an AMD passthrough break access of RBD, letting CVM stuck accessing storage? ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello, - - Having issues with AMD and RBD Driver. Running on latest impish, using libvirt7.6ubuntu1. + Having issues with AMD and RBD Driver. Running on latest impish, using + libvirt7.6ubuntu1. Having following setup (not sure if matters): Dedicated-Host (AMD) -> Level1-KVM (cpu-pass-through, rbd) -> "Customer- VM"=CVM ubuntu20.04 -> impish -> custom What happens? It seems Level1-KVM is struggeling with RBD storage access, breaking/preventing CVM's operating system to fully boot. Half of the booting process is going through, but later at random point in time (still booting the kernel) it seems to deadlock, letting CVM's CPU spin endless. - Following tests setups i verified to isolate the issue: - Dedicated-Host (Intel) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = works - Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, direct storage=virtio) -> CVM = works + Dedicated-Host (Intel) -> Level1-KVM (impish=7.6,cpu-pass-through, + rbd=virtio) -> CVM = works + + Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, direct + storage=virtio) -> CVM = works + Dedicated-Host (Intel) -> Level1-KVM (focal=6.0,cpu-pass-through, rbd=virtio) -> CVM = works - Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = works - Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, direct storage=virtio) -> CVM = works + + Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, + rbd=virtio) -> CVM = works + + Dedicated-Host (AMD) -> Level1-KVM (focal=6.0,cpu-pass-through, direct + storage=virtio) -> CVM = works + + + --- Dedicated-Host (AMD) -> Level1-KVM (impish=7.6,cpu-pass-through, rbd=virtio) -> CVM = stuck - - Out of those tests, the issue seems to be IMO located in libvirt 7.6, sadly im not able to check it against 7.4 (which was shortly available for impish, but was already removed from the repo mirror..). + Out of those tests, the issue seems to be IMO located in libvirt 7.6, + sadly im not able to check it against 7.4 (which was shortly available + for impish, but was already removed from the repo mirror..). Any idears what could make an AMD passthrough break access of RBD, letting CVM stuck accessing storage? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943729 Title: AMD impish Libvirt7.6 nested amd-v, rbd storage broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1943729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943423] Re: mgr crashs in 16.2.5 / clock-skew
Heres are the last lines when the MGR is running, but kicked out of the cluster: 2021-09-14T00:00:42.062+ 7f05361b8640 -1 received signal: Hangup from pkill -1 -x ceph-mon|ceph-mgr|ceph-mds|ceph-osd|ceph-fuse|radosgw|rbd-mirror|cephfs-mirror (PID: 1137578) UID: 0 2021-09-14T00:00:42.530+ 7f0526ffd640 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2021-09-13T23:00:42.534987+) 2021-09-14T00:00:43.530+ 7f0526ffd640 -1 monclient: _check_auth_rotating possible clock skew, rotating keys expired way too early (before 2021-09-13T23:00:43.535155+) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943423 Title: mgr crashs in 16.2.5 / clock-skew To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1943423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943238] Re: memory requirements
Thanks for this hint. But im already using this Parameter in combination with ipxe. Lowering to less then 3 GB brings it sometimes to fail. Doing about 50-100 installs per week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943238 Title: memory requirements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1943238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943423] [NEW] mgr crashs in 16.2.5 / clock-skew
Public bug reported:
Hello,
Running inside an KVM, impish with latest ceph version.
Can at least reproduce it in 3 reinstalled fresh ceph clusters.
Heres the crash info for my mgr's:
ceph crash info
2021-09-12T21:09:22.866793Z_2419107c-082c-457a-b5e6-a376d779b32f
{
"archived": "2021-09-13 07:59:37.681606",
"backtrace": [
"/lib/x86_64-linux-gnu/libc.so.6(+0x46510) [0x7f62e074e510]",
"(std::_Rb_tree_increment(std::_Rb_tree_node_base*)+0x13)
[0x7f62e0af5573]",
"(PGMap::apply_incremental(ceph::common::CephContext*,
PGMap::Incremental const&)+0xb60) [0x5633639f6320]",
"(ClusterState::notify_osdmap(OSDMap const&)+0x29d) [0x563363a89f1d]",
"(Mgr::handle_osd_map()+0x854) [0x563363ae0694]",
"(Mgr::ms_dispatch2(boost::intrusive_ptr const&)+0x568)
[0x563363ae0eb8]",
"(MgrStandby::ms_dispatch2(boost::intrusive_ptr const&)+0xb8)
[0x563363af1118]",
"(Messenger::ms_deliver_dispatch(boost::intrusive_ptr
const&)+0x450) [0x7f62e1101d30]",
"(DispatchQueue::entry()+0x647) [0x7f62e10ff0e7]",
"(DispatchQueue::DispatchThread::entry()+0x11) [0x7f62e11be921]",
"/lib/x86_64-linux-gnu/libc.so.6(+0x988d7) [0x7f62e07a08d7]",
"/lib/x86_64-linux-gnu/libc.so.6(+0x129510) [0x7f62e0831510]"
],
"ceph_version": "16.2.5",
"crash_id":
"2021-09-12T21:09:22.866793Z_2419107c-082c-457a-b5e6-a376d779b32f",
"entity_name": "mgr.ceph-2",
"os_id": "21.10",
"os_name": "Ubuntu Impish Indri (development branch)",
"os_version": "21.10 (Impish Indri)",
"os_version_id": "21.10",
"process_name": "ceph-mgr",
"stack_sig":
"eccaccb958ebf382237486176ce43b704db9b0ec4b004a7697e77140821e88e9",
"timestamp": "2021-09-12T21:09:22.866793Z",
"utsname_hostname": "ceph-2.dc-003.xxx",
"utsname_machine": "x86_64",
"utsname_release": "5.13.0-14-generic",
"utsname_sysname": "Linux",
"utsname_version": "#14-Ubuntu SMP Mon Aug 2 12:43:35 UTC 2021"
}
On top MGRs having sometimes "clock-skew" issues, even though the daemon is
running its loosing connection and kicked out of the cluster. For sure Host and
KVM is ntp synchronized.
Not sure if this "clock-skew" is related to this crash here, but will
post the log as soon as i have it again.
** Affects: ceph (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/1943423
Title:
mgr crashs in 16.2.5 / clock-skew
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1943423/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943238] [NEW] memory requirements
Public bug reported: Hello, Was running now multiple times into the issue that the minimum memory requirements for the installer was not met. Processes got random killed by kernel with OOM, leading to a very weird behavior of the installer. My experience says that (in case of loading the installer iso into the memory for example by using ipxe) the minimal requirements is about 3 GB of RAM. Can anybody confirm this? Maybe could the installer also check this and denie/warn about the installation instead of dieing randomly? ** Affects: subiquity (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/1943238 Title: memory requirements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1943238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943125] Re: devscripts breaks apt
** Also affects: apt (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/1943125 Title: devscripts breaks apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1943125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943125] [NEW] devscripts breaks apt
Public bug reported: Hello, devscripts package seem to break apt installs. using following Dockerfile: FROM ubuntu:impish ENV DEBIAN_FRONTEND noninteractive RUN apt-get update -qq && apt-get install -y nano RUN apt-get update -qq && apt-get install -y devscripts RUN apt-get update -qq && apt-get install -y htop docker build -t test . Will break installing "htop" with random post apt install errors: E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true' E: Sub-process returned an error code Excluding devscripts package will solve the issue. Any idears why devscripts is breaking apt? ** Affects: devscripts (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello, devscripts package seem to break apt installs. using following Dockerfile: FROM ubuntu:impish ENV DEBIAN_FRONTEND noninteractive - RUN apt-get update -qq && apt-get install -y nano && \ - rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin && \ - rm -rf /var/lib/apt/lists/* && \ - rm -rf /tmp/* - - RUN apt-get update -qq && apt-get install -y devscripts && \ - rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin && \ - rm -rf /var/lib/apt/lists/* && \ - rm -rf /tmp/* - - RUN apt-get update -qq && apt-get install -y htop && \ - rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin && \ - rm -rf /var/lib/apt/lists/* && \ - rm -rf /tmp/* + RUN apt-get update -qq && apt-get install -y nano + RUN apt-get update -qq && apt-get install -y devscripts + RUN apt-get update -qq && apt-get install -y htop docker build -t test . Will break installing "htop" with random post apt install errors: E: Problem executing scripts APT::Update::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true' E: Sub-process returned an error code - Excluding devscripts package will solve the issue. - Any idears why devscripts is breaking apt? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943125 Title: devscripts breaks apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1943125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942168] [NEW] ALX drivers for ethernet card not coming back from Hibernate Suspend
Public bug reported: Whenever ubuntu 20.04 goes to hibernate the network interface cards specifically ethernet does not come back. Its using ALX drivers, similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772 I can correct this issue by doing a script that does modprobe -r alx modprobe -i alx Would be nice if this could be taken care of automatically and drivers dont fail after hibernation Description:Ubuntu 20.04.3 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 30 22:30:49 2021 InstallationDate: Installed on 2021-08-31 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942168 Title: ALX drivers for ethernet card not coming back from Hibernate Suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1942168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939039] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
Public bug reported: System nofification of bug. I don't know anything more. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-25-generic Date: Thu Aug 5 06:39:04 2021 InstallationDate: Installed on 2021-03-11 (147 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939039 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1939039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937110] [NEW] dhcp option 121 & 249
Public bug reported: Hello, I'm running into issues with subiquity on a cloud provider. The cloud provider is using an on-link L3 gateway. His DHCP response looks like this: OPTION: 53 ( 1) DHCP message type 5 (DHCPACK) OPTION: 54 ( 4) Server identifier 172.31.1.1 OPTION: 51 ( 4) IP address leasetime 86400 (24h) OPTION: 1 ( 4) Subnet mask 255.255.255.255 OPTION: 3 ( 4) Routers 172.31.1.1 OPTION: 6 ( 12) DNS server OPTION: 121 ( 14) Classless Static Route20ac1f010100 ... ac1f0101 .. OPTION: 249 ( 14) MSFT - Classless route20ac1f010100 ... ac1f0101 .. Im booting the subiquity process with an patched ipxe (https://github.com/ipxe/ipxe/pull/104) like this: #!ipxe kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null initrd .../initrd boot initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso Sadly subiquity is stuck with a broken network (because of missing dhcp option 121/249 support). It happens when its running the /init from the kernel right after kernel is booted, i guess even before the subiquity is started(?). After further debugging, it looks like the provided kernel 5.4.80 #90 Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc- dhclient-4.4.1 which is lacking the given options. Would be awesome if this could be fixed.. maybe just a simple busybox compile option? ** Affects: subiquity Importance: Undecided Status: New ** Affects: busybox (Ubuntu) Importance: Undecided Status: New ** Also affects: busybox (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/1937110 Title: dhcp option 121 & 249 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921597] [NEW] locks up
Public bug reported: I don't know what would be useful for you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Mar 27 15:06:57 2021 DistUpgraded: 2020-12-23 16:47:59,374 DEBUG /openCache(), new cache size 63671 DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] InstallationDate: Installed on 2015-04-03 (2184 days ago) InstallationMedia: Edubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130214) MachineType: LENOVO 765818U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-136-generic root=UUID=e7e9746b-52c2-49ae-ab18-189b8d46be33 ro drm.debug=0xe nopat vesafb.invalid=1 plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-12-23 (93 days ago) dmi.bios.date: 12/27/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETA9WW (2.09 ) dmi.board.name: 765818U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETA9WW(2.09):bd12/27/2007:svnLENOVO:pn765818U:pvrThinkPadT61:rvnLENOVO:rn765818U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T61 dmi.product.name: 765818U dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Mar 26 14:45:08 2021 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.8 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921597 Title: locks up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1921597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921556] [NEW] computer crash
Public bug reported: after looking at a couple sites my computer stops responding ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-136.140-generic 4.15.18 Uname: Linux 4.15.0-136-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.23 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Mar 26 16:32:35 2021 DistUpgraded: 2020-12-23 16:47:59,374 DEBUG /openCache(), new cache size 63671 DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5] InstallationDate: Installed on 2015-04-03 (2183 days ago) InstallationMedia: Edubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130214) MachineType: LENOVO 765818U PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-136-generic root=UUID=e7e9746b-52c2-49ae-ab18-189b8d46be33 ro drm.debug=0xe nopat vesafb.invalid=1 plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-12-23 (92 days ago) dmi.bios.date: 12/27/2007 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETA9WW (2.09 ) dmi.board.name: 765818U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETA9WW(2.09):bd12/27/2007:svnLENOVO:pn765818U:pvrThinkPadT61:rvnLENOVO:rn765818U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T61 dmi.product.name: 765818U dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Mar 26 14:45:08 2021 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.8 xserver.video_driver: modeset ** Affects: ubuntu Importance: Undecided Status: New ** Tags: apport-bug bionic i386 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921556 Title: computer crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1921556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914892] [NEW] Upgrade from 18.04 to 20.04 fails
Public bug reported: Python 2.7 and 3.6 installed. This was likely caused by: * Unofficial software packages not provided by Ubuntu Please use the tool 'ppa-purge' from the ppa-purge package to remove software from a Launchpad PPA and try the upgrade again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Feb 6 21:41:44 2021 InstallationDate: Installed on 2020-04-11 (302 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-02-07 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914892 Title: Upgrade from 18.04 to 20.04 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1914892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914838] [NEW] Unable to upgrade from 18.04 to 20.04
Public bug reported: Using graphical tool to upgrade from 18.04 to 20.04, upgrade gets to second step and reports could not calculate the upgrade. Cannot determine what is causing this. Removed several packages, ran sudo ppa- purge, still receive same error. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVersionSignature: Ubuntu 5.4.0-65.73~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Feb 5 17:15:21 2021 InstallationDate: Installed on 2020-04-11 (300 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2021-02-05 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914838 Title: Unable to upgrade from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1914838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909603] Re: fwupd-refresh.service: Failed with result 'exit-code'
Its a bug in 1.3.* as you can read here: https://github.com/fwupd/fwupd/issues/391#issuecomment-756941356 Also they dont want to bring an update for ubuntu 20.04 LTS as you can read here: https://github.com/fwupd/fwupd/issues/2708#issuecomment-758850957 Further information can also be found here: https://github.com/fwupd/fwupd/issues/2532 Can someone explain why exactly this fwupd is installed on ubuntu 20.04 server editions? I see mostly consumer hardware in their list of provided firmwares: https://cdn.fwupd.org/lvfs/devices/ On most servers thers prob. no advantage of having this daemon running/failing especially when they dont want to bring stability to their sofware used in LTS versions.. Im removing this daemon from my servers.. ** Bug watch added: github.com/fwupd/fwupd/issues #391 https://github.com/fwupd/fwupd/issues/391 ** Bug watch added: github.com/fwupd/fwupd/issues #2708 https://github.com/fwupd/fwupd/issues/2708 ** Bug watch added: github.com/fwupd/fwupd/issues #2532 https://github.com/fwupd/fwupd/issues/2532 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909603 Title: fwupd-refresh.service: Failed with result 'exit-code' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1909603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906364] Re: [SRU] unattended-upgrade still restarts blacklisted daemons
Thanks for beeing fully ignored.. Well see us on the next production outtake.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: [SRU] unattended-upgrade still restarts blacklisted daemons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906364] Re: unattended-upgrade still restarts blacklisted daemons
Thanks @bryce for the detailed updates. For us personally its the second time we run into a docker daemon restart on production (including all container restarts). The only reason why this time it got much more attention is that a bug prevented a clean restart of the daemon, leaving containers offline. This fact tells us that most of the people never noticed that their containers were also during the last update restartet. (Which is fine because mostly a short restart, for example of a webserver nobody would notice) This is also fine of most of our servers because they running lightweight containers. The only reason why we noticed it (this and last time) is that we running heavy database containers (for example elasticsearch with couple of TBs) which have a restart time of minutes instead of seconds. Especially its critical (and loosing consistency) when containers of the same kind get restarted at the same time. All of this chain is triggered by the unattended updates. Thats why we excluded the automatic updates for the docker package. But this doesnt help if depending package updates still restarting the docker daemon/containers. Since the unattended package is still marked as 'wont-fix', and the dependencies problem is explained above.. The only way to safely prevent docker daemon restarts is to fully disable the whole unattended updates? Can someone confirm this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: unattended-upgrade still restarts blacklisted daemons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1906364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906364] Re: unattended-upgrade still restarts blacklisted daemons
Sorry but im not really on your side here and it also doesnt really solve the problem. I added docker.io to the blacklist because i want to take care manually about the upgrades, it should leave in any case this package alone. Adding here dependencies (containerd) for the packages will never solve the issue, also i have to maintain this list, because dependencies (at least in theorie) could change over time. Just to prevent docker.io from restart i have to add a huge set of packages (out of the list here https://packages.ubuntu.com/focal/docker.io) to prevent it from updating. On top i have to go through all of the first level packages, to check if it has dependencies on the next level, because those could trigger a restart of the first level package, which will chain on the package which i try to prevent. As far as i get it currently, if unattended-upgrades is not considering dependencies of blacklisted packages, theres no way except building an incredibly huge list of packages which you dont want to update, and regulary recalculate this list, because of maybe changed dependencies.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: unattended-upgrade still restarts blacklisted daemons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/containerd/+bug/1906364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906364] [NEW] unattended-upgrade still restarts blacklisted daemons
Public bug reported: Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! >From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-12-01 06:40:46,996 INFO All upgrades installed 2020-12-01 06:40:50,732 INFO Starting unattended upgrades script 2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:50,733 INFO Initial whitelist (not strict): Also this happened for us on plenty of our servers almost at the same (why the unattended updates are not spread over time?), which destroyed the second time an production environment. This is not how unattended-upgraded should be, sadly this package lost our trust and we disable it and schedule the 'unattended updates' now on our own. PS: Not to say that on some servers the docker daemon did not even restart.. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello, Today plenty of our systems running ubuntu 20.04 were restarting the docker daemon, even if i blacklisted the docker package. Since docker has an dependency on containerd thats the reason why it was restarted. IMO the blacklist should also check the full tree of dependencies... This should NOT happen! From the log you find: 2020-12-01 06:40:13,881 INFO Starting unattended upgrades script 2020-12-01 06:40:13,882 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:13,882 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:13,882 INFO Initial whitelist (not strict): 2020-12-01 06:40:19,139 INFO Packages that will be upgraded: containerd qemu-block-extra qemu-kvm qemu-system-common qemu-system-data qemu-system-gui qemu-system-x86 qemu-utils 2020-12-01 06:40:19,140 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2020-12-01 06:40:46,996 INFO All upgrades installed 2020-12-01 06:40:50,732 INFO Starting unattended upgrades script 2020-12-01 06:40:50,732 INFO Allowed origins are: o=Ubuntu,a=focal, o=Ubuntu,a=focal-security, o=UbuntuESMApps,a=focal-apps-security, o=UbuntuESM,a=focal-infra-security 2020-12-01 06:40:50,733 INFO Initial blacklist: docker docker.io 2020-12-01 06:40:50,733 INFO Initial whitelist (not strict): - - Also this happened for us on plenty of our servers almost at the same (why the unattended updates are not spread over time?), which destroyed the second time an production environment. + Also this happened for us on plenty of our servers almost at the same + (why the unattended updates are not spread over time?), which destroyed + the second time an production environment. This is not how unattended-upgraded should be, sadly this package lost our trust and we disable it and schedule the 'unattended updates' now on our own. + + PS: Not to say that on some servers the docker daemon did not even + restart.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906364 Title: unattended-upgrade still restarts blacklisted daemons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1906364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901919] Re: Missing module bochs-drm: no display on QEMU -vga std
** Description changed: The bochs-drm module is not enabled in the build config of the linux-kvm kernel. Therefore, there is no display output when running in QEMU with -vga std. The image I used is focal-server-cloudimg-amd64-disk-kvm.img from cloud-images.ubuntu.com. + Steps to reproduce: + 1. curl -LO https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img + 2. qemu-system-x86_64 -enable-kvm -hda focal-server-cloudimg-amd64-disk-kvm.img -vga std + 3. Observe the screen stay on the boot message + + The missing Kconfig is CONFIG_DRM_BOCHS=y Ubuntu release: Ubuntu 20.04.1 LTS linux-kvm version: 5.4.0.1026.24 (amd64) + + Corresponding bug for the linux package: + https://bugs.launchpad.net/bugs/1872863 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901919 Title: Missing module bochs-drm: no display on QEMU -vga std To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1901919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901919] [NEW] Missing module bochs-drm: no display on QEMU -vga std
Public bug reported: The bochs-drm module is not enabled in the build config of the linux-kvm kernel. Therefore, there is no display output when running in QEMU with -vga std. The image I used is focal-server-cloudimg-amd64-disk-kvm.img from cloud-images.ubuntu.com. The missing Kconfig is CONFIG_DRM_BOCHS=y Ubuntu release: Ubuntu 20.04.1 LTS linux-kvm version: 5.4.0.1026.24 (amd64) ** Affects: linux-kvm (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/1901919 Title: Missing module bochs-drm: no display on QEMU -vga std To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1901919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 673755] Re: Problem with installation ubuntu 10.10
I've been trying for days now to install Eclipse on Ubuntu 10.10 but it never works. if I double click on Eclipse icon, it does nothing. https://www.talktosonic.website/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/673755 Title: Problem with installation ubuntu 10.10 To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/673755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I have the same MSFT0001:00 04F3:3186 touchpad, however, the touchpad will show as Elantech Touch Pad under windows and it is listed under the firmware section: Elantech Touch Pad Firmware 1.0.0.2 Device type:Firmware Manufacturer: Elantech Ltd. Locatioon: on Microsft UEFI-Compliant System https://www.catalog.update.microsoft.com/ScopedViewInline.aspx?updateid=88c5455c-404a-4e6b-b2a0-382ff0017406 And I found it's driver on windows is actually raw data called "SA469D-22HM_Fv0x02.bin". I tried to disassembly it but the output doesn't make much sense. I think to try to understand why do this type of touchpads work on windows may help understanding why do them do not work on most Linux distributions. There are also some docs about Precision Touchpad on MS' site: https://docs.microsoft.com/en-us/windows-hardware/design/component-guidelines/touchpad-windows-precision-touchpad-collection https://docs.microsoft.com/en-us/windows-hardware/design/component-guidelines/windows-precision-touchpad-required-hid-top-level-collections -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892595] Re: TigerVNC server listening on unix domain socket doesn't work
I found the source of the error and fixed the bug, at least for the purposes of my own project. Essentially, the script waits for a port to be used even though we are listening on a file. Obviously, it won't find this port, so eventually it times out. Since I've never used Perl before, my fix is not pretty/clean. However, I will provide as much assistance as I can to whoever ends up officially fixing this bug. My email is aerobinso...@gmail.com. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892595 Title: TigerVNC server listening on unix domain socket doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tigervnc/+bug/1892595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554455] Re: "update-initramfs" is executed several times when you remove old kernels
It's been 4 years and nothing has been changed, this still happening. executing "update-initramfs" several times is wasting of processing power and time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554455 Title: "update-initramfs" is executed several times when you remove old kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1554455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893264] [NEW] package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.6 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 128
Public bug reported: failed to update package ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.6 ProcVersionSignature: Ubuntu 4.15.0-1027.32-oem 4.15.18 Uname: Linux 4.15.0-1027-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Aug 27 14:15:05 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+matira-5-7-r+X58 ErrorMessage: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-08-06 (21 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: openssl Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.6 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893264 Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.6 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error exit status 128 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1893264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892595] [NEW] TigerVNC server listening on unix domain socket doesn't work
Public bug reported: When I try to start a TigerVNC server listening on a unix domain socket, it doesn't work. No clear error message is provided. The exact command I used was 'tigervncserver -rfbunixpath /tmp/mysocket'. I have written about this issue in more detail here: https://github.com/tigervnc/tigervnc/issues/1071 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: tigervnc-standalone-server 1.10.1+dfsg-3 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 22 15:59:57 2020 InstallationDate: Installed on 2020-08-21 (0 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 SourcePackage: tigervnc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tigervnc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892595 Title: TigerVNC server listening on unix domain socket doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tigervnc/+bug/1892595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890327] [NEW] MSFT touchpad not working [ 0.826524] i2c_hid i2c-MSFT0001:00: supply vdd not found, using dummy regulator
Public bug reported:
Hello
dmesg:
[0.826524] i2c_hid i2c-MSFT0001:00: supply vdd not found, using dummy
regulator
[0.826538] i2c_hid i2c-MSFT0001:00: supply vddl not found, using dummy
regulator
Best regards
DistroRelease: Ubuntu 20.04
Kernel: 5.4.*,5.7.*,5.8.*
Processor: AMD Ryzen 4600H
lspci:
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Renoir IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host
Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host
Bridge
00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe GPP Bridge
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host
Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP
Bridge to Bus
00:08.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP
Bridge to Bus
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 51)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Renoir Device 24:
Function 7
01:00.0 VGA compatible controller: NVIDIA Corporation Device 1f99 (rev a1)
01:00.1 Audio device: NVIDIA Corporation Device 10fa (rev a1)
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD
Controller SM981/PM981/PM983
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411
PCI Express Gigabit Ethernet Controller (rev 15)
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Renoir (rev c7)
04:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h
(Models 10h-1fh) Platform Security Processor
04:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
04:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Renoir USB 3.1
04:00.5 Multimedia controller: Advanced Micro Devices, Inc. [AMD]
Raven/Raven2/FireFlight/Renoir Audio Processor (rev 01)
04:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models
10h-1fh) HD Audio Controller
05:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller
[AHCI mode] (rev 81)
05:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller
[AHCI mode] (rev 81)
//lspci isn't showing touchpad
/
xinput:
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Control id=13 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=15 [slave pointer (2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpadid=16 [slave pointer (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave keyboard (3)]
↳ Power Button id=6[slave keyboard (3)]
↳ Video Bus id=7[slave keyboard (3)]
↳ Video Bus id=8[slave keyboard (3)]
↳ Power Button id=9[slave keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Controlid=11 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboard id=12 [slave keyboard (3)]
↳ Ideapad extra buttons id=14 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=17 [slave keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Control id=18 [slave
keyboard (3)]
Under OS that can use this device (e.g. MS_win10):
Device Type: Firmware
Manufacturer: Elantech Ltd.
Location: On UEFI
UEFI\RES_{234124e9-40b7-43ef-9b5e-97470808d440}_2
UEFI\RES_{234124e9-40b7-43ef-9b5e-97470808d440}
[Bug 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries
Hi Guilherme, Thanks for the update! I tested and it works! Cheers, Arthur -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/187 Title: Bionic ubuntu ethtool doesn't check ring parameters boundaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries
Hi Guilherme, Thanks for your reply. No need for an exact ETA, but can you give me some sort of feeling, maybe how often do these amis get released? once a month? 2 months? Cheers, Arthur -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/187 Title: Bionic ubuntu ethtool doesn't check ring parameters boundaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries
Question - when is this fix expected to be released to the official Bionic and Xenial AMIs in AWS? Thank! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/187 Title: Bionic ubuntu ethtool doesn't check ring parameters boundaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1456789] Re: restarting services hangs on systemd-tty-ask-password-agent
This crap here drives me crazy. Im having this on an apt-installation of "redis-server". Ubuntu 18.04 systemctl / networkctl all clean. kernel is not booted with console parameters (also with console parameters doesnt work) I tried like everything, even replacing this stupid .. /bin/systemd-tty-ask-password-agent with /bin/true Im running everything as root to avoid permission issues and theres no fucking way to bypass this stupid /bin/systemd-tty-ask-password-agent Im currently having NO WAY to install anything on the system because its stuck on this stupid process... Fucking get rid of this shit or bring a solution to enter the password. Already spend 2 hours on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1456789 Title: restarting services hangs on systemd-tty-ask-password-agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1456789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855889] Re: cannot perform operation: mount --rbind /root /tmp/snap.rootfs_vWwNbw//root: Permission denied
Just for completeness, I've found the solution. I googled some more as none of my other snaps were working and found a little tidbit I hadn’t come across before. It mentioned something about using the mount system for /root. My /root was a symlink to /home/root. I deleted the symlink Created a new /root folder Created a mount entry in /etc/fstab: /data/home/root /root none rbind Now my snaps are working. The full thread where I got this from is here: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1729576 the comment in question is #13. Thank you again for your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855889 Title: cannot perform operation: mount --rbind /root /tmp/snap.rootfs_vWwNbw//root: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1879976] Re: pads revert to same workspace after loging out and back in
Xpad heavily depends on GTK, an application framework, which (IMHO) has the tendency to break things. Which desktop environment is used by PopOS? Is that Lxqt, KDE plasma, gnome, ... ? On Sun, 24 May 2020 at 15:35, Alan Griffith <1879...@bugs.launchpad.net> wrote: > Yes, it worked right before and doesn't now. I don't know what could have > been different to reproduce the change > > On Sun, May 24, 2020 at 3:00 AM Arthur Borsboom < > 1879...@bugs.launchpad.net> > wrote: > > > Do I understand it correct that both Xpad 5.0 and 5.4 have the same issue > > and is unrelated to the PopOS upgrade, since the issue is in both PopOS > > versions with both Xpad versions? > > > > > > On Fri, 22 May 2020 at 22:25, Alan Griffith <1879...@bugs.launchpad.net> > > wrote: > > > > > I tried installing popos 19.10 in a vm, updating all packages to latest > > > 19.10 version, installing xpad, creating notes, moving to different > > > workspaces and logging out and logging back in. All notes moved back to > > the > > > same workspace > > > > > > > > > On Fri, May 22, 2020 at 2:46 PM Alan Griffith > wrote: > > > > > > > The previous OS release https://packages.ubuntu.com/eoan/xpad has > > > 5.4.0-1 > > > > the same as the current release > https://packages.ubuntu.com/focal/xpad > > > > > > > > I tested xpad 5.0.0-1 from > > > > https://mirrors.edge.kernel.org/ubuntu/pool/universe/x/xpad/ on the > > > > current version of PopOS and the notes move back to the same > workspace > > > > after logging out and in > > > > > > > > On Fri, May 22, 2020 at 1:10 PM Arthur Borsboom < > > > > 1879...@bugs.launchpad.net> wrote: > > > > > > > >> Do you know which version was being used in Pop!_OS 19.10 ? > > > >> Are you are able to downgrade to that version to test if it makes a > > > >> difference? > > > >> > > > >> On Thu, 21 May 2020 at 19:40, Alan Griffith < > > 1879...@bugs.launchpad.net > > > > > > > >> wrote: > > > >> > > > >> > xpad 5.4.0-1 > > > >> > > > > >> > On Thu, May 21, 2020, 12:25 Arthur Borsboom < > > > 1879...@bugs.launchpad.net > > > >> > > > > >> > wrote: > > > >> > > > > >> > > Which version of Xpad shows this behavior? > > > >> > > > > > >> > > -- > > > >> > > You received this bug notification because you are subscribed to > > the > > > >> bug > > > >> > > report. > > > >> > > https://bugs.launchpad.net/bugs/1879976 > > > >> > > > > > >> > > Title: > > > >> > > pads revert to same workspace after loging out and back in > > > >> > > > > > >> > > Status in Xpad: > > > >> > > New > > > >> > > Status in Ubuntu: > > > >> > > New > > > >> > > > > > >> > > Bug description: > > > >> > > pads revert to same workspace after logging out and back in > > > >> > > This started happening after upgrading to Pop!_OS 20.04 LTS > from > > > >> 19.10. > > > >> > > > > > >> > > To manage notifications about this bug go to: > > > >> > > https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > > > >> > > > > > >> > > > > >> > -- > > > >> > You received this bug notification because you are subscribed to > > Xpad. > > > >> > Matching subscriptions: Arthur Borsboom > > > >> > https://bugs.launchpad.net/bugs/1879976 > > > >> > > > > >> > Title: > > > >> > pads revert to same workspace after loging out and back in > > > >> > > > > >> > Status in Xpad: > > > >> > New > > > >> > Status in Ubuntu: > > > >> > New > > > >> > > > > >> > Bug description: > > > >> > pads revert to same workspace after logging out and back in > > > >> > This started happening after upgrading to Pop!_OS 20.04 LTS from > > > >> 19.10. > > > >> > > > >
Re: [Bug 1879976] Re: pads revert to same workspace after loging out and back in
Do I understand it correct that both Xpad 5.0 and 5.4 have the same issue and is unrelated to the PopOS upgrade, since the issue is in both PopOS versions with both Xpad versions? On Fri, 22 May 2020 at 22:25, Alan Griffith <1879...@bugs.launchpad.net> wrote: > I tried installing popos 19.10 in a vm, updating all packages to latest > 19.10 version, installing xpad, creating notes, moving to different > workspaces and logging out and logging back in. All notes moved back to the > same workspace > > > On Fri, May 22, 2020 at 2:46 PM Alan Griffith wrote: > > > The previous OS release https://packages.ubuntu.com/eoan/xpad has > 5.4.0-1 > > the same as the current release https://packages.ubuntu.com/focal/xpad > > > > I tested xpad 5.0.0-1 from > > https://mirrors.edge.kernel.org/ubuntu/pool/universe/x/xpad/ on the > > current version of PopOS and the notes move back to the same workspace > > after logging out and in > > > > On Fri, May 22, 2020 at 1:10 PM Arthur Borsboom < > > 1879...@bugs.launchpad.net> wrote: > > > >> Do you know which version was being used in Pop!_OS 19.10 ? > >> Are you are able to downgrade to that version to test if it makes a > >> difference? > >> > >> On Thu, 21 May 2020 at 19:40, Alan Griffith <1879...@bugs.launchpad.net > > > >> wrote: > >> > >> > xpad 5.4.0-1 > >> > > >> > On Thu, May 21, 2020, 12:25 Arthur Borsboom < > 1879...@bugs.launchpad.net > >> > > >> > wrote: > >> > > >> > > Which version of Xpad shows this behavior? > >> > > > >> > > -- > >> > > You received this bug notification because you are subscribed to the > >> bug > >> > > report. > >> > > https://bugs.launchpad.net/bugs/1879976 > >> > > > >> > > Title: > >> > > pads revert to same workspace after loging out and back in > >> > > > >> > > Status in Xpad: > >> > > New > >> > > Status in Ubuntu: > >> > > New > >> > > > >> > > Bug description: > >> > > pads revert to same workspace after logging out and back in > >> > > This started happening after upgrading to Pop!_OS 20.04 LTS from > >> 19.10. > >> > > > >> > > To manage notifications about this bug go to: > >> > > https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > >> > > > >> > > >> > -- > >> > You received this bug notification because you are subscribed to Xpad. > >> > Matching subscriptions: Arthur Borsboom > >> > https://bugs.launchpad.net/bugs/1879976 > >> > > >> > Title: > >> > pads revert to same workspace after loging out and back in > >> > > >> > Status in Xpad: > >> > New > >> > Status in Ubuntu: > >> > New > >> > > >> > Bug description: > >> > pads revert to same workspace after logging out and back in > >> > This started happening after upgrading to Pop!_OS 20.04 LTS from > >> 19.10. > >> > > >> > To manage notifications about this bug go to: > >> > https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > >> > > >> > >> > >> -- > >> Arthur Borsboom > >> Phone: +31629089953 > >> > >> -- > >> You received this bug notification because you are subscribed to the bug > >> report. > >> https://bugs.launchpad.net/bugs/1879976 > >> > >> Title: > >> pads revert to same workspace after loging out and back in > >> > >> Status in Xpad: > >> New > >> Status in Ubuntu: > >> New > >> > >> Bug description: > >> pads revert to same workspace after logging out and back in > >> This started happening after upgrading to Pop!_OS 20.04 LTS from > 19.10. > >> > >> To manage notifications about this bug go to: > >> https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > >> > > > > -- > You received this bug notification because you are subscribed to Xpad. > Matching subscriptions: Arthur Borsboom > https://bugs.launchpad.net/bugs/1879976 > > Title: > pads revert to same workspace after loging out and back in > > Status in Xpad: > New > Status in Ubuntu: > New > > Bug description: > pads revert to same workspace after logging out and back in > This started happening after upgrading to Pop!_OS 20.04 LTS from 19.10. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > -- Arthur Borsboom Phone: +31629089953 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879976 Title: pads revert to same workspace after loging out and back in To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1879976] Re: pads revert to same workspace after loging out and back in
Do you know which version was being used in Pop!_OS 19.10 ? Are you are able to downgrade to that version to test if it makes a difference? On Thu, 21 May 2020 at 19:40, Alan Griffith <1879...@bugs.launchpad.net> wrote: > xpad 5.4.0-1 > > On Thu, May 21, 2020, 12:25 Arthur Borsboom <1879...@bugs.launchpad.net> > wrote: > > > Which version of Xpad shows this behavior? > > > > -- > > You received this bug notification because you are subscribed to the bug > > report. > > https://bugs.launchpad.net/bugs/1879976 > > > > Title: > > pads revert to same workspace after loging out and back in > > > > Status in Xpad: > > New > > Status in Ubuntu: > > New > > > > Bug description: > > pads revert to same workspace after logging out and back in > > This started happening after upgrading to Pop!_OS 20.04 LTS from 19.10. > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > > > > -- > You received this bug notification because you are subscribed to Xpad. > Matching subscriptions: Arthur Borsboom > https://bugs.launchpad.net/bugs/1879976 > > Title: > pads revert to same workspace after loging out and back in > > Status in Xpad: > New > Status in Ubuntu: > New > > Bug description: > pads revert to same workspace after logging out and back in > This started happening after upgrading to Pop!_OS 20.04 LTS from 19.10. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions > -- Arthur Borsboom Phone: +31629089953 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879976 Title: pads revert to same workspace after loging out and back in To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879976] Re: pads revert to same workspace after loging out and back in
Which version of Xpad shows this behavior? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879976 Title: pads revert to same workspace after loging out and back in To manage notifications about this bug go to: https://bugs.launchpad.net/xpad/+bug/1879976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863021] Re: [SRU] eventlet monkey patch results in assert len(_active) == 1 AssertionError
** Changed in: manila (Ubuntu Groovy) Assignee: (unassigned) => Arthur Dayne (palagend) ** Changed in: watcher (Ubuntu Groovy) Assignee: (unassigned) => Arthur Dayne (palagend) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863021 Title: [SRU] eventlet monkey patch results in assert len(_active) == 1 AssertionError To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1863021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863021] Re: [SRU] eventlet monkey patch results in assert len(_active) == 1 AssertionError
** Changed in: barbican (Ubuntu Groovy) Assignee: (unassigned) => Arthur Dayne (palagend) ** Changed in: mistral (Ubuntu Groovy) Assignee: (unassigned) => Arthur Dayne (palagend) ** Changed in: ironic (Ubuntu Groovy) Assignee: (unassigned) => Arthur Dayne (palagend) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863021 Title: [SRU] eventlet monkey patch results in assert len(_active) == 1 AssertionError To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1863021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries
Hi, Bumping this ticket up. Is there still something missing in the ticket that I can provide to make it workable? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/187 Title: Bionic ubuntu ethtool doesn't check ring parameters boundaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries
Tried running apport-collect but since my machine has no guy I couldn't authorize. Tried running apport-cli --save file.out - this also failed with: "No pending crash reports. Try --help for more information." I have no idea how to continue here, and I don't see the point as it is fairly easy to run an ubuntu instance with the latest ubuntu 18.04 ami to reproduce the issue and I filled all the necessary information on how to fix the issue as well. Moving the status to Confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete => Opinion ** Changed in: linux (Ubuntu) Status: Opinion => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/187 Title: Bionic ubuntu ethtool doesn't check ring parameters boundaries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874444] [NEW] Bionic ubuntu ethtool doesn't check ring parameters boundaries
Public bug reported:
Upstream linux kernel implemented ring parameter boundaries check in commit:
37e2d99b59c4 ("ethtool: Ensure new ring parameters are within bounds during
SRINGPARAM")
(see link
https://patchwork.ozlabs.org/project/netdev/patch/1515420026-11970-2
-git-send-email-tar...@mellanox.com/)
Due to this commit, the community doesn't allow ring parameter boundary
checks in driver code.
The Bionic ubuntu kernel does not include this patch. And some network drivers
rely on this patch for
boundary checking of ring params.
This causes bugs in case a ringparam was given an illegal value.
Reproduction steps in AWS:
1. Create new c5.4xlarge instance with the ubuntu 18.04 official ami (uses the
ENA network driver) and update to latest kernel using apt-get dist-upgrade and
reboot for the new kernel to load.
2. Run ethtool -g ens5
output:
Ring parameters for ens5:
Pre-set maximums:
RX: 16384
RX Mini:0
RX Jumbo: 0
TX: 1024
Current hardware settings:
RX: 1024
RX Mini:0
RX Jumbo: 0
TX: 1024
3. Change the tx ring size to a legal number within boundaries - works!
4. Change the tx ring size to an illegal number such as 2048 with the command -
sudo ethtool -G ens5 tx 2048.
Expected behavior - operation not allowed
Actual behavior - causes a crash of the driver since boundaries are not checked
by ethtool.
Proposed fix - include the above commit 37e2d99b59c4 ("ethtool: Ensure
new ring parameters are within bounds during SRINGPARAM") in bionic (and
probably other ubuntu releases as well)
More data about the machine where the bug occured:
ubuntu@ip-172-31-80-28:~/bionic$ lsb_release -rd
Description:Ubuntu 18.04.4 LTS
Release:18.04
ubuntu@ip-172-31-80-28:~/bionic$ uname -r
4.15.0-1065-aws
** Affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/187
Title:
Bionic ubuntu ethtool doesn't check ring parameters boundaries
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/187/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 823152] Re: [needs-packaging] OS-Uninstaller
** Changed in: ubuntu Status: Confirmed => In Progress ** Changed in: os-uninstaller Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/823152 Title: [needs-packaging] OS-Uninstaller To manage notifications about this bug go to: https://bugs.launchpad.net/os-uninstaller/+bug/823152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865403] Re: clip selection issue
Its working fine on 2.4. Tks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865403 Title: clip selection issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flowblade/+bug/1865403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865401] Re: Dissolve can't process clips
On 2.4 some times it is possible and other times is not possible. I am trying to understand the behavior to determine why. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865401 Title: Dissolve can't process clips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flowblade/+bug/1865401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865403] Re: clip selection issue
** Description changed: Whem I try to use yhe Box selection it os possible until the 5th step only. The 6th clip do not permit to be selected. - I attached a video reproducing the bug. + I attached a video reproducing the bug. I am using version 2.2.0-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865403 Title: clip selection issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flowblade/+bug/1865403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865403] [NEW] clip selection issue
Public bug reported: Whem I try to use yhe Box selection it os possible until the 5th step only. The 6th clip do not permit to be selected. I attached a video reproducing the bug. ** Affects: flowblade (Ubuntu) Importance: Undecided Status: New ** Attachment added: "out-8.ogv" https://bugs.launchpad.net/bugs/1865403/+attachment/5332577/+files/out-8.ogv -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865403 Title: clip selection issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flowblade/+bug/1865403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865401] [NEW] Dissolve can't process clips
Public bug reported: Hi, The dissolve effect do not works with some clips. I do a cut on 15 frames by each clip and the software accuses no frame available to proceed it. ** Affects: flowblade (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screen showing more than 15 frames by each side and dissolve tools saying there is no frame available." https://bugs.launchpad.net/bugs/1865401/+attachment/5332576/+files/Captura%20de%20tela%20de%202020-03-01%2023-01-15.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865401 Title: Dissolve can't process clips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flowblade/+bug/1865401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865184] [NEW] gvfsd-afc crashed with SIGSEGV in g_str_equal()
Public bug reported: Got this internal error on startup today. On previous days there was a message of just system error. Device: Dell Latitude E6410 Memory: 7.6 GiB Processor Intel Core i5 CPU M 520 @ 2.40GHz x 4 Graphics: Intel Ironlake Mobile GNOME: 3.28.2 OS Type: 64-bit Disk 491.2 GB Package: gvfs-backends 1.36.1-0ubuntu1.3.3 Problem Type: Crash ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CoreDump: (binary data) Current Desktop: ubuntu:GNOME Date: Thu Feb27 11:52:18 2020 Dependencies: Disassembly DistroRelease:Ubuntu 18.04 InstallationDate: Installed on 2020-02-15 (12 days ago) InstalattionMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" -Release amd64 (20200203.1) Journal Errors: -Logs begin at Sat 2020-02-15 11:57:13 EST end Fro 2020-02-28 10:07:39 EST -- Feb 28 10:04:04 hostname kernel: intel ips :00: 1f.6: ME failed to update for more than 1s, likely hung " " Package Architecture: amd64 ProcCmdline: /usr/lib/gvfs/gvfsd-afc--spawner:1.7/org/gtk/gvfs/exec_spaw/12 ProcCpuinfoMinimal: processor: 3 vendor_id: GenuineIntel cpu family: 6 model: 37 model name: Intel(R) Core(TM) i5 CPU M 520 @2.40GHz stepping: 5 microcode: 0x7 cpu MHZ:2197.705 cache size: 3072 KB physical id:0 siblings: 4 core id:2 cpu cores: 2 apicid: 5 initial apicid: 5 fpu:yes fpu exeption: yes cpuid level:11 wp: yes flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts scpi mmx fxsr sse sse2 ht tm pbe syscall nx rdscp lm constant_tsc_arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmsx smx est im2 ssse3 cx16 xtpr pdcmpcid sse4_1 sese4_2 popcnt aes hahf_lm pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid dtherm ida arat flush_l1d bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf nds swapgs itlb_multihit bogomips: 4788.04 clflush size: 64 cashe_allignment: 64 address sizes: 36 bits physical, 48 bits virtural ProcVersionSignature: Ubuntu 5.3.0-40.32-18.04.1-generic 5.3.18 Seg Revision: reading NULL VMA Signal: 11 Source Package: gvfs SacktraceAddressSignature: /usr/lib/gvfs/gvfsd-afc:11/lib/x86_64-linux-gnu/libc-2.27.so+a9e8a:/usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.5600.4+3b569:usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.4+3aa6c: /usr/lib/gvfs/gvfsd-afc+5942:/usr/lib/gvfs/gvfsd-afc+8664:usr/lib/x86_64-linux-gnu/gvfs /libgvfsdarmon.so+f8ea/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.4+74b60:/usr/lib /x86_64-linux-gnu/libglib-2.0.so.0.5600.4+74195:/lib/x86_64-linux-gnu/libpthread- 2.27.so+76db:/lib/x86_64-linux-gnu/libc-2.27.so+12188f ** Affects: gvfs (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/1865184 Title: gvfsd-afc crashed with SIGSEGV in g_str_equal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1865184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10
Hi there, Just in case this helps someone else until the Ubuntu version of Chromium works again on a system similar to mine. I ended up following this thread: https://askubuntu.com/questions/1204571/chromium-without-snap and installed from the Debian Buster repositories. Regards, Arthur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855889 Title: Can't run Chromium since upgrade to Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10
Hi Oliver, is there any other information you need me to supply? Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855889 Title: Can't run Chromium since upgrade to Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860035] [NEW] Andreev
Public bug reported: i dont know what write ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 22:43:03 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=ru_RU.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 LC_NUMERIC=C.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 bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860035 Title: Andreev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1860035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10
Hi Oliver, That's not a problem. Here's the output of the command: arthur@atze:~$ journalctl -f | grep DEN Jan 15 19:55:35 atze audit[15557]: AVC apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/snap/snapd/5754/usr/lib/snapd/snap-confine" name="/tmp/snap.rootfs_P2ZGhz/root/" pid=15557 comm="snap-confine" srcname="/home/root/" flags="rw, rbind" Jan 15 19:55:35 atze kernel: audit: type=1400 audit(1579083935.697:45): apparmor="DENIED" operation="mount" info="failed flags match" error=-13 profile="/snap/snapd/5754/usr/lib/snapd/snap-confine" name="/tmp/snap.rootfs_P2ZGhz/root/" pid=15557 comm="snap-confine" srcname="/home/root/" flags="rw, rbind" Thank you for looking into it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855889 Title: Can't run Chromium since upgrade to Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10
Hi Oliver, is there any other information you need me to supply? Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855889 Title: Can't run Chromium since upgrade to Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858441] [NEW] After installation on Ubuntu 18.04.3 LTS, the Docker service does not start automatically after reboot.
Public bug reported: After Installing docker on ubnuntu 18.04.3 via kickstart/preseed, Docker doesn't start automatically after the next boot as expected. 'systemctl status docker' shows that it should: systemctl status docker ● docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; disabled; vendor preset: enabled) Active: inactive (dead) Docs: https://docs.docker.com The symlink to the docker unit file is 'not' present after installation in: /etc/systemd/system/multi-user.target.wants Running the following after installation as a workaround: systemctl enable docker systemctl start docker System build information: DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" Docker version 18.09.7, build 2d0083d apt-cache policy docker: docker: Installed: (none) Candidate: 1.5-1build1 Version table: 1.5-1build1 500 500 http://some_mirror/ubuntu bionic/universe amd64 Packages ** Affects: docker (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/1858441 Title: After installation on Ubuntu 18.04.3 LTS, the Docker service does not start automatically after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker/+bug/1858441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10
Hi, Does anyone have any idea when a working version of Chromium for Ubuntu 19.10 will be available? Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855889 Title: Can't run Chromium since upgrade to Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10
Hi Oliver, /dev/sdc1 119133984 61659788 51352828 55% / /dev/sdc2 119366868 92011264 21249032 82% /home arthur@atze:~$ echo $HOME /home/arthur Thank you. On 18/12/19 12:50 am, Olivier Tilloy wrote: > Where is your $HOME directory? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855889 Title: Can't run Chromium since upgrade to Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10
Hello again, What is the way to install a version of Chromium that works? The Snap version doesn't work and the regular package does not seem to be available in the repositories. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855889 Title: Can't run Chromium since upgrade to Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10
** Attachment added: "ijkihgmhdfgoejej.png" https://bugs.launchpad.net/bugs/1855889/+attachment/5312690/+files/ijkihgmhdfgoejej.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855889 Title: Can't run Chromium since upgrade to Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10
Hi Oliver, Thanks for getting back to me. Sorry I can't reply to the forum, I keep getting: Output of df is: $ df Filesystem 1K-blocks Used Available Use% Mounted on udev 16374724 0 16374724 0% /dev tmpfs 3280988 1780 3279208 1% /run /dev/sdc1 119133984 60472912 52539704 54% / tmpfs 16404924 596 16404328 1% /dev/shm tmpfs 5120 4 5116 1% /run/lock tmpfs 16404924 0 16404924 0% /sys/fs/cgroup /dev/loop0 157184 157184 0 100% /snap/chromium/958 /dev/loop1 45312 45312 0 100% /snap/gtk-common-themes/1353 /dev/loop2 55936 55936 0 100% /snap/core18/1279 /dev/loop3 23040 23040 0 100% /snap/snapd/5643 /dev/sdc2 119366868 91341652 21918644 81% /home /dev/sdc3 258095 11674 246421 5% /boot/efi //192.168.xxx.xxx/hitc1 5621472524 3896681696 1724790828 70% /media/username/network/ATZE-NAS/hitc1 192.168.xxx.xxx:/mnt/HD/HD_a2 958852160 179446560 779405600 19% /media/username/network/dlink/Volume_1 tmpfs 3280984 28 3280956 1% /run/user/1000 On 11/12/19 1:37 am, Olivier Tilloy wrote: > This looks similar to bug #1729576. > What does your filesystem layout look like? I.e. what's the output of command > "df" ? > > ** Changed in: chromium-browser (Ubuntu) >Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855889 Title: Can't run Chromium since upgrade to Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10
Hi Oliver, Thanks for getting back to me. Output of df is: $ df Filesystem 1K-blocks Used Available Use% Mounted on udev 16374724 0 16374724 0% /dev tmpfs 3280988 17803279208 1% /run /dev/sdc1 119133984 60472912 52539704 54% / tmpfs16404924596 16404328 1% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs16404924 0 16404924 0% /sys/fs/cgroup /dev/loop0 157184 157184 0 100% /snap/chromium/958 /dev/loop1 45312 45312 0 100% /snap/gtk-common-themes/1353 /dev/loop2 55936 55936 0 100% /snap/core18/1279 /dev/loop3 23040 23040 0 100% /snap/snapd/5643 /dev/sdc2 119366868 91341652 21918644 81% /home /dev/sdc3 258095 11674 246421 5% /boot/efi //192.168.xxx.xxx/hitc1 5621472524 3896681696 1724790828 70% /media/username/network/ATZE-NAS/hitc1 192.168.xxx.xxx:/mnt/HD/HD_a2 958852160 179446560 779405600 19% /media/username/network/dlink/Volume_1 tmpfs 3280984 283280956 1% /run/user/1000 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855889 Title: Can't run Chromium since upgrade to Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855889] [NEW] Can't run Chromium since upgrade to Ubuntu 19.10
Public bug reported: Hi, I try to run Chromium from the menu and nothing happens. If I run it from the CLI I get: cannot perform operation: mount --rbind /root /tmp/snap.rootfs_vWwNbw//root: Permission denied I tried uninstalling and reinstalling. I tried uninstalling and reinstalling snapd. Tried anything related I could find on-line, but nothing works. Upgrade snap to the latest version on the pre-release channel. For some reason Chromium does not show up in the Software centre either. Thanks for any help. $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 78.0.3904.108 958 stablecanonicalâ - $ apt-cache policy chromium-browser chromium-browser: Installed: 77.0.3865.120-0ubuntu1.19.10.1 Candidate: 77.0.3865.120-0ubuntu1.19.10.1 Version table: *** 77.0.3865.120-0ubuntu1.19.10.1 500 500 http://mirror.overthewire.com.au/ubuntu eoan-updates/universe amd64 Packages 100 /var/lib/dpkg/status 77.0.3865.120-0ubuntu1~snap1 500 500 http://mirror.overthewire.com.au/ubuntu eoan/universe amd64 Packages $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 78.0.3904.108 958 stablecanonicalâ - $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonicalâ contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: stable refresh-date: today at 23:00 ACST channels: stable:78.0.3904.108 2019-11-25 (958) 160MB - candidate: 78.0.3904.108 2019-11-22 (952) 160MB - beta: 79.0.3945.74 2019-12-06 (966) 155MB - edge: 80.0.3983.2 2019-12-05 (964) 156MB - installed: 78.0.3904.108(958) 160MB ** Affects: chromium-browser (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/1855889 Title: Can't run Chromium since upgrade to Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1855889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
