[Bug 2066986] [NEW] Crash on exit
Public bug reported: ``` GNU Image Manipulation Program version 2.10.36 git-describe: GIMP_2_10_36 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-13 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/libexec --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-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr --enable-offload-defaulted --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) # Libraries # using babl version 0.1.108 (compiled against version 0.1.108) using GEGL version 0.4.48 (compiled against version 0.4.48) using GLib version 2.80.0 (compiled against version 2.80.0) using GdkPixbuf version 2.42.10 (compiled against version 2.42.10) using GTK+ version 2.24.33 (compiled against version 2.24.33) using Pango version 1.52.1 (compiled against version 1.52.1) using Fontconfig version 2.15.0 (compiled against version 2.15.0) using Cairo version 1.18.0 (compiled against version 1.18.0) ``` > fatal error: Segmentation fault Stack trace: ``` /lib/x86_64-linux-gnu/libgimpbase-2.0.so.0(gimp_stack_trace_print+0x496)[0x73334159f2c6] /usr/bin/gimp-2.10(+0xecb41)[0x5e976867fb41] /usr/bin/gimp-2.10(+0xecf1c)[0x5e976867ff1c] /usr/bin/gimp-2.10(+0xecf75)[0x5e976867ff75] /lib/x86_64-linux-gnu/libc.so.6(+0x45320)[0x733340645320] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x97968)[0x733341697968] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(gtk_button_set_label+0x5d)[0x7333416989ed] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x261fa)[0x733340bf21fa] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_set_valist+0x1e6)[0x733340bf54b6] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_set+0xbd)[0x733340bf592d] /usr/bin/gimp-2.10(+0x13f445)[0x5e97686d2445] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x14a)[0x733340be12fa] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x4490c)[0x733340c1090c] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x35591)[0x733340c01591] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x41)[0x733340c017c1] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x93)[0x733340c01883] /usr/bin/gimp-2.10(gimp_container_remove+0xf3)[0x5e97689781b3] /usr/bin/gimp-2.10(+0x465f3c)[0x5e97689f8f3c] /usr/bin/gimp-2.10(gimp_container_clear+0x64)[0x5e9768977cf4] /usr/bin/gimp-2.10(+0x3e5fa5)[0x5e9768978fa5] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_unref+0x7e)[0x733340bf03fe] /usr/bin/gimp-2.10(+0x13d2de)[0x5e97686d02de] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x1f137)[0x733340beb137] /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x3c4e3)[0x733340abf4e3] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x2132b)[0x733340bed32b] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_object_run_dispose+0x34)[0x733340bf06c4] /usr/bin/gimp-2.10(+0x13ed5f)[0x5e97686d1d5f] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x14a)[0x733340be12fa] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x4490c)[0x733340c1090c] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x35591)[0x733340c01591] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x41)[0x733340c017c1] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x93)[0x733340c01883] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_closure_invoke+0x14a)[0x733340be12fa] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x4490c)[0x733340c1090c] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(+0x35591)[0x733340c01591] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit_valist+0x41)[0x733340c017c1] /lib/x86_64-linux-gnu/libgobject-2.0.so.0(g_signal_emit+0x93)[0x733340c01883] /lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0(+0x97b99)[0x733341697b99]
[Bug 1970957] Re: suspend problem
Lenovo ThinkPad X1 Yoga 1st, Intel® Core™ i7-6600U CPU @ 2.60GHz × 4 , with Mesa Intel® HD Graphics 520 (SKL GT2), does not resume after suspending or closing the lid. Various suggested tweaks to the login XDM, etc. don't appear to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970957 Title: suspend problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970686] [NEW] package mcollective-plugins-nettest 0.0.0~git20120507.df2fa81-0ubuntu2 failed to install/upgrade: installed mcollective-plugins-nettest package post-installation script subprocess
Public bug reported: I'm once again attempting to install Ubuntu. Once again it crashed. Once again I'm posting this to you: I'm trying to do a "clean installation of Ubuntu 22.04LTS I generally fail to be able to get Boinc-manager running under Ubuntu. Because of this I always fall back to using some other operating system - I'm currently using Zorin 16 64-bit, but usual end up using Linux Mint debian edition - which sometimes fails because it gets some piece of software I can't remove from my display, given that I am NOT even able to get BOINC to run on Ubuntu anything so far - it ran for years on my old computer (ASUS with an AMD processor with 8 cores running 4ghz/core), but my caretaker opted to take it to the dump when I wasn't able to get it to restart at some point because I mucked up its BIOS inadvertently... I'm NOT a programmer, but AM a bicyclist (person who regularly rides a bicycle?) and am geriatric (78 years old). I am in a retirement facility in Port Townsend, WA, which is an area that is 'proud' of the fact it's home to 'thousands' of "Rain gardens", many of which have signs to that effect sitting in them next to lawns,etc... My e.mail address is if you need to get hold of me. Thanks and Later, -Tim- (TBI = Traumatic Brain Injured - this would be because 20 years ago I managed to hit a herd of deer on my bicycle going through a corner at about 35mph (downhill corner that had several cars parked on the side of the (recently paved rural) road in Oregon, which put me into a hospital for about a year under the "Oregon Health Plan", which was terminated by the Federal Government because it was apparently an incursion on an area they hold to be Federal rather than "State" - subsequently I was taken over by the VA, which pays my rent in here in 'my' retirement facility, thankfully) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: mcollective-plugins-nettest 0.0.0~git20120507.df2fa81-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 27 19:12:53 2022 ErrorMessage: installed mcollective-plugins-nettest package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-04-28 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2 apt 2.4.5 SourcePackage: mcollective-plugins Title: package mcollective-plugins-nettest 0.0.0~git20120507.df2fa81-0ubuntu2 failed to install/upgrade: installed mcollective-plugins-nettest package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mcollective-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970686 Title: package mcollective-plugins-nettest 0.0.0~git20120507.df2fa81-0ubuntu2 failed to install/upgrade: installed mcollective-plugins-nettest package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mcollective-plugins/+bug/1970686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940900] Re: Grub failed boot detection - invalid enviroment block
Same issue here. Was a machine that I had not touched for several months. Booted it and after updating, got this error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940900 Title: Grub failed boot detection - invalid enviroment block To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1940900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955996] Re: gnome-shell uses excessive memory
I'm trying logging in with 'Ubuntu on Xorg'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955996 Title: gnome-shell uses excessive memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955996] [NEW] gnome-shell uses excessive memory
Public bug reported: I leave my computer running for days at a time. I noticed that gnome- shell was using something like 8-gigs of memory. I just kill the process on a regular basis. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 29 10:20:23 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-22 (706 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-10-19 (70 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955996 Title: gnome-shell uses excessive memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1955996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955355] [NEW] printer driver hangs when searching
Public bug reported: I installed a print driver and chose the wrong printer. If I open properties and click on change, it pops up a message saying 'searching for drivers' but hangs. I have to close the pop-up with X and it asks if I want to force close. The only way to change the driver is remove and start from scratch. Installed: 1.5.12-0ubuntu1.1 Candidate: 1.5.12-0ubuntu1.1 Version table: *** 1.5.12-0ubuntu1.1 500 500 http://mirror.cs.pitt.edu/ubuntu/archive focal-updates/main amd64 Packages 500 http://mirror.cs.pitt.edu/ubuntu/archive focal-updates/main i386 Packages 100 /var/lib/dpkg/status 1.5.12-0ubuntu1 500 500 http://mirror.cs.pitt.edu/ubuntu/archive focal/main amd64 Packages 500 http://mirror.cs.pitt.edu/ubuntu/archive focal/main i386 Packages ** 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/1955355 Title: printer driver hangs when searching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1955355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1940749] Re: Hardinfo 'storage' output not showing devices
Doug, I was informed by another user that he didn't see any other bug reports related to storage not populating. So I went ahead and submitted a report since it didn't work on both machines. As for that bug 1841037 - I was unaware of that bug until now. Other users have also concurred with what I found so I let it be. With all of that being said if this is indeed a duplicate then that should be noted appropriately so users aren't chasing around the same issue twice. I just checked the bug report 1841037 and the difference between 1841037 and mine is nothing actually populated in the Storage window for me which would be because I only have the nvme drive and I also noticed that a warning was thrown by hardinfo regarding the /cpu/procinfo "Flags" field being in excess of 896 characters. So I guess it's up to you and your colleagues who are working out the bugs to decide if this is indeed a duplicate. By all means identify it as such if you feel it's appropriate. Sincerely, Tim Brockway On Sun, Aug 22, 2021 at 5:00 PM Doug Smythies <1940...@bugs.launchpad.net> wrote: > Since you discovered that it is nvme drives that are not found, doesn't > that make this bug report a duplicate of bug #1841037? And read therein > that an update release is coming. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1940749 > > Title: > Hardinfo 'storage' output not showing devices > > Status in hardinfo package in Ubuntu: > Confirmed > > Bug description: > I installed Hardinfo on my Dell Inspiron 3501 running Ubuntu 20.04. I > installed hardinfo: > > sudo apt-get install -y hardinfo > > When I select 'Storage' in the GUI nothing populates. The pane/window > is totally blank. I have run hardinfo in the command line and I am > receiving the following error: > > Warning: truncated a line (probably flags list) longer than 896 bytes > while reading /proc/cpuinfo. > > Upon further inspection the 'Flags' field in /proc/cpuinfo is > populated with a large quantity of strings and characters. Therefore > this error is to be expected in my opinion. > > I just ran: > > sudo apt-get install --reinstall hardinfo > > This did not fix the issue with 'storage'. I have checked the other > "sections" of the GUI and all other portions of the output seem to be > functioning normally. I have also posted the link of the forum in > which I first reported the issue to the askubuntu community, where I > have detailed all the steps I have taken so far to attempt to fix the > issue. > > > https://askubuntu.com/questions/1359220/hardinfo-doesnt-display-anything-in-the-storage-section?noredirect=1#comment2328347_1359220 > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > DistributionChannelDescriptor: ># This is the distribution channel descriptor for the OEM CDs ># For more information see > http://wiki.ubuntu.com/DistributionChannelDescriptor >canonical-oem-somerville-focal-amd64-20200502-85 > DistroRelease: Ubuntu 20.04 > InstallationDate: Installed on 2021-07-02 (50 days ago) > InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary > 20200502-05:58 > Package: hardinfo 0.5.1+git20180227-2 > PackageArchitecture: amd64 > ProcVersionSignature: Ubuntu 5.10.0-1044.46-oem 5.10.46 > Tags: focal > Uname: Linux 5.10.0-1044-oem x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/hardinfo/+bug/1940749/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940749 Title: Hardinfo 'storage' output not showing devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hardinfo/+bug/1940749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1940749] Re: Hardinfo 'storage' output not showing devices
Hello Chris Guiver, I ran the apport command and sent the data, I hope it helped. Sincerely, Tim Brockway On Sun, Aug 22, 2021 at 12:20 AM Chris Guiver <1940...@bugs.launchpad.net> wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please execute the following command only once, as it > will automatically gather debugging information, in a terminal: > > apport-collect 1940749 > > When reporting bugs in the future please use apport by using 'ubuntu- > bug' and the name of the package affected. You can learn more about this > functionality at https://wiki.ubuntu.com/ReportingBugs. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1940749 > > Title: > Hardinfo 'storage' output not showing devices > > Status in hardinfo package in Ubuntu: > New > > Bug description: > I installed Hardinfo on my Dell Inspiron 3501 running Ubuntu 20.04. I > installed hardinfo: > > sudo apt-get install -y hardinfo > > When I select 'Storage' in the GUI nothing populates. The pane/window > is totally blank. I have run hardinfo in the command line and I am > receiving the following error: > > Warning: truncated a line (probably flags list) longer than 896 bytes > while reading /proc/cpuinfo. > > Upon further inspection the 'Flags' field in /proc/cpuinfo is > populated with a large quantity of strings and characters. Therefore > this error is to be expected in my opinion. > > I just ran: > > sudo apt-get install --reinstall hardinfo > > This did not fix the issue with 'storage'. I have checked the other > "sections" of the GUI and all other portions of the output seem to be > functioning normally. I have also posted the link of the forum in > which I first reported the issue to the askubuntu community, where I > have detailed all the steps I have taken so far to attempt to fix the > issue. > > https://askubuntu.com/questions/1359220/hardinfo-doesnt-display- > anything-in-the-storage-section?noredirect=1#comment2328347_1359220 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/hardinfo/+bug/1940749/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940749 Title: Hardinfo 'storage' output not showing devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hardinfo/+bug/1940749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940749] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1940749/+attachment/5519768/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940749 Title: Hardinfo 'storage' output not showing devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hardinfo/+bug/1940749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940749] Re: Hardinfo 'storage' output not showing devices
apport information ** Tags added: apport-collected focal ** Description changed: I installed Hardinfo on my Dell Inspiron 3501 running Ubuntu 20.04. I installed hardinfo: sudo apt-get install -y hardinfo When I select 'Storage' in the GUI nothing populates. The pane/window is totally blank. I have run hardinfo in the command line and I am receiving the following error: Warning: truncated a line (probably flags list) longer than 896 bytes while reading /proc/cpuinfo. Upon further inspection the 'Flags' field in /proc/cpuinfo is populated with a large quantity of strings and characters. Therefore this error is to be expected in my opinion. I just ran: sudo apt-get install --reinstall hardinfo This did not fix the issue with 'storage'. I have checked the other "sections" of the GUI and all other portions of the output seem to be functioning normally. I have also posted the link of the forum in which I first reported the issue to the askubuntu community, where I have detailed all the steps I have taken so far to attempt to fix the issue. - https://askubuntu.com/questions/1359220/hardinfo-doesnt-display- - anything-in-the-storage-section?noredirect=1#comment2328347_1359220 + https://askubuntu.com/questions/1359220/hardinfo-doesnt-display-anything-in-the-storage-section?noredirect=1#comment2328347_1359220 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-07-02 (50 days ago) + InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 + Package: hardinfo 0.5.1+git20180227-2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.10.0-1044.46-oem 5.10.46 + Tags: focal + Uname: Linux 5.10.0-1044-oem x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1940749/+attachment/5519766/+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/1940749 Title: Hardinfo 'storage' output not showing devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hardinfo/+bug/1940749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940749] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1940749/+attachment/5519767/+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/1940749 Title: Hardinfo 'storage' output not showing devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hardinfo/+bug/1940749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1940749] Re: Hardinfo 'storage' output not showing devices
Hello Ian, I posted an update in the bug report which states the following: HardInfo is a small application that displays information about your hardware and operating system. Currently it knows about PCI, ISA PnP, USB, IDE, SCSI, Serial and parallel port devices. The Processor is Intel(R) Pentium(R) Gold 7505 @ 2.00GHz x 4 and the Storage device is an SSD, BC711 NVMe SK hynix(128GB). I suspect hardinfo doesn't recognize the SSD and it doesn't like the extended flags in /proc/cpuinfo Otherwise hardinfo seems to function normally. Please let me know if anyone has an SSD that is being recognized and I will keep digging. Thank you Let me know if this is inaccurate. Sincerely, Tim On Sat, Aug 21, 2021 at 4:10 PM Ian Bruntlett <1940...@bugs.launchpad.net> wrote: > Hi, > > I tried this on my lenovo T420 laptop, running Ubuntu 20.04.3. > > The flags entry in /proc/cpuinfo is 100 characters long. > > I ran hardinfo (0.6-alpha) and checked the "Storage" pane and displayed > this (correct) info:- > > -SCSI Disks- > ATA CT1000MX500SSD1 > HL-DT-ST DVDRAM GT33N > > HTH, > > > Ian > > -- > -- ACCU - Professionalism in programming - http://www.accu.org > -- My writing - https://sites.google.com/site/ianbruntlett/ > -- Free Software page - > https://sites.google.com/site/ianbruntlett/home/free-software > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1940749 > > Title: > Hardinfo 'storage' output not showing devices > > Status in hardinfo package in Ubuntu: > New > > Bug description: > I installed Hardinfo on my Dell Inspiron 3501 running Ubuntu 20.04. I > installed hardinfo: > > sudo apt-get install -y hardinfo > > When I select 'Storage' in the GUI nothing populates. The pane/window > is totally blank. I have run hardinfo in the command line and I am > receiving the following error: > > Warning: truncated a line (probably flags list) longer than 896 bytes > while reading /proc/cpuinfo. > > Upon further inspection the 'Flags' field in /proc/cpuinfo is > populated with a large quantity of strings and characters. Therefore > this error is to be expected in my opinion. > > I just ran: > > sudo apt-get install --reinstall hardinfo > > This did not fix the issue with 'storage'. I have checked the other > "sections" of the GUI and all other portions of the output seem to be > functioning normally. I have also posted the link of the forum in > which I first reported the issue to the askubuntu community, where I > have detailed all the steps I have taken so far to attempt to fix the > issue. > > https://askubuntu.com/questions/1359220/hardinfo-doesnt-display- > anything-in-the-storage-section?noredirect=1#comment2328347_1359220 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/hardinfo/+bug/1940749/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940749 Title: Hardinfo 'storage' output not showing devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hardinfo/+bug/1940749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940749] Re: Hardinfo 'storage' output not showing devices
This is my flags list: Is it possible that this is causing the issue with Storage? I am not sure how to fix this because we purchased these Dell computers pre-installed with ubuntu 20.04. flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l2 invpcid_single cdp_l2 ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves split_lock_detect dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp hwp_pkg_req avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg avx512_vpopcntdq rdpid movdiri movdir64b fsrm avx512_vp2intersect md_clear flush_l1d arch_capabilities -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940749 Title: Hardinfo 'storage' output not showing devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hardinfo/+bug/1940749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940749] Re: Hardinfo 'storage' output not showing devices
I also installed hardinfo on my wife's Dell Inspiron 3501 running Ubuntu 20.04. I ran: sudo apt-get install -y hardinfo when I checked 'Storage' the pane/window is completely blank as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940749 Title: Hardinfo 'storage' output not showing devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hardinfo/+bug/1940749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940749] [NEW] Hardinfo 'storage' output not showing devices
Public bug reported: I installed Hardinfo on my Dell Inspiron 3501 running Ubuntu 20.04. I installed hardinfo: sudo apt-get install -y hardinfo When I select 'Storage' in the GUI nothing populates. The pane/window is totally blank. I have run hardinfo in the command line and I am receiving the following error: Warning: truncated a line (probably flags list) longer than 896 bytes while reading /proc/cpuinfo. Upon further inspection the 'Flags' field in /proc/cpuinfo is populated with a large quantity of strings and characters. Therefore this error is to be expected in my opinion. I just ran: sudo apt-get install --reinstall hardinfo This did not fix the issue with 'storage'. I have checked the other "sections" of the GUI and all other portions of the output seem to be functioning normally. I have also posted the link of the forum in which I first reported the issue to the askubuntu community, where I have detailed all the steps I have taken so far to attempt to fix the issue. https://askubuntu.com/questions/1359220/hardinfo-doesnt-display- anything-in-the-storage-section?noredirect=1#comment2328347_1359220 ** Affects: hardinfo (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/1940749 Title: Hardinfo 'storage' output not showing devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hardinfo/+bug/1940749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937019] [NEW] FIDO2 tokens not supported on this build
Public bug reported: I'm trying to test systemd-cryptenroll with FIDO2 keys in the new systemd version 248 on impish. Running "systemd-cryptenroll --fido2-device=list" results in the message: FIDO2 tokens not supported on this build. Would it be possible to build systemd with FIDO support in time for the impish release? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #991129 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991129 ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991129 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/1937019 Title: FIDO2 tokens not supported on this build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936257] [NEW] package mysql-server-8.0 (not installed) failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1
Public bug reported: lsb_release: Description:Ubuntu 20.04.2 LTS Release:20.04 apt-cache policy mysql mysql-server: Installed: (none) Candidate: 8.0.25-0ubuntu0.20.04.1 Version table: 8.0.25-0ubuntu0.20.04.1 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 8.0.19-0ubuntu5 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu focal/main i386 Packages Have been having issues with installing Apache, MySQL, PHPMyAdmin and PHP since yesterday. It has only now given me an error but I cannot show the stack trace as I just restarted my computer. MySQL I was unable to log in. PHP wasn't getting served in Apache and PHPMyAdmin was also not working. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 (not installed) ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jul 13 17:34:25 2021 ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-23 (21 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 (not installed) failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936257 Title: package mysql-server-8.0 (not installed) failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1936257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934183] [NEW] ARMHF Firefox crashes when receiving passwords via Firefox Sync
Public bug reported: Also tested on 20.04.2 LTS (GNU/Linux 5.10.34+ aarch64) on AWS. 1. Install ARMHF Firefox package (ARM64 and x8-64 packages work correctly). 2. Create new profile 3. Sign into Firefox Sync (with at least one password saved in sync account) 4. Within a few minutes Firefox crashes with a Segmentation Fault. If started with a synced profile, it is stable until a password is added or changed in the sync account by another instance of Firefox, after which it shortly crashes. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 89.0.2+build1-0ubuntu0.21.04.1 Uname: Linux 4.14.213-teb6 armv7l AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65.1 Architecture: armhf AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tim1338 F pulseaudio BuildID: 20210622155641 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Wed Jun 30 13:33:23 2021 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: default via 10.211.92.1 dev wlan0 proto static metric 600 10.211.92.0/24 dev wlan0 proto kernel scope link src 10.211.92.19 metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 Lspci: PciNetwork: Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:355 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=89.0.2/20210622155641 Profile0 - LastVersion=89.0.2/20210622155641 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2021-06-12 (18 days ago) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934183 Title: ARMHF Firefox crashes when receiving passwords via Firefox Sync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1934183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926225] Re: Maxima fails to start with error message "The assertion realpath(s, o) on line 471 of main.c in function mbin failed: Invalid argument Aborted (core dumped)"
I tried to compile the source code and it's broken too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926225 Title: Maxima fails to start with error message "The assertion realpath(s,o) on line 471 of main.c in function mbin failed: Invalid argument Aborted (core dumped)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1926225/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927725] Re: PID file no longer created
There seems to have been some issue during the upgrade that blocked the creation of the PID file. Manually killing the exim process and re- starting it seems to have fixed the issue. Apologies for the noise! ** Changed in: exim4 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927725 Title: PID file no longer created To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/1927725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927725] [NEW] PID file no longer created
Public bug reported: Since the latest release, no PID file is created in /run/exim4/exim.pid when Exim is run. No local configuration changes have been made between the working and non-working versions. The command line arguments are '/usr/sbin/exim4 -bd -q30m', and there are no PID-related configuration arguments set. Setting SMTPLISTENEROPTIONS='-oP /run/exim4/exim.pid' in /etc/default/exim produces the correct command-line arguments, but also does not create the specified PID file. I presume this is related to the fix for CVE-2020-28014: 'An attacker who obtained the privileges of the "exim" user can abuse the -oP override_pid_file_path option to create (or overwrite) an arbitrary file, as root'. If this new behaviour is intentional, then the documentation may need updating. This is on Ubuntu 20.04, exim version 4.93-13ubuntu1.5. Version 4.93-13ubuntu1.1 (released in May 2020) works correctly. Thanks! ** Affects: exim Importance: Unknown Status: Unknown ** Affects: exim4 (Ubuntu) Importance: Undecided Status: New ** Bug watch added: bugs.exim.org/ #2738 http://bugs.exim.org/show_bug.cgi?id=2738 ** Also affects: exim via http://bugs.exim.org/show_bug.cgi?id=2738 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/1927725 Title: PID file no longer created To manage notifications about this bug go to: https://bugs.launchpad.net/exim/+bug/1927725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923455] Re: fonts not rendering properly after update
Well, after a flurry of updates to mesa, vulkan and the amd graphics driver, the problem has gone away. This can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923455 Title: fonts not rendering properly after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923455/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923455] [NEW] fonts not rendering properly after update
Public bug reported: After a recent update, many fonts are no longer rendering properly. Only four characters will render for any text object. The problem is widespread, and appears to affect gtk programs, but gtk was not among the packages updated. As a control, I updated a laptop that I hadn't used in about a week, and no problems occurred on that computer. The biggest difference between the two computers is the presence of a Radeon graphics card in the affected machine (the laptop is using Intel). And graphics drivers are among the updated packages on the affected machine. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal Linux Thor 5.4.0-70-generic #78-Ubuntu SMP Fri Mar 19 13:29:52 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Extracted from /var/log/dpkg.log: 2021-04-11 08:23:51 upgrade libapt-pkg6.0:amd64 2.0.4 2.0.5 2021-04-11 08:23:52 upgrade apt:amd64 2.0.4 2.0.5 2021-04-11 08:23:54 upgrade apt-utils:amd64 2.0.4 2.0.5 2021-04-11 08:23:54 upgrade alsa-ucm-conf:all 1.2.2-1ubuntu0.5 1.2.2-1ubuntu0.6 2021-04-11 08:23:54 upgrade libdrm-common:all 2.4.104+git2103311700.6d8216~oibaf~f 2.4.105+git2104091700.991e95~oibaf~f 2021-04-11 08:23:54 upgrade libdrm2:i386 2.4.104+git2103311700.6d8216~oibaf~f 2.4.105+git2104091700.991e95~oibaf~f 2021-04-11 08:23:54 upgrade libdrm2:amd64 2.4.104+git2103311700.6d8216~oibaf~f 2.4.105+git2104091700.991e95~oibaf~f 2021-04-11 08:23:54 upgrade libdrm-amdgpu1:amd64 2.4.104+git2103311700.6d8216~oibaf~f 2.4.105+git2104091700.991e95~oibaf~f 2021-04-11 08:23:55 upgrade libdrm-amdgpu1:i386 2.4.104+git2103311700.6d8216~oibaf~f 2.4.105+git2104091700.991e95~oibaf~f 2021-04-11 08:23:55 upgrade libdrm-intel1:amd64 2.4.104+git2103311700.6d8216~oibaf~f 2.4.105+git2104091700.991e95~oibaf~f 2021-04-11 08:23:55 upgrade libdrm-intel1:i386 2.4.104+git2103311700.6d8216~oibaf~f 2.4.105+git2104091700.991e95~oibaf~f 2021-04-11 08:23:55 upgrade libdrm-nouveau2:i386 2.4.104+git2103311700.6d8216~oibaf~f 2.4.105+git2104091700.991e95~oibaf~f 2021-04-11 08:23:55 upgrade libdrm-nouveau2:amd64 2.4.104+git2103311700.6d8216~oibaf~f 2.4.105+git2104091700.991e95~oibaf~f 2021-04-11 08:23:55 upgrade libdrm-radeon1:amd64 2.4.104+git2103311700.6d8216~oibaf~f 2.4.105+git2104091700.991e95~oibaf~f 2021-04-11 08:23:55 upgrade libdrm-radeon1:i386 2.4.104+git2103311700.6d8216~oibaf~f 2.4.105+git2104091700.991e95~oibaf~f 2021-04-11 08:23:56 upgrade libegl-mesa0:amd64 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:23:56 upgrade libgbm1:amd64 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:23:56 upgrade libllvm12:amd64 1:12.0.0~++rc3-1~exp1~oibaf~f 1:12.0.0~++rc5-1~oibaf~f 2021-04-11 08:23:58 upgrade libllvm12:i386 1:12.0.0~++rc3-1~exp1~oibaf~f 1:12.0.0~++rc5-1~oibaf~f 2021-04-11 08:24:01 upgrade libgl1-mesa-dri:i386 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:02 upgrade libgl1-mesa-dri:amd64 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:03 upgrade libosmesa6:i386 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:04 upgrade libosmesa6:amd64 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:04 upgrade libglx-mesa0:i386 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:04 upgrade libglx-mesa0:amd64 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:05 upgrade libglapi-mesa:amd64 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:05 upgrade libglapi-mesa:i386 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:05 upgrade libgl1-mesa-dev:amd64 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:05 upgrade libgl1-mesa-glx:i386 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:05 upgrade libxatracker2:amd64 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:06 upgrade mesa-va-drivers:i386 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:06 upgrade mesa-va-drivers:amd64 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:07 upgrade mesa-vdpau-drivers:i386 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:07 upgrade mesa-vdpau-drivers:amd64 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:08 upgrade mesa-vulkan-drivers:i386 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:09 upgrade mesa-vulkan-drivers:amd64 21.1~git2103270600.b95c62~oibaf~f 21.1~git2104110600.ba8737~oibaf~f 2021-04-11 08:24:09 upgrade syncthing:amd64 1.14.0 1.15.1 ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added:
[Bug 1914961] [NEW] Contains literal path: /usr/lib/${DEB_HOST_MULTIARCH}
Public bug reported:
The libnss3 package contains a directory named
"/usr/lib/${DEB_HOST_MULTIARCH}", which is probably a mistake.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-41.46-lowlatency 5.8.18
Uname: Linux 5.8.0-41-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Sun Feb 7 12:27:15 2021
SourcePackage: nss
UpgradeStatus: Upgraded to groovy on 2020-11-20 (78 days ago)
** Affects: nss (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1914961
Title:
Contains literal path: /usr/lib/${DEB_HOST_MULTIARCH}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1914961/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884103] Re: Null pointer derefernce when iterating trees
** Changed in: python-pygit2 (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/1884103 Title: Null pointer derefernce when iterating trees To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pygit2/+bug/1884103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1854573/+attachment/5453684/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1854573/+attachment/5453681/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1854573/+attachment/5453682/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1854573/+attachment/5453680/+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/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1854573/+attachment/5453685/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1854573/+attachment/5453679/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1854573/+attachment/5453683/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1854573/+attachment/5453678/+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/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1854573/+attachment/5453677/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] Re: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken
apport information ** Tags added: apport-collected focal ** Description changed: If system call number -1 is called and the process is being traced with PTRACE_SYSCALL, for example by strace, the seccomp check is skipped and -ENOSYS is returned unconditionally (unless altered by the tracer), rather than carrying out action specified in the seccomp filter. The consequence of this is that it is not possible to reliably strace a seccomp based implementation of a foreign system call interface in which r7/x8 is permitted to be -1 on entry to a system call. I have traced this bug to commit f086f67485c5c126bcec4b0e96ac7319a2e59ab8 which attempts to implement PTRACE_SYSEMU. Contrary to x86-64 and the man ptrace page which states "For PTRACE_SYSEMU, continue and stop on entry to the next system call, which will not be executed.", on PTRACE_SYSEMU skips the current system call and stops on entry to the next system call. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1007-aws 5.3.0-1007.8 ProcVersionSignature: User Name 5.3.0-1007.8-aws 5.3.7 Uname: Linux 5.3.0-1007-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Sat Nov 30 13:38:28 2019 Ec2AMI: ami-0e88d70910be26319 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: a1.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: Upgraded to eoan on 2019-11-09 (21 days ago) + --- + ProblemType: Bug + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.14 + Architecture: arm64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + CRDA: N/A + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + Ec2AMI: ami-035df3cfe31bdea3b + Ec2AMIManifest: (unknown) + Ec2AvailabilityZone: eu-west-1c + Ec2InstanceType: t4g.nano + Ec2Kernel: unavailable + Ec2Ramdisk: unavailable + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lspci-vt: + -[:00]-+-00.0 Amazon.com, Inc. Device 0200 + +-01.0 Amazon.com, Inc. Device 8250 + +-04.0 Amazon.com, Inc. Device 8061 + \-05.0 Amazon.com, Inc. Elastic Network Adapter (ENA) + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Lsusb-t: + + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: + MachineType: Amazon EC2 t4g.nano + Package: linux-aws 5.4.0.1035.36 + PackageArchitecture: arm64 + PciMultimedia: + + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1035-aws root=UUID=fe13e7d5-0777-4e3b-9eaf-85a58e21fa9f ro console=ttyS0 nvme_core.io_timeout=4294967295 + ProcVersionSignature: Ubuntu 5.4.0-1035.37-aws 5.4.78 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-1035-aws N/A + linux-backports-modules-5.4.0-1035-aws N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal ec2-images + Uname: Linux 5.4.0-1035-aws aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 11/1/2018 + dmi.bios.vendor: Amazon EC2 + dmi.bios.version: 1.0 + dmi.board.asset.tag: i-05c89f713a209b22c + dmi.board.vendor: Amazon EC2 + dmi.chassis.asset.tag: Amazon EC2 + dmi.chassis.type: 1 + dmi.chassis.vendor: Amazon EC2 + dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd11/1/2018:svnAmazonEC2:pnt4g.nano:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: + dmi.product.name: t4g.nano + dmi.sys.vendor: Amazon EC2 ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1854573/+attachment/5453676/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908435] Re: Ubuntu Installation Failure With Formatted Disk
I was able to get ubuntu installed successfully using ZFS by doing an offline minimal installation both `Download Updates` and `Third Party Software` disabled. The installation was successful and Ubuntu booted ok. I have now switched my production desktop over to the new installation. I suspect the majority of the failures were due to `Third Party Software` option (https://bugs.launchpad.net/ubuntu- cdimage/+bug/1871268). As its possible that I got a false positive on the bug, I suggest that you close this ticket until I get time to do some playing around to see if drive formatting is actually an issue with current builds of ubiquity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908435 Title: Ubuntu Installation Failure With Formatted Disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1908435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908435] Re: Ubuntu Installation Failure With Formatted Disk
Update, my last 'successful' install failed because it looks like gparted did not completely nuke the drive and the installation did not boot up after it completed. At boot, I got the Busybox screen with no clear errors. When I pulled up the drive in Ubuntu live cd, the partitions were very odd sda1, sda2, sda5, sda6, sda7 and no sda3, or sda4. I used 'disks' utility to wipe all partitions and used `df` to verify that there were no partitions left on the disk and am now trying 20.04.1 install again... This is another failure mode of Ubuntu installer not really wiping the drive before before starting install; a 'successful' installation that does not boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908435 Title: Ubuntu Installation Failure With Formatted Disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1908435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908435] [NEW] Ubuntu Installation Failure With Formatted Disk
Public bug reported: Ubuntu Installer fails when trying to install on a Drive that is previously formatted by Ubuntu installer. I know this issue has been around for a long time but is there a way that the installer can detect a formatted drive automatically and if the usecase is to wipe the drive anyway, automatically format the drive before running any code that may fail due to the existing drive formatting? I can imagine this issue can be a real roadblock for newbies as when it fails as there are virtually no hints of why it is failing. Background: Today, I was installing Ubuntu 20.04 on an new computer I used a DVD I burned back in May of this year. The installer failed and it appears to have already formatted the drive at that point. I had assumed that the DVD may have been damaged so I downloaded 20.04.1 and burned a new DVD. When I installed, it failed again before I got to the final "install" button. I did let the system send the bug report up to the server at the time (about 13:00 EST). I have seen this issue before and it was related to the drive formatting causing the installer to bail so I used Ubuntu Live and gparted to delete any data on the drive. When I re-installed, it installed successfully. During all the above installations, I used the `Wipe drive and use ZFS` option. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: drive format installer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908435 Title: Ubuntu Installation Failure With Formatted Disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1908435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877668] Re: KDESVN Context Menu issue
This issue was resolved by installing `kde-plasma-desktop` which put in all the necessary libraries to get KDE apps working much better. This installation also fixed KFind and other KDE apps that I use. Note `kde-plasma-desktop` is huge and after installing and before restarting the computer run `sudo apt update`. If you don't run this update, may brick gnome on reboot making it a very tricky to get back up and running. I made this mistake the first time I installed 20.04 by rebooting without an `apt update`. My Gnome was pooched and I had to do a revert to a ZVN snapshot, which is never ideal as the revert will not fix files under your home which were modified by kde library installation leaving gnome working but in a sad place. If this happens, you would need to hand revert files in home that were modified during kde libs install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877668 Title: KDESVN Context Menu issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesvn/+bug/1877668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906555] [NEW] Aarch64 Ubuntu 18.04 version is incompatible with the version of the Erlang dependancy.
Public bug reported: When Elixir is installed using apt on 18.04, Elixir 1.3.3 is installed along with Erlang OTP version 20 as a dependency. Erlang OTP version 20 is too modern for Elixir 1.3.3 to work and so the package doesn't work. ** Affects: elixir-lang (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/1906555 Title: Aarch64 Ubuntu 18.04 version is incompatible with the version of the Erlang dependancy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elixir-lang/+bug/1906555/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1901962] Re: There’s a bug that causes artifact to build up on panel icons over time, causing them to become illegible. The bug has been in evidence since I started using Ubuntu Budgie in 18.
You asked me to submit the bug through the command line in the user forum. I did as requested as soon as I saw the message. This isn't a new issue. This is only follow-up from the old issue I reported on the user forum. I tested for presence of the problem and it appears to be fixed. Tim Methodology used for testing for the bug. Ignore if irrelevant: I removed the kludge of a panel restart startup item that masks the bug effects and logged in again. I then repeatedly generated events in my calendar to cause the notification area icon to display, connected to different strength WiFi networks, launched & closed various apps with notification tray icons. All of these would previously elicit notification area artifacts from the bug. None of these actions elicit the bug artifact anymore. As far as I can tell it's fixed. On Thu, Oct 29, 2020, 1:00 AM fossfreedom <1901...@bugs.launchpad.net> wrote: > This was fix and released by report #1898427 > > Note. You have that installed but you need to reboot since that was > installed. > > If this is still occurring after a reboot then there isn't anything more > we can do since it is looks like a new upstream issue ... the code is > identical to upstream. > > > ** Changed in: budgie-desktop (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1901962 > > Title: > There’s a bug that causes artifact to build up on panel icons over > time, causing them to become illegible. The bug has been in evidence > since I started using Ubuntu Budgie in 18.04 and has persisted in > 20.04. > > Status in budgie-desktop package in Ubuntu: > Incomplete > > Bug description: > I was told to do this:fossfreedom Ubuntu Budgie Team Member > September 15 > I have a fix now for 20.04 but I need a bug report to fix against! (also > @Gabb1995 since you have reported this at 19.10 as well) Please can you run > in a terminal: ubuntu-bug budgie-desktop This will create a bug report - > once I have uploaded the fix you will be pinged by a Canonical team member… > > This is in reference to: https://discourse.ubuntubudgie.org/t/panel- > artifact-and-kludge-to-fix-it/4053 > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: budgie-desktop 10.5.1-6ubuntu0.1 > ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 > Uname: Linux 5.4.0-48-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.10 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: Budgie:GNOME > Date: Wed Oct 28 19:18:15 2020 > InstallationDate: Installed on 2019-12-16 (317 days ago) > InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 > (20191017) > PackageArchitecture: all > SourcePackage: budgie-desktop > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1901962/+subscriptions > ** Changed in: budgie-desktop (Ubuntu) Status: Incomplete => 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/1901962 Title: There’s a bug that causes artifact to build up on panel icons over time, causing them to become illegible. The bug has been in evidence since I started using Ubuntu Budgie in 18.04 and has persisted in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1901962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901962] [NEW] There’s a bug that causes artifact to build up on panel icons over time, causing them to become illegible. The bug has been in evidence since I started using Ubuntu Budgie in 18.04
Public bug reported: I was told to do this: fossfreedom Ubuntu Budgie Team Member September 15 I have a fix now for 20.04 but I need a bug report to fix against! (also @Gabb1995 since you have reported this at 19.10 as well) Please can you run in a terminal: ubuntu-bug budgie-desktop This will create a bug report - once I have uploaded the fix you will be pinged by a Canonical team member… This is in reference to: https://discourse.ubuntubudgie.org/t/panel- artifact-and-kludge-to-fix-it/4053 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: budgie-desktop 10.5.1-6ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Wed Oct 28 19:18:15 2020 InstallationDate: Installed on 2019-12-16 (317 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: budgie-desktop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: budgie-desktop (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/1901962 Title: There’s a bug that causes artifact to build up on panel icons over time, causing them to become illegible. The bug has been in evidence since I started using Ubuntu Budgie in 18.04 and has persisted in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1901962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
For those approaching the issue from afresh it looks like HSP/HFP shares functionality with bluetooth modems rather than solely audio. As such there's a disagreement between pulseaudio who are only interested in the audio parts, ofono who deals with the modem parts and the bluetooth stack (bluez) who connect the to the hardware. The issue came about as support was dropped (assuming someone else would pick it up) as pulse audio and bluez went to later versions. It hasn't been resolved because no one wants to ether deal with the other part, or have another abstraction layer to switch between modem and audio functionality -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890508] [NEW] Installation of Ubuntu 20.04
Public bug reported: I'm not sure. I attempted to install it and it just had issues and didn't get anywhere. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 5 19:20:53 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890508 Title: Installation of Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1890508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884146] [NEW] .desktop file isn't valid
Public bug reported: The .desktop file that kate writes to ~/.local/share/applications produces errors when run through desktop-file-validate. The other side effect of this is that kate doesn't show up in the applications menu search but the desktop file does. Clicking on the desktop file just opens a text editor with desktop file as a source. ** Affects: kate (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/1884146 Title: .desktop file isn't valid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kate/+bug/1884146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884103] [NEW] Null pointer derefernce when iterating trees
Public bug reported:
Reproduce with:
git init t
cd t
mkdir x
touch x/y
git add x/y
git write-tree
python3 -c 'import pygit2; repo = pygit2.Repository(".");
next(iter(repo["7904c9b632eaca0cd04c4a30f4b50c994d434c9a"] / "x"))'
Fixed in upstream commit ccf4df153c68d4af7d3d0f4f4f9104afc6f38d43
** Affects: python-pygit2 (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/1884103
Title:
Null pointer derefernce when iterating trees
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pygit2/+bug/1884103/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883418] [NEW] location services not working
Public bug reported: I have allowed access on websites that I am trying to use and made sure that location services are enabled in settings, but the site does not have access to my location. Have tried google maps just to test, also doesn't have access to my location. I have also tested on a windows machine from the same router and it is working as expected. Seems to be an Ubuntu issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Jun 14 04:10:32 2020 InstallationDate: Installed on 2020-06-10 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883418 Title: location services not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1883418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876598] Re: octave does not link to openblas
I can confirm that the issue is not present in the Octave Flatpak, either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876598 Title: octave does not link to openblas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openblas/+bug/1876598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877668] [NEW] KDESVN Context Menu issue
Public bug reported: With KdeSVN 2.1.0 on Ubuntu 20.04, the context menu is not staying up when the user right clicks an item and instead eaither closes or sometimes automatically selects the first option in the context menu. The only way to use the context menu at present is to right click and hold and drag to the item to select. This was not the behavior with kdesvn on 18.04. ** Affects: kdesvn (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/1877668 Title: KDESVN Context Menu issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdesvn/+bug/1877668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866999] Re: gnome-calendar does not sync with Google Calendar
Same issue here. What is the best way o can help get this resolved? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866999 Title: gnome-calendar does not sync with Google Calendar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568459] Re: unison incompatible with older ubuntu/debian versions
Just as a note on recompiling, I have tried to build a statically-linked
binary on Ubuntu 19.10 (with OCaml 4.05.0) and run it on 20.04; it
yields the same errors as the dynamically-linked 19.10 binary when run
on 20.04:
Unison failed: Uncaught exception Failure("input_value: ill-formed message")
Raised at file "/tmp/unison-2.48.4/lwt/lwt.ml", line 135, characters 6-13
Called from file "list.ml", line 85, characters 12-15
Called from file "/tmp/unison-2.48.4/lwt/lwt.ml", line 31, characters 2-37
Called from file "/tmp/unison-2.48.4/lwt/lwt.ml" (inlined), line 83, characters
17-46
Called from file "/tmp/unison-2.48.4/lwt/generic/lwt_unix_impl.ml", line 55,
characters 6-23
Called from file "/tmp/unison-2.48.4/lwt/generic/lwt_unix_impl.ml", line 147,
characters 6-40
Called from file "/tmp/unison-2.48.4/main.ml", line 202, characters 6-24
Called from file "/tmp/unison-2.48.4/main.ml", line 131, characters 4-9
Perhaps someone more experienced with OCaml can add some insight.
I have added this information to the upstream bug report at
. We may need to open a
new bug, though, since this doesn't appear to be a packaging issue.
** Bug watch added: github.com/bcpierce00/unison/issues #334
https://github.com/bcpierce00/unison/issues/334
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568459
Title:
unison incompatible with older ubuntu/debian versions
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unison/+bug/1568459/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725649] Re: Fullscreen games lose "fullscreen" after an Alt+Tab
Bug is present in 20.04. Tested with Stellaris in fullscreen mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725649 Title: Fullscreen games lose "fullscreen" after an Alt+Tab To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1725649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863803] [NEW] Installer crashed
Public bug reported: Near the end of the install the Installer crashes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.14 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CasperVersion: 1.394.3 Date: Tue Feb 18 15:01:57 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) 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.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863803 Title: Installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1863803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863663] [NEW] installer crashed
Public bug reported: near the end of the install I get a screen saying that the installer crashed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.14 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CasperVersion: 1.394.3 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 17 11:54:47 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.14 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863663 Title: installer crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1863663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] Re: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken
** Also affects: linux (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/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860042] Re: openCL application gives error after update
The eoan-proposed repository didn't work for me. This is what apt-cache says: mesa-opencl-icd: Installed: 19.2.8-0ubuntu0~19.10.1 Candidate: 19.2.8-0ubuntu0~19.10.1 Version table: *** 19.2.8-0ubuntu0~19.10.1 500 500 http://ca.archive.ubuntu.com/ubuntu eoan-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 19.2.8-0ubuntu0~19.10.1~ppa1 500 500 http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu eoan/main amd64 Packages 19.2.1-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1860042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860042] Re: openCL application gives error after update
I fixed it myself. I'm going to try to get a merge request. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1860042] Re: openCL application gives error after update
I've upgraded to Ubuntu 19.10 and used the PPA that you recommended and the error is still there. I could give you a patch with the changes that I made to ac_rtld.c that fixed the problem for my computer. On Wed, Jan 22, 2020 at 5:35 AM Timo Aaltonen wrote: > could you test with a newer mesa from this ppa > > https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates > > it's got latest bugfix release of the series, 19.2.8, and it's now > pending as a distro update as well > > ** Changed in: mesa (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1860042 > > Title: > openCL application gives error after update > > Status in mesa package in Ubuntu: > Incomplete > > Bug description: > My OpenCL program was working normally until a software update. > > The program prints out: > > ac_rtld error: !s->is_rx > LLVM failed to upload shader > > when clEnqueueNDRangeKernel is called. > > I've downloaded the source for mesa and traced the problem to the > gallium radeon driver. The first error message is from > > mesa-19.2.1/src/amd/common/ac_rtld.c > > and the second error message is from > > mesa-19.2.1/src/gallium/drivers/radeonsi/si_compute.c > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: libllvm9 1:9-2~ubuntu18.04.1 > ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 > Uname: Linux 4.15.0-74-lowlatency x86_64 > ApportVersion: 2.20.9-0ubuntu7.9 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Thu Jan 16 14:35:15 2020 > InstallationDate: Installed on 2018-04-28 (628 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > SourcePackage: mesa-opencl-icd > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860042] Re: openCL application gives error after update
** Description changed: My OpenCL program was working normally until a software update. The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. I've downloaded the source for mesa and traced the problem to the - gallium radeon driver. + gallium radeon driver. The first error message is from + + mesa-19.2.1/src/amd/common/ac_rtld.c + + and the second error message is from + + mesa-19.2.1/src/gallium/drivers/radeonsi/si_shader.c + ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mesa-opencl-icd UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: My OpenCL program was working normally until a software update. The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. I've downloaded the source for mesa and traced the problem to the gallium radeon driver. The first error message is from mesa-19.2.1/src/amd/common/ac_rtld.c and the second error message is from - mesa-19.2.1/src/gallium/drivers/radeonsi/si_shader.c - + mesa-19.2.1/src/gallium/drivers/radeonsi/si_compute.c ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mesa-opencl-icd UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860042] Re: openCL application gives error after update
** Description changed: My OpenCL program was working normally until a software update. The log file (/var/log/apt/history.log) contains: Start-Date: 2020-01-16 12:48:13 Commandline: aptdaemon role='role-commit-packages' sender=':1.131' Install: libllvm9:amd64 (1:9-2~ubuntu18.04.1, automatic), libclang-common-9-dev: amd64 (1:9-2~ubuntu18.04.1, automatic) Upgrade: libdrm-nouveau2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1 ), libclc-amdgcn:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git20190827-1~u buntu18.04.1), libclc-dev:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git201 90827-1~ubuntu18.04.1), libclc-r600:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0. 2.0+git20190827-1~ubuntu18.04.1), libdrm-amdgpu1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), libdrm2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubunt u1~18.04.1), libdrm-intel1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04 .1), libdrm-radeon1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), li bdrm-dev:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), libdrm-common :amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1) End-Date: 2020-01-16 12:48:35 The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. - It could be in any one of the packages that were upgraded or installed. - I chose libllvm9 because of the error message. + I've downloaded the source for mesa and traced the problem to the + gallium radeon driver. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: llvm-toolchain-9 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - My OpenCL program was working normally until a software update. The log file (/var/log/apt/history.log) contains: - Start-Date: 2020-01-16 12:48:13 - Commandline: aptdaemon role='role-commit-packages' sender=':1.131' - Install: libllvm9:amd64 (1:9-2~ubuntu18.04.1, automatic), libclang-common-9-dev: - amd64 (1:9-2~ubuntu18.04.1, automatic) - Upgrade: libdrm-nouveau2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1 - ), libclc-amdgcn:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git20190827-1~u - buntu18.04.1), libclc-dev:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git201 - 90827-1~ubuntu18.04.1), libclc-r600:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0. - 2.0+git20190827-1~ubuntu18.04.1), libdrm-amdgpu1:amd64 (2.4.97-1ubuntu1~18.04.1, - 2.4.99-1ubuntu1~18.04.1), libdrm2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubunt - u1~18.04.1), libdrm-intel1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04 - .1), libdrm-radeon1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), li - bdrm-dev:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), libdrm-common - :amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1) - End-Date: 2020-01-16 12:48:35 + My OpenCL program was working normally until a software update. The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. I've downloaded the source for mesa and traced the problem to the gallium radeon driver. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) - SourcePackage: llvm-toolchain-9 + SourcePackage: mesa-opencl-icd UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860042] Re: openCL application gives error after update
** Package changed: llvm-toolchain-9 (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860199] [NEW] OpenCL programs give error messages
Public bug reported: OpenCL programs print ac_rtld error: !s->is_rx LLVM failed to upload shader when calling clEnqueueNDRangeKernel. lsb_release -rd displays: Description:Ubuntu 19.10 Release:19.10 apt-cache policy mesa-opencl-icd displays: mesa-opencl-icd: Installed: 19.2.1-1ubuntu1 Candidate: 19.2.1-1ubuntu1 Version table: *** 19.2.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mesa-opencl-icd 19.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.427 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 17 23:09:17 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] [1002:9874] (rev e1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Wani [Radeon R5/R6/R7 Graphics] [103c:82fe] LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Pavilion Desktop PC 570-p0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2017 dmi.bios.vendor: AMI dmi.bios.version: F.20 dmi.board.asset.tag: CNV7500FYH dmi.board.name: 82FE dmi.board.vendor: HP dmi.board.version: 11 dmi.chassis.asset.tag: CNV7500FYH dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.20:bd10/30/2017:svnHP:pnHPPavilionDesktopPC570-p0xx:pvr:rvnHP:rn82FE:rvr11:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion dmi.product.name: HP Pavilion Desktop PC 570-p0xx dmi.product.sku: Z5P18AA#ABL dmi.sys.vendor: HP 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.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 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mesa (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/1860199 Title: OpenCL programs give error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739805]
(In reply to haarp from comment #34) > Where are the settings to be found? I can't find anything new in the Power > Manager's setting screen. I ended up manually adding them with the settings > editor. With the patch applied, on the General tab of Xfce Power Manager, there should be a "Brightness step count" field and an "Exponential" checkbox next to it. > The exponential feature is really comfortable to use. However there's one > caveat. It starts too slow, so that the first 3 of 10 steps have pretty much > no effect at all. Is there a way to weigh it a little more towards the later > steps? I believe the effect of exponential steps is very much dependent on the characteristics of the LCD backlight. For my last two laptops, there are very visible differences between every step on the scale. Perhaps you can try reducing the number of steps to 6? Enlarging the step sizes towards the lower end complicates the maths quite a bit, and may not suit everyone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739805 Title: Backlight tuning has not enough steps To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-power-manager/+bug/1739805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860042] Re: openCL application gives error after update
** Description changed: My OpenCL program was working normally until a software update. The log file (/var/log/apt/history.log) contains: Start-Date: 2020-01-16 12:48:13 Commandline: aptdaemon role='role-commit-packages' sender=':1.131' Install: libllvm9:amd64 (1:9-2~ubuntu18.04.1, automatic), libclang-common-9-dev: amd64 (1:9-2~ubuntu18.04.1, automatic) Upgrade: libdrm-nouveau2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1 ), libclc-amdgcn:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git20190827-1~u buntu18.04.1), libclc-dev:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git201 90827-1~ubuntu18.04.1), libclc-r600:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0. 2.0+git20190827-1~ubuntu18.04.1), libdrm-amdgpu1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), libdrm2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubunt u1~18.04.1), libdrm-intel1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04 .1), libdrm-radeon1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), li bdrm-dev:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), libdrm-common :amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1) End-Date: 2020-01-16 12:48:35 - The program just prints out: + The program prints out: ac_rtld error: !s->is_rx LLVM failed to upload shader when clEnqueueNDRangeKernel is called. It could be in any one of the packages that were upgraded or installed. I chose libllvm9 because of the error message. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: llvm-toolchain-9 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-9/+bug/1860042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860042] Re: openCL application gives error after update
** Description changed: - My OpenCL program was working normally until a software update. The log file contains: + My OpenCL program was working normally until a software update. The log file (/var/log/apt/history.log) contains: Start-Date: 2020-01-16 12:48:13 Commandline: aptdaemon role='role-commit-packages' sender=':1.131' Install: libllvm9:amd64 (1:9-2~ubuntu18.04.1, automatic), libclang-common-9-dev: amd64 (1:9-2~ubuntu18.04.1, automatic) Upgrade: libdrm-nouveau2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1 ), libclc-amdgcn:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git20190827-1~u buntu18.04.1), libclc-dev:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git201 90827-1~ubuntu18.04.1), libclc-r600:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0. 2.0+git20190827-1~ubuntu18.04.1), libdrm-amdgpu1:amd64 (2.4.97-1ubuntu1~18.04.1, - 2.4.99-1ubuntu1~18.04.1), libdrm2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubunt + 2.4.99-1ubuntu1~18.04.1), libdrm2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubunt u1~18.04.1), libdrm-intel1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04 .1), libdrm-radeon1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), li bdrm-dev:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), libdrm-common :amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1) End-Date: 2020-01-16 12:48:35 - The program just prints out 'LLVM failed to upload shader - ac_rtld error: !s->is_rx'. + The program just prints out: + + ac_rtld error: !s->is_rx + LLVM failed to upload shader + + when clEnqueueNDRangeKernel is called. + + It could be in any one of the packages that were upgraded or installed. + I chose libllvm9 because of the error message. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: llvm-toolchain-9 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-9/+bug/1860042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860042] Re: openCL application gives error after update
** Summary changed: - openCL application gives error + openCL application gives error after update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860042 Title: openCL application gives error after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-9/+bug/1860042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860042] [NEW] openCL application gives error
Public bug reported: My OpenCL program was working normally until a software update. The log file contains: Start-Date: 2020-01-16 12:48:13 Commandline: aptdaemon role='role-commit-packages' sender=':1.131' Install: libllvm9:amd64 (1:9-2~ubuntu18.04.1, automatic), libclang-common-9-dev: amd64 (1:9-2~ubuntu18.04.1, automatic) Upgrade: libdrm-nouveau2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1 ), libclc-amdgcn:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git20190827-1~u buntu18.04.1), libclc-dev:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0.2.0+git201 90827-1~ubuntu18.04.1), libclc-r600:amd64 (0.2.0+git20190306-1~ubuntu18.04.1, 0. 2.0+git20190827-1~ubuntu18.04.1), libdrm-amdgpu1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), libdrm2:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubunt u1~18.04.1), libdrm-intel1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04 .1), libdrm-radeon1:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), li bdrm-dev:amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1), libdrm-common :amd64 (2.4.97-1ubuntu1~18.04.1, 2.4.99-1ubuntu1~18.04.1) End-Date: 2020-01-16 12:48:35 The program just prints out 'LLVM failed to upload shader ac_rtld error: !s->is_rx'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libllvm9 1:9-2~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-74.84-lowlatency 4.15.18 Uname: Linux 4.15.0-74-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 16 14:35:15 2020 InstallationDate: Installed on 2018-04-28 (628 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: llvm-toolchain-9 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: llvm-toolchain-9 (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/1860042 Title: openCL application gives error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-9/+bug/1860042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858285] Re: SSH not honoring use of ~/.ssh/authorized_keys
Update, possible workaround. Still a bug that needs permanently fixed as other distros honor ~/.ssh/authorized_keys properly with settings in /etc/ssh/sshd_config use a directive within the ~/.ssh/config file but seems it requires both private and public keys to be present/exchanged for the required hosts. host short_hostname hostname IPaddr_or_FQDN user username port 22 or other port if not 22 identityfile /home/username/.ssh/private_key_filename -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858285 Title: SSH not honoring use of ~/.ssh/authorized_keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1858285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858285] Re: SSH not honoring use of ~/.ssh/authorized_keys
mistyped, it's a problem in 17.10 as well so the same problem has persisted for a few releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858285 Title: SSH not honoring use of ~/.ssh/authorized_keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1858285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858285] Re: SSH not honoring use of ~/.ssh/authorized_keys
Also, i just tested this on Ubuntu 17.10 "Artful" as well so it seems to not be a problem for 19.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858285 Title: SSH not honoring use of ~/.ssh/authorized_keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1858285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858285] [NEW] SSH not honoring use of ~/.ssh/authorized_keys
Public bug reported: Have tested this successfully on other distros, used the same steps to updating /etc/ssh/sshd_config but SSH will not honor the use of ~/.ssh/authorized_keys. Simple test mkdir -m 700 ~/.ssh cd ~/.ssh ssh-keygen -t rsa -b 4096 press enter to accept the defaults and empty passphrase cp id_rsa.pub authorized_keys ssh localhost /bin/date works mv id-rsa $(hostname -s) mv id-rsa.pub $(hostname -s).pub ssh localhost /bin/date **fails. this works on CentOS, RHEL ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: openssh-server 1:8.0p1-6build1 ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10 Uname: Linux 5.3.0-1014-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Sat Jan 4 12:42:58 2020 ExecutablePath: /usr/sbin/sshd ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858285 Title: SSH not honoring use of ~/.ssh/authorized_keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1858285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739805]
Created attachment 9307 Adjustable brightness steps with support for exponential step sizes I've updated the patch against latest master, with whitespace fixes. The slider on the pop-up menu now also obeys uses the same steps as the brightness buttons (allowing for rounding errors). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739805 Title: Backlight tuning has not enough steps To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-power-manager/+bug/1739805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739805]
Sorry, I completely missed the slider on the pop-up menu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739805 Title: Backlight tuning has not enough steps To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-power-manager/+bug/1739805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854574] [NEW] Seccomp generated SIGSYS has wrong return address if x0 = -513
Public bug reported: The seccomp man page states the for signals generated by SECCOMP_RET_TRAP, "The program counter will be as though the system call happened (i.e., the program counter will not point to the system call instruction)." However if x0 (first argument and return value) contains the value -513 (-ERESTARTNOINTR), or if SA_RESTART is enabled on the signal handler and x0 contains -512 (-ERESTARTSYS) the saved program counter value points to the system call instruction. I can reproduce this bug on upstream AArch32 kernels, but not on current x86-64 kernels. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1007-aws 5.3.0-1007.8 ProcVersionSignature: User Name 5.3.0-1007.8-aws 5.3.7 Uname: Linux 5.3.0-1007-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Sat Nov 30 14:10:31 2019 Ec2AMI: ami-0e88d70910be26319 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: a1.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: Upgraded to eoan on 2019-11-09 (21 days ago) ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 ec2-images eoan ** Attachment added: "sigsys_test.c" https://bugs.launchpad.net/bugs/1854574/+attachment/5308878/+files/sigsys_test.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854574 Title: Seccomp generated SIGSYS has wrong return address if x0 = -513 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1854574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] [NEW] Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken
Public bug reported: If system call number -1 is called and the process is being traced with PTRACE_SYSCALL, for example by strace, the seccomp check is skipped and -ENOSYS is returned unconditionally (unless altered by the tracer), rather than carrying out action specified in the seccomp filter. The consequence of this is that it is not possible to reliably strace a seccomp based implementation of a foreign system call interface in which r7/x8 is permitted to be -1 on entry to a system call. I have traced this bug to commit f086f67485c5c126bcec4b0e96ac7319a2e59ab8 which attempts to implement PTRACE_SYSEMU. Contrary to x86-64 and the man ptrace page which states "For PTRACE_SYSEMU, continue and stop on entry to the next system call, which will not be executed.", on PTRACE_SYSEMU skips the current system call and stops on entry to the next system call. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1007-aws 5.3.0-1007.8 ProcVersionSignature: User Name 5.3.0-1007.8-aws 5.3.7 Uname: Linux 5.3.0-1007-aws aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Sat Nov 30 13:38:28 2019 Ec2AMI: ami-0e88d70910be26319 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: a1.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: Upgraded to eoan on 2019-11-09 (21 days ago) ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 ec2-images eoan ** Attachment added: "Test case for skipped syscall" https://bugs.launchpad.net/bugs/1854573/+attachment/5308874/+files/sigsys_skip_test.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] Re: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken
** Attachment added: "Test case for skipped syscall" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1854573/+attachment/5308877/+files/sysemu_test.c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
Apologies, comment #32 is incorrect, this worked a couple times but the problem is still present intermittently. I have since downgraded to BIOS v1.2.0 to avoid the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
I believe I have a workaround provided by a kernel engineer I was discussing the issue with. Adding the following to the kernel boot options resulted in the keyboard and touchpad working without issue: i8042.nomux=1 i8042.reset It appears that Dell uses i8042 to emulate a ps/2 interface rather than using USB for the built-in keyboard and touchpad. The following stackexchange link provided more info: https://unix.stackexchange.com/questions/28736/what-does- the-i8042-nomux-1-kernel-option-do-during-booting-of-ubuntu I've attached a new dmesg output from a successful boot using these boot options[0] [0] boot_i8042_options_keyboard_usable_dmesg.log ** Attachment added: "dmesg i8042 boot options keyboard usable" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5280162/+files/boot_i8042_options_keyboard_usable_dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
I can confirm I have encountered this issue with BIOS v. 1.6.1 from 21 Jul 2019 Device - Dell XPS 15 9575 Intel Core i7-8705G BIOS - version 1.6.1 OS - Fedora 30 Kernel - kernel-5.1.19-300 Additional info: - I have an encrypted root partition. During boot, I am able to usethe keyboard for <1 second at the screen where I enter the password for the root partition. Then the keyboard is disabled. - I tested this with a previously installed kernel 5.0.9-301 and I was able to use the keyboard to enter the password for the root partition, but once I arrive at the login screen for fedora the keyboard/touchpad is unusable (cannot even switch TTYs) - Using the grub boot menu option "fedora rescue" which is installed by default with fedora, I am able to use the keyboard to login without issue. I'm happy to share any additional information that is requested. I don't see any specific errors in dmesg that stand out here, but I've provided a dmesg from a boot when the keyboard would not function [0]. I will also upload a dmesg from a functional boot[1]. [0] boot_k509_keyable_unusable_dmesg.log [1] boot_rescue_keyboard_usable_dmesg.log ** Attachment added: "dmesg kernel-509-301 bios 1.6.1 keyboard unusable" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5280155/+files/boot_k509_keyable_unusable_dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
** Attachment added: "dmesg fedora rescue bios 1.6.1 keyboard usable" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822394/+attachment/5280156/+files/boot_rescue_keyboard_usable_dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133133]
It does absolutely nothing for me in Windows 7 Ultimate 64-bit. It has been broken for me for several months. Using latest version (FF43). Why doesn't it work anymore for me? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/133133 Title: "Open containing folder" is only working if nautilus is present To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/133133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739805]
Created attachment 8653 Adjustable brightness steps with support for exponential step sizes Fixed compilation problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739805 Title: Backlight tuning has not enough steps To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-power-manager/+bug/1739805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739805]
Created attachment 8652 Adjustable brightness steps with support for exponential step sizes Rebased to latest master as of 2019-06-19. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739805 Title: Backlight tuning has not enough steps To manage notifications about this bug go to: https://bugs.launchpad.net/xfce4-power-manager/+bug/1739805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831343] [NEW] [bionic] Full GNOME Session crash shortly after login
Public bug reported: >From /var/log/syslog Jun 1 10:52:50 armadillo gnome-session[1187]: gnome-session-binary[1187]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Jun 1 10:52:50 armadillo gnome-session-binary[1187]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Jun 1 10:52:50 armadillo gnome-session-binary[1187]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Jun 1 10:52:50 armadillo gnome-session[1187]: gnome-session-binary[1187]: CRITICAL: We failed, but the fail whale is dead. Sorry Jun 1 10:52:50 armadillo gnome-session-binary[1187]: CRITICAL: We failed, but the fail whale is dead. Sorry Version 3.28.1-0ubuntu3 Has happened on multiple different installs on two different PCs (Dell Latitude e6430 and Thinkpad x131e) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session-bin 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 1 11:43:05 2019 ExecutablePath: /usr/lib/gnome-session/gnome-session-binary InstallationDate: Installed on 2019-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: From /var/log/syslog Jun 1 10:52:50 armadillo gnome-session[1187]: gnome-session-binary[1187]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Jun 1 10:52:50 armadillo gnome-session-binary[1187]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Jun 1 10:52:50 armadillo gnome-session-binary[1187]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Jun 1 10:52:50 armadillo gnome-session[1187]: gnome-session-binary[1187]: CRITICAL: We failed, but the fail whale is dead. Sorry Jun 1 10:52:50 armadillo gnome-session-binary[1187]: CRITICAL: We failed, but the fail whale is dead. Sorry Version 3.28.1-0ubuntu3 + + Has happened on multiple different installs on two different PCs (Dell + Latitude e6430 and Thinkpad x131e) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session-bin 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 1 11:43:05 2019 ExecutablePath: /usr/lib/gnome-session/gnome-session-binary InstallationDate: Installed on 2019-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: - LANGUAGE=en_CA:en - PATH=(custom, user) - XDG_RUNTIME_DIR= - LANG=en_CA.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_CA:en + PATH=(custom, user) + XDG_RUNTIME_DIR= + LANG=en_CA.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831343 Title: [bionic] Full GNOME Session crash shortly after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1831343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767808] Re: "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated Graphics with Kernel 4.15
okay I install Ukuu 18.9 then i had it install Linux kernel v5.1 Disabled video=SVIDEO-1:d in grub restated the computer and now like a champ it is working. napalmfred@pop-os:~$ neofetch /napalmfred@pop-os /- ///*767 OS: Pop!_OS 19.04 x86_64 //7676767676*// Host: Inspiron 1525 /76767//7676767// Kernel: 5.1.0-050100-generic /767676///*76767/// Uptime: 12 mins ///767676///76767.///7676*///Packages: 1865 (dpkg) /767676//76767///767676 Shell: bash 5.0.3 //7676767676776767/ Resolution: 1280x800 ///76767676//7676// DE: GNOME 3.32.1 ,7676,///767/// WM: GNOME Shell /*7676///76 WM Theme: Pop ///7676 Theme: Pop-slim-dark [GTK2/3] ///7676///767Icons: Pop [GTK2/3] //' Terminal: gnome-terminal //.7676767676767676767,// CPU: Pentium T4200 (2) @ 2.000GHz /767676767676767676767/ GPU: Intel Mobile GM965/GL960 /// Memory: 1588MiB / 5948MiB / / -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767808 Title: "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated Graphics with Kernel 4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823815] [NEW] outdated version/votca bug #179 fix available, package update requested
Public bug reported: https://github.com/votca/csg/issues/179 A change in the behavior of /bin/dash broke some perl components of votca-csg, as per the thread in the link above. The issue seems to have been resolved in the new 1.5x releases of the votca package that's available in disco, but the updated package has not made it to bionic. There is a workaround, but it's not a particularly great one, and the result is that the 1.4 package as it stands has broken components in bionic due to this bug. I'm not sure I'm asking in the right place, here, but if there's anyone who can offer some guidance or help me figure out the right place/person to ask to get this package (and its associated packages?) updated for bionic, I'd appreciate it greatly. Thanks. main package: votca-csg/bionic 1.4.1-1build1 amd64 VOTCA's coarse-graining engine ** Affects: votca-csg (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/1823815 Title: outdated version/votca bug #179 fix available, package update requested To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/votca-csg/+bug/1823815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814252] [NEW] package grub-pc 2.02+dfsg1-5ubuntu10 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1
Public bug reported: A error occur when install grub-pc ProblemType: Package DistroRelease: Ubuntu 19.04 Package: grub-pc 2.02+dfsg1-5ubuntu10 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Fri Feb 1 19:20:20 2019 ErrorMessage: installed grub-pc package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-12-08 (55 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic root=UUID=25b94c1c-8aba-4a36-8b43-af9964615720 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.7, Python 3.7.2, python3-minimal, 3.7.2-1 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.2ubuntu2 apt 1.8.0~beta1 SourcePackage: grub2 Title: package grub-pc 2.02+dfsg1-5ubuntu10 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814252 Title: package grub-pc 2.02+dfsg1-5ubuntu10 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1814252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783964] Re: Please make CONFIG_PWM_LPSS_PCI and CONFIG_PWM_LPSS_PLATFORM built in to make brightness adjustment working on various BayTrail/CherryTrail-based devices
Hello guys, I'm kind of new regarding kernel patching. I've Asus T102HA and saw some other blogs about how to control the backlight brightness. I tried to message to people and asked for help but I got no response. Would you guys help me how to fix the backlight brightness step by step? Currently, I tried to install linux mint 19 mate edition and Crunchbangplusplus versions. Both are working but couldn't set the brightness to lower setting. 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/1783964 Title: Please make CONFIG_PWM_LPSS_PCI and CONFIG_PWM_LPSS_PLATFORM built in to make brightness adjustment working on various BayTrail/CherryTrail- based devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800951] Re: Me-TV on 18.10
** Description changed: Me-Tv with an ATI TV Wonder 600 worked fine on Lubuntu 18.04. On 18.10 I - get a "failed to lock channel" error. DMESG conforms that the DVB-T + get a "failed to lock channel" error. DMESG confirms that the DVB-T device is recognized and loaded. Me-TV tries to scan for channels but no luck. Nothing has changed on my setup except for the clean install upgrade to 18.10. I reloaded the firmware and re-installed the Me-TV deb after the upgrade to 18.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800951 Title: Me-TV on 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/me-tv/+bug/1800951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800951] [NEW] Me-TV on 18.10
Public bug reported: Me-Tv with an ATI TV Wonder 600 worked fine on Lubuntu 18.04. On 18.10 I get a "failed to lock channel" error. DMESG conforms that the DVB-T device is recognized and loaded. Me-TV tries to scan for channels but no luck. Nothing has changed on my setup except for the clean install upgrade to 18.10. I reloaded the firmware and re-installed the Me-TV deb after the upgrade to 18.10. ** Affects: me-tv (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/1800951 Title: Me-TV on 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/me-tv/+bug/1800951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783972] [NEW] libglew-dev does not include cmake config files
Public bug reported: libglew-dev does not include the cmake files required in /usr/lib/cmake/glew CopyImportedTargetProperties.cmake glew-config.cmake glew-targets.cmake glew-targets-release.cmake These allow the GLEW library to be found by CMake's find_package() function when used in config mode. (Apologies for assigning this bug to the wrong package. It is claimed that https://packages.ubuntu.com/bionic/libglew-dev is not part of Ubuntu) ** Affects: glew (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/1783972 Title: libglew-dev does not include cmake config files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glew/+bug/1783972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783323] [NEW] package util-linux 2.31.1-0.4ubuntu3.1 failed to install/upgrade: package util-linux is already installed and configured
Public bug reported: none . new to this ProblemType: Package DistroRelease: Ubuntu 18.04 Package: util-linux 2.31.1-0.4ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 AptdaemonVersion: 1.1.1+bzr982-0ubuntu19 Architecture: amd64 CrashReports: 600:0:117:252164:2018-07-24 08:07:20.20799 -0400:2018-07-24 08:07:21.20799 -0400:/var/crash/util-linux.0.crash Date: Tue Jul 24 08:07:20 2018 DpkgTerminalLog: Preparing to unpack .../util-linux_2.31.1-0.4ubuntu3.1_amd64.deb ... Unpacking util-linux (2.31.1-0.4ubuntu3.1) over (2.31.1-0.4ubuntu3) ... Log started: 2018-07-24 08:07:20 dpkg: error processing package util-linux (--configure): package util-linux is already installed and configured DuplicateSignature: package:util-linux:2.31.1-0.4ubuntu3.1 Unpacking util-linux (2.31.1-0.4ubuntu3.1) over (2.31.1-0.4ubuntu3) ... Log started: 2018-07-24 08:07:20 dpkg: error processing package util-linux (--configure): package util-linux is already installed and configured ErrorMessage: package util-linux is already installed and configured InstallationDate: Installed on 2018-07-23 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: dpkg Title: package util-linux 2.31.1-0.4ubuntu3.1 failed to install/upgrade: package util-linux is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783323 Title: package util-linux 2.31.1-0.4ubuntu3.1 failed to install/upgrade: package util-linux is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1783323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782459] [NEW] Upgrade to Chef 13.8.7 package from upstream
Public bug reported: Chef 12 is currently end of life and many cookbook maintainers including Chef are dropping support for Chef 12 in their cookbooks. This makes it very difficult to use the Chef release included in Ubuntu with modern codebases. Debian sid currently has Chef 13.8.7, which isn't current, but is still a supported release. It would be great to pull in the latest Chef package for the next Ubuntu release. ** Affects: chef (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/1782459 Title: Upgrade to Chef 13.8.7 package from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chef/+bug/1782459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777925] [NEW] package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: installation error. I'm new to linux so my knowledge of attaching additional information is limited. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 20 14:03:44 2018 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-06-10 (10 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: gnome-menus Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-06-20 (0 days ago) ** Affects: gnome-menus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777925 Title: package gnome-menus 3.13.3-11ubuntu1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1777925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770883] [NEW] Shift key does not work for first character of password
Public bug reported: Ubuntu 18.04 LTS gnome-shell 3.28.1-0ubuntu2 Repro: 1. Cold boot OR resume from standby OR lock (e.g. super + L) and wait for screen to fade 2. Use mouse to reveal password input 3. (optional, can happen whether or not you do this) Right click password box and select "Show Text" 4. Press SHIFT + (any key) Expected result: Character corresponding to SHIFT + key is inputted into the password box. Actual result: Character corresponding to key (without SHIFT) is inputted into the password box. Other notes: If any key is pressed prior to inputting password then the SHIFT + key works properly. E.g. if I press enter to reveal the password input, or if I press SHIFT an extra time before step 4 of the repro. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Shift key sometimes does not work for first character of password + Shift key does not work for first character of password -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770883 Title: Shift key does not work for first character of password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1770883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767402] Re: hash mismatch or wrong accept-license key trying to install virtualbox-ext-pack 5.2.10
great! thank you @zebul666 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767402 Title: hash mismatch or wrong accept-license key trying to install virtualbox-ext-pack 5.2.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1767402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767402] Re: hash mismatch or wrong accept-license key trying to install virtualbox-ext-pack 5.2.10
Ah I found this: https://unix.stackexchange.com/questions/138188/easily- unpack-deb-edit-postinst-and-repack-deb :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767402 Title: hash mismatch or wrong accept-license key trying to install virtualbox-ext-pack 5.2.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1767402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767402] Re: hash mismatch or wrong accept-license key trying to install virtualbox-ext-pack 5.2.10
Hi, thanks for the solution. How do I edit the "postinst file of the package"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767402 Title: hash mismatch or wrong accept-license key trying to install virtualbox-ext-pack 5.2.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1767402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769413] [NEW] package boinc-app-seti-graphics 8.00~svn3701-1 failed to install/upgrade: installed boinc-app-seti-graphics package post-installation script subprocess returned error exit status 1
Public bug reported: update-boinc-applinks is missing. The installation script of boinc-app- seti-graphics fails running the update-boinc-applinks ProblemType: Package DistroRelease: Ubuntu 18.04 Package: boinc-app-seti-graphics 8.00~svn3701-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: freeglut3:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun May 6 13:19:16 2018 ErrorMessage: installed boinc-app-seti-graphics package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2015-05-20 (1081 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: boinc-app-seti Title: package boinc-app-seti-graphics 8.00~svn3701-1 failed to install/upgrade: installed boinc-app-seti-graphics package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2018-05-06 (0 days ago) ** Affects: boinc-app-seti (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769413 Title: package boinc-app-seti-graphics 8.00~svn3701-1 failed to install/upgrade: installed boinc-app-seti-graphics package post- installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc-app-seti/+bug/1769413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
