[Bug 1975533] Re: No longer possible to use do-release-upgrade on Groovy
** Attachment added: "ubuntu-upgrader-DistUpgrade.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1975533/+attachment/5592729/+files/ubuntu-upgrader-DistUpgrade.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975533 Title: No longer possible to use do-release-upgrade on Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1975533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975533] Re: No longer possible to use do-release-upgrade on Groovy
@Brian Murray, if you don't mind, I will post my notes here, as comments, so that it will be easier for someone else to follow my thought process on getting familiar with the problem, i.e., getting to better know how does `do-release-upgrade` and `DistUpgrade.cfg` work. It is very important to know all recent Ubuntu release names (https://wiki.ubuntu.com/Releases) in order to keep track with the analysis below. Ok, so I inspected the `DistUpgrade.cfg` file (https://git.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/tree/data/DistUpgrade.cfg?h=ubuntu%2Fjammy#n109; stored in my file system at `/usr/share/ubuntu-release-upgrader/DistUpgrade.cfg`). It contains: ... 108 [Sources] 109 From=impish 110 To=jammy ... So it represents my most recent update. (I finally did groovy=>impish, and impish=>jammy.) Then, during the next update, it would look like: ... 108 [Sources] 109 From=jammy 110 To=kinetic ... (see: https://git.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/tree/data/DistUpgrade.cfg#n110) I also found the `DistUpgrade.cfg.focal` (https://git.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/tree/data/DistUpgrade.cfg.focal), and it contains: ... 108 [Sources] 109 From=focal 110 To=jammy ... Interestingly, the `DistUpgrade.cfg.focal` stored at my file system (at "~/.local/share/Trash/files/DistUpgrade.cfg.focal") contains: ... 108 [Sources] 109 From=focal 110 To=hirsute ... E.g., it was moved to the trash when the `ubuntu-hirsute` branch was in use on my system, see: https://git.launchpad.net/ubuntu/+source/ubuntu- release-upgrader/tree/data/DistUpgrade.cfg.focal?h=ubuntu%2Fhirsute#n109 . --- @Brian Murray, your other suggestion was to create `demoted.cfg.groovy`. Indeed, in the https://git.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/tree/utils there is no `demoted.cfg.groovy`. Maybe part of the simplest solution (for the others to use) is, as you suggest, to create "demoted.cfg.groovy" which contains basically the same packages as "demoted.cfg.focal". --- Brian Murray wrote: > "For what its worth I tested an upgrade of a stock Ubuntu 20.10 system to Ubuntu 21.10 by copying DistUpgrade.cfg.focal to DistUpgrade.cfg.groovy and did not run into any issues" It worked because of this piece of code: lines 44 & 45 here: https://git.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/tree/DistUpgrade/DistUpgradeConfigParser.py#n44 ( ``` if os.path.exists(maincfg + "." + from_release): maincfg += "." + from_release ``` ) It is not a particularly neat solution, but it will work. In the ideal world, there would be a mechanism similar to this: https://git.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/tree/DistUpgrade/DistUpgradeConfigParser.py#n39 (from_release = ...) in combination with the list of known releases (https://wiki.ubuntu.com/Releases) for the `DistUpgradeConfigParser.py` not to take fixed release names (from `DistUpgrade.cfg`/focal/groovy), but dynamically decide what is the release on the system, and what is the next available release, so that the `do-release-upgrade` would attempt to upgrade to the next available release. This way upgrades from the EOL systems would be supported, or as @Scott Carle wrote in the title of his bug report: it would be "easy peasy" (https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1745754), now upgrading from EOL is not that simple. Getting back to the technicalities: the problem now seems to be that both groovy=>impish and hirsute=>impish should be supported. With release names being fixed on the branches, it is not possible (see: https://git.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/tree/data/DistUpgrade.cfg?h=ubuntu%2Fimpish#n109). I am still missing one point: how did my groovy knew that impish was the latest supported system? That's it for the analysis. I will try to come up with some solution (in the code) that will support upgrading from at least groovy, if not from any EOL release, to the first available, still supported release (e.g., at the moment, groovy=>impish and hirsute=>impish). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975533 Title: No longer possible to use do-release-upgrade on Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1975533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975533] Re: No longer possible to use do-release-upgrade on Groovy
@Brian Murray, first, thank you so much for confirming the issue and creating this bug report. Just to be clear, I finally was able to upgrade from groovy to impish by following the instructions in this post: https://blog.invid.eu/2022/02/24/upgrade-eol-ubuntu-server- from-20-10-to-21-10-an-upgrade-from-groovy-to-impish-is-not-supported- with-this-tool-ubuntu-ubuntugeek-ubuntu-linux-eol-upgrade/ ; see also the official documentation: https://help.ubuntu.com/community/EOLUpgrades To the people new to this thread: see also my comment (https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1745754/comments/6) in the other bug report: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1745754 ; and my notes on the issue: https://gist.github.com/mikbuch/2c349e1281c69818b48893a460c5accb @Brian Murray, your suggestion for the minimal fix is all OK, but I wonder if a more general mechanism could be implemented, to support upgrading from an EOL release X to a (EOL) release Y (as the `do- release-upgrade` already says/recognizes with which release there was a problem to which: "An upgrade from ‘groovy’ to ‘impish’ is not supported with this tool."). I don't fully grasp how the DistUpgrade.cfg work, maybe my issue is/was related only to groovy. Either way, if the current bug will be resolved, maybe it is also good idea to update the documentation on EOL upgrades, as well (https://help.ubuntu.com/community/EOLUpgrades). I can help, and I will, as soon as I will get more familiar with the `do-release-upgrade` process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975533 Title: No longer possible to use do-release-upgrade on Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1975533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745754] Re: upgrading from an End of Life release is not easy peasy
@Scott Carle, I agree. @Brian Murray,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/1745754 Title: upgrading from an End of Life release is not easy peasy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1745754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745754] Re: upgrading from an End of Life release is not easy peasy
@Scott Carle, I had a very similar problem. I got "An upgrade from ‘groovy’ to ‘impish’ is not supported with this tool." error when I was trying to upgrade my EOL end-of-life Ubuntu release with use `do-release-upgrade` (command line). I have some initial notes no that: https://gist.github.com/mikbuch/2c349e1281c69818b48893a460c5accb As my problem is slightly different, namely, I'd like the `do-release- upgrade` support EOL upgrades as well, I will create a new issue for that. Nevertheless, I very much agree with you, that what would be very helpful for Ubuntu users (especially the less technical ones), is better support for (EOL) release upgrades. I have upvoted your bug (the current issue) and subscribed the notifications. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745754 Title: upgrading from an End of Life release is not easy peasy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1745754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] Re: touchpad not working after resume on kernel 4.13
I don't think this is the same bug and new bug report should be opened. I've reported problem here back in October 2017 with my laptop and problem was solved with kernel upgrade on Artful. Recently I upgraded same laptop to Bionic and I am not affected by the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722379] Re: Touchpad not working after resume
*** This bug is a duplicate of bug 1723799 *** https://bugs.launchpad.net/bugs/1723799 This problem is fixed with latest kernel update on Ubuntu 17.10: # uname -rv 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 ** This bug has been marked a duplicate of bug 1723799 touchpad not working after resume on kernel 4.13 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722379 Title: Touchpad not working after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1722379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] Re: touchpad not working after resume on kernel 4.13
This problem is fixed with latest kernel update on Ubuntu 17.10: # uname -rv 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] Re: touchpad not working after resume on kernel 4.13
I did the same with: $ uname -rv 4.13.7-041307-generic #201710141430 SMP Sat Oct 14 14:31:12 UTC 2017 and also this kernel works for me and touchpad works after resume. What is also nice, Wi-Fi works after resume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] Re: touchpad not working after resume on kernel 4.13
I did following: dpkg -i \ linux-headers-4.14.0-041400rc5_4.14.0-041400rc5.201710152230_all.deb \ linux-headers-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb \ linux-image-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb and rebooted the system to new kernel. Yes I can confirm that kernel 4.14.0-041400rc5-generic fixes the problem for me. With this new kernel however Wi-Fi doesn't work, but that's another issue. Wi-Fi works with 4.13.0-16-generic and previous kernels from Ubuntu 17.10 ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] Re: touchpad not working after resume on kernel 4.13
Let me know do you need anything else. Will be possible to backport fixes from 4.14 to final release of Ubuntu 17.10, so touchpad works after resume on default Artful Aardvark install? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] Re: touchpad not working after resume on kernel 4.13
Per external references to RedHat's bugzilla solution for the problem should be: https://patchwork.kernel.org/patch/9858267/ however I didn't had a chance to test it yet on latest Ubuntu 17.10 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] Re: touchpad not working after resume on kernel 4.13
errors from kernel after resume (same as one of my previous comments) ** Attachment added: "resume-failed-hid.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+attachment/4972614/+files/resume-failed-hid.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] Re: touchpad not working after resume on kernel 4.13
** Attachment added: "dmesg-before-suspend.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+attachment/4972612/+files/dmesg-before-suspend.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] Re: touchpad not working after resume on kernel 4.13
** Attachment added: "lsmod.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+attachment/4972615/+files/lsmod.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] Re: touchpad not working after resume on kernel 4.13
** Attachment added: "dmesg-after-suspend.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+attachment/4972613/+files/dmesg-after-suspend.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] Re: touchpad not working after resume on kernel 4.13
Previous dmesgs are with 4.13.0-12-generic, as the same problem was present with 4.13.0-12-generic, 4.13.0-15-generic and now is present with 4.13.0-16-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] Re: touchpad not working after resume on kernel 4.13
a bit more lines from syslog when issue happens: Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.0001: rmi_hid_read_block: timeout elapsed Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.0001: rmi_hid_read_block: timeout elapsed Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.0001: rmi_hid_read_block: timeout elapsed Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.0001: rmi_hid_read_block: timeout elapsed Oct 08 18:04:27 mi-air kernel: hid-rmi 0018:06CB:7EA5.0001: rmi_hid_read_block: timeout elapsed Oct 08 18:04:27 mi-air kernel: rmi4_physical rmi4-00: rmi_driver_reset_handler: Failed to read current IRQ mask. Oct 08 18:04:27 mi-air kernel: dpm_run_callback(): i2c_hid_resume+0x0/0x120 [i2c_hid] returns -11 Oct 08 18:04:27 mi-air kernel: PM: Device i2c-SYNA3105:00 failed to resume async: error -11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723799] [NEW] touchpad not working after resume on kernel 4.13
Public bug reported: I'm running Ubuntu 17.10 [Ubuntu Artful Aardvark (development branch) installed from beta 2 ISO with latest apt update && apt dist-upgrade] with kernel: $ uname -rv 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 and after putting system to sleep via closing laptop lid and then resuming it by opening laptop lid makes touchpad not working. Kernel message buffer contains following error message after resume: PM: Device i2c-SYNA3105:00 failed to resume async: error -11 and I can find other people reporting similar issue on other distros: https://bugzilla.redhat.com/show_bug.cgi?id=1431375 https://bugzilla.kernel.org/show_bug.cgi?id=195949 https://bugzilla.redhat.com/show_bug.cgi?id=1442699 like in those other bug reports I can workaround the problem by: rmmod i2c-hid modprobe i2c-hid in systemd-suspend.service(8) post scripts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mkucharski 1367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 22:49:38 2017 HibernationDevice: RESUME=UUID=aa9acb18-b692-4020-9811-d58e5c8b8857 InstallationDate: Installed on 2017-10-06 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03a1 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Timi TM1607 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB200P0100 dmi.board.asset.tag: Any dmi.board.name: TM1607 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB200P0100:bd05/07/2017:svnTimi:pnTM1607:pvr:rvnTimi:rnTM1607:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1607 dmi.sys.vendor: Timi ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1237725] Re: indicator-session-service crashed with SIGSEGV in g_strdup()
*** This bug is a duplicate of bug 1201659 *** https://bugs.launchpad.net/bugs/1201659 ** This bug is no longer a duplicate of bug 1230021 Gnome-Panel crashed after attempting to add a weather location on the clock applet ** This bug has been marked a duplicate of bug 1201659 gnome-panel crashed with SIGSEGV in gweather_location_equal() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1237725 Title: indicator-session-service crashed with SIGSEGV in g_strdup() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1237725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1230021] Re: Gnome-Panel crashed after attempting to add a weather location on the clock applet
*** This bug is a duplicate of bug 1201659 *** https://bugs.launchpad.net/bugs/1201659 ** This bug has been marked a duplicate of bug 1201659 gnome-panel crashed with SIGSEGV in gweather_location_equal() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1230021 Title: Gnome-Panel crashed after attempting to add a weather location on the clock applet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1230021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180554] Re: gnome-panel buttons maximice minimizer and close sometimes stop working... ubuntu 13.04
*** This bug is a duplicate of bug 1158267 *** https://bugs.launchpad.net/bugs/1158267 ** This bug has been marked a duplicate of bug 1158267 Regression: Broken (click-through) window decoration on some maximized windows -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180554 Title: gnome-panel buttons maximice minimizer and close sometimes stop working... ubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1180554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078767] Re: lbzip2 crashed with error "retrieve.c:275: YBdec_retrieve: Assertion `in_avail >= 1' failed."
I don't think it will be ever fixed as only severe bugs and security vulnerabilities are generally fixed in stalbe releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078767 Title: lbzip2 crashed with error "retrieve.c:275: YBdec_retrieve: Assertion `in_avail >= 1' failed." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lbzip2/+bug/1078767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1078767] Re: lbzip2 crashed with error "retrieve.c:275: YBdec_retrieve: Assertion `in_avail >= 1' failed."
As upstream maintainer and Debian package maintainer I can confirm this was fixed in 2.2. Fixed version (2.2) is available in current stable release (quantal), but Ubuntu 12.04 (precise) is still affected. I don't maintain this package in Ubuntu, nor I know Ubuntu update policies, but If maintainers are interested in fixing this I can work on a patch. ** Changed in: lbzip2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1078767 Title: lbzip2 crashed with error "retrieve.c:275: YBdec_retrieve: Assertion `in_avail >= 1' failed." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lbzip2/+bug/1078767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969860] Re: [fglrx] compiz uses 100% CPU when screen turns off (spinning in glXWaitVideoSyncSGI or glXSwapBuffers)
Same bug (AMD A8-3510MX). Workaround from first post worked for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969860 Title: [fglrx] compiz uses 100% CPU when screen turns off (spinning in glXWaitVideoSyncSGI or glXSwapBuffers) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/969860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 849091] Re: Brightness resets on computer restart
Similar problem on HP probook 6465b running Ubuntu 12.04. Screen brightness and brightess setting resets to max afeter every reboot. Also, even thought I've set the screen to be turned off after 3 min idling, it's not. It only fades to black, but you can still see that the backlight is working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/849091 Title: Brightness resets on computer restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/849091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974205] Re: VA API doesn't work with fglrx driver from restricted repos
My Ubuntu 12.04 running on HP Probook 6465b is also affected. I managed to sort of fix it and get HW accelerated playback in VLC and mplayer by manualy putting "fglrx_drv_video.so" in /usr/lib/x86_64-linux-gnu/dri/. I took it from the package xvba-video_0.8.0-1_amd64.deb. HW accelerated playback is confirmed by vainfo and lower cpu usage. $ vainfo libva: VA-API version 0.32.0 Xlib: extension "XFree86-DRI" missing on display ":0.0". libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/x86_64-linux-gnu/dri/fglrx_drv_video.so libva: va_openDriver() returns 0 vainfo: VA-API version: 0.32 (libva 1.0.15) vainfo: Driver version: Splitted-Desktop Systems XvBA backend for VA-API - 0.8.0 vainfo: Supported profile and entrypoints VAProfileH264High : VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD $ fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon HD 6620G OpenGL version string: 4.2.11627 Compatibility Profile Context -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/974205 Title: VA API doesn't work with fglrx driver from restricted repos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/974205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 565528] Re: cairo-clock crashes on start
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/44617348/Dependencies.txt -- cairo-clock crashes on start https://bugs.launchpad.net/bugs/565528 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 565528] [NEW] cairo-clock crashes on start
Public bug reported: Binary package hint: cairo-clock $ cairo-clock (cairo-clock:1772): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (cairo-clock:1772): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated (cairo-clock:1772): libglade-WARNING **: could not find a parent that handles internal children for `vbox' Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: cairo-clock 0.3.4-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Sat Apr 17 20:47:23 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100406.1) ProcEnviron: LANG=pl_PL.utf8 SHELL=/bin/bash SourcePackage: cairo-clock ** Affects: cairo-clock (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- cairo-clock crashes on start https://bugs.launchpad.net/bugs/565528 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 525293] Re: gnome-about box crashes on start
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/39473910/Dependencies.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/39473911/XsessionErrors.txt -- gnome-about box crashes on start https://bugs.launchpad.net/bugs/525293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 525293] [NEW] gnome-about box crashes on start
Public bug reported:
$ gnome-about
/usr/share/themes/airlines/gtk-2.0/gtkrc:86: Murrine configuration option
"scrollbar_color" is no longer supported and will be ignored.
/usr/share/themes/airlines/gtk-2.0/gtkrc:91: Murrine configuration option
"gradients" is no longer supported and will be ignored.
Traceback (most recent call last):
File "/usr/bin/gnome-about", line 1040, in
about = GnomeAbout ()
File "/usr/bin/gnome-about", line 844, in __init__
self.create_ui ()
File "/usr/bin/gnome-about", line 923, in create_ui
info_labels = map (make_info_label, self.system_infos)
File "/usr/bin/gnome-about", line 914, in make_info_label
label.set_markup (_("%(name)s: %(value)s") % infos_dict)
KeyError: u'nazwa'
Problem: Crash
ProblemType: Bug
Architecture: i386
Date: Sun Feb 21 14:21:42 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: gnome-about 1:2.28.1-0ubuntu3
PackageArchitecture: all
ProcEnviron:
LANG=pl_PL.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
SourcePackage: gnome-desktop
Tags: ubuntu-unr
Uname: Linux 2.6.31-20-generic i686
** Affects: gnome-desktop (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 ubuntu-unr
--
gnome-about box crashes on start
https://bugs.launchpad.net/bugs/525293
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 360728] [NEW] Weather applet missing location: Lodz, Poland
Public bug reported: Ubuntu 9.04 beta libgweather Version: 2.26.0-0ubuntu1 Hi! The weather location database is missing Łódź, Poland, the third-largest city in Poland. http://en.wikipedia.org/wiki/%C5%81%C3%B3d%C5%BA http://www.flyhoward.com/AptSearch.aspx?Search=epll The entry missing from Locations.xml is: Łódź 51.721881 19.398133 Łódź EPLL 51.721881 19.398133 it works correctly for me. Thanks. ** Affects: libgweather (Ubuntu) Importance: Undecided Status: New -- Weather applet missing location: Lodz, Poland https://bugs.launchpad.net/bugs/360728 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
