the same here!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065348
Title:
[SRU] python3-docker `from_env()` broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
.15.0-112.122 should be blocked since it prevents
multiple generations of Laptop and Desktop APUs from booting.
Special thanks to Barry K. for bisecting!
Thanks Armin W. for driving the fix and everyone else for your inputs.
Take care,
Willem
--
You received this bug notification because you are a m
Hello, i have rebuild the debian sid package on ubuntu to see if this
fixes the issue.
https://packages.debian.org/source/sid/python-docker
The binary from that package seems to work.
Can this be ported to ubuntu 24.04 to make use of python and docker
possible again?
Best regards,
William
--
tor ID: Ubuntu
+ Description: Ubuntu Jammy Jellyfish (development branch)
+ Release: 22.04
+ Codename: jammy
+
+ Linux willem-Aspire-A315-53 5.15.0-18-generic #18-Ubuntu SMP Fri Jan 21
+ 14:57:54 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
+
After upgrading from 21.04 tot 22.04 I did:
ove / or
remove -m / or
remove -m -v
All the output:
willem@willem-Aspire-A315-53:~$ sudo apt update && sudo apt full-upgrade
[sudo] wachtwoord voor willem:
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd... Klaar
De statusinformatie wordt gelezen... Kla
perhaps the dependency of fwupd-signed should be to fwupd-unsigned
instead of fwupd itself?
the fwupd-signed/jammy-proposed 1.41+1.1-3 amd64 version required fwupd
1.1-3 but only the fwupd-unsigned package has that version..
--
You received this bug notification because you are a member of Ubunt
the complete message .. during a second upgrade completion attempt
Do you want to continue? [Y/n] y
Setting up openssh-client (1:8.7p1-3) ...
update-alternatives: and can't be the same
Use 'update-alternatives --help' for program usage information.
dpkg: error processing package openssh-client
grub-efi-am64-signed/bin 2.06-2ubuntu3 update works as expected .. thank
you for fixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954566
Title:
jammy-proposed grub-efi-amd64-signed 1.175+2.06 2
I had same EFI error: out of memory error: you need to load the kernel
first.
as I am using a "real pc" not a VM
my question now is why would "set debug=all" fix this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
note: booting windows partition is not affected .. only linux partitions
fail to boot when debug is off .. i.e. normal state ..
if another grub menu item is selected to boot linux w/o debug turned on
it fails as described earlier .. lack of kernel memory etc.
--
You received this bug notificatio
ok tried that .. to reduce the data spew I added: set pager=1 and set
debug=all lines to the first grub menu selection .. this turns debugging on
only if this menu is selected .. and although we got lots of output .. boot was
normal ..
if these lines were removed boot failed again .. this the
filed bug #1954566
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953490
Title:
keep grub 2.06 in proposed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gr
Public bug reported:
grub-efi-amd64-signed/jammy-proposed,now 1.175+2.06-2ubuntu2 amd64 [installed]
GRand Unified Bootloader, version 2 (EFI-AMD64 version, signed)
on boot: select a bootable partition, error appears ...kernel file not
loaded please load kernel first.. enter to continue .. hp bo
FYI Jammy-proposed testing issues
grub-efi-amd64-bin/jammy-proposed,now 2.06-2ubuntu2 amd64 [installed]
GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
grub-efi-amd64-signed/jammy-proposed,now 1.175+2.06-2ubuntu2 amd64 [installed]
GRand Unified Bootloader, version 2 (EFI-AMD64 versio
So why does ubiquity not recognize that it is installing on an mbr
partitioned disk? and adjust accordingly.. seems rather wrong that the
install all fails at the install of grub .. especially as everything
else is ok..
also stealing 500 MB for an efi partition when it is not needed is
rather a w
confirmed that manual partition selection install without EFI fat32 partition
present will fail on grub install .. due to install media EFI fat32 partition
being substituted into new install fstab ..
autobug report generated .. with "duplicate of bug 1922105" title
** Changed in: ubiquity (Ub
hirsute daily apr 5, 2021 xubuntu still has bug 1922105 for manual
partitioning grub fails to install if EFI partition is not present
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922571
Title:
dup
Public bug reported:
as per bug 1922105
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.13
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu
this bug appears to be fixed in xubuntu apr 5, 2021 hirsute daily build
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
** Changed in: ubiquity (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
fix only present if auto resize is used .. will still fail with manual
resizing.
Auto resize adds a EFI fat32 partition during the resize. this prevents
the grub install failure.
if an EFI partition is not present the installer will fail ..
--
You received this bug notification because you are
Artifacts left behind..
incomplete grub-install .. fixed with via a chroot -> grub-install
--target i386-pc /dev/sda
Reference to usbstick efi partition in fstab prevents boot .. fixed
commented out in /etc/fstab
then normal boot proceeds .. everything else appears normal
--
You received this
this bug is still not dead .. this is a duplicate of other reports
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922105
Title:
Installer crashed (grub not installed) on bios/mbr based system .. no
Public bug reported:
Hirsute xubuntu daily march 31,2021 pre?beta
lenova sl500 intel graphics core2
already running hirsute on another partition
This is a test install
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.12
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874954
Title:
[SRU] settings manager window will not shrink horizontally after
expanding
To manage notificat
I have tested this in xubuntu 20.10 and can confirm that it worked as
expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874954
Title:
[SRU] settings manager window will not shrink horizontall
with Kazam (https://imgur.com/a/g78YH62)
but the recording does not show the flickering unfortunately.
I'm testing in VM in Boxes.
Running Linux willem-Standard-PC-i440FX-PIIX-1996 5.10.0-14-generic #15-Ubuntu
SMP Fri Jan 29 15:10:03 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
product: Intel
rtl8821ce package was as rtl8821ce-dkms-5.5.2.1-0ubuntu4~20.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911605
Title:
rebuild of rtl8821ce-dkms fails with linux-5.10 kernel version and new
okay .. I installed focal 20.4.2.0 (xubuntu) along side hirsute on a
separate partition ..
used a edimax usb wireless dongle to do the install and updates of focal
..
added proposed to apt sources .. then installed rtl8821ce-dkms as well
as other updates
rebooted (without usb wi/fi) and rtl8821c
yes that works I now have use of the rtl8821ce wireless connection
again..
thank you!
How soon will this be merged with hirsute?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911605
Title:
rebuil
this did not get uploaded automatically: rtl8821ce-dkms.0.crash
** Attachment added: "rtl8821ce-dkms.0.crash"
https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1911605/+attachment/5454939/+files/rtl8821ce-dkms.0.crash
--
You received this bug notification because you are a member of U
other newer antenna styles also unsupported by rtw88_8821ce firmware..
it appears that rtl8821ce-dkms is antenna and firmware agnostic and work
for kernels 5.8 and lower .. at least one site has a module that fixes
the symbol issue and allows compilation of an rtl8821ce module ..
https://github.co
It appears that firmware for rfc2 type antenna is not yet available as
per comment #2 at following link:
https://forum.siduction.org/index.php?topic=8134.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
note: same firmware appears to work for kernel 5.8 versions using
rtl8821ce-dkms .. no errors appear in dmesg ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911605
Title:
rebuild of rtl8821ce-dkm
problem appears to be firmware name miss-match .. according to other
reports the firmware is not up to date or older/newer chip sets are not
supported this effects wifi and bluetooth (dual function chip)
did a
modprobe -r rtw88_8821ce
modprobe rtw88_8821ce
dmesg .. tail ..
[ 208.374092] rtw_8
modules are loaded but are not functioning .. dkms registration was
required with previous modules is some kind of registration required for
the newer modules?
(an alternate usb wireless nic does work so everything else is ok)
** Summary changed:
- rebuild of rtl8821ce-dkms fails with linux-5.10
seems there is a kernel module now for rtl8821ce ..rtw88_8821ce .. but
it does not function .. (dkms removed from system)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911605
Title:
rebuild of rtl8
Public bug reported:
upgrade to 5.10 kernel headers causes rebuild of rtl8821ce-dkms to fail
due to missing symbols as per make.log
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: rtl8821ce-dkms 5.5.2.1-0ubuntu4
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.
I found out that I should look in the gnu.trace file, there these lines
are logged:
* 12:41:37 ERROR swift.c: 524: Too many bytes in line, maybe not
SWIFT
* 12:41:37 ERROR swift.c: 111: Error importing data (-1)
* 12:41:37 WARN gnc_file_aqbanking_import: Error on
import
I tried this with
opens
Experienced behaviour: File dialog just closes
I tried to run with --extra CLI option for extra info, but it fails
silently.
Thanks in advance for your efforts.
Cheers,
Willem Voogd
** Affects: gnucash (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notifi
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1890978
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1891324
relevant info:https://bugs.launchpad.net/ubuntu/+source/grub-
installer/+bug/1890978/comments/4
--
You received this bug notification because you are a memb
discovered during a manual partitioning install ..
found that fstab had an entry for /boot/efi mount vfat type pointed to
the /dev/sdb2 efi partition of the install media (USB)
deleted the fstab entry..
also deleted the mount point /boot/efi as no EFI partition existed on
an MBR based system (
Public bug reported:
Using Lubuntu, Bug began not too long ago, fine before then, short
sounds are fine. Discovered bug using YouTube
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: pulseaudio 1:13.0-1ubuntu1.2
ProcVersionSignature: Ubuntu 5.3.0-64.58-generic 5.3.18
Uname: Linux 5.3.0-64-ge
had a quick look at the diff file between ubuntu thinderbird versions
78.2.1 and 78.2.2 .. there is a massive amount of deleted lines .. a lot
to do with twitter accounts .. is this on purpose or has something gone
amiss ..
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Happened on upgrade from 78.2.1 to 78.2.2 lost all folder views ..
Groovy .. regular updates via proposed..etc. (xubuntu flavour)
Installed thunderbird 78.2.2 from thunderbird.net into personal home
directory works properly..
so it is an ubuntu regression issue .. someth
Public bug reported:
The Scap security content is outdated.
The latest profiles only contain the vulnerabilities for Ubuntu 16.04,
while there is a profile for Ubuntu 18.04 available.
** Affects: scap-security-guide (Ubuntu)
Importance: Undecided
Status: New
--
You received this
Just wondering: Is there any news on this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876613
Title:
Wallpaper not retained between reboots
To manage notifications about this bug go to:
http
This doesn't work in 4.14.3-1 (Xubuntu 20.04). Setting a display as
primary does not move the panels & desktop icons to it, when the other
display is positioned left.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
@hatbollen, I tried the 2 commands but that did not resolve the issue.
My wallpaper still reverts to the/a default after rebooting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876613
Title:
Wallp
Just to make clear that I'm my case it's not an upgrade, but a clean
20.04 install.
** Description changed:
Linux willem-kubuntu-001 5.4.0-28-generic #32-Ubuntu SMP Wed Apr 22
17:40:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Running an up to date Kubuntu 20.04.
WHen i
I have tried to see if the location of the wallpaper is relevant to
whether or not the wallpaper is retained. I moved the wallpaper from a
network mount to a local mount of the laptop. Unfortunately that does
not solve the problem, Is there any log I could have a look at to find
some more informati
Public bug reported:
Linux willem-kubuntu-001 5.4.0-28-generic #32-Ubuntu SMP Wed Apr 22
17:40:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Running an up to date Kubuntu 20.04.
WHen i change the wallpaper from the default to some wallpaper I
downloaded (and used in 18.04), this new wallpaper will
** Attachment added: "Xorg.0.log for information"
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1873318/+attachment/5355667/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
Processor : AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx
Memory : 10112MB (985MB used)
-Display-
Resolution : 1600x900 pixels
OpenGL Renderer : AMD RAVEN2 (DRM 3.35.0, 5.4.0-24-generic, LLVM 9.0.1)
X11 Vendor : The X.Org Foundation
note when booting through recovery mode and then starting xubuntu the
user screen is normal no staircasing.. (different graphic driver)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873318
Title:
x
** Attachment added: "a view of the screen with xfwm4 running"
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1873318/+attachment/5355662/+files/Screenshot_2020-04-16_13-27-01.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Public bug reported:
This happens under xubuntu and lubuntu (if using xfwm4 as window manager
instead of openbox)
with the latest update xfwm4-4.14.1-0ubuntu1 ..
previoius version had no issues..
first happened under xubuntu installed lubuntu to determine if graphic
driver was the issue but pro
having multiple real installs on a computer of different versions of
linux (ubuntu spins, lts, development versions) allows testing in a real
environment .. as opposed to a vm .. was a standard practise prior to
vm's existing
--
You received this bug notification because you are a member of Ubunt
I was try to reproduce the bug on the same computer .. by adding another
install .. on another partition .. that worked .. bug was reproducible
..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872077
When I pass the device it shuts up..
OKAY .. my initial report was bug 1872097 my original and still existing
install partition (sda5) for focal ( dec 2019) I used dpkg-reconfigure
there and of course then debconf-get-selections did not give the correct
info ..
So I created a new partition (sda6)
ok: grub-install --target=x86_64-efi /dev/sda
works properly... sorry for the noise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872077
Title:
package grub-efi-amd64-signed 1.140+2.04-1ubuntu24 f
going back to the previous partition (trying to make it the default again)
I ran the following:
grub-install /dev/sda
Installing for x86_64-efi platform.
grub-install: warning: disk does not exist, so falling back to partition device
/dev/sda2.
grub-install: warning: disk does not exist, so fall
opps dropped a line at the end:
grub-install: error: disk `hostdisk//dev/sda2' not found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872077
Title:
package grub-efi-amd64-signed 1.140+2.04-1ubun
on a fresh install on a new partition of focal fossa (03/28) on
upgrading during the first boot into the install came across the same
error
did not "continue the install of grub-efi" so the disk was not altered
installed debconf-utils then ran debconf-get-selections | grep grub-efi
gave the foll
this crash happened to me on a fresh install of focal while doing the
first software update.
Blueman-applet was running in the panel and apparently is running again
after the crash ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
>From bug#1872097
Ran sudo dpkg-reconfigure grub-efi-amd64-signed
response was confusing .. but I approved the install and everything appears to
boot normally.
after installing debconf-utils ran command from comment#2 above.
sudo debconf-get-selections | grep grub-efi
grub-pc grub-efi/install_
*** This bug is a duplicate of bug 1872077 ***
https://bugs.launchpad.net/bugs/1872077
If I run dpkg-reconfigure it will install correctly .. but the
confirmation message is confusing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
still running previous version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872097
Title:
grub-efi-amd64-signed 1.140+2.04-1ubuntu24 throws an error during set-
up
To manage notifications about
Public bug reported:
An upgrade to this version failed
Fails with the following ..
Setting up grub-efi-amd64-signed (1.140+2.04-1ubuntu24) ...
Unknown device "/dev/": Inappropriate ioctl for device
Unknown device "/dev/": Inappropriate ioctl for device
Unknown device "/dev/": Inappropriate ioctl
after update .. not rebooted
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860851
Title:
blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't
decode byte 0x8e in position 4: invali
Public bug reported:
related to bug 1870858.. similar fault different program (parole)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vlc 3.0.8-4
ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29
Uname: Linux 5.4.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd6
RE: Yoannjap
On my machine this is independent from the GSConnect extension. I did
not have it installed and installing/removing makes no difference. Bug
is there and is so consistently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
running apt --fix-broken install
does not fix the issue:
The following additional packages will be installed:
libvte-2.91-common
The following packages will be upgraded:
libvte-2.91-common
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to
I have mutter (3.35.91-1ubuntu1) installed and the bug is still there
(on 20.04 development branch) in both WPS and LibreOffice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852183
Title:
[X11] co
I am seeing this in my log as well,
Kubuntu 19.10
Linux willem-Aspire-A315-53 5.3.0-29-generic #31-Ubuntu SMP Fri Jan 17
17:27:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Operating System: Kubuntu 19.10
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.12.4
Kernel Version
I am seeing this on my Kubuntu 19.10
Operating System: Kubuntu 19.10
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.12.4
Kernel Version: 5.3.0-29-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 3,7 GiB
Linux willem-Aspire-A315-53 5.3.0
I am seeing this as well.
running Linux willem-Aspire-A315-53 5.3.0-29-generic #31-Ubuntu SMP Fri
Jan 17 17:27:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Operating System: Kubuntu 19.10
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.12.4
Kernel Version: 5.3.0-29-generic
fixed during/ or by the linux-5.4.0-13 kernel release
** Changed in: linux-signed-5.4 (Ubuntu)
Status: New => 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/1860561
Title:
cpu l
Public bug reported:
similar to previous issue with 5.4.0-11 cpu lockups note plymouth only
runs in terminal mode instead of graphic mode .. prior to lockups .. 22
seconds watch dog show alerts for systemd-udevd on cpu1 , [migration]
processes 1,2,3 on cpu 2,3,4 this repeats every 22 seconds
a r
Public bug reported:
version linux-image-5.4.0-11-generic fails to boot at leat two cpu
lock ups 2 and plus hardware failures
version linux-image-5.4.0-9-generic works fine
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-11-generic 5.4.0-11.14
ProcVersionSignature: Ubu
Can also confirm being affected by this bug. Strangely it randomly
happens in LibreOffice for me, but constantly in WPS Office. When I copy
something it either pasts nothing (suggesting nothing was copied) or
pasts as a bitmap. Sometimes this bitmap shows all content that was
copied, sometimes a ra
Public bug reported:
system problem at login a few seconds after xfce desktop appears
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups-browsed 1.26.0-1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Architecture
A work around exists .. at the pause .. do you want to continue? in
another terminal manually edit /etc/apt/sources.list to change all eoan
to focal ..save then press y to proceed and everything proceeds normally
..
my comment #9 was incorrect the first list shown is eoan then the
sources are sw
In fact in comment #7 the first package list after opening focal.tar.gz
should be based on focal as well ..
so the focal.tar.gz appears to be a renamed eoan.tar.gz not the true
focal upgrade core.. !!!
what happened!!! .. I know the mirrors were messed-up nov 1-nov2 ..
did other files get renam
appears to be using eoan package sources for focal upgrade..
first check normal state of apt update to eoan for reference:
derk@zlink1 ~ $ sudo apt update
Hit:1 http://ca.archive.ubuntu.com/ubuntu eoan InRelease
Hit:2 http://ca.archive.ubuntu.com/ubuntu eoan-updates InRelease
Hit:3 http://ca.arch
Happens to me too and only happens on the "Frequent" section (like Paul
above). The "All" section is fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842053
Title:
One or two app icons appear un
seeing this on 18.04.3 xubuntu:
Aug 18 17:25:32 LAPTOP gpu-manager[806]: Error: can't open
/lib/modules/5.0.0-25-generic/updates/dkms
Any more info I can provide?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Seeing this on Linux LAPTOP 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu
Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux, running xubuntu
18.04.3.
description: Notebook
product: Aspire A315-53 ()
vendor: Acer
*-pci
description: Host bridge
pr
Two network printers on local LAN. Potentially more network printers
discoverable across VPN, but not configured in CUPS. Will report to
upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183824
SAL_DISABLE_CUPS=true libreoffice
resolves the issue
None of the others do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838249
Title:
crash on startup
To manage notifications about this bug go
Same result.
I also tried adding
false
in case it was OpenCL instead of OpenGL.
Still crashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838249
Title:
crash on startup
To manage notification
Here is what I did:
sudo apt autoremove --purge libreoffice*
sudo reboot
rm -Rf .config/libreoffice
sudo apt install libreoffice-writer
mkdir -p .config/libreoffice/4/user/
cp -a registrymodifications.xcu .config/libreoffice/4/user/
This is registrymodifications.xcu
http://openoffice.org/2001/r
Disabling OpenGL DOES NOT resolve the issue. I previously added
false
false
to the registrymodifications.xcu and it still crashes with the same traceback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Any hope of getting this looked at?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838249
Title:
crash on startup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
Same problem with or without --safe-mode:
localc --norestore --safe-mode
dbus[893]: arguments to dbus_message_iter_append_basic() were incorrect,
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file
../../../dbus/dbus-message.c line 2754.
This is normally a bug in some application us
The new version of xsnow is now available on sourceforge:
https://sourceforge.net/projects/xsnow/
>From the website:
Finally, a working xsnow for Gnome, KDE, etc. Based on the original
xsnow-1.42 created by Rick Jansen, after the xsnow-2019 conference in
Antas (Spain) we now have available a xsn
There is a new xsnow, based on the original, working in gnome, kde,
fvwm, lxde, raspbian and probably many more:
https://www.ratrabbit.nl/ratrabbit/content/xsnow/introduction
It is the intention to push this version to the Debian repo's.
--
You received this bug notification because you are a me
happened while attempting to add an app to an an existing launcher menu
list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/92787
Title:
[apport] xfce4-panel crashed with SIGSEGV in g_slice_alloc()
Fine tuning: only one extra mount is necessary .. then plymouth
finishes very quickly .. and xorg/lightdm start normally!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821609
Title:
lightdm login
** Summary changed:
- lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 (boot timing issues implicated)
--
You received this bug notification because you ar
okay I have another solution to the timing issue .. add two partition
mounts to fstab ..
my existing sda1 disco install has /home (sda2) and /home/store1 (sda5)
mounted via fstab .. this was the original install configuration .. thus
always a mount delay ..
to test .. added the same partions to
1 - 100 of 769 matches
Mail list logo
