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 1902802
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Please run apport-collect on the system where you experience the hanging
(failure to shutdown)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902802
Title:
live L/X/K/UBUNTU under YUMI, hangs on re
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 1903029
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Users are still seeing this, eg. https://askubuntu.com/questions/1289286
/upgrading-with-1386architecture (yesterday though user is non-
technical & vague)
(though the number of users reporting it aren't great, likely less than
one a week that I see)
--
You received this bug notification becaus
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 1903212
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. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1903206
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.
If GNOME-shell suffers from a crash, all programs are killed & the user
is logged out. There can be many reasons for this, however it's not
related to the `ubuntu-release-upgrader` package which upgrades a
release
This issue can re-created by booting the Lubuntu daily live (hirsute),
logging out and as you go to `sddm` you see the issue. done with
today's hirsute daily.
@Kai-Heng Feng (kaihengfeng)
Using the installation done in comment #21-22, I added
- lightdm
no issues discovered, I could login norma
continuing comment #24 (links to photos)
- gdm3 photos
https://photos.app.goo.gl/koM6HAL4ZDFDTdvc8
https://photos.app.goo.gl/SgBroo8vrMB8Bp6K9
https://photos.app.goo.gl/txdBXNVxii5mHZrZ6
https://photos.app.goo.gl/TVLNm4WFuPQbsTSq6
- logged into plasma (missing character example)
https://photos
Walter/wxl asked me to test `sddm-theme-breeze` I skipped in comment
#22, report posted (https://discourse.lubuntu.me/t/login-screen-
flashes/1634/17?u=guiverc) days ago now pasted here
---
I added `sddm-theme-breeze` and rebooted, yuk! (I had forgotten to perform the
`sudo update-alternatives --
Public bug reported:
Intending to explore an unrelated issue with sddm/video-graphics
(https://bugs.launchpad.net/bugs/1895905) I booted the current hirsute
daily on
dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt)
sddm & video issue primarily, using hirsute for comparison)
No "T
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1903378/+attachment/5432103/+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/1903378
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1903378/+attachment/5432102/+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/
apport information
** Attachment added: "UbiquityDebug.txt"
https://bugs.launchpad.net/bugs/1903378/+attachment/5432104/+files/UbiquityDebug.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19033
apport information
** Attachment added: "UbiquityDm.txt"
https://bugs.launchpad.net/bugs/1903378/+attachment/5432105/+files/UbiquityDm.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903378
Ti
apport information
** Description changed:
- To be filled in (on decent keyboard)
+ Intending to explore an unrelated issue with sddm/video-graphics
+ (https://bugs.launchpad.net/bugs/1895905) I booted the current hirsute
+ daily on
+
+ dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600
apport information
** Attachment added: "UbiquitySyslog.txt"
https://bugs.launchpad.net/bugs/1903378/+attachment/5432106/+files/UbiquitySyslog.txt
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1903378/+attachment/5432101/+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/1903378
I'm going to use this for a like issue on amd64/hirsute
QA-test (Kubuntu HIRSUTE daily) on
dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt)
(exploring sddm & video issue primarily, using hirsute for comparison)
session is horrid; graphic glitches are a PAIN. mainly black triangular
Used box with Kubuntu hirsute daily
dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt)
The session there was almost impossible to use (flashing quickly gave me a
headache & made me feel queezy). I filed issue under
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1891408
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.
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 1903630
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. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1903794
When reporting bugs in the future please use apport by using 'ubuntu-
bu
filed https://gitlab.freedesktop.org/drm/nouveau/-/issues/20
** Bug watch added: gitlab.freedesktop.org/drm/nouveau/-/issues #20
https://gitlab.freedesktop.org/drm/nouveau/-/issues/20
** Also affects: linux via
https://gitlab.freedesktop.org/drm/nouveau/-/issues/20
Importance: Unknown
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 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.
Public bug reported:
I'll fill in shortly
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: calamares 3.2.32.1-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
.etc.calamares.modules.finished.conf:
---
restartNowMode: user-checked
restar
I suspect of no use, but I started filing the bug before install completed.
The session.log is attached.
I've not noticed this behavior (cursor jumping to end of field) anywhere
else, but I'll now look for it.
** Description changed:
- I'll fill in shortly
+ Lubuntu hirsute daily QA-test install
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 1904485
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.
You've filed this bug against ubuntu-release-upgrader, but don't seem to
describe a problem related to the upgrade process, so I'm a little
confused by that.
I get the (uneducated) feeling that it relates to GNOME
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 1904672
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Using my Lubuntu hirsute system, I installed gnome-nibbles & played a
bit... On working out what was going on, I killed my character and crash
guiverc@d960-ubu2:/de2900/lubuntu_64$ gnome-nibbles
Gtk-Message: 16:48:02.401: Failed to load module "appmenu-gtk-module"
(gnome-nibbles:263865): dbind
** 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/1904672
Title:
Game crash when a player dies
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+so
Public bug reported:
Lubuntu hirsute daily install on dc7700 with internet
https://ipapi.co/json reports
---
ip "58.7.111.61"
version "IPv4"
city"Melbourne"
region "Victoria"
region_code "VIC"
country "AU"
country_name"Australia"
country_code"AU"
country_code_iso3
session.log at completion of install
** Attachment added: "~/.cache/calamares/session.log"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1904974/+attachment/5436281/+files/session.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
I did a QA-test install of Lubuntu hirsute on dc7700 (with internet)
[not sure it's important, it detected my location as perth; west side of
australia instead of east side; about ~2722km out as the bird flies]
On reboot & first install, I got the prompt telling me there were
updates & I entered
Another QA-test install on different box (d755-8) and same issue.
Web search reported me in Melbourne, but calamares on screen said Perth
Identical IP address (dynamic); but my ISP's head office is Subiaco
(Perth) WA which is where it reports, and occasionally my GeoIPlocation
reports me at that l
** Description changed:
Intending to explore an unrelated issue with sddm/video-graphics
(https://bugs.launchpad.net/bugs/1895905) I booted the current hirsute
daily on
dell [optiplex] 990 (i7-2600, 16gb, nvidia geforce gt 6600 gt)
- sddm & video issue primarily, using hirsute for c
Kubuntu hirsute daily booted on
- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400
pro/xt)
attempt at full disk installation. I'm filing under this bug report,
however the response on this box is different (or it's changed since
initial filing).
I've got background on both
Another try of Kubuntu hirsute daily on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
different result on this box; no background, no mouse-cursor - just
BLACK SCREEN. result is the same though, session is unusable.
(this box usually doesn't give me troubles on installs)
Rik Mills has sug
Repeat of #14 boot on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
RikMills suggested I remove "maybe-ubiquity" from kernel line, I did so
and session booted normally :)
operation of system looks good, but listing here as it only booted with
"maybe-ubiquity" removed.
ALSO installer/ubiqui
Boot on (kubuntu hirsute daily)
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
normal boot (no change to kernel line), same ISO was written with `dd` as
before; prior boxes attempted tonight were BIOS, this is uEFI
on dell-755-8 (bios) the boot goes to background & mouse-pointer.
on hp
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 15.10 (wily) reached end-of-life on July 28, 2016.
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. But
Thank you for reporting this bug to Ubuntu.
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 and you might not be interested
in discussing it any more. Bu
Thank you for reporting this bug to Ubuntu.
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 and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be
Thank you for reporting this bug to Ubuntu.
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 and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
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.
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
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/783551
Title:
eee pc 901 power button does not work
To manage notifications about this bu
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
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. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
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.
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 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
** 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/1706701
Title:
Default Keyring is not unlocked for the user in Lubuntu
To manage notifications about this bug go to:
https://bugs
** Changed in: ibus
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325987
Title:
shuffled keys in keyboard buffer
To manage notifications about this bug go to:
http
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
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 to Ubuntu.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
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. But i
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
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. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
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. But
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 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 and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
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 and you might not be interested
in discussing it any more.
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 1589391
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.
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.
Thank you for reporting this bug to Ubuntu.
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 and you might not be interested
in discussing it any more.
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 9.10 (karmic) reached end-of-life on April 30, 2011.
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 to Ubuntu.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
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.
Thank you for reporting this bug to Ubuntu.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
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. But i
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 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. Bu
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.
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 1792877
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Thank you for reporting this bug to Ubuntu.
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 and you might not be interested
in discussing it any more.
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 1809951
When reporting bugs in the future please use apport by using 'ubuntu-
bu
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 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.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
Ubuntu 17.04 (
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
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.
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
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.
Thank you for reporting this bug to Ubuntu.
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 and you might not be interested
in discussing it any more. Bu
Thank you for reporting this bug to Ubuntu.
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 and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
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 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 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 1906794
When reporting bugs in the future please use apport by using 'ubuntu-
b
This is likely an upstream issue...
I just experienced this in Fedora 33; so NOT Lubuntu only
Qt 5.14.2, liblxqt 0.15.0 (details for upstream if/when filed)
(I'll aim to test in opensuse tumbleweed, and if occurs there, will file
upstream when I can)
--
You received this bug notification beca
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 1906919
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. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1906920
When reporting bugs in the future please use apport by using 'ubuntu-
bu
I could NOT re-create it on opensuse tumbleweed
Qt 5.15.1, liblxqt 0.16.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905947
Title:
lubuntu hirsute: display configuration doesn't survive logout/r
I booted opensuse tumbleweed again, tried again to re-create issue but
failed. (numerous display changes, apply&save, then logout & login
again.. repeated many times). opensuse is installed on hp8200 which
I've not reported the issue on, but I doubt that's important, it also
has fedora 33 which w
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Unfortunately, we cannot work on this bug because your description
didn't include enough information. You may find it helpful to read "How
to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bug
I've changed the status to "incomplete" as I think you need support more
than having a bug issue. If you believe I'm in error, or can better
explain the install issue (and how it relates to hplip), please correct
the description or leave a comment, and the status can be returned to
"New".
Thank yo
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
This installation looks like it was caused by a corrupted file system,
or device problems (sda1). I notice in the logs
Dec 7 11:19:51 ubuntu kernel: [ 720.753542] EXT4-fs error (device sda5):
__ext4_find_ent
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
There is no package named `ubuntu-manager-core`
https://packages.ubuntu.com/search?suite=all&searchon=names&keywords
=ubuntu-manager-core
You start with what looks like an `apt-cache policy apport` but then
switc
Public bug reported:
Ubuntu hirsute QA-test install on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
Testcase was replace partition sda1 using "Something-else" or 'Manual
partitioning', replacing the last Lubuntu QA-test install performed a
few days ago in the same manner without issue (reg
** Summary changed:
- hirsute QA-test install; 'grub-install /dev/sda failed' .. box regularly used
for QA-test installs
+ hirsute QA-test install; 'grub-install /dev/sda failed' .. box regularly used
for QA-test installs (BIOS only box, but uEFI error)
** Summary changed:
- hirsute QA-test i
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
replacing a partition (sda1), format ext4
grub install failed :(appears to be looking for uEFI when it's an old BIOS box)
`ubuntu-bug ubiquity` .. on hitting OKAY to restart box..
OH NO, SOMETHING WENT WRONG..
hit enter and again
OH NO, SOMETHING
** Description changed:
Ubuntu hirsute QA-test install on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
Testcase was replace partition sda1 using "Something-else" or 'Manual
partitioning', replacing the last Lubuntu QA-test install performed a
few days ago in the same manner wit
I re-did a Lubuntu QA-test install (current hirsute daily), "Replace a
partition" using same sda1 on same box without issues, so this is
something different to Lubuntu
(it's Lubuntu that I test most regularly)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
501 - 600 of 3989 matches
Mail list logo
