[Bug 1853022] Re: shim-signed package can not be configured on Lenovo Yoga C630 WOS
Isn't these ARM laptops is only aarch64 devices that need signed shim to boot with enabled Secure Boot? Maybe it's make sense to modify shim- signed package to not fail if UEFI variable can not be modified and throw warning message instead? I propose this because AFAIK this "UEFI variable writing" issue is not going anywhere anytime soon, and current version of the script prevent regular distribution upgrades because shim-signed package installation/upgrade will always fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853022 Title: shim-signed package can not be configured on Lenovo Yoga C630 WOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1853022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1708852] Re: Touchpad not detected
the click right and left touchpad is not function -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1708852 Title: Touchpad not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811496] Re: Make grub-ipxe work under UEFI
** Merge proposal linked: https://code.launchpad.net/~alkisg/ubuntu/+source/ipxe/+git/ipxe/+merge/376817 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811496 Title: Make grub-ipxe work under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipxe/+bug/1811496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811496] Re: Make grub-ipxe work under UEFI
I don't know if it helps, but I uploaded it as a merge proposal too: https://code.launchpad.net/~alkisg/ubuntu/+source/ipxe/+git/ipxe/+merge/376817 It'd be nice to have it fixed for Focal, yeah. The new LTSP supports UEFI clients, so many people will use it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811496 Title: Make grub-ipxe work under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipxe/+bug/1811496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856445] [NEW] Cannot import secret keys
Public bug reported: I exported secret keys by gpg --export-secret-keys --export-options backup >file and later tried to restore it by gpg --homedir . --import --import-options restore file but gpg just creates pubring.kbx, not secret keys are imported. To its output includes: gpg: key /: error sending to agent: No such file or directory gpg: error building skey array: No such file or directory gpg: Total number processed: 1 gpg: imported: 1 gpg: secret keys read: 1 Is there a workaround? Wouldn't it be easier just to backup ~/.gnupg /private-keys-v1.d directory and copy it to "homedir", if needed? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnupg 2.2.4-1ubuntu1.2 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Dec 15 11:05:39 2019 InstallationDate: Installed on 2019-07-08 (159 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnupg2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnupg2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856445 Title: Cannot import secret keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1856445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856446] [NEW] [SRU] libreoffice 6.3.4 for eoan
Public bug reported: [Impact] * LibreOffice 6.3.4 is in its fourth bugfix release of the 6.3 line. Version 6.3.4 is currently in focal. For a list of fixed bugs compared to 6.3.3 see the list of bugs fixed in the two release candidates: https://wiki.documentfoundation.org/Releases/6.3.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.3.4/RC2#List_of_fixed_bugs (that's a total of 126 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 126 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Affects: libreoffice (Ubuntu) Importance: High Assignee: Marcus Tomlinson (marcustomlinson) Status: New ** Affects: libreoffice (Ubuntu Eoan) Importance: High Assignee: Marcus Tomlinson (marcustomlinson) Status: New ** Also affects: libreoffice (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: libreoffice (Ubuntu Eoan) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: libreoffice (Ubuntu Eoan) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856446 Title: [SRU] libreoffice 6.3.4 for eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1856446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo
Hi there, Seems like I resolved my issue which is the same as this one by upgrading firmware on BIOS from F13 to F14. Mi motherboard is GIGABYTE B360 HD3(https://www.gigabyte.com/Motherboard/B360-HD3-rev-10#kf). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856431] Re: Snap and dangling symlinks
** Package changed: ubuntu => snapd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856431 Title: Snap and dangling symlinks To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1856431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811496] Re: Make grub-ipxe work under UEFI
Another issue was that 20_ipxe didn't call save_default_entry, to save the selected grub entry for subsequent reboots. Since it was only a 2-line diff in the same spot, I added it as a second commit. I also built the package in https://code.launchpad.net/~ts.sch.gr/+recipe/ipxe in case anyone needs it for previous Ubuntu versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811496 Title: Make grub-ipxe work under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipxe/+bug/1811496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856448] [NEW] Hardware keyboard does not work on resume after suspend
Public bug reported: Steps to reproduce: 1. Login to Ubuntu and use apps, e.g. I was using Firefox and Visual Studio Code 2. Close the laptop lid (note that I did not power down or close apps prior to closing lid) 3. Some time later...open the laptop lid *** Keyboard does not respond - i.e. I can't type my password into the login field *** Trackpad works fine. Touchscreen and "soft keyboard" work fine. *** If I restart ubuntu logging in, the keyboard starts working fine. While searching for a resolution to this problem, I found this StackExchange question which describes a similar problem on a similar type of laptop - Dell Inspiron. https://askubuntu.com/questions/1171931/keyboard-no-longer-works- intermittently-after-suspend-18-04-dell-inspiron-13 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-37-generic 5.0.0-37.40~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 13:13:12 2019 InstallationDate: Installed on 2019-12-13 (1 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856448 Title: Hardware keyboard does not work on resume after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1856448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1513914] Re: Dell E7440 touchpad jumps position
The same issue on the following 2 setups: 1. xubuntu 18.04, linux 4.15.0-72-generic 2. xubuntu 19.04, linux 5.0.0-37-generic Dell BIOS A27 (date: 31.10.2018) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1513914 Title: Dell E7440 touchpad jumps position To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1513914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
Here's an update. The problem persists with 5.3.0.24 (and with Pop_os 5.3.0-7625). However, I have noticed that after a few days of use, without any further change, the problem disappears. Until I boot to Windows. After that, the problem appears again, stronger than ever. Now this may explain a couple of observations. Maybe the problem is a result of some setting Windows does to the adapter through their driver, that persists when linux boots and doesn't work very well. Maybe once this setting is undone after a number of linux boot ups (and no windows), the problem goes away until Windows boots up and restarts the whole chain of events. Also maybe this explains why some people (who don't dual boot) don't have the issue at all. Sorry for the lack of technical description here. However the correlation between booting Windows and then Linux and the appearance of the problem is very strong. Whether that correlation also means causation is left for the more technical people to address. 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/1848921 Title: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856347] Re: Tilix unable to open theme parsing error
I solve te issue editing
/usr/share/glib-2.0/schemas/com.gexperts.Tilix.gschema.xml
search
and replace the next line
${title}
with
'Default'
My file at the end looklike this:
'Default'
Save and
sudo glib-compile-schemas /usr/share/glib-2.0/schemas/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856347
Title:
Tilix unable to open theme parsing error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1856347/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853277] Re: Touchpad not showing up in /proc/bus/input/devices
Same issue on ThinkBook 14 IML, running Ubuntu 18.04. A quick test with Manjaro 18.1.3 showed the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Touchpad not showing up in /proc/bus/input/devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743027] Re: error loading realtime clock since upgrading to 17.10
I have this same problem on Ubuntu 19.10 on ThinkPad X1 Carbon 7th gen. sudo rtcwake -u -s 60 -m mem rtcwake: /dev/rtc0: unable to find device: No such file or directory -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743027 Title: error loading realtime clock since upgrading to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856452] [NEW] .desktop "Open with" UI menu is not consistent with other file types "Open with" UI menu.
Public bug reported: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) Right clicked on a .desktop file and then clicked "Open With Other Application". "Open With" menu should be consistent. 4) The "Open With" menu does not match the "Open With" menu displayed for other files. ** Affects: gnome-shell (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/1856452 Title: .desktop "Open with" UI menu is not consistent with other file types "Open with" UI menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855259] Re: apt broken by unattended upgrade in Ubuntu 19.10
I think I figured out a partial solution. I found a similar bug report here on Launchpad, Bug #1739991. I turned off Sophos real-time scanning, and I was able to successfully run 'sudo apt --fix-broken install'. It seems like there are multiple causes for this issue, but I hope this helps somewhat. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855259 Title: apt broken by unattended upgrade in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1855259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856438] Re: auto suggest previously used commands
This should be a feature request against the command line shell, not the terminal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856438 Title: auto suggest previously used commands To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1856438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856453] [NEW] Gimp crashed with a fatal error.
Public bug reported: ``` GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-8 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1) using GEGL version 0.4.14 (compiled against version 0.4.12) using GLib version 2.62.1 (compiled against version 2.58.1) using GdkPixbuf version 2.40.0 (compiled against version 2.38.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.42.3 (compiled against version 1.42.3) using Fontconfig version 2.13.1 (compiled against version 2.13.0) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Аварийный останов Stack trace: ``` /lib/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x397)[0x7fc4753e68c7] gimp-2.10(+0xd14a0)[0x555a2bb6f4a0] gimp-2.10(+0xd18d8)[0x555a2bb6f8d8] gimp-2.10(+0xd2037)[0x555a2bb70037] /lib/x86_64-linux-gnu/libpthread.so.0(+0x15540)[0x7fc4748f4540] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7fc4747323eb] /lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7fc474711899] /lib/x86_64-linux-gnu/libc.so.6(+0x25769)[0x7fc474711769] /lib/x86_64-linux-gnu/libc.so.6(+0x37006)[0x7fc474723006] /lib/x86_64-linux-gnu/libX11.so.6(+0x3f493)[0x7fc4745e7493] /lib/x86_64-linux-gnu/libX11.so.6(+0x3f53d)[0x7fc4745e753d] /lib/x86_64-linux-gnu/libX11.so.6(_XEventsQueued+0x5a)[0x7fc4745e783a] /lib/x86_64-linux-gnu/libX11.so.6(XPending+0x61)[0x7fc4745d9171] /lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0(+0x5c3ef)[0x7fc4754a73ef] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_check+0x1d1)[0x7fc474aa8471] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x519e2)[0x7fc474aa89e2] /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_loop_run+0x83)[0x7fc474aa8dc3] gimp-2.10(app_run+0x357)[0x555a2bb6ecb7] gimp-2.10(main+0x395)[0x555a2bb6e5b5] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0x7fc4747131e3] gimp-2.10(_start+0x2a)[0x555a2bb6e73a] ``` ** Affects: gimp (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/1856453 Title: Gimp crashed with a fatal error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1856453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854895] Re: touchpad stopped working after the update
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 ** Also affects: xorg-driver-synaptics 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/1854895 Title: touchpad stopped working after the update To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1854895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856439] Re: Add "Set Application as Default" to the "Open with Other Application" popup.
** Attachment added: "App-select.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1856439/+attachment/5312476/+files/App-select.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856439 Title: Add "Set Application as Default" to the "Open with Other Application" popup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1856439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 424561] Re: clicking out of 'rename' on playlist does not save name, only pressing 'enter'
Upstream report has moved to https://gitlab.gnome.org/GNOME/rhythmbox/issues/847 Still an issue in bionic and focal ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #847 https://gitlab.gnome.org/GNOME/rhythmbox/issues/847 ** Tags added: bionic focal ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #847 https://gitlab.gnome.org/GNOME/rhythmbox/issues/847 ** Changed in: rhythmbox Importance: Low => Unknown ** Changed in: rhythmbox Status: Expired => Unknown ** Changed in: rhythmbox Remote watch: GNOME Bug Tracker #603081 => gitlab.gnome.org/GNOME/rhythmbox/issues #847 ** Changed in: hundredpapercuts Status: Incomplete => Triaged ** Description changed: Binary package hint: rhythmbox - If you try to import or rename a playlist and then click-out, having written something, it is lost. - Clicking out should preserve what has been written, like clicking 'enter' + If you try to import or rename a playlist and then click-out, having + written something, it is lost. Clicking out should preserve what has + been written, like clicking 'enter'. + + Note that if you write the name and click elsewhere in the sidebar it + will rename correctly, but if you click in the music panel or the search + panel etc, the rename does not take effect and returns to the old + value/blank. ProblemType: Bug Architecture: i386 Date: Fri Sep 4 21:07:34 2009 DistroRelease: Ubuntu 9.10 Package: rhythmbox 0.12.4-1ubuntu1 ProcEnviron: - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-9.29-generic SourcePackage: rhythmbox Uname: Linux 2.6.31-9-generic i686 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/424561 Title: clicking out of 'rename' on playlist does not save name, only pressing 'enter' To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/424561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856452] Re: .desktop "Open with" UI menu is not consistent with other file types "Open with" UI menu.
** Attachment added: "open_with.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856452/+attachment/5312477/+files/open_with.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856452 Title: .desktop "Open with" UI menu is not consistent with other file types "Open with" UI menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856455] [NEW] Properties "Open with" UI menu is not consistent with select application "Open with" UI menu.
Public bug reported: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) "Open With" UI menus should be consistent. 4) Properties "Open With" UI menu does not match the Select Application "Open With" UI menu. ** Affects: gnome-shell (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/1856455 Title: Properties "Open with" UI menu is not consistent with select application "Open with" UI menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322980] Re: SRU rhythmbox 3.0.3 bugfix release
Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019. Closing as bug report is no longer valid. ** Changed in: rhythmbox (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322980 Title: SRU rhythmbox 3.0.3 bugfix release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1322980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856455] Re: Properties "Open with" UI menu is not consistent with select application "Open with" UI menu.
** Attachment added: "different_open_with.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856455/+attachment/5312493/+files/different_open_with.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856455 Title: Properties "Open with" UI menu is not consistent with select application "Open with" UI menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707193] Re: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'"
Workaround: Solved for me by using Generic Driver "Generic IPP Everywhere Printer" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1707193 Title: adding printer with IPP network printer via DNS-DS fails due to "There was an error during the CUPS operation: 'server-error-internal-error'" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1707193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
@vanvugt: I booted the latest 20.04 daily (which does contain the new pulseaudio package) and I confirm the behaviour is now back to "normal", which is to say to the 19.04 (and older) behaviour. So this is indeed fixed on Focal in my point of view. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 618345] Re: Music Playback goes on on Pause
Upstream bug has moved to https://gitlab.gnome.org/GNOME/rhythmbox/issues/961 Reproducible still in bionic and focal ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #961 https://gitlab.gnome.org/GNOME/rhythmbox/issues/961 ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #961 https://gitlab.gnome.org/GNOME/rhythmbox/issues/961 ** Changed in: rhythmbox Importance: Medium => Unknown ** Changed in: rhythmbox Status: Expired => Unknown ** Changed in: rhythmbox Remote watch: GNOME Bug Tracker #626985 => gitlab.gnome.org/GNOME/rhythmbox/issues #961 ** Tags added: bionic focal ** Description changed: Binary package hint: rhythmbox With Crossfading enabled a song can't be paused after starting fading out. (while the Player already show's the next song). + + The easiest way to reproduce this bug is to turn the crossfade on and + set the time to 60 seconds. Once the song gets to 60 seconds before the + end it starts the next song. Press pause. The song it is fading into + pauses but the one that is fading out now keeps playing until it is all + the way done. + + The expected behaviour would for both songs to stop and then for both to + resume when you press play again. ** Summary changed: - Music Playback goes on on Pause + Pausing while crossfading does not work correctly ** Description changed: Binary package hint: rhythmbox With Crossfading enabled a song can't be paused after starting fading out. (while the Player already show's the next song). The easiest way to reproduce this bug is to turn the crossfade on and set the time to 60 seconds. Once the song gets to 60 seconds before the end it starts the next song. Press pause. The song it is fading into pauses but the one that is fading out now keeps playing until it is all the way done. - The expected behaviour would for both songs to stop and then for both to - resume when you press play again. + The expected behaviour would be for both songs to stop and then for both + to resume when you press play again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/618345 Title: Pausing while crossfading does not work correctly To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/618345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313914] Re: Rhythmbox zeitgeist plugin doesn't activate when selected in Rhythmbox plugin preferences
As per Debian report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728532 in version 3.4.3-2 the zeitgist plugin has been removed as it is not compatible with python 3 ** Bug watch added: Debian Bug tracker #728532 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728532 ** Also affects: rhythmbox via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728532 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313914 Title: Rhythmbox zeitgeist plugin doesn't activate when selected in Rhythmbox plugin preferences To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1313914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856460] [NEW] [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at all
Public bug reported: I have a dual boot system with windows 10. In windows I don't find any problem but on Ubuntu the microphone doesn't seem to work or be recognized. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.3.16-050316-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 15:04:59 2019 InstallationDate: Installed on 2019-11-26 (19 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH failed Symptom_Type: No sound at all Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856460 Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856460/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856457] [NEW] Extreme low/high fan1 speed.
Public bug reported: 1) Ubuntu 19.10 2) sensors version 3.5.0 with libsensors version 3.5.0 3) Correct fan1 speed. 4) Sometimes fan1 low speed is -1. Sometimes fan1 high speed is 337500. ** Affects: lm-sensors (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/1856457 Title: Extreme low/high fan1 speed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1856457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856457] Re: Extreme low/high fan1 speed.
** Attachment added: "fan1_extreme_low.png" https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1856457/+attachment/5312494/+files/fan1_extreme_low.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856457 Title: Extreme low/high fan1 speed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1856457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856457] Re: Extreme low/high fan1 speed.
** Attachment added: "fan1_extreme_high.png" https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1856457/+attachment/5312495/+files/fan1_extreme_high.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856457 Title: Extreme low/high fan1 speed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1856457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856459] [NEW] Update FFmpeg to 3.4.7 in Bionic
*** This bug is a security vulnerability *** Public security bug reported: https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/n3.4.7:/Changelog version 3.4.7: - avcodec/g729dec: require buf_size to be non 0 - avcodec/alac: Fix integer overflow in lpc_prediction() with sign - avcodec/wmaprodec: Fix buflen computation in save_bits() - avcodec/vc1_block: Fix integer overflow in AC rescaling in vc1_decode_i_block_adv() - avcodec/vmdaudio: Check chunk counts to avoid integer overflow - avformat/mxfdec: Clear metadata_sets_count in mxf_read_close() - avcodec/nuv: Use ff_set_dimensions() - avcodec/ffwavesynth: Fix integer overflow with pink_ts_cur/next - avcodec/ralf: Fix integer overflows with the filter coefficient in decode_channel() - avcodec/g729dec: Use 64bit and clip in scalar product - avcodec/mxpegdec: Check for multiple SOF - avcodec/nuv: Move comptype check up - avcodec/wmavoice: Fix integer overflow in synth_frame() - avcodec/rawdec: Check bits_per_coded_sample more pedantically for 16bit cases - avutil/lfg: Correct index increment type to avoid undefined behavior - avcodec/cngdec: Remove AV_CODEC_CAP_DELAY - avcodec/iff: Move index use after check in decodeplane8() - avcodec/atrac3: Check for huge block aligns - avcodec/ralf: use multiply instead of shift to avoid undefined behavior in decode_block() - avcodec/wmadec: Require previous exponents for reuse - avcodec/vc1_block: Fix undefined behavior in ac prediction rescaling - avcodec/qdm2: The smallest header seems to have 2 bytes so treat 1 as invalid - avcodec/apedec: Fixes integer overflow of res+*data in do_apply_filter() - avcodec/sonic: Fix integer overflow in predictor_calc_error() - avformat/mp3dec: Check that the frame fits within the probe buffe - lavc/tableprint_vlc: Remove avpriv_request_sample() from included files. - avcodec/wmaprodec: get frame during frame decode - avcodec/interplayacm: Fix overflow of last unused value - avcodec/adpcm: Fix undefined behavior with negative predictions in IMA OKI - avcodec/cook: Move up and extend block_align check - avcodec/twinvq: Check block_align - avcodec/cook: Enlarge gain table - avcodec/cook: Check samples_per_channel earlier - avcodec/atrac3plus: Check split point in fill mode 3 - avcodec/wmavoice: Check sample_rate - avcodec/xsubdec: fix overflow in alpha handling - avcodec/iff: Check available space before entering loop in decode_long_vertical_delta2() / decode_long_vertical_delta() - avcodec/apedec: Fix integer overflow in filter_3800() - avutil/lfg: Document the AVLFG struct - avcodec/ffv1dec: Use a different error message for the slice level CRC - avcodec/apedec: Fix undefined integer overflow in long_filter_ehigh_3830() - avcodec/dstdec: Check that AC probabilities are within range - avcodec/dstdec: Check read_table() for failure - avcodec/snowenc: Set mb_num to avoid ratecontrol floating point divisions by 0.0 - avcodec/snowenc: Fix 2 undefined shifts - avformat/nutenc: Do not pass NULL to memcmp() in get_needed_flags() - avcodec/aacdec_template: Check samplerate - avcodec/truemotion2: Fix several integer overflows in tm2_low_res_block() - avcodec/utils: Check block_align - avcodec/wmalosslessdec: Fix some integer anomalies - avcodec/adpcm: Fix invalid shifts in ADPCM DTK - avcodec/apedec: Only clear the needed buffer space, instead of all - avcodec/libvorbisdec: Fix insufficient input checks leading to out of array reads - avcodec/g723_1dec: fix invalid shift with negative sid_gain - avcodec/vp5: Check render_x/y - avcodec/qdrw: Check input for header/skiped space before get_buffer() - avcodec/ralf: Skip initializing unused filter variables - avcodec/takdec: Fix overflow with large sample rates - avcodec/alsdec: Check that input space for header exists in read_diff_float_data() - avformat/pjsdec: Check duration for overflow - avcodec/ptx: Check that the input contains at least one line - avcodec/alac: Fix integer overflow in LPC - avcodec/smacker: Fix integer overflows in pred[] in smka_decode_frame() - avcodec/aliaspixdec: Check input size against minimal picture size - avcodec/ffwavesynth: Fix integer overflows in pink noise addition - avcodec/vc1_block: Fixes integer overflow in vc1_decode_i_block_adv() - avcodec/wmalosslessdec: Check block_align - avcodec/g729postfilter: Fix left shift of negative value - avcodec/binkaudio: Check sample rate - avcodec/adpcm: Check initial predictor for ADPCM_IMA_EA_EACS - avcodec/g723_1dec: Fix overflow in shift - avcodec/apedec: Fix integer overflow in predictor_update_3930() - avcodec/g729postfilter: Fix undefined intermediate pointers - avcodec/g729postfilter: Fix undefined shifts - avcodec/lsp: Fix undefined shifts in lsp2poly() - avcodec/adpcm: Fix left shifts in AV_CODEC_ID_ADPCM_EA - avformat/shortendec: Check k in probe - avfilter/vf_geq: Use av_clipd() instead of av_clipf() - avcodec/wmaprodec: Check that the streams channels do not exceed the overall channels - avcodec/qdmc: Check input space in qdmc_get_vlc() - avcodec/pcm: Check b
[Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
Sounds good. I'm not sure if matters or not but, I'm now on Ubuntu 19.10. I'm seeing the exact same behavior as before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846090] Re: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad Screenpad support
I've got the same problem on ASUS Zenbook UX334FL. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846090 Title: Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad Screenpad support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856210] Re: bionic/linux-hwe: 5.3.0-25.27~18.04.2 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854762 packages: lrm: linux-restricted-modules-hwe main: linux-hwe meta: linux-meta-hwe signed: linux-signed-hwe phase: Testing phase-changed: Friday, 13. December 2019 21:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856210 Title: bionic/linux-hwe: 5.3.0-25.27~18.04.2 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856462] [NEW] scroll wheel first tick not registered
Public bug reported: I verified this bug appears consistently on 3 different computers running Ubuntu 19.10, and another one running Ubuntu 18.? (It happens on clean installs too, and even during the installation process when selecting the options like the language for example) The bug also happens on a clean install of Kubuntu 19.10, but only in some applications (for example google Chrome and Chromium) === Description of the bug In any application, the first scroll wheel tick is not taken into account. By "first tick" I mean : - the first time you try to use scroll wheel after launching the application - when you move the mouse cursor out of the application window, then move it back inside the window, and then try to use the scroll wheel === Steps to reproduce : 1. open a new terminal window 2. make sure that the terminal contains enough lines to let you scroll (for example write "ls -la" a few times to generate lines) 3. with a mouse, try to use the scroll wheel (be careful to only turn one tick): the first tick will not do anything, while the following ticks will scroll the content as expected 4. move the mouse cursor out of the window (without clicking anywhere) 5. move the mouse cursor back into the window (without clicking anywhere) 6. repeat step 3: the same behavior will happen (first scroll click won't work) Expected behavior: At steps 3 and 6, I would expect the content to scroll with the first scroll wheel tick Observed behavior: At steps 3 and 6, the first scroll wheel tick doesn't do anything, while the next ticks scroll the content as expected === Additional details In Ubuntu 19.10, I didn't find any application that doesn't have this bug (-> all applications seem to have it, for example the terminal, the settings window, gedit, ...) In Kubuntu 19.10 however, I found that most default applications (default text editor, terminal, settings window) are not affected by this bug, but other applications (for example google Chrome and Chromium, Visual Studio Code, ...) are affected. Other people already discussed about a similar behavior here: https://bbs.archlinux.org/viewtopic.php?id=223470 A workaround for this bug is to set the environment variable "GDK_CORE_DEVICE_EVENTS" to "1", but it is definitely not a solution. This workaround doesn't fix the bug in every application (for example in google Chrome and Chromium, and in Visual Studio code, this workaround doesn't work) ** 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/1856462 Title: scroll wheel first tick not registered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1856462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856203] Re: xenial/linux-azure: 4.15.0-1066.71 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 13. December 2019 15:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856203 Title: xenial/linux-azure: 4.15.0-1066.71 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846899] Re: X won't start at boot with either nvidia driver on GeForce GT 730 (bionic)
The video card in question has died... The machine wouldn't boot at all with the video card in the machine. So I think the bug report should be retired, not so much resolved as unresolvable. I can't collect any more data on the symptoms and I can't swear the problem wasn't an early indication of hardware failure. Thanks to all who had suggestions. I did manage to try the NVidia 430 driver before it died. It didn't work, but it had different symptoms. X wouldn't come up, but I could ctrl-alt-f1 to get to a command line and switch back to nouveau, instead of having to boot to command line. It was replaced with an even older card (GeForce 9500 GT), which also didn't work with the NVidia drivers, and had an unreliable fan, so I had to put an extra fan in the case until I got around to applying a crowbar to the notoriously tight wallet and get a brand new Radeon RX580. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846899 Title: X won't start at boot with either nvidia driver on GeForce GT 730 (bionic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856462] Re: scroll wheel first tick not registered
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1856462/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856462 Title: scroll wheel first tick not registered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1856462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 940841] Re: Acer Aspire One D255 Microphone not working
*** This bug is a duplicate of bug 723532 *** https://bugs.launchpad.net/bugs/723532 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (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/940841 Title: Acer Aspire One D255 Microphone not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/940841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1280999] Re: wrapper-2.0 crashed with SIGSEGV in gtk_menu_attach_to_widget()
i have change the driver of an ol' laptop, reboot and crash ... oh, i must think on Linus T. "famous Words" ;-) lsb_release -rd Description:Ubuntu 19.04 Release:19.04 apt-cache policy pkgname xfce4-panel xfce4-panel: Installiert: 4.13.4-1ubuntu1 Installationskandidat: 4.13.4-1ubuntu1 Versionstabelle: *** 4.13.4-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu disco/universe amd64 Packages 100 /var/lib/dpkg/status N: Paket pkgname kann nicht gefunden werden. ** Attachment added: "0bit file?" https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1280999/+attachment/5312501/+files/crash.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1280999 Title: wrapper-2.0 crashed with SIGSEGV in gtk_menu_attach_to_widget() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1280999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856463] Re: Network selection menu shows a different wireless signal strength than the menu bar, so one is wrong.
gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856463 Title: Network selection menu shows a different wireless signal strength than the menu bar, so one is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1856463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856463] [NEW] Network selection menu shows a different wireless signal strength than the menu bar, so one is wrong.
Public bug reported: When I noticed the Menu bar showed a medium connection strength, I opened up the network menu in Settings. Settings showed a strong connection strength. This inconsistency is a bug in itself and one of the two are wrong. You can see both the menu bar and system settings claiming two different strengths if you look at their icons in the attached screenshots. I expect the system settings and the menu bar to be consistent on wi-fi strength However, in actuality, one is claiming a medium strength connection, the other a stronger one, for the same network, which is NETGEAR18. Because I am unsure of what is actually correct, I filed this under the network manager messing up. Network manager, the menu bar, and system settings appear to be out of sync. I reported this bug as soon as it happened. Description:Ubuntu 19.10 Release:19.10 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 11:38:18 2019 InstallationDate: Installed on 2019-11-20 (24 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "The screenshot I was referring to." https://bugs.launchpad.net/bugs/1856463/+attachment/5312502/+files/Screenshot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856463 Title: Network selection menu shows a different wireless signal strength than the menu bar, so one is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1856463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1609700] Re: username is not saved in openconnect connection dialog
I can also confirm the same bug is present in Ubuntu 19.10 with package network-manager 1.20.4-2ubuntu2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1609700 Title: username is not saved in openconnect connection dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856465] [NEW] Apport icon did not appear in gnome even though it was running and displaying windows.
Public bug reported: When I attempted to send a bug report for gnome-control-center via terminal, the Apport window appeared saying "Collecting information". However, the gnome side-dock did not display the apport logo at all, only the system monitor, systems-settings, and every other running program with windows being displayed. I expected the Apport icon to appear on the side-dock. It never did, and I was unable to see the report or send it as a result, except by opening Notifications and clicking "Ubuntu is ready". This issue occurred at around 11:54 AM, EDT, on December 15, 2019. Description:Ubuntu 19.10 Release:19.10 gnome-shell: Installed: 3.34.1+git20191024-1ubuntu1~19.10.1 Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1 Version table: *** 3.34.1+git20191024-1ubuntu1~19.10.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.34.1-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Dec 15 11:54:07 2019 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2019-11-20 (24 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Basically what the dock looked like." https://bugs.launchpad.net/bugs/1856465/+attachment/5312518/+files/Screenshot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856465 Title: Apport icon did not appear in gnome even though it was running and displaying windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856465/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855668] Comment bridged from LTC Bugzilla
--- Comment From naynj...@ibm.com 2019-12-15 12:11 EDT--- Daniel Axtens would be performing the testing and update the results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855668 Title: lockdown on power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1855668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855736] Re: Duplicity fails to start
** Changed in: duplicity Status: In Progress => Won't Fix ** Changed in: duplicity Status: Won't Fix => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1476736] Re: Crash in cairo-scaled-font.c:459: _cairo_scaled_glyph_page_destroy: Assertion `!scaled_font->cache_frozen' failed.
*** This bug is a duplicate of bug 1294699 *** https://bugs.launchpad.net/bugs/1294699 Hi everybody I vave installed Mathematica in Ubuntu-19.10, and I have the following problem Mathematica: cairo-scaled-font.c :459 : _cairo_scaled_glyph_page_destroy: l'assertion « !scaled_font->cache_frozen » a échoué. Aborted (core dumped) LinkConnect::linkc: -- Message text not found -- (LinkObject[i4d7w_shm, 3, 1]) How can I fixed this problem Regards Abdelmalek Boumali -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1476736 Title: Crash in cairo-scaled-font.c:459: _cairo_scaled_glyph_page_destroy: Assertion `!scaled_font->cache_frozen' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1476736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856469] [NEW] GIMP 2.10 Crashed retrieving photo from server
Public bug reported: ``` GNU Image Manipulation Program version 2.10.14 git-describe: GIMP_2_10_12-511-ga4f55d6c7e C compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-7 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) using babl version 0.1.72 (compiled against version 0.1.72) using GEGL version 0.4.18 (compiled against version 0.4.18) using GLib version 2.56.4 (compiled against version 2.56.4) using GdkPixbuf version 2.36.11 (compiled against version 2.36.11) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.40.14 (compiled against version 1.40.14) using Fontconfig version 2.12.6 (compiled against version 2.12.6) using Cairo version 1.15.10 (compiled against version 1.15.10) ``` > fatal error: Segmentation fault Stack trace: ``` # Stack traces obtained from PID 18688 - Thread 18688 # [New LWP 18690] [New LWP 18692] [New LWP 18693] [New LWP 18696] [New LWP 19672] [New LWP 19674] [New LWP 22675] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [34m---[34m[1m[regs] [0m [32mRAX:[0m 0xFE00 [32mRBX:[0m 0x0014 [32mRCX:[0m 0x7F4B2200E384 [32mRDX:[0m 0x0100 [1m[4m[31mo d I t s Z a P c [0m [32mRSI:[0m 0x7FFFE4FBA750 [32mRDI:[0m 0x0014 [32mRBP:[0m 0x7FFFE4FBA750 [32mRSP:[0m 0x7FFFE4FBA360 [32mRIP:[0m 0x7F4B2200E384 [32mR8 :[0m 0x [32mR9 :[0m 0x [32mR10:[0m 0x [32mR11:[0m 0x0246 [32mR12:[0m 0x0100 [32mR13:[0m 0x55FF7D0A54D0 [32mR14:[0m 0x [32mR15:[0m 0x4900 [32mCS:[0m 0033 [32mDS:[0m [32mES:[0m [32mFS:[0m [32mGS:[0m [32mSS:[0m 002B[0m [36m[0m[34m---[34m[1m[code] [0m=> 0x7f4b2200e384 <__libc_read+68>: cmprax,0xf000 0x7f4b2200e38a <__libc_read+74>: ja 0x7f4b2200e3c4 <__libc_read+132> 0x7f4b2200e38c <__libc_read+76>: movedi,r8d 0x7f4b2200e38f <__libc_read+79>: movQWORD PTR [rsp+0x8],rax 0x7f4b2200e394 <__libc_read+84>: call 0x7f4b2200e060 <__pthread_disable_asynccancel> 0x7f4b2200e399 <__libc_read+89>: movrax,QWORD PTR [rsp+0x8] 0x7f4b2200e39e <__libc_read+94>: addrsp,0x10 0x7f4b2200e3a2 <__libc_read+98>: poprbx [34m- [0m0x7f4b2200e384 in __libc_read (fd=0x14, buf=0x7fffe4fba750, nbytes=0x100) at ../sysdeps/unix/sysv/linux/read.c:27 Id Target Id Frame * 1Thread 0x7f4b26e3ee00 (LWP 18688) "gimp-2.10" 0x7f4b2200e384 in __libc_read (fd=0x14, buf=0x7fffe4fba750, nbytes=0x100) at ../sysdeps/unix/sysv/linux/read.c:27 2Thread 0x7f4b184c8700 (LWP 18690) "worker" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7f4b15b85700 (LWP 18692) "gmain" 0x7f4b21d20bf9 in __GI___poll (fds=0x55ff79cdd2a0, nfds=0x2, timeout=0x) at ../sysdeps/unix/sysv/linux/poll.c:29 4Thread 0x7f4b15384700 (LWP 18693) "gdbus" 0x7f4b21d20bf9 in __GI___poll (fds=0x55ff7ddd87d0, nfds=0x4, timeout=0x) at ../sysdeps/unix/sysv/linux/poll.c:29 5Thread 0x7f4af0ccf700 (LWP 18696) "async" syscall () at ../sysdeps/unix/sysv/linux/x86_64/sys
[Bug 1767817] Re: Full text search does not work
or since it has been posted as update? I should have it since I have the updated and upgraded my system? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767817 Title: Full text search does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856471] [NEW] package firmware-b43-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43-installer script pre-removal devolvió el código de salida de error 12
Public bug reported: no me reconoce la tarjeta de red ProblemType: Package DistroRelease: Ubuntu 19.10 Package: firmware-b43-installer 1:019-4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 AptOrdering: firmware-b43-installer:amd64: Purge b43-fwcutter:amd64: Purge NULL: ConfigurePending NULL: PurgePending NULL: ConfigurePending Architecture: amd64 Date: Sun Dec 15 12:02:31 2019 ErrorMessage: el subproceso instalado paquete firmware-b43-installer script pre-removal devolvió el código de salida de error 123 InstallationDate: Installed on 2019-12-14 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: b43-fwcutter Title: package firmware-b43-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43-installer script pre-removal devolvió el código de salida de error 123 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: b43-fwcutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856471 Title: package firmware-b43-installer 1:019-4 failed to install/upgrade: el subproceso instalado paquete firmware-b43-installer script pre-removal devolvió el código de salida de error 123 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1856471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800740] Re: /usr/share/applications/evolution-calendar.desktop Exec program 'evolution -c calendar' has not ben found in th PATH
This had affected me... I discovered this when starting menulibre, as a parse error. On diagnosis of my system, I was just going to remove evolution and reinstall it to to see if that fixed the problem... # sudo apt-get remove evolution Even though the evoltution-calendar.desktop file existed in my /usr/share/applications directory, the system (in fact) was correct in saying it couldn't find evolution in the run path... Because on my system (at least), the Evolution package was not installed. So: # sudo apt-get update # sudo apt-get install evolution evolution-ews Now menulibre parses evolution-calendar.desktop correctly on my system (and it shows in the Gnome Application Menu DropDown), because it is "now present" in the PATH on my system... (LOL) That was my work-around. On my guess of what happened to cause this for me on my old laptop?: I had installed Lubuntu 18.04 (32 bit), not 64 bit version like the OP... I had then installed Gnome 3 Desktop and Ubuntu Desktop... in ubuntu-desktop, while installing default apps of, I think it ommited the Evolution package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800740 Title: /usr/share/applications/evolution-calendar.desktop Exec program 'evolution -c calendar' has not ben found in th PATH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/menulibre/+bug/1800740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856428] Re: Disable TLS1.0, TLS 1.1, DTLS1.0
** Summary changed: - Raise minimum key requirements to 2k and disable TLS 1.0 and 1.1 + Disable TLS1.0, TLS 1.1, DTLS1.0 ** Description changed: - Raise minimum key requirements to 2k and disable TLS 1.0 and 1.1 + Disable TLS 1.0, TLS1.1, DTLS1.0 - As par of focal commitment, we shall raise minimum key requirements and - disable obsolete protocols by default. + As part of focal commitment, we shall disable obsolete protocols by + default. Users can override this behaviour with a config file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856428 Title: Disable TLS1.0, TLS 1.1, DTLS1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1856428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847514] Re: libssh-0.8 is detected as 0.7
** Also affects: libssh (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libssh (Ubuntu Bionic) Status: New => Confirmed ** Changed in: libssh (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/1847514 Title: libssh-0.8 is detected as 0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1847514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856475] [NEW] Battery icon is red when the laptop has 45% battery left; it should only turn red when it hits 10%
Public bug reported: Whenever the laptop is running on battery power, and the battery remaining is less than 50%, the battery icon on the Gnome Status Bar turns red. This should only happen if there is critically low battery; the red icon is a misnomer Expected results: Battery icon remains white until the battery hits 10% or lower Actual Results: Battery icon is red whenever the battery life is less than 50% or 30%. Description: Ubuntu 19.10 Release: 19.10 yaru-theme-gnome-shell: Installed: 19.10.4 Candidate: 19.10.4 Version table: *** 19.10.4 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu eoan/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: yaru-theme-gnome-shell 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Dec 15 14:05:05 2019 Dependencies: InstallationDate: Installed on 2019-11-20 (24 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Screenshot of the red icon when the battery is 43% charged" https://bugs.launchpad.net/bugs/1856475/+attachment/5312530/+files/Screenshot%20from%202019-12-15%2014-06-10.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856475 Title: Battery icon is red when the laptop has 45% battery left; it should only turn red when it hits 10% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1856475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856476] [NEW] can only write to root level of smb share
Public bug reported: I have a smb share with guest access set up on an OpenMediaVault box. >From a Windows 10 PC I can read and write the whole folder tree of this share, without password. On my Ubuntu box, I can do the same using smbclient, with null password. However when using Gnome Files to access the share, choosing "anonymous" connect, I can only create or write files in the top level folder. Attempts to create or write to a subfolder result in a "Permission denied" error. Reading works across the whole folder tree. The same happens when using the gio command line interface (here trying to create folders): $ gio list smb://herkules.local/gvfs-bug new1 $ gio mkdir smb://herkules.local/gvfs-bug/new2 $ gio list smb://herkules.local/gvfs-bug new1 new2 $ gio mkdir smb://herkules.local/gvfs-bug/new2/new-sub gio: smb://herkules.local/gvfs-bug/new2/new-sub: Permission denied $ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 15 18:31:16 2019 InstallationDate: Installed on 2014-08-03 (1960 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: gvfs UpgradeStatus: Upgraded to bionic on 2019-11-16 (29 days ago) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1856476 Title: can only write to root level of smb share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1856476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856478] Re: [Budgie 20.04] Terminal (tilix) does not start after system update.
** Attachment added: "com.gexperts.Tilix.gschema.xml-ERR" https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1856478/+attachment/5312539/+files/com.gexperts.Tilix.gschema.xml-ERR -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856478 Title: [Budgie 20.04] Terminal (tilix) does not start after system update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1856478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856478] [NEW] [Budgie 20.04] Terminal (tilix) does not start after system update.
Public bug reported:
summary:
About 4 days ago, there was a “system update” with a system restart.
After that, the terminal (tilix) will not start. No error message is
displayed.
usage environment:
Ubuntu Budgie 20.04 Daily (Japanese environment)
$ cat /var/log/installer/media-info
Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20191125)
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu Focal Fossa (development branch)"
$ uname -r
5.3.0-24-generic
---
$ tilix --version
バージョン
Tilix バージョン: 1.9.1
VTE バージョン: 0.58
GTK バージョン: 3.24.13
:
---
Details:
-> I installed the “gnome-terminal” app instead.
$ tilix
(tilix:10513): GLib-GIO-ERROR **: 23:24:53.608: Settings schema
'com.gexperts.Tilix.Keybindings' is not installed
Trace/breakpoint trap (コアダンプ)
---
Searched for similar bug reports:
[Don't core dump if a settings schema key is not found. #1234]
(https://github.com/gnunn1/tilix/issues/1234)
it's a little different. The following solution failed.
$ glib-compile-schemas /usr/share/glib-2.0/schemas/
/usr/share/glib-2.0/schemas/com.gexperts.Tilix.gschema.xml:207:1 Failed to
parse value of type “s”: 0:expected value. This entire file has been
ignored.
---
Correspondence:
I checked the xml file.
$ cd /usr/share/glib-2.0/schemas/
$ sudo cp com.gexperts.Tilix.gschema.xml com.gexperts.Tilix.gschema.xml-ERR
$ sudo gedit com.gexperts.Tilix.gschema.xml
Check around line 207:
205
206 ${title}
207 The default name to use for a session
Fix line 206:
206 '${title}'
-> overwrite save
$ sudo glib-compile-schemas /usr/share/glib-2.0/schemas/
$ tilix
-> “Tilix” has started.
$ ls -l com.gexperts.Tilix.gschema.xml*
-rw-r--r-- 1 root root 59791 12月 16 02:08 com.gexperts.Tilix.gschema.xml
-rw-r--r-- 1 root root 59789 12月 12 14:12 com.gexperts.Tilix.gschema.xml-ERR
-> The “/usr/share/glib-2.0/schemas/com.gexperts.Tilix.gschema.xml” file
was invalid. Please correct it. (Here is com.gexperts.Tilix.gschema.xml-
ERR.)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: tilix 1.9.3-3 [modified:
usr/share/glib-2.0/schemas/com.gexperts.Tilix.gschema.xml]
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu13
Architecture: amd64
CurrentDesktop: Budgie:GNOME
Date: Mon Dec 16 04:02:08 2019
InstallationDate: Installed on 2019-11-27 (18 days ago)
InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64
(20191125)
SourcePackage: tilix
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: tilix (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/1856478
Title:
[Budgie 20.04] Terminal (tilix) does not start after system update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1856478/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856475] Re: Battery icon is red when the laptop has 45% battery left; it should only turn red when it hits 10%
This seems a duplicate of #1854179 ** Changed in: yaru-theme (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856475 Title: Battery icon is red when the laptop has 45% battery left; it should only turn red when it hits 10% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1856475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1643706] Re: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs
Got my files in a common mount point /vol/media where all members of the family have access too (we share the same computer). No one should have to make a local copy of a family video in their respective /home directory to look at it. And it is a bit ridiculous that now, going forward, every mount points, including those that our on non-removable media, should be done in /media to get things to work. There are also businesses/schools that have mount points elsewhere, network mounts, hard coded at one location, on system where users do not have root access. And if you make use of the 'mount bind' workaround, then you hit the problem of file transfers and Trash not working anymore. Damn if you do, damn if you do not. Please introduce a configuration file. It is easy to implement, and leave us, users/administrators to decide to move away from the current default. Mount bind issue: https://unix.stackexchange.com/questions/406351 /mount-bind-in-the-same-filesystem-move-files-as-in-the-same-filesystem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643706 Title: snap apps need to be able to browse outside of user $HOME dir. for Desktop installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1643706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856479] [NEW] Document Viewer displays the first page on the right side instead of the left when I select "Dual" in the view menu, despite the PDF being multiple pages (more than 2)
Public bug reported: When I opened a PDF in Document Viewer, and then set the view mode to "dual", I noticed how the pdf application put the first page on the right side, which does not look as good as putting the page on the left side and page 2 on the right side. Steps to Reproduce: 1. Open the attached PDF in Document Viewer 2. Set the view to Dual 3. Notice the odd number page is to the right when it should be to the left by default. Description:Ubuntu 19.10 Release:19.10 evince: Installed: 3.34.1-1 Candidate: 3.34.1-1 Version table: *** 3.34.1-1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: evince 3.34.1-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Dec 15 14:42:04 2019 InstallationDate: Installed on 2019-11-20 (24 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "PDF used to reproduce the issue" https://bugs.launchpad.net/bugs/1856479/+attachment/5312540/+files/How%20the%20Border%20Crossed%20Us_%20Filling%20the%20Gap%20between%20Plume%20v.%20Sewar.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856479 Title: Document Viewer displays the first page on the right side instead of the left when I select "Dual" in the view menu, despite the PDF being multiple pages (more than 2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1856479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856479] Re: Document Viewer displays the first page on the right side instead of the left when I select "Dual" in the view menu, despite the PDF being multiple pages (more than 2)
** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1856479/+attachment/5312546/+files/Screenshot%20from%202019-12-15%2014-39-52.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856479 Title: Document Viewer displays the first page on the right side instead of the left when I select "Dual" in the view menu, despite the PDF being multiple pages (more than 2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1856479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1450947] Re: [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys have no effect
The bug still affects me on 18.04.3 LTS. I do not seem to have access to change to Confirmed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1450947 Title: [ThinkPad X60 - HDA Intel AD1981, playback] Volume Mute, Up, Down keys have no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1450947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855736] Re: Duplicity fails to start
I got that update, and things have changed a bit. usr/lib/python3/dist-packages$ python3 duplicity/dup_main.py returns nothing, which I think is what you wanted. But: /usr/lib/python3/dist-packages$ duplicity Traceback (most recent call last): File "/usr/bin/duplicity", line 55, in from duplicity.dup_main import main ImportError: No module named duplicity.dup_main (the same if I repeat the command from my home directory) Or: /usr/lib/python3/dist-packages$ duplicity/dup_main.py bash: duplicity/dup_main.py: Permission denied Or: sudo duplicity/dup_main.py [sudo] password for ...: sudo: duplicity/dup_main.py: command not found As you can tell, I've no idea what to try, or what's really going on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779942] Re: package python3-apt 1.6.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: packagekit (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/1779942 Title: package python3-apt 1.6.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1779942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799669] Re: package python3-louis 3.5.0-1ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: liblouis (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/1799669 Title: package python3-louis 3.5.0-1ubuntu0.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liblouis/+bug/1799669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856480] [NEW] "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu
Public bug reported: Whenever I attempt to print a document to a printer over the network, Ubuntu finds the printer and acts as if it is configured until I actually send a print job. When I do this, I get a message that says "Printing" in LibreOffice, but then nothing happens because the printers are not configured according to Ubuntu. I expected the document I sent over the network to print without issue. However, I am unable to on ubuntu because it is apparently not configured. Description:Ubuntu 19.10 Release:19.10 cups: Installed: 2.2.12-2ubuntu1 Candidate: 2.2.12-2ubuntu1 Version table: *** 2.2.12-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Dec 15 15:01:50 2019 InstallationDate: Installed on 2019-11-20 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lpstat: device for Officejet_Pro_8600_AB0C33_: ipp://HP843497AB0C33.local:631/ipp/printer Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 Papersize: letter ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Image of printing error" https://bugs.launchpad.net/bugs/1856480/+attachment/5312547/+files/Screenshot%20from%202019-12-15%2015-07-59.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856480 Title: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856481] [NEW] wifi printer
Public bug reported: i don't find my wifi printer ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-72.81~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Dec 15 21:08:14 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics Controller (primary) [1043:14e2] Subsystem: ASUSTeK Computer Inc. Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1043:14e2] InstallationDate: Installed on 2019-12-11 (3 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: ASUSTeK Computer Inc. F9E ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=1ad1cd83-1015-4efe-9a3e-7377f0d2e6e5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: F9E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr305:bd09/01/2008:svnASUSTeKComputerInc.:pnF9E:pvr1.0:rvnASUSTeKComputerInc.:rnF9E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: F9E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Dec 15 20:35:29 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856481 Title: wifi printer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855736] Re: Duplicity fails to start
To be clear, I'm now on version 0.8.09-0ubuntu0ppa1526~ubuntu19.10.1 (eoan) I rebooted after installing (just in case). I didn't purge beforehand, so I then did so, did an apt autoremove, and reinstalled it. No change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855736 Title: Duplicity fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1855736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856480] Re: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu
Printer port of OfficeJet: 650 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856480 Title: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856480] Re: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu
Correction: Port is 631, not 650. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856480 Title: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856480] Re: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856480 Title: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856463] modified.conffile..etc.apport.crashdb.conf.txt
apport information ** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt" https://bugs.launchpad.net/bugs/1856463/+attachment/5312587/+files/modified.conffile..etc.apport.crashdb.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856463 Title: Network selection menu shows a different wireless signal strength than the menu bar, so one is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1856463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856463] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1856463/+attachment/5312586/+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/1856463 Title: Network selection menu shows a different wireless signal strength than the menu bar, so one is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1856463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856463] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1856463/+attachment/5312583/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856463 Title: Network selection menu shows a different wireless signal strength than the menu bar, so one is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1856463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856463] modified.conffile..etc.apport.crashdb.conf.txt
apport information ** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt" https://bugs.launchpad.net/bugs/1856463/+attachment/5312584/+files/modified.conffile..etc.apport.crashdb.conf.txt ** Description changed: When I noticed the Menu bar showed a medium connection strength, I opened up the network menu in Settings. Settings showed a strong connection strength. This inconsistency is a bug in itself and one of the two are wrong. You can see both the menu bar and system settings claiming two different strengths if you look at their icons in the attached screenshots. I expect the system settings and the menu bar to be consistent on wi-fi strength However, in actuality, one is claiming a medium strength connection, the other a stronger one, for the same network, which is NETGEAR18. Because I am unsure of what is actually correct, I filed this under the network manager messing up. Network manager, the menu bar, and system settings appear to be out of sync. I reported this bug as soon as it happened. Description: Ubuntu 19.10 Release: 19.10 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 11:38:18 2019 InstallationDate: Installed on 2019-11-20 (24 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 GsettingsChanges: InstallationDate: Installed on 2019-11-20 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-11-20 (25 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: gnome-control-center 1:3.34.1-1ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + Tags: eoan + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856463 Title: Network selection menu shows a different wireless signal strength than the menu bar, so one is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1856463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856463] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1856463/+attachment/5312585/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856463 Title: Network selection menu shows a different wireless signal strength than the menu bar, so one is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1856463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856463] Re: Network selection menu shows a different wireless signal strength than the menu bar, so one is wrong.
apport information ** Tags added: apport-collected ** Description changed: When I noticed the Menu bar showed a medium connection strength, I opened up the network menu in Settings. Settings showed a strong connection strength. This inconsistency is a bug in itself and one of the two are wrong. You can see both the menu bar and system settings claiming two different strengths if you look at their icons in the attached screenshots. I expect the system settings and the menu bar to be consistent on wi-fi strength However, in actuality, one is claiming a medium strength connection, the other a stronger one, for the same network, which is NETGEAR18. Because I am unsure of what is actually correct, I filed this under the network manager messing up. Network manager, the menu bar, and system settings appear to be out of sync. I reported this bug as soon as it happened. Description: Ubuntu 19.10 Release: 19.10 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 11:38:18 2019 InstallationDate: Installed on 2019-11-20 (24 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + DisplayManager: gdm3 + DistroRelease: Ubuntu 19.10 + GsettingsChanges: + + InstallationDate: Installed on 2019-11-20 (25 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 + Tags: eoan + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1856463/+attachment/5312581/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856463 Title: Network selection menu shows a different wireless signal strength than the menu bar, so one is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1856463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856463] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1856463/+attachment/5312582/+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/1856463 Title: Network selection menu shows a different wireless signal strength than the menu bar, so one is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1856463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856482] [NEW] ubi-partman crashed
Public bug reported: While trying to install ubuntu 18.04 LTS, install failed with the message : ubi-partman crashed For information, I try to install it to erase a failed upgrade from ubuntu 19.04 to 19.10. I will try again to install ubuntu 18.04 LTS 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: Sun Dec 15 20:22:05 2019 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=fr_FR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1856482 Title: ubi-partman crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1856482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292438] Re: Can't connect to PulseAudio server
2020 and i am having the same issue with hdmi. tried uninstally pulseaudio, but then i don't have sound. any alternatives to pulseaudio? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292438 Title: Can't connect to PulseAudio server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1292438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856488] [NEW] Installing 18.04.3 from USB stick fails, unable to install grub
Public bug reported: Final part of install of Ubuntu 18.04.3 from USB stick fails. Installation was replacing broken 18.04 on dual Windows/Ubuntu system. uname -a (for installer) gives: Linux ubuntu 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Tried to running grub install manually: ubuntu@ubuntu:~$ sudo apt install grub-efi-amd64-signed Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: grub-efi-amd64-signed : Depends: grub-efi-amd64-bin (= 2.02+dfsg1-5ubuntu8) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Installing boot-repair from yannubuntu/boot-repair and running it was enough to make a bootable installation, but I don't know if anything else is missing from the install. 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 Date: Sun Dec 15 21:18:11 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) 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/1856488 Title: Installing 18.04.3 from USB stick fails, unable to install grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1856488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856489] [NEW] Need Way to Configure dockerd Proxy Settings
Public bug reported: I'm trying to use use the Docker snap behind an http proxy and I need a way to provide the proxy connection information to the Docker daemon. I found a forum topic ( https://forum.snapcraft.io/t/configure-proxy-to- be-used-by-dockerd/9647/11?u=zicklag ) that mentioned it being possible to patch the systemd service for the Docker snap and I have verified that that works, but it was brought up that a bug/issue should be reported about getting a snap config option for the proxy settings. Extra information: Ubuntu Version: Description:Ubuntu 18.04.3 LTS Release:18.04 Snap Version: docker 18.09.9423 stable ** 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/1856489 Title: Need Way to Configure dockerd Proxy Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker/+bug/1856489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856490] [NEW] Night light effect dissapears after screen dim
Public bug reported: hello, after screen goes off due to no user activity it turns back on without night light effect - no reddish color after opening settings and reenabling this feature, it goes back to work ps night light seems to break while dimming animation hits in - before dimming starts screen looses night light effect and immediately starts to dim ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..1d.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:1d:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 22:43:37 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-24-generic, x86_64: installed nvidia, 435.21, 5.3.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d1] InstallationDate: Installed on 2019-11-19 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. MS-7A32 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-25-generic root=UUID=5068e932-3f8c-4fd6-8003-574703a9a2f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.J0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X370 GAMING PRO CARBON (MS-7A32) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.J0:bd10/31/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX370GAMINGPROCARBON(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A32 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856490 Title: Night light effect dissapears after screen dim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856490/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856491] [NEW] after suspend system freezes for a while after mouting new device
Public bug reported: hello after resuming system from sleep two problems appears: (not sure if thats gnome bug) - after plugging in usb device (eg android phone) or mounting local drive ui freezes for a minute, mouse is working but ui doesnt react at all - wallpaper becomes pixel-crazy mess pc has to be suspended for longer time otherwise i couldnt reproduce these problems ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 22:55:27 2019 DisplayManager: lightdm InstallationDate: Installed on 2019-11-19 (26 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856491 Title: after suspend system freezes for a while after mouting new device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856492] [NEW] linux-generic-hwe-18.04=5.3.0.25.94 in bionic-proposed causes a conflict with virtualbox-guest-x11-hwe
Public bug reported: How to reproduce this bug? -- 1.) create a minimal ubuntu with debootstrap 2.) use this sources.list: deb http://de.archive.ubuntu.com/ubuntu bionic main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-security main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-updates main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-proposed main restricted universe multiverse deb http://de.archive.ubuntu.com/ubuntu bionic-backports main restricted universe multiverse deb http://archive.canonical.com/ubuntu bionic partner 3.) update package lists apt-get update 4.) install kernel 5.3.0 from bionic-proposed apt-get install linux-generic-hwe-18.04 5.) install virtualbox apt-get install virtualbox virtualbox-guest-x11-hwe virtualbox-ext-pack --- actual result: linux-generic-hwe-18.04 is being removed due to invalid dependencies expected result: linux-generic-hwe-18.04 keeps installed ** Affects: linux-meta-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: conflict linux-image virtualbox -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856492 Title: linux-generic-hwe-18.04=5.3.0.25.94 in bionic-proposed causes a conflict with virtualbox-guest-x11-hwe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1856492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855259] Re: apt broken by unattended upgrade in Ubuntu 19.10
Yes! I can't thank you enough. Sophos AV was the culprit. The following was able to get my system fully updated again: sudo systemctl stop sav-protect.service sudo apt --fix-broken install sudo apt update sudo apt full-upgrade sudo apt autoremove sudo systemctl start sav-protect.service I'll have to report this to Sophos. The reason for using Sophos was its on-demand scanning. If I have to permanently disable it to prevent it from breaking kernel updates, then that's far from ideal. I'll have to switch to a different AV product. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855259 Title: apt broken by unattended upgrade in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1855259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467716] Re: "gem install" fetches packages from unencrypted HTTP URL
On Bionic, the stock default sources are using HTTPS: $ gem environment | grep -A1 'REMOTE SOURCES' - REMOTE SOURCES: - https://rubygems.org/ So it's no longer required to create a /etc/gemrc or ~/.gemrc file. ** Changed in: ruby1.9.1 (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/1467716 Title: "gem install" fetches packages from unencrypted HTTP URL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ruby1.9.1/+bug/1467716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855259] Re: apt broken by unattended upgrade in Ubuntu 19.10
*** This bug is a duplicate of bug 1685984 *** https://bugs.launchpad.net/bugs/1685984 ** This bug has been marked a duplicate of bug 1685984 packages (multiple) failed to install/upgrade: unable to open 'x.dpkg-new': Operation not permitted -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855259 Title: apt broken by unattended upgrade in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1855259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856347] Re: Tilix unable to open theme parsing error
The work around is successful, but this still needs to be addressed for those don't want to edit schemas in the root file system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856347 Title: Tilix unable to open theme parsing error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tilix/+bug/1856347/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856495] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1856495/+attachment/5312682/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856495 Title: Gnome-power-manager throttles apps when the battery hits 50%, and sends a low power notification at 50%, instead of at 10% or lower. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1856495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856495] Re: Gnome-power-manager throttles apps when the battery hits 50%, and sends a low power notification at 50%, instead of at 10% or lower.
** Attachment added: "upower.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1856495/+attachment/5312681/+files/upower.txt ** Tags added: apport-collected ** Description changed: Simply, whenever the battery goes less than 50%, the apps start throttling, taking longer to respond, etc. This is likely the work of gnome-power-manager giving low battery notifications at 50% when it should be 10% or below. Model: Inspiron 5567 15 inch laptop gnome-power-manager: Installed: 3.32.0-1 Candidate: 3.32.0-1 Version table: *** 3.32.0-1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-power-manager 3.32.0-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 18:38:42 2019 InstallationDate: Installed on 2019-11-20 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.2 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-11-20 (25 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: upower 0.99.11-1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + Tags: eoan + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856495 Title: Gnome-power-manager throttles apps when the battery hits 50%, and sends a low power notification at 50%, instead of at 10% or lower. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1856495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856495] modified.conffile..etc.apport.crashdb.conf.txt
apport information ** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt" https://bugs.launchpad.net/bugs/1856495/+attachment/5312684/+files/modified.conffile..etc.apport.crashdb.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856495 Title: Gnome-power-manager throttles apps when the battery hits 50%, and sends a low power notification at 50%, instead of at 10% or lower. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1856495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856495] Re: Gnome-power-manager throttles apps when the battery hits 50%, and sends a low power notification at 50%, instead of at 10% or lower.
** Attachment added: "upower.log.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1856495/+attachment/5312680/+files/upower.log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856495 Title: Gnome-power-manager throttles apps when the battery hits 50%, and sends a low power notification at 50%, instead of at 10% or lower. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1856495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856495] [NEW] Gnome-power-manager throttles apps when the battery hits 50%, and sends a low power notification at 50%, instead of at 10% or lower.
Public bug reported: Simply, whenever the battery goes less than 50%, the apps start throttling, taking longer to respond, etc. This is likely the work of gnome-power-manager giving low battery notifications at 50% when it should be 10% or below. Model: Inspiron 5567 15 inch laptop gnome-power-manager: Installed: 3.32.0-1 Candidate: 3.32.0-1 Version table: *** 3.32.0-1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-power-manager 3.32.0-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 18:38:42 2019 InstallationDate: Installed on 2019-11-20 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-20 (25 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: upower 0.99.11-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160 ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected eoan ** Attachment added: "Remaining battery when this issue occurrred." https://bugs.launchpad.net/bugs/1856495/+attachment/5312675/+files/Screenshot%20from%202019-12-15%2018-44-13.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856495 Title: Gnome-power-manager throttles apps when the battery hits 50%, and sends a low power notification at 50%, instead of at 10% or lower. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1856495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856495] Re: Gnome-power-manager throttles apps when the battery hits 50%, and sends a low power notification at 50%, instead of at 10% or lower.
** Attachment added: "g-s-d-debug.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1856495/+attachment/5312679/+files/g-s-d-debug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856495 Title: Gnome-power-manager throttles apps when the battery hits 50%, and sends a low power notification at 50%, instead of at 10% or lower. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1856495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856495] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1856495/+attachment/5312683/+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/1856495 Title: Gnome-power-manager throttles apps when the battery hits 50%, and sends a low power notification at 50%, instead of at 10% or lower. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1856495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
