Lubuntu hirsute (daily) test on
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
repeat of testing covered in comments #10-12 on different box
On both dc7700 (#10-12) & this box, I was unable to correct issue
(changing wallpaper would change half visible on the one display; other
would remai
** Description changed:
Originally Lubuntu 19.10 daily
deb cdrom:[Lubuntu 19.10 _Eoan Ermine_ - Beta amd64 (20190926.1)]/ eoan main
multiverse restricted universe
I adjusted the monitor.settings to match my setup, also changing the
primary screen and it did exactly what I wanted, howev
I can re-create this on opensuse tumbleweed
My tumbleweed is using openbox too, reaction is identical with menu
being LXQt on the display with wallpaper, openbox menu appearing on now-
black monitor...
Issue occurs with one screen orientation, reverse it and issue does not
occur.
this needs
Turns out Debian Bullseye/sid is running LXQt 0.16 too, so tested there
and could create it there too.
** Description changed:
Originally Lubuntu 19.10 daily
deb cdrom:[Lubuntu 19.10 _Eoan Ermine_ - Beta amd64 (20190926.1)]/ eoan main
multiverse restricted universe
I adjusted the monito
On the debian bullseye/sid box, I switched out openbox ..
I could NOT re-create the issue using `xfwm4`
I could NOT re-create the issue using `icewm`
switching back to openbox & issue could be re-created again..
it's openbox only it appears... so maybe this issue is mis-filed?
(I'm also tired, b
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can
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 1917101
When reporting bugs in the future please use apport by using 'ubuntu-
bu
FYI: A picture, or (link to) short video may also help.
Yes your description reminds me of issues I experienced with Lubuntu
18.04.5 (radeon too, using HWE kernel, but issues didn't exist using GA
kernel including when updated to 18.04.5), but without photograph/video
evidence, it could be someth
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
(You mentioned removing "every ppa repository", but did that most
importantly include packages that w
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 1917131
When reporting bugs in the future please use apport by using 'ubuntu-
b
Possibly related to
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1917175
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917178
Title:
As of today in hirsute no longer possible to use open-fpr
Possibly related to
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1917178
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917175
Title:
gdm login screen says "Something went wrong please try
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 1917191
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can
Lubuntu hirsute QA-test install on sony vaio thingy
testcase: uEFI, full disk, no internet, no encryption, no swap
Installation Failed
---
External command finished with errors.
Command apt install -y --no-upgrade -o
Acquire::gpgv::Options::=--ignore-time-conflict grub-efi-$(if grep -q 64
/sys/f
sorry I was intended to upload session.log
** Attachment added: "~/.cache/calamares/session.log"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1917292/+attachment/5471458/+files/session.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I didn't want to FAIL the QA-test, so I
- quit calamares
- restarted calamares
- "manual partitioning" install..
but that too failed with the same error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
You say "I can install Ubuntu 20.10 But I can't Map any Local Network
Drives" so the installation of
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. Bu
Thank you for reporting this bug, and helping to make Lubuntu better.
I can only comment, your exploration (and testing) of the system is
further than my own, as I tend to concentrate on things I use, and think
I'd use for various use-cases I can imagine, so well done & thank you.
I had a quick p
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 1917446
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can
If you believe I'm in error, please leave a comment as to why, and you
can change the status back to "New".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917554
Title:
VGA driver not available for
I fear this is the consequence of an announced google chrome/chromium
change, and will not be changed (in fact the API is being removed in the
not too distant future and this is just the start of the the changes
announced with
https://developers.google.com/web/updates/2020/12/chrome-88-deps-rems)
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. B
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 1928559
When reporting bugs in the future please use apport by using 'ubuntu-
bu
I'll provide my 2c.
Hirsute (21.04) ISO is already released & development completed. Only
security fixes are now being performed on the now stable 21.04 system,
which does not include this issue (as this issue relates to the ISO
itself, and re-spins are only done for LTS releases, ie. next ISO wi
Public bug reported:
I'll add detail shortly.
QA-test install on d755-5, upgrade via re-install process.
re-use sda6 as / (no format)
re-use sda7 as /home (no format)
This was a 18.04/bionic install; though I've tried to install Lubuntu
focal daily on it twice (errors twice) so this could reve
** Description changed:
- I'll add detail shortly.
+ QA-test install on
+ - dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
- QA-test install on d755-5, upgrade via re-install process.
+ Upgrade via re-install process.
re-use sda6 as / (no format)
re-use sda7 as /hom
** Description changed:
QA-test install on
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
Upgrade via re-install process.
re-use sda6 as / (no format)
re-use sda7 as /home (no format)
+
+ Error I see:
+ May 18 06:03:42 kubuntu /plugininstall.py: Could not
** Description changed:
QA-test install on
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
Upgrade via re-install process.
re-use sda6 as / (no format)
re-use sda7 as /home (no format)
Error I see:
May 18 06:03:42 kubuntu /plugininstall.py: Could not
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 1928744
When reporting bugs in the future please use apport by using 'ubuntu-
bu
changed HWE to linux as I see no reference to a HWE (5.4) kernel
** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
@piotr (peterq94)
refer comments #22 & #24 on this report.
I've written about this (work-around) on Lubuntu's discourse I believe
too (https://discourse.lubuntu.me/t/login-screen-flashes/1634/7 and
maybe elsewhere too). I've lost access to the d990 (which wasn't my
box) so I can't test further
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is mostly about finding & fixing problems thus preventing
future users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can
Public bug reported:
I'll add details shortly (on real keyboard)
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: casper 1.461
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu66
Architecture: amd64
CasperMD5CheckRe
** Description changed:
- I'll add details shortly (on real keyboard)
+ Lubuntu impish daily (QA-test) live boot on
+ - motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
+
+ At computerbank (CBV Victoria) we timed boots of Ubuntu installs and if
+ they didn't meet a minimum requirem
Booted the current focal daily (what will become 20.04.3) on
- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
Stop watch started at GRUB screen when I pressed ENTER for Start Lubuntu
~50 secs the plymouth screen was shown & it was validating media (showing %
progress; this actual
This issue still exists in impish.
Refer https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1928939
Current Lubuntu Focal daily vs Impish daily
plymouth: Focal: ~46 sec Impish: 7 mins 20 secs
scan media start: Focal: ~50 sec
scan media pass: Focal: 3 min 08 sec
black screen & mouse-pointer: Fo
Focal QA-test can be found at
http://iso.qa.ubuntu.com/qatracker/milestones/408/builds/230902/testcases/1303/results/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928939
Title:
excessive boot time
Lubuntu 18.04 is EOL (see https://lubuntu.me/bionic-eol/) as flavors
only provide 3 years of supported life (using packages found in
'universe').
Main Ubuntu Desktop, Server and packages from 'main', which include the
kernel you're asking do have 5 years of support with regards security
fixes.
I
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
This package failure looks like it was caused by bad ISO download,
corrupted install media, or device failure. eg. look in the logs and
you'll see messages like these :-
May 20 03:28:18 ubuntu kernel: [ 229.997
Public bug reported:
Ubuntu impish daily written to thumb-drive using GNOME-DISKS (restore image)
takes 11 mins 17 secs to boot (stop watch started @ grub)
will add details when at a real keyboard; and mark it duplicate..
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: casper 1.461
ProcVer
*** This bug is a duplicate of bug 1928939 ***
https://bugs.launchpad.net/bugs/1928939
** Description changed:
- Ubuntu impish daily written to thumb-drive using GNOME-DISKS (restore image)
+ Ubuntu impish daily written to thumb-drive using GNOME-DISKS (restore
+ image)
+
+ QA-test on
+ -
+
*** This bug is a duplicate of bug 1928939 ***
https://bugs.launchpad.net/bugs/1928939
** Description changed:
Ubuntu impish daily written to thumb-drive using GNOME-DISKS (restore
image)
-
- QA-test on
- -
- motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
-
** Comp
See duplicate
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1929029
for comparison of times using Ubuntu daily.
Ubuntu impish daily written using GNOME-disks (restore image)
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
takes 3 mins 30 secs to be fully operational
- motion comput
** Package changed: ubuntu => ubuntu-release-upgrader (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929146
Title:
Can't upgrade from 18.04 to 20.04
To manage notifications about this bug
You can find help with your problem in the support forum of your local
Ubuntu community http://loco.ubuntu.com/ or asking at
https://askubuntu.com or https://ubuntuforums.org, or for more support
options please look at https://discourse.ubuntu.com/t/community-
support/709
(I intended adding this s
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
The error message you obtained says
"* Unofficial software packages not provided by Ubuntu
Please use the tool 'ppa-purge' from the ppa-purge
package to remove software from a Launchpad PPA and
try the upgrade a
*** This bug is a duplicate of bug 1922342 ***
https://bugs.launchpad.net/bugs/1922342
** This bug is no longer a duplicate of bug 1928939
excessive boot time with nothing on screen but blinking cursor (some bios
boxes only); ubuntu/lubuntu impish daily
** This bug has been marked a duplic
*** This bug is a duplicate of bug 1922342 ***
https://bugs.launchpad.net/bugs/1922342
** This bug has been marked a duplicate of bug 1922342
HIrsute live session takes ages to boot on BIOS systems
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
I'm 'floored' (WOW) by Thomas Schmitt (scdbackup)'s comment 32.
The long delay still exists in impish (on some devices only).
Ubuntu impish - https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1929029
Lubuntu impish - https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1928939
Delay occurs
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 1929213
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. B
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://w
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old a
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. B
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Tags added: disco focal hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827501
Title:
keyboard layout different changes during installation set-up and boot
for de-encrypting unencrypting
(No this is unlikely to be fixed I'm closing a few bugs currently,
and can say with an extremely high certainty that the Lubuntu team will
not fix this bug, but I won't close it, as bionic still has near two
years of life for 'main' packages, and if a wider Ubuntu community
member wants to fix
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also f
FYI: the askubuntu question I referred to can be found at
https://askubuntu.com/questions/1313885/how-can-i-change-the-frequency-
of-the-lubuntu-update-notifier-lubuntu-20-04
It'll outline how to change the value.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
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 1929346
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Also note:
> Anyone who wants to install Lubuntu 20.04 LTS in the BIOS
> mode with MBR, needs to go for a manual partitioning, and
> then creating a MBR partitioning table.
Lubuntu 20.04 LTS along with all releases, is QA-tested and installs
fine in all BIOS boxes tested (the team has access to).
*** This bug is a duplicate of bug 1927928 ***
https://bugs.launchpad.net/bugs/1927928
Public bug reported:
2021-05-26 - 14:34:13 [1]: ERROR: Installation failed:
2021-05-26 - 14:34:13 [6]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
- message: "E
** Tags added: hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929709
Title:
Segmentation fault on launch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
Public bug reported:
2021-05-27 - 15:15:52 [1]: ERROR: Installation failed:
2021-05-27 - 15:15:52 [6]: void
Calamares::ViewManager::onInstallationFailed(const QString&, const QString&)
- message: "Failed to unpack image \"/cdrom/casper/filesystem.squashfs\""
2021-05-27 - 15:15:52 [6]: void
typed wrong package name sorry
** Attachment added: "~/.cache/calamares/session.log"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1929776/+attachment/5500610/+files/session.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
We've also had a user report it on 18.10/cosmic (closed as EOL so no
clues)
https://discourse.lubuntu.me/t/installation-failing-error-code-11/940
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929776
** Attachment added: "sudo dmesg >dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1929776/+attachment/5500611/+files/dmesg.txt
** Description changed:
+ 2021-05-27 - 15:15:52 [1]: ERROR: Installation failed:
+ 2021-05-27 - 15:15:52 [6]: void
Calamares::ViewManager::onIns
I've had this before it turns out... (groovy on different box)
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1894364
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929776
Title:
lubuntu
Rebooted & repeated install... same issue
`sudo -E calamares -d` was used to start this time
** Attachment added: "~/.cache/calamares/session.log"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1929776/+attachment/5500623/+files/session.log
--
You received this bug notification be
Public bug reported:
Xubuntu focal install using daily on
- sl510
was a 18.04 install
- sda1 = / (no format, ext4)
- sda5 = /home (no format, ext4)
because no re-size is used, nor a format, I'd have expected install to
progress rather quickly but it's stayed at the "who are you" (where I
enter u
A quick glance and I note
May 27 07:59:28 xubuntu ubiquity: apt_pkg.Error: E:Write error - write (28: No
space left on device), E:IO Error saving source cache, E:The package lists or
status file could not be parsed or opened.
May 27 07:59:28 xubuntu ubiquity:
May 27 07:59:28 xubuntu ubiquity: D
install was maybe in artful (17.10) days... turns out I have an
encrypted /home (sda5) partition & didn't realize it...
I suspect this is 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/19297
I'm now rather suspicious, being a laptop I had encryption on (sda5)
/home (using a method that was common likely in artful days?) which
possibly created the issue..
/ or sda1 was not encrypted..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
this issue is inconsistent.
I've booted today's focal daily on
- lenovo thinkpad x201 (i5, 4gb, i915)
and had it NOT OCCUR
then on a subsequent boot
I'm without icon pictures (look like shadows) on the desktop (for
mounted drives) & menu items are square boxes & CTRL+ALT+T doesn't work.
`xfset
install was re-tried (third time) on
- lenovo thinkpad sl510 (c2d-t6570, 2gb ram, i915)
manual partitioning; no format with sda1 as / , sda5 /home
On third attempt
- space was created on /
- I installed `ecryptfs-utils` before starting ubiquity
all great this time
** Changed in: ubiquity
This bug report is about 2 network icons on taskbar on package that is
now EOL; nothing will happen.
If the issue also occurs in Lubuntu 20.04 LTS that is supported; the
software stack is very different (different desktop for starters) so a
new bug should be filed.
> How I can help you with find
** Package changed: ubiquity (Ubuntu) => grub-installer (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929888
Title:
grub crashed while installing Ubuntu on a Dell D620 with Nvidia 110
gp
Top right you should see a "Padlock This report contains Public
Information Padlock" type area which you can change to a higher
setting...
Too high though and other users of launchpad won't be able to see it and
click the "affects me too" providing the confirmation required for it to
get attention
If you need support, I suggest you ask on a support site (see
https://discourse.ubuntu.com/t/community-support/709)
If you note the bug you referenced in your last comment (#8), the MATE
issue was fixed in hirsute; or what was the then development release
(21.04 now) listing the package containing
Sorry I didn't notice the request for info...
Hirsute has released so it doesn't matter there...
I can resurrect this if I confirm it's the case with impish.
I zsync'd today's Xubuntu ISO (impish) and confirm the issue remains :(
- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon h
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
I've not tagged it again (in QA-test), so no evidence of re-occurrence.
I just completed a QA-test install (impish) to
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
all looks good, I also rebooted the device twice and greeter had
background images both times.
(the case where it was r
Just did a manual install (impish daily; re-use partitions (/ & efi)
from the prior install) and again no issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898975
Title:
xubuntu groovy qa-test
Thank you for taking the time to report this bug and helping to make
Ubuntu better
The upgrade is not currently open, to avoid systems upgrading and
failing to boot post-upgrade due to bug.
If you read the release notes -
Kubuntu 21.04 release notes -
https://wiki.ubuntu.com/HirsuteHippo/Releas
Please refer to my prior comment.
The shim issue in https://bugs.launchpad.net/ubuntu/+source/ubuntu-
release-upgrader/+bug/1930369 has not been corrected.
(I addressed the update is available & then no longer available in that
comment with a provided answer found on a support site)
Your pastes
Public bug reported:
Error report uploaded primarily so I can peruse & hopefully learn from
it.
My primary box; dual-boot/alternate 18.04 system
Cause for sure will be 3rd party as reported...
(I have no idea what's on it; haven't used this install since the early cosmic
cycle)
This was li
I removed telegram, skype, virtualbox, cool-retro-term packages &
commented out sources (& apt autoremove);
I didn't expect issues with costales/anoise, and chose to ignore
google/chrome or opera/stable
Again tried to release-upgrade; again 3rd party packages error.
I then removed ubuntu-mate-c
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Lubuntu 18.04.5 was the last Lubuntu to use the LXDE desktop, and
supported upgrades can only be performed via re-install, ie. release
notes of 18.10 & later contain text like the following (found in
https://lubunt
** Package changed: ubuntu => gnome-maps (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930699
Title:
gnome-maps fails to start
To manage notifications about this bug go to:
https://bugs.l
Public bug reported:
System was recently upgraded to 20.04 (upgrade via re-install) so I was
exploring
A "Recommended Graphic Application" however when selected shows
"WARNING: THIS SNAP IS UNMAINTAINED. CONTACT ME IF YOU WISH TO MAINTAIN
IT."
The goodwill-type value of store risks being erode
101 - 200 of 3883 matches
Mail list logo
