** Description changed:
19.04 daily image QA testing x86 & x86_64
Added additional info:
this bug was originally discovered on x86 & concentrates on firefox. It
occurs on other programs/windows (eg. qterminal, pcmanfm-qt) and occurs on
other systems (hp 8200 x86_64 qa-test, d980 x86_64
** Description changed:
Lubuntu 19.04 QA-Test
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
I have two monitors, both 1920x1080 in vertical arrangement (one above
the other). I boot 'live' image, and then navigate to
preferences->LXQt.settings->Monitor.settings then second 'Set
** Description changed:
QA-test of Lubuntu 19.04 (x86_64) on
"hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
and I'm getting lots of strange behavior on windows.. this for now will
cover the first noticed.
I have two monitors, both 1920x1080 in vertical arrangement (one above
** Description changed:
19.04 daily image QA testing x86 & x86_64
Added additional info:
this bug was originally discovered on x86 & concentrates on firefox. It
occurs on other programs/windows (eg. qterminal, pcmanfm-qt) and occurs on
other systems (hp 8200 x86_64 qa-test, d980 x86_64
** Description changed:
Lubuntu 19.04 [x86_64] installed system (upgraded from 18.04 85 days ago)
-
addendums:
1: package suggestion by krytarik on #lubuntu-devel
2: possibly duplicate; & my reason why no (but linked for sure!)
3: occurs on QA-test of 19.04 daily
1:
I'm sure I had experienced this on my recent opensuse tumbleweed install
(on 8200 box).
In trying to re-create it for bugzilla (opensuse) report, I could no
longer get it to occur, so have removed the mention in description &
make only this comment.
** Description changed:
Lubuntu 19.04 QA-Tes
** Description changed:
QA-test of Lubuntu 19.04 (x86_64) on
"hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)"
and I'm getting lots of strange behavior on windows.. this for now will
cover the first noticed.
I have two monitors, both 1920x1080 in vertical arrangement (one above
** Description changed:
19.04 daily image QA testing x86 & x86_64
Added additional info:
this bug was originally discovered on x86 & concentrates on firefox. It
occurs on other programs/windows (eg. qterminal, pcmanfm-qt) and occurs on
other systems (hp 8200 x86_64 qa-test, d980 x86_64
** Description changed:
Lubuntu 19.04 [x86_64] installed system (upgraded from 18.04 85 days ago)
-
addendums:
1: package suggestion by krytarik on #lubuntu-devel
2: possibly duplicate; & my reason why no (but linked for sure!)
3: occurs on QA-test of 19.04 daily
1:
I had this issue again today on
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400
pro/xt)
testcase: full disk, bios, internet, no-encryption
this box reliably has this issue, but I noticed something unusual after
the test when I tried to use the box instead for a 'live' te
It's been doing this since Monday for me (it's Wednesday my local time)
but I usually like confirming the issue on another box before I bug
report. On my other (qa-test install so almost untouched; nfs-common &
some very minor changes) box it uploads without issue? hence I didn't
file bug report.
I'll add my primary desktop (20.04 where I had this issue) is bloated
with lubuntu, xubuntu, ubuntu-mate & ubuntu desktops installed. It's
because of this that I test first on a 'clean' (or near clean) system as
well. I was using LXQt on both
--
You received this bug notification because you are
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 1863829
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Still crashes for me too
I closed chromium, `sudo apt update; sudo apt full-upgrade` and `snap refresh`
waited briefly, then re-open chromium, go to mewe & try and click icon to
upload a photo & crash before file-dialog...
I last rebooted a little under 10 hours ago
when I run `snap run chromium
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 :-
Feb 19 21:33:35 ubuntu kernel: [ 724.175
Nothing new, but I zsync'd latest ISO & did QA-test install on
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
and this bug occurred again, but it's the only box I've had this issue with
(not that I do full-disk installs on many boxes).
Using KDE Partition Manager
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
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 1864162
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 1863992
When reporting bugs in the future please use apport by using 'ubuntu-
bu
*** This bug is a duplicate of bug 1864270 ***
https://bugs.launchpad.net/bugs/1864270
Public bug reported:
Loading SGT Puzzles Collection from menu the launcher appears
On selecting Galaxies from the selection of games
Expected outcome:
-
I expect the game to start
Actual
*** This bug is a duplicate of bug 1864270 ***
https://bugs.launchpad.net/bugs/1864270
** This bug has been marked a duplicate of bug 1864270
can't open Galaxies from launcher
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
The ubuntu-release-upgrader package is used when you run `do-release-
upgrade` and move from 18.04 to 18.10, or in the future from 18.04 to
20.04 (future because it won't work yet as is enabled after 20.04.1 is
r
Still having this issue on
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400
pro/xt)
Full disk install, BIOS, no encryption & internet.
Disk contained last 20.04 QA-test install (performed comment #32)
--
You received this bug notification because you are a member of Ubunt
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 hadn't noticed request to upload session.log; so test re-performed,
failed and file uploaded from re-run of install
** Attachment added: "~/.cache/calamares/session.log (I hadn't closed
calamares; file was taken at point of 'cannot create partition sfdisk /dev/sda'"
https://bugs.launchpad.
QA- install on
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
testcase: manual partitioning, using free space, BIOS, ENCRYPTION, internet
On reboot, after validating the 'new' install I adjusted displays to
match my setup; and had https://bugs.launchpad.net/ubuntu/+source/lxqt-
session/+bug/1
QA-test install on dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon
rv610/radeon hd2400 pro/xt)
testcase: full disk, BIOS, no encryption, internet
the purpose of which is to test wxl's theory; ie. `sudo ln -s
/usr/bin/udevadm /sbin/udevadm` will be performed prior to starting
calamares/install
Public bug reported:
Currently I'm convinced this has been reported before, but I cannot find
it.
Lubuntu 20.04 daily QA-test, running through all menu options.
Assessories -> QtPass causes the dialog
"Please install GnuPG on your system. Install gpg using your .."
However package appears to
Public bug reported:
I'll add details shortly; also confirm if this is a duplicate of 1851188
Lubuntu 20.04 install on
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
(not the d755 that gets/got issue 1851188), but still maybe related
I was attempting to replace sda8 (/ wi
** Description changed:
- I'll add details shortly; also confirm if this is a duplicate of 1851188
-
Lubuntu 20.04 install on
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
(not the d755 that gets/got issue 1851188), but still maybe related
I was attempting to r
Public bug reported:
Another re-try (third fail), but I didn't reboot so I wonder if this
result is tainted by that...
Lubuntu 20.04 install on
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
Manual partitioning install; re-use space that prior to todays tests was
sda8 (bt
This bug is LIKELY related to http://launchpad.net/bugs/1864787
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864791
Title:
Lubuntu failed install "wipefs --all /dev/sda9"
To manage notifications
This bug is LIKELY related to
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1864791
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864787
Title:
Lubuntu failed install "sfdisk --force --a
I've had the issue again, same box, reboot & another re-try (4th maybe)
The installer failed to create partition on disk 'ST3160815AS'.
Create a new partition (22.00 GiB, ext4) on ‘/dev/sda’
Job: Create new partition on device ‘/dev/sda’
Command: sfdisk --force --append /dev/sda
Job: Create fi
xubuntu 20.04 QA-test on hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
another box where this issue occurred.
I also had strange white/black box pattern on boot that was rather
unpleasant, strobe-like effect on mouse movement but it soon settled
down. I did `dmesg |grep squash` & no squashfs e
booted today's daily on
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550
or system in main report, no background on boot?
i rebooted & same. Changing wallpapers works for some, but creates a
visual mess for others
** Attachment added: "just changed wallpaper; expected blu
I've a QA-test install going on
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
full disk, bios, internet & no-encryption.
This box would have previously failed with this bug, it's well past the
crash point so fix has worked.
Yeah WXL (#49) I'll likely have run ca
same dell optiplex d755
same issue, I didn't see anything in dmesg or journalctrl of note
** Attachment added: "~/.cache/calamares/session.log"
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1864787/+attachment/5331848/+files/session.log
--
You received this bug notification becau
I tried to use KDE Partition Manager to do what I expected `calamares`
to do and got
Could not delete file system on ‘/dev/sda9’.
Delete file system on ‘/dev/sda9’: Error
Delete partition ‘/dev/sda9’ (22.00 GiB, unknown): Error
This issue could be HARDWARE related; so I'll have to look at it
I'l
Another qa-test and I had repeat of 1864787 thus on completion I exited
& tried to use KDE Partition Manager to do what I expected `calamares`
to do and got
Could not delete file system on ‘/dev/sda9’.
Delete file system on ‘/dev/sda9’: Error
Delete partition ‘/dev/sda9’ (22.00 GiB, unknown): Erro
Public bug reported:
Xubuntu 19.04 daily (20190325) x86_64
Checked media integrity before booting.
This machine has two displays; right screen is rotated-left so in portrait
orientation.
I went into display settings, selected 2nd display and clicked
'rotation:' drop down until it showed left an
screenshot of what (display setup) I was trying to achieve.
I also tried alignment other variations (including when you select
'left' & initial placement)
** Attachment added: "Screenshot_2019-03-26_00-00-10.png"
https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1821652/+attachmen
I tested today using Xubuntu 19.04 daily (20190325) and could NOT re-create
this issue.
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
--
comment #10 was I believe build 20190322, and on box
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
ta
Xubuntu 19.04 DAILY (live) QA-Test (20190325)
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
general play using menu, I'd earlier added another panel, updates were
downloading & installing and whilst using menu crash appeared.
No unusual behavior was noticed.
http://iso.q
// PLEASE NOTE: this an next comment are re-do's of this, as my right-screen
rototated during this
// PLEASE NOTE: next comment is a retry of only some of the steps in this
I booted the live thumb drive (19.04 daily described above; it hasn't
been re-written).
Verified that my display.change was
// PLEASE NOTE: this is a re-do of prior comment (#5) at a slower pace
// PLEASE NOTE: and some steps only. Firefox wasn't loaded, I saved
// PLEASE NOTE: this to `mousepad` & is copied from there to launchpad
// my commentary or notes can be seen by ^// (// at start of line)
// opened term
// s
Lubuntu 19.04 daily QA-test (20190326.1 from /etc/apt/sources.list)
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
.
suspended system, waited, it resumed, circles on firefox, then after eth
reconnected it resumed (silently). vlc wouldn't play sound either...
:(https://bu
Public bug reported:
Lubuntu 19.04 (x86_64) QA-Test install
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
On first boot, i expected to see (on either display) a single login box
for username/password. Instead I got a box on each display (as if
mirrored) but no
I added all updates, did a reboot & same cosmetic issue remained.
I've also just done a no-internet install now (lubuntu 19.04 checklist);
with me resisting the urge to correct screen orientation this time.
Identical issue on no-network install; without any changes to screen
setup from default.
Public bug reported:
Lubuntu 19.04 full-disk encrypted install (BIOS)
Install went perfectly, rebooted on request however resulted in finding
myself in grub-rescue
I rebooted the install-media, and mounted the disk (using my passphrase)
and a cursory glance showed no issues. /boot & a few other
** Description changed:
Lubuntu 19.04 (x86_64) QA-Test install
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
On first boot, i expected to see (on either display) a single login box
for username/password. Instead I got a box on each display (as if
** Description changed:
Lubuntu 19.04 full-disk encrypted install (BIOS)
Install went perfectly, rebooted on request however resulted in finding
myself in grub-rescue
+
+ error: no such device: 969bff21-1ee3-490a-8922-6fc36941da6f
+ error: unknown filesystem
+ Entering rescue mode..
+ gr
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822249
Title:
calamares crashed with SIGSEGV in KPMHelpers::isPartitionNew()
To manage notification
** Description changed:
Lubuntu 19.04 QA checklist installs.
- This install was going to re-use my /home, and have auto-login enabled
- using manual partitioning.
+ This install was going to re-use my partitions (keep my /home & format
+ my /) and have auto-login enabled using manual partitio
I just re-tried this on a virtual box VM & it failed too
Host system: hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
Host OS: Fedora 29 x86_64
Virtual Box : 5.2.26 r128414 (Qt 5.6.1)
Lubuntu 19.04 ISO : 20190326.1
Install no issues, i okay reboot and pressed to remove ISO,
rebooted to
erro
changing to 'confirmed' due to second installation (VM) on different box
having same result
** Changed in: calamares (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
Lubuntu 19.04 x86_64 install
Working on https://phab.lubuntu.me/w/release-team/testing-checklist/?v=17
Install : "Full disk install with encryption on a EFI system without secure
boot"
System : sony vaio ultrabook (i5-9400u, 4gb, intel haswell-ULT)
Install was as expected
** Description changed:
- // i'll add more when on a real keyboard
+ Lubuntu 19.04 x86_64 install
+ Working on https://phab.lubuntu.me/w/release-team/testing-checklist/?v=16
+ Install : "Full disk install with encryption on a EFI system without secure
boot"
+ System : sony vaio ultrabook (i5-
booted 19.04 daily (yesterday's as I checked it too late) and
sudo add-apt-repository ppa:lubuntu-ci/unstable-ci
sudo apt full-upgrade
logout, login back in & install again.
same result; with only UUID value being different.
--
You received this bug notification because you are a member of Ubu
my last comment related to attempt on d780 box or the original box
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
I retried using 20190330 19.04 Lubuntu daily x86_64 with
sudo add-apt-repository ppa:lubuntu-ci/unstable-ci
sudo apt full-upgrade
logout, login agai
You can view this by booting the daily ISO (noticed on 20190330) by
booting it, logging out, and viewing the login screen there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822230
Title:
lubuntu
Attempted again on box :
sony vaio ultrabook (i5-9400u, 4gb, intel haswell-ULT)
using Lubuntu 19.04 daily x86_64 (20190330)
install, reboot & gnu grub 2.02 minimal bash..
Another attempt again on box
using Lubuntu 19.04 daily x86_64 (20190330)
sudo add-apt-repository ppa:lubuntu-ci/unstable-ci
s
I have booted the live-installer & then opened the sdd using `pcmanfm-
qt`, I was asked for my passphrase 'please' and it opened the partition.
All looks like I believe it should (for an installed system).
I don't know how it's supposed to get me to unlock the partition (ie.
asking for my 'please'
@chmp/@chmp99
x86 ISO's stopped being produced mid-late Dec-2018
(https://lubuntu.me/sunsetting-i386/) so no it won't be fixed for 19.04.
The x86 ISO's however would boot on any tested system that was x86 (the
machines it failed on above were really x86_64)
The x86_64 ISO however booted on each
Lubuntu 19.04 daily QA-Test comments -
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
adjust monitors to match my setup (change left & right position;
..
I'll explore https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1810075
as these are the same monit
** Summary changed:
- 19.04 BIOS full-disk install with encryption failed to boot (grub-rescue)
+ 19.04 Lubuntu BIOS full-disk install with encryption failed to boot
(grub-rescue)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
I followed Tom's REPRODUCTION test, and got exactly what Tom said I would.
I can confirm the issue with 256 character passwords.
(I used `wc` to count characters in my buffer)
I could set the 256 character password (I used it with a backspace to
enter the old password, so it was only 1 character
Booted up a Ubuntu 14.04 LTS box & followed test procedure.
Same result - steps followed fine until I once 256 char password was
entered, I was unable to `sudo whoami` (password was not accepted)
OS: Ubuntu 14.04.6 LTS x86_64
Host: HP Compaq dc7700 Small Form Factor
Kernel: 3.13.0-168-generic
** Description changed:
Lubuntu 19.04 (x86_64) QA-Test install
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
On first boot, i expected to see (on either display) a single login box
for username/password. Instead I got a box on each display (as if
I just booted a 'live' Ubuntu 19.04 x86 daily (note: old or last x86 daily) on
my eeepc
asus eepc 1000HE (intel atom n270, 1gb, intel mobile 945gse integrated)
My battery health (on panel) dropped from 80% when booted; to 79%, 78%
.. 76%. When I plugged in charger it changed image (orientation c
Downloaded 18.10 [x86], verified & wrote to thumb-drive. Booted in asus eeepc
1000HE
[ asus eepc 1000HE (intel atom n270, 1gb, intel mobile 945gse integrated) ]
and redid same test I did on [old] 19.04 Lubuntu daily image.
The battery was 75% charged when I started test, it dropped to 74%, 73%
on
Thank you for taking the time to report this bug and helping to make
Ubuntu better Ivan.
I hadn't opened or read the forum thread you (Ivan) posted in the
initial description, where I now see you noted different behavior when
using 'live' media to your 'installed' system; so my 'live' tests
wouldn
Public bug reported:
Lubuntu 19.04 [x86_64] installed system (upgraded from 18.04 85 days
ago)
When the screensaver takes effect, both displays go dim & go black for
maybe a second then one shows screensaver, the other returns to normal
display.
If i have windows (hexchat, htop/glances running)
on this box I normally don't have LOCKED SCREEN enabled, but I get the
same result if that box is ticked or not. I tried changing screensaver &
it made no difference (my default was random anyway), and the issue only
occurs in Lubuntu (not Xubuntu) so it's likely a different package or
config at fa
in #lubuntu-devel Krytarik suggested I try an older version
guiverc: From a quick web search and given the behavior, it
still seems likely that xscreensaver is at fault there though. Could
downgrade the packages you've got manually to the previous version here
and test if it's the same with tha
in #lubuntu-devel
guiverc: Okay. Try and reproduce this on a Lubuntu 18.04 Live
medium to perhaps exclude LXQt being a factor.
krytarik, does arch matter? (my box is x86_64, have found lubuntu
18.04 i686 thumb-drive) will that do?
or should i keep looking (or write a x86_64)?
No, can't ima
Lubuntu 19.10 QA-test (LIVE) using 2019-10-10 daily
No issues opening vlc from menu or using files (pcmanfmq-qt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842382
Title:
/proc/self/maps paths mi
Public bug reported:
19.10 Lubuntu daily (2019-10-10) install on sony vaio ultrabook
(i5-9400u, 4gb, intel haswell-ULT)
Install failed - @kc2bez first noted this providing
https://share.riseup.net/#qX3sjh1OqLVCHZdgqPNKdg
The ISO installs fine on BIOS machines, but has failed on EFI installs.
P
same issue with or without internet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847700
Title:
lubuntu 19.10 EFI install failed -- held broken packages 2019-10-10
daily
To manage notifications
** Changed in: lxqt-powermanagement (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846976
Title:
powel managment icon does not respond when computer is char
19.10 Lubuntu LIVE qa-tests (x2)
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
On 2nd d780 box my comments are (the MUTE/UNMUTE from panel is new) :-
suspend - it resumed without
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
This failure was caused by a corrupted file system, or device failure.
eg. look in the logs and you'll see messages like these :-
Oct 12 06:46:16 ubuntu kernel: [ 424.281840] SQUASHFS error: zlib
decompression
fyi: the SQUASHFS errors I saw relate to your install media, be it
CD/DVD/thumb-drive/etc, and maybe logical or physical. Once I saw them
I stopped looking as it wasn't a bug - but user error before the install
started... (what my prior message is talking about, ie. validate
download is flawless,
Update - the glitch appears to have gone, or more correctly moved.
I no longer see it at the left-side of my top monitor, but as it stands
now a `chromium` window has the vertical glitch in it's top 2/5ths of
bar. It won't stand out well in the attached picture (in real life it's
dancing in time w
Update - the glitch appears to have gone, or more correctly moved.
I no longer see it at the left-side of my top monitor, but as it stands
now a `chromium` window has the vertical glitch in it's top 2/5ths of
bar. It won't stand out well in the attached picture (in real life it's
dancing in time w
** Summary changed:
- vertical graphic lines glitch (on secondary top monitor)
+ vertical graphic lines glitch (on secondary top monitor) [possibly radeon
related]
** Tags added: disco eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is likely unhelpful, but Lubuntu doesn't use `ubiquity` (calamares
instead) and has had this issue awhile too. I just tested with current
2019-10-12 (22:30) ISO
(following cut/paste from QA-test comments)
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
re-install with sole purpose of loo
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
Examining the information you have given us, this looks more like you
need support rather than having a bug. Have you attempted to `sudo apt-
get -f install` or other usual first steps? You provided no evidence
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 1847975
When reporting bugs in the future please use apport by using 'ubuntu-
b
http://iso.qa.ubuntu.com/qatracker/milestones/407/builds/201047/testcases
I've done 2x installs using Xubuntu 19.10 (2019-10-12)
http://iso.qa.ubuntu.com/qatracker/milestones/407/builds/201047/testcases/1451/results
http://iso.qa.ubuntu.com/qatracker/milestones/407/builds/201047/testcases/1689/re
http://iso.qa.ubuntu.com/qatracker/milestones/407/builds/201047/testcases/1300/results/
"Install (entire disk) in Xubuntu Desktop amd64 in Eoan Daily" completed
without issue using 2019-10-12 (daily/final) -- identical install
testcase & same box
** Changed in: ubiquity (Ubuntu)
Status:
I just did an install 20191014 (20:02) using Lubuntu (BIOS, no-
encryption, internet) and had message to eject & press enter... :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837934
Title:
There
bionic (daily) test using 20191015 (latest 'daily')
http://iso.qa.ubuntu.com/qatracker/milestones/384/builds/201164/testcases/1303/results/
vlc is not found on ISO, so it was installed (`sudo apt install vlc`)
vlc opened from terminal, from menu, and from pcmanfm (ie. navigating to
files and cl
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I'm going to mark this bug as incomplete, as it reads very much that
you're an end-user having trouble with a web site, and not the hoster of
'Delta Wars'.
If however, you are the hoster of the site having trouble
I missed Erich's 18.10 is EOL; please re-test - so this is belated
sorry.
Issue still occurs - box is now eoan (19.10); different image
Load picture of bird; trimmed photo to 1920x1440 (didn't bother shrinking to
1920x1040)
Filters -> Eg -> ISO Noise reduction ... churns awhile then crash; nothi
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Wifi appears to be working on your 18.04 system where you filed the bug.
To gain information about problems with 19.04 the bug should be filed
whilst running Ubuntu 19.04
Ubuntu 19.04 is also 2/3rd through it's li
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
What is the problem? I don't see any description of the problem, what
you are trying to do, what you did, what occurred, or what you expected
to occur.
Unfortunately, we cannot work on this bug because your descr
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Have you verified your ISO download ? -
https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-ubuntu#0
or you could use the install media verification step
(https://help.ubuntu.com/community/Installation/CD
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848980
Title:
system hangs on suspend
To manage notifications about this b
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It looks like you've only recently installed 18.04.3, and are still
running 18.04.3 thus haven't used ubuntu-release-upgrader to move to a
later supported release; thus I'm marking this invalid (I've linked your
is
801 - 900 of 3989 matches
Mail list logo
