[Bug 1950868] [NEW] Display error after reopening notebook top
Public bug reported: Hi all, I probably experienced an error within amdgpu. After closing and reopeing the notebook top, the display is totally distorted. Switching to a virtual console doesnt help. You may find a screenshot attached. The error came up in recent version (X)Ubuntu 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stefan 1076 F pulseaudio /dev/snd/controlC0: stefan 1076 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Nov 13 20:10:24 2021 InstallationDate: Installed on 2021-11-12 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: HP HP Laptop 15-bw0xx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=bd57dbcb-cf6a-489f-ac26-1f6e146458e0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/17/2017 dmi.bios.release: 15.21 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8332 dmi.board.vendor: HP dmi.board.version: 28.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 28.32 dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/17/2017:br15.21:efr28.32:svnHP:pnHPLaptop15-bw0xx:pvrType1ProductConfigId:rvnHP:rn8332:rvr28.32:cvnHP:ct10:cvrChassisVersion:sku1UR07EA#ABD: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bw0xx dmi.product.sku: 1UR07EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish kernel package-from-proposed ** Attachment added: "2023_200342.jpg" https://bugs.launchpad.net/bugs/1950868/+attachment/5540643/+files/2023_200342.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950868 Title: Display error after reopening notebook top To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925328] [NEW] Virtual Box Guest Additions won't build
Public bug reported: Hi there, this is from the log file: stefan@Ubuntu-hirsute:/var/log$ more vboxadd-setup.log Building the main Guest Additions 6.1.18 module for kernel 5.11.0-16-generic. Building the shared folder support module. Building the graphics driver module. Error building the module. Build output follows. make V=1 CONFIG_MODULE_SIG= CONFIG_MODULE_SIG_ALL= -C /lib/modules/5.11.0-16-gen eric/build M=/tmp/vbox.0 SRCROOT=/tmp/vbox.0 -j1 modules test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it. "; \ echo >&2 ; \ /bin/false) Best regards Stefan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: virtualbox-guest-additions-iso 6.1.18-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 21 11:59:21 2021 InstallationDate: Installed on 2021-02-01 (79 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210123) PackageArchitecture: all SourcePackage: virtualbox-guest-additions-iso UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox-guest-additions-iso (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925328 Title: Virtual Box Guest Additions won't build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-guest-additions-iso/+bug/1925328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905798] [NEW] package libjpeg9-dev (not installed) failed to install/upgrade: Versuch, »/usr/include/jerror.h« zu überschreiben, welches auch in Paket libjpeg-turbo8-dev:amd64 2.0.3-0ubuntu2 ist
Public bug reported: Error when trying to install libjpeg9-dev: /tmp/apt-dpkg-install-9TVCNG/02-libjpeg9-dev_1%3a9d-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 21.04 Package: libjpeg9-dev (not installed) ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu53 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 27 01:00:40 2020 ErrorMessage: Versuch, »/usr/include/jerror.h« zu überschreiben, welches auch in Paket libjpeg-turbo8-dev:amd64 2.0.3-0ubuntu2 ist InstallationDate: Installed on 2020-11-22 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201121) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-8 RelatedPackageVersions: dpkg 1.20.5ubuntu3 apt 2.1.11 SourcePackage: libjpeg9 Title: package libjpeg9-dev (not installed) failed to install/upgrade: Versuch, »/usr/include/jerror.h« zu überschreiben, welches auch in Paket libjpeg-turbo8-dev:amd64 2.0.3-0ubuntu2 ist UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libjpeg9 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905798 Title: package libjpeg9-dev (not installed) failed to install/upgrade: Versuch, »/usr/include/jerror.h« zu überschreiben, welches auch in Paket libjpeg-turbo8-dev:amd64 2.0.3-0ubuntu2 ist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg9/+bug/1905798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903916] [NEW] Default keys cannot be restored from keyserver
Public bug reported: Hi all, the default keys for trustworthy software sources are gone (or at least won't display) in software-properties-gtk in Groovy Gorilla MATE. I tried to recreate them by using the button in bottom right corner. After entering system password no change seems to be done. However, keyserver de.archive.ubuntu.com seems to work for updates. Can this be fixed easily? Kind regards Stefan ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: software-properties-gtk 0.99.3 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Nov 11 22:06:38 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2018-09-25 (778 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to groovy on 2020-11-01 (10 days ago) ** Affects: software-properties (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/1903916 Title: Default keys cannot be restored from keyserver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1903916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Update to mutter 3.36.1-1ubuntu0.20.04.1 in focal/proposed also fixed the bug for AMD. Good work, thanks and cheers! :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
> PopOS pushed a fix pretty quickly, so you > can see that there are Ubuntu flavors who are actively managing > themselves better than Canonical is managing the main distro. Isn't PopOS more a new distro based on Ubuntu rather than a flavor like KUbuntu, UbuntuMate, XUbuntu? However, when PopOS people fixed it, it should be possible to learn from their code to fix mutter faster. But this had to be done by someone. I *am* able to code, and probably could take a look, but also my skills and my speed are far not good enough, when hundreds of persons are very eager to get a fix fast >> If you are skilled enough to contribute code, why don't you help but instead >> complain? > > I probably WILL dedicate time to this, but the bug has an assignee and I > am not sure if I would be re-doing redundant work that is already done. Then why not contact the assignee and offer your willingness to help? Best regards Stefan -- stefan.czinczoll[at]arcor.de https://schollsky.jimdofree.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
Hi Cristiano, on 09.09.20 um 18:47 you wrote: > This thread is about a bug in "mutter 3.36.4-0ubuntu0.20.04.2". Just it. > (not about arguing philosophies). You are partially right. > As it is a bug, it ends up embarrassing people. It's normal. Agreed. > "Freedom of choice" doesn't mean bad software. It is a wrong idea. Also, > Canonical is a company and there are people working there to fix bugs. How much did you pay to Canonical for using Ubuntu 20.04? How much are you willing to pay to Canonical for a fix? > In this case, the only person behaving like a child on this thread is > you. > > Sorry for my sincerity, I haven't taken offence. Who takes a dig at someone must be able to take -- stefan.czinczoll[at]arcor.de https://schollsky.jimdofree.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
Hi Cristiano, on 09.09.20 um 18:47 you wrote: > This thread is about a bug in "mutter 3.36.4-0ubuntu0.20.04.2". Just it. > (not about arguing philosophies). You are partially right. > As it is a bug, it ends up embarrassing people. It's normal. Agreed. > "Freedom of choice" doesn't mean bad software. It is a wrong idea. Also, > Canonical is a company and there are people working there to fix bugs. How much did you pay to Canonical for using Ubuntu 20.04? How much are you willing to pay to Canonical for a fix? > In this case, the only person behaving like a child on this thread is > you. > > Sorry for my sincerity, I'm not taking offence. Who takes a dig at someone must be able to take stick. Perhaps it's possible to fix mutter faster than Canonical. Why not crowdfund a fix fast and sell it to Canonical later? Best regards Stefan -- stefan.czinczoll[at]arcor.de https://schollsky.jimdofree.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
Hello Telework Inc. on 09.09.20 um 17:26 you wrote: > That’s an extremely limited perspective, Stefan. My point is that ideally, > nobody would push a version of mutter with a massive bug that breaks > desktops around the world in the first place. OK, you state it's a massive bug breaking desktops. Is this really true? Is it a security issue? Are you not able to use the desktop because of this bug? IMHO it's just a minor issue causing an annoying graphics design. I even would never have taken notice of the bug on my system if not a forum user of https://ubuntuusers.de/ asked for help there. How many users do experience this bug? > As I said, it is extremely embarrassing. Defending bad software design is > even more embarrassing. It’s not asking for “free lunch” to say that > packages in the universe repos should be free of critical bugs, I have no > idea what kind of uninspired simpleton would defend a major package staying > broken for several months. OK, packages in universe repo should be free of critical bugs. But as we all know, bugs are phenomena in software engineering, that can occur due to human nature of programmers. Nobody's perfect thus no human work is ever perfect. I'm very sure there are good reasons for the delay. My guess is simply there's not enough manpower in regard to the severity of the mutter bug. Software engineering is a very time consuming task and good code doesn't come from heaven. If you are skilled enough to contribute code, why don't you help but instead complain? Best regards, Stefan -- stefan.czinczoll[at]arcor.de https://schollsky.jimdofree.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
This tendency is childish. If you want warranted security with fast(?) bug fixing, look out for a proprietary OS solution or better contribute to Ubuntu by coding support. Please stop behaving like a child: https://en.wikipedia.org/wiki/There_ain't_no_such_thing_as_a_free_lunch If you want freedom of choice, you should better get along with the implications. Best regards Stefan Am 09.09.20 um 08:32 schrieb Telework Inc.: > vervelover is honestly right, this is pretty embarrassing. > -- stefan.czinczoll[at]arcor.de https://schollsky.jimdofree.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894755] [NEW] Dock won't show up on screen
Public bug reported: Hi there, recent installation of dashtodock is not in function. The GNOME extension has been installed in 20.10. First activation and adjusting (placement lower screen) was tried by using gnome-tweaks. System environment is a virtual machine, x11 session. After checking gnome-tweaks again it reports error during loading the extension. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-dashtodock 68-1 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Sep 7 22:50:42 2020 InstallationDate: Installed on 2020-09-02 (5 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200831) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-dashtodock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-dashtodock (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/1894755 Title: Dock won't show up on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1894755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894755] Re: Dock won't show up on screen
Checking wayland presents same error (cannot load). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894755 Title: Dock won't show up on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1894755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2
I see the same problem, running AMD GPU RX580 and X11 (problem doesn't seem to apper in Wayland). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893534] [NEW] Initial ramdisk as second parameter is left out
Public bug reported:
Hi there,
multiboot with Ubuntu, Windows and Manjaro worked fine for some time.
However, os-prober doesn't take care of Manjaros initial ramdisk any
more. This is an example of how it's now on my system from file
/boot/grub/grub.cfg:
menuentry 'Manjaro Linux (20.0.3) (auf /dev/nvme0n1p5)' --class manjarolinux
--class gnu-linux --class gnu --class os $menuentry_id_option '
osprober-gnulinux-simple-52768e35-66bf-4dd6-ab95-64fd30abb67e' {
savedefault
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
52768e35-66bf-4dd6-ab95-64fd30abb67e
else
search --no-floppy --fs-uuid --set=root
52768e35-66bf-4dd6-ab95-64fd30abb67e
fi
linux /boot/vmlinuz-5.8-x86_64
root=UUID=52768e35-66bf-4dd6-ab95-64fd30abb67e rw quiet apparmor=1
security=apparmor udev.log_priorit
y=3
initrd /boot/amd-ucode.img
Comparing this to the output from Manjaro:
menuentry 'Manjaro Linux' --class manjaro --class gnu-linux --class gnu --class
os $menuentry_id_option 'gnulinux-simple-52768e35-66bf-4dd6-
ab95-64fd30abb67e' {
savedefault
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
52768e35-66bf-4dd6-ab95-64fd30abb67e
else
search --no-floppy --fs-uuid --set=root
52768e35-66bf-4dd6-ab95-64fd30abb67e
fi
linux /boot/vmlinuz-5.8-x86_64
root=UUID=52768e35-66bf-4dd6-ab95-64fd30abb67e rw quiet apparmor=1
security=apparmor udev.log_prio
rity=3
initrd /boot/amd-ucode.img /boot/initramfs-5.8-x86_64.img
Is there a workaround until fixed?
Kind regards
Stefan
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: os-prober 1.74ubuntu2
Uname: Linux 5.8.5-050805-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 29 23:30:06 2020
InstallationDate: Installed on 2019-05-02 (484 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: os-prober
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: os-prober (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/1893534
Title:
Initial ramdisk as second parameter is left out
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1893534/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882293] [NEW] Changing keyboard layout doesn't work during installation
Public bug reported: This issue goes to non-English/US keyboard/language users: During installation I chose German keymap, but English was used instead. I was installing inside VirtualBox. Installed system uses correct settings though. $ lsb_release -rd Description:Ubuntu Groovy Gorilla (development branch) Release:20.10 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu37 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 5 20:30:21 2020 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity InstallationDate: Installed on 2020-06-04 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200603) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882293 Title: Changing keyboard layout doesn't work during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1882293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851936] Re: User profile won't load after upgrade - prompt to create new profile
Dear Sirs, bug reappears with single home directory under dual boot condition with Manjaro. Could this be fixed or do I have to reinstall package and/or config file? Kind regards schollsky -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851936 Title: User profile won't load after upgrade - prompt to create new profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1851936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857949] [NEW] Binutils (18.04) on Launchpad does not link gtest library
Public bug reported: Hi there, I found some strange behavior with /usr/bin/ld trying to build gnome- commander on Launchpad for 18.04 LTS. gtest library was included, but not found. The same code builds fine with version 19.04. You can find PPA here: https://launchpad.net/~schollsky/+archive/ubuntu/gcmd Kind regards schollsky >From the buildlog: [...] make[3]: Entering directory '/<>/tests' g++ -std=gnu++11 -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -D_REENTRANT -DORBIT2=1 -pthread -I/usr/include/libgnomeui-2.0 -I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 -I/usr/include/libxml2 -I/usr/include/libgnome-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/orbit-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gail-1.0 -I/usr/include/libart-2.0 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/x86_64-linux-gnu/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DGTEST_HAS_PTHREAD=0 -I../src -I.. -I../src -I../src/intviewer -I. -DGTK_DISABLE_SINGLE_INCLUDES -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -D_REENTRANT -DORBIT2=1 -pthread -I/usr/include/libgnomeui-2.0 -I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0 -I/usr/include/libxml2 -I/usr/include/libgnome-2.0 -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0 -I/usr/include/orbit-2.0 -I/usr/include/libgnomecanvas-2.0 -I/usr/include/gail-1.0 -I/usr/include/libart-2.0 -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/gnome-vfs-2.0 -I/usr/lib/x86_64-linux-gnu/gnome-vfs-2.0/include -I/usr/include/gconf/2 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DGTEST_HAS_PTHREAD=0 -I../src -I.. -I../src -I../src/intviewer -I. -DGTK_DISABLE_SINGLE_INCLUDES -DGDK_PIXBUF_DISABLE_SINGLE_INCLUDES -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o iv_textrenderer-gcmd_tests_main.o `test -f 'gcmd_tests_main.cc' || echo './'`gcmd_tests_main.cc make[3]: Leaving directory '/<>/tests' make[3]: Entering directory '/<>/tests' g++ -std=gnu++11 -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0
