Thank you for your response, and effort to make Ubuntu even better.
InstallationDate: Installed on 2019-10-16 (4 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
You installed 18.04.3 yes, and it is supported till April 2023.
The ubuntu-release-upgrader package upg
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Tags removed: dist-upgrade
--
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 notifica
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 :-
Jan 28 05:17:10 ubuntu kernel: [ 1666.240
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 :-
Jan 29 00:29:40 ubuntu kernel: [ 351.847
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 :-
Jan 29 22:47:21 ubuntu kernel: [ 81.339
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
I suspect your failure may have been caused caused by bad ISO download,
corrupted install media (ie. bad write to your install media).
You filed the bug report against Ubuntu (not ubiquity) so details that
would
Public bug reported:
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
replace a 19.04 install I don't need anymore for support.
I didn't format, and it's now trying to 'Restoring previously installed
packages" which I expected it to produce some issues (packages
I'll endeavour to re-do this install tomorrow; over whatever was
installed on this partition... (on sda1)
It's been left another 30-40 minutes when I came to this box & looked on
launchpad for other issues like it, then created this issue, and yet
nothing on screen has changed
still "Restoring pr
apport information
** Attachment added: "UbiquitySyslog.txt"
https://bugs.launchpad.net/bugs/1861405/+attachment/5324185/+files/UbiquitySyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/186
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1861405/+attachment/5324183/+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/1861405
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1861405/+attachment/5324184/+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
** Tags added: apport-collected bionic lubuntu package-from-proposed
** Description changed:
dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
replace a 19.04 install I don't need anymore for support.
I didn't format, and it's now tryi
I eventually rebooted (using sysrq-reisub) given I couldn't start text
terminal, or gui-terminal to run apport-collect or ubuntu-bug.
The 'live' system was re-run, and apport-collect run on a freshly
rebooted system (same d780 box)
--
You received this bug notification because you are a member o
I realize this will be known (Walter), but related I believe to
https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1851188
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861465
Title:
Calamar
I have seen this also (most likely with flavors), but ignored it sorry
(probably over ~two weeks??? but very subjective)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861470
Title:
BIOS logo reappe
Today I re-zsync'd & wrote new 18.04.4 ISO to media, checked it valid as
usual, then attempted to re-install using same partition.
This install was flawless.. Options used should have been identical
(though partition data now reported as being 18.04.3 or data from last
install instead of prior 19
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
I see no evidence of you trying to perform a release-upgrade (ie. bump
yourself to a later release of Ubuntu) which is the purpose of the
ubuntu-release-upgrader package. Thus the package change. If I'm wrong,
p
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 1 00:06:48 xubuntu kernel: [ 343.04
The problem was your install media was corrupted, ie. either an
incorrect ISO was downloaded (md5sum or sda256sum wasn't performed to
check it's integrity), or the write to install media failed (thus it
wrote a corrupted or incorrect data) or the device was faulty and thus
didn't store the correct
Thanks for taking the time to report this bug.
I suspect your issues maybe related to issues on your system, and not a
software bug. You may want to 'fsck' your file system.
[ 429.038199] EXT4-fs error (device sda2): ext4_generic_delete_entry:2338:
inode #45875320: block 183509480: comm dpkg:
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 1861554
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Public bug reported:
Lubuntu 18.04.4 QA-test install testcase (Install Alongside)
Box has 3 drives; I want to install alongside the prior full-disk
install on SDA (ie. auto-resize)
I've tried this twice, it's only letting me select SCSI4/SDC (80gb)
where I want SDA/40gb drive
I'd expect the dr
Public bug reported:
Lubuntu 18.04.4 QA-install (i38)
hp dx6120mt (mini-tower, pentium 4 dual core, 3gb, winfast clone of
nvidia 7600gt)
Two prior installs on this box failed - filed under
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1861777 (not a
blocker bug in my opinion)
In hopes
** Description changed:
- Lubuntu 18.04.4 QA-install (i38)
+ Lubuntu 18.04.4 QA-install (i386)
hp dx6120mt (mini-tower, pentium 4 dual core, 3gb, winfast clone of
nvidia 7600gt)
Two prior installs on this box failed - filed under
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bu
Lubuntu 18.04.4 QA-test install
post-install & booting, I get grub-type brief text flash (also reminded
me of text unlock for encryption on [lubuntu] focal) then VAIO logo
again, black screen, VAIO then very brief plymouth then greeter
ie. I'm expressing an opinion this is occurring in BIONIC too
I'm trying to install Xubuntu 18.04.4 (QA-test) on the box using the
same drive (SDA), using full disk was good & completed (just like
Lubuntu), however using install-alongside like this bug related to; I'm
noticing errors on screen relating to other drives (sdb).
I believe this bug is related to
I'm trying to install Xubuntu 18.04.4 (QA-test) on the box using the
same drive (SDA), using full disk was good & completed (just like
Lubuntu), however using install-alongside which is what I was trying to
do and filed this bug.
Xubuntu 18.04.4 also won't let me select any other drive than SDC
-
Public bug reported:
hp dx6120mt (mini-tower, pentium 4 dual core, 3gb, winfast clone of nvidia
7600gt)
My last install (QA-test) was FULL DISK on SDA
I wanted to INSTALL ALONGSIDE that prior install on SDA; however it
won't let me select any drive other than SDC.
I had this same issu
** Description changed:
- I'll add this detail very shortly
+
+ hp dx6120mt (mini-tower, pentium 4 dual core, 3gb, winfast clone of nvidia
7600gt)
+
+ My last install (QA-test) was FULL DISK on SDA
+
+ I wanted to INSTALL ALONGSIDE that prior install on SDA; however it
+ won't let me sel
I changed my mind and filed Xubuntu on different report - hoping it'd
provide more detail as it's wasn't just a 'live' system, but a running
system which had details of `ubiquity` actually running
Filed under
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1861965
It's possible I had
I tried writing ubuntu-mate 18.04.4 i386 ISO (8x) to a thumb-drive but
validation failed each time until I had to go to sleep last night (new thumb
drive too)
Walter (wxl) asked me to add my 2c here
Fails on Lubuntu i386 (install alongside)
http://launchpad.net/bugs/1861777
http://launchpad.net
Public bug reported:
hp dx6120mt (mini-tower, pentium 4 dual core, 3gb, winfast clone of nvidia
7600gt)
((it didn't let me select drive which I hoped to do, but it's installing
install has hung up & is stuck -- I can use text terminal (ctrl+alt+f4)
so exploring..
on display is "Removed libfcit
** Description changed:
hp dx6120mt (mini-tower, pentium 4 dual core, 3gb, winfast clone of nvidia
7600gt)
- ((it didn't let me select drive which I hoped to do, but it's installing
+ ((it didn't let me select drive which I hoped to do, but it's installing
install has hung up & is stuck -
Public bug reported:
Kubuntu 18.04.4 (i386) QA-test install
install on hp dx6120mt (mini-tower, pentium 4 dual core, 3gb, winfast
clone of nvidia 7600gt)
my intention is to split prior full-disk install on SDA; dividing it
into two. (three drives & i only badblocks tested sda before 18.04.4
inst
On request I added this to my system (`sudo apt install`; 20.04)
I opened it at menu, it sat there happily without issue. A few menu
items were clicked without issue. Left alone 90+ secs without issue.
I went to https://lubuntu.me/downloads/ and grabbed a 19.10 magnet file,
and opened that in qb
I looked again and my issue may be slightly different, as not SIGABRT
(explicit) but SIGSEGV is detected when run from CLI
guiverc@d960-ubu2:/de2900/music$ qbittorrent
*
Please file a bug report at http://bug.qbittorrent.org and provi
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 1862144
When reporting bugs in the future please use apport by using 'ubuntu-
bu
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 6 13:01:31 ubuntu kernel: [ 175.548
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
I noted '' in your
messages, note after EOL has been reached mirrors can drop support for
the rel
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. At best your bug report could be read
as a feature request if it doesn't already handle it (support sites can
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 8 03:32:14 ubuntu kernel: [ 299.549
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.
*** This bug is a security vulnerability ***
Public security bug reported:
Clementine has been crashing many times a day in recent day(s).
I tried submitting `ubuntu-bug` each time, but no offers to login to
browser were offered (possibly because my stack was outdated as it had
started nagging m
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
Examining the information you have given us, this does not appear to be
a bug report so we are closing it and converting it to a question in the
support tracker.
We understand the difficulties you are facing, 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 1859530
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 reports are primarily about fixing problems so future users won't be
hit by the issue, where as support is more about fixing your current
issue.
This bug report can be converted to a question (which is aimed a
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. You seem to need support more than have
issues with a bug
>dpkg: error processing package linux-headers-4.15
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 issue and helping to make
Ubuntu better.
Jan 15 00:53:52 ubuntu kernel: [ 146.529219] ata1.00: NCQ disabled due to
excessive errors
Jan 15 00:53:52 ubuntu kernel: [ 146.529222] ata1.00: exception Emask 0x0 SAct
0x800 SErr 0x5 action 0x6 froz
I was able to re-create this using today's focal ISO (2020-01-15)
The only difference was as PRTSCR is now handled by `screengrab`, I
selected "Edit In.." and selected `lximage`.
[ sony vaio ultrabook (i5-9400u, 4gb, intel haswell-ULT) ]
** Tags added: focal
--
You received this bug notificat
Look at https://discourse.lubuntu.me/t/keep-monitors-attached-expected-
behavior/689 on hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290) on
very recent (yesterday?) install of 20.04 & this issue re-occurred.
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
(it shares same monitors as hp 8200 rep
I just noticed my primary d960 box (dell [optiplex] 960 (c2q-q9400, 8gb,
amd/ati cedar radeon hd 5000/6000/7350/8350)) has no wallpaper anymore
on it's top monitor, but 'top' of wallpaper on my bottom monitor.
The box was also used in testing mentioned in comment #3, but windows
covered the wallpa
I just noticed screensaver kicked in on both my displays on my primary
(d960) 20.04 box. This maybe the first time I've seen this on this box
since Lubuntu went to LXQt (whilst using LXQt/Lubuntu anyway).
The only change made relates to https://discourse.lubuntu.me/t/keep-
monitors-attached-expec
On d960 box..
To have screensaver hide only 'top' of my two displays (positioned one
above the other with top slightly right)
- tick "Keep monitors attached"
- move a monitor so they snap together
- in screensaver click 'preview' or wait until it kicks in
The screensaver will only show on top di
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
How far did you get in troubleshooting your issue? Can you login via
terminal? Have you space in your $HOME directory? (GUI logins require
the use of work files created there, if you're out of space login will
f
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 :-
Jan 12 21:40:18 ubuntu kernel: [ 39.408
Public bug reported:
Note: launchpad suggested
https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1815486 but it
related to an older version packaged for xenial/bionic however it could
be same issue
Ubuntu 20.04 LTS QA-test (live using latest daily)
dell [optiplex] 755 (c2d-e6850, 5gb, am
** Description changed:
Note: launchpad suggested
https://bugs.launchpad.net/ubuntu/+source/ristretto/+bug/1815486 but it
related to an older version packaged for xenial/bionic however it could
be same issue
Ubuntu 20.04 LTS QA-test (live using latest daily)
dell [optiplex] 755 (c
** Tags removed: iso-testing
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854668
Title:
trouble with ubuntu 20.04 daily (likely invalid, crappy thumb-drive?)
To manage notif
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
There are many support options and not just Ask Ubuntu, eg.
https://answers.launchpad.net/ubuntu, the support forum of your local
Ubuntu community http://loco.ubuntu.com/ or asking at
https://askubuntu.com or https
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
You've tagged this bug as relating to pulseaudio (ie. sound) thus
details about your system's sound was collected by apport. You however
describe a graphics problem so I'm changing package to xorg-server
** Packa
Please run this command again:
apport-collect 1860308
I have made 311 a duplicate of this one as this contained more
information
** This bug is no longer a duplicate of bug 1860311
After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts
--
You received this bug notific
*** This bug is a duplicate of bug 1860308 ***
https://bugs.launchpad.net/bugs/1860308
** This bug has been marked a duplicate of bug 1860308
After upgrade 19.01.2020 display resolution only 640x480. Lubuntu 18.04 lts
--
You received this bug notification because you are a member of Ubunt
Lubuntu 18.04.4 QA-test install on hp dx6120mt (box mentioned in last
comment)
I didn't realize there was anything in cd/dvd tray except post-boot
after install I noted 2x "Blank CD-R Disc" icons on desktop on first
login. I expected tray to be empty but it did contain a blank CD-R
(possibly b/c o
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 :-
Jan 20 18:19:36 ubuntu kernel: [ 409.908
Public bug reported:
Lubuntu 18.04.4 (daily) QA-test install on
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
The box hdd (80gb) had 2x prior installs sharing drive; the purpose of
install was to replace an existing install with this 18.04.4 image
(http://iso.qa.
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. You seem to need support more than have
issues with a bug
I believe a Support site would be more appropriate
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
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
http://loco.ubuntu.com/ or
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 :-
Jan 22 06:25:53 ubuntu kernel: [ 689.036
You have software that is not from Ubuntu repos, eg.
https://packages.ubuntu.com/search?suite=all&searchon=names&keywords
=xorg-video-abi-23
All the 3rd party details should be removed (ie. your system returned to
clean Ubuntu, then perform the release-upgrade, then add back any needed
3rd party s
Thank you for your report.
Ubuntu 18.04 LTS is intended to upgrade to Ubuntu 18.10
(https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes) or to Ubuntu
20.04 LTS (after 20.04.1's release), ie. the next release or next LTS
release.
If you read Ubuntu 19.04's release notes
(https://wiki.ubuntu.com/
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.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug. You seem to need support more than have
issues with a bug
I believe a Support site may be more appropriate,
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.04 LTS has two upgrade paths
1: non-LTS path is to the next release which was 18.10, is now closed as
it's EOL. That is the only upgrade path tested & supported off LTS path
2. to the next LTS which won't open until the launch of Ubuntu 20.04
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. You seem to need support more than have
issues with a bug
You appear to be using out-dated disco (19.04) pac
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
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 :-
Jan 27 10:46:27 backbox kernel: [ 303.09
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
Probable duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854798
"Synaptics, product: TM3108-002" (that report impacts Synaptics s3203 and
TM2714-002)
--
You received this bug notification
Same sessin as #23; except Qterminal is maximized
Qterminal is full width of display (landscape display) but has almost no height
and is unusable as a terminal. Top window dressing, menu & tab is about all
that can be seen
(technically this image was done before #23; but I enlarge
Monitor.Settin
20.04 QA-test on daily on dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar
radeon hd 5000/6000/7350/8350)
Purpose today was testing for a different bug so loads of different screens
setups were being tried.. I noticed I'd lost ability to maximize qterminal on
one display
This image shows scre
** Changed in: ubuntu
Status: New => Invalid
** Description changed:
- https://www.probola228.com/";
rel="nofollow">https://www.probola228.com/
- https://mahabola168.com/"; rel="nofollow">https://mahabola168.com/
- https://probola228.live/"; rel="nofollow">http://probola.live/
- https://j
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
Examining the information you have provided, this looks to me like you'd
benefit from support rather than having a bug. You tagged Xorg
(graphical display server) but report a printer issue? I don't see the
conn
No details were given on why Xorg was tagged. If Xorg was tagged for a
reason, please leave a comment as to why and it can be changed back to
"New"
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I suggest looking at the aforementioned link
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854798), and
trying what has been suggested there (eg. comment 13 OR 15).
If you try it, and it works PLEASE report back here or on other 1854798
bug report. (this report can be marked a duplicate
Public bug reported:
Lubuntu 20.04 daily.
(on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600))
Exploring another issue, I booted daily and opened Monitor.Settings to
adjust the displays to match my setup. I then opened Qterminal (I'll
need that too). Then I adjusted the Monitor.Settings conf
Lubuntu 20.04 qa-test
I tried to re-create this issue yesterday on d780 (c2q-q9400, 8gb, amd/ati
cedar radeon hd 5000/6000/7350/8350, portrait + landscape displays) but failed
I've now re-created it on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro
600) or box it was filed under initially.
I'll
Lubuntu 20.04 qa-test
I tried to re-create this issue yesterday on d780 (c2q-q9400, 8gb, amd/ati
cedar radeon hd 5000/6000/7350/8350, portrait + landscape displays) but failed
I've now re-created it on hp 8200 elite sff (i5-2400, 8gb, nvidia quadro
600) or box it was filed under initially.
I'll
same hp8200 session as comment #11
`rm ~/.config/vl* -rf`
`sudo apt install xfwm4`
`xfwm4 --replace`
open VLC from menu (different issue; I couldn't anymore from pcmanfm-qt
as menu wouldn't appear with right-click..) and VLC's PaNAP opens in
middle of other screen. See screengrab.
I rm vlc conf
Lubuntu 20.04 QA-test on
hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
Exploring the vlc privacy & network.. appearing and this issue was
noticed still occurring.
I acknowledged this first whilst running XFWM4; returning to openbox it
was there though. Sorry.
To create it on hp 8200; it
Public bug reported:
Lubuntu 20.04 daily testing on hp dc7700 (c2d-e6320, 5gb, nvidia quadro
nvs 290)
Exploration for other bugs, which involved numerous changes of screen
positions (relative to one another using Monitor.Settings). On
selecting a position (changed) to test I tried to drag pcmanf
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
No details about your touchpad have been provided (make model etc), but
if it's a Synaptics s3203, TM3108-002, TM2714-002 .. it's possible that
this is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux
*** This bug is a duplicate of bug 1854798 ***
https://bugs.launchpad.net/bugs/1854798
** This bug has been marked a duplicate of bug 1854798
Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
--
You received this bug notification because you are a member of Ubu
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I note the following in your `dmesg` log
[1.074876] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer:
Synaptics, product: TM3096-001, fw id: 2019836
Possibly related :
https://bugs.launchpad.net/ubuntu/+
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Reading your report it appears you are mostly after support.
This bug report can be converted to a question (aimed at support, bug
reports are aimed and finding problems and fixing so subsequent users
won't stumbl
I've been doing some testing of this on hp dc7700 (c2d-e6320, 5gb,
nvidia quadro nvs 290) on a very recent QA-test install (20.04) fully
upgraded.
To reset 'vlc' (to get PrivNetAccPolicy to show) I'm using `rm
~/.config/vl* -rf`
I was unable to re-create it (and this box shares the screens of hp
Okay before I shutdown the system I remembered I had to have panels on
specific displays... Once I had a panel on both displays, I could re-
create it on dc7700
Thus reported boxes (unless I missed one) are :-
dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
dell [optiplex] 960 (c2q-q9400, 8gb, amd/
QA-test, 20.04 daily on dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati
cedar radeon hd 5000/6000/7350/8350)
at first I couldn't re-create this issue.. Once I added the second panel
so each display had a panel - issue occurred. The % of end-users who
have this setup (have panel on both displays) and
Lubuntu 20.04 QA-Test on
dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
This issue was re-created today. Please refer to comments on
http://iso.qa.ubuntu.com/qatracker/milestones/408/builds/204243/testcases/1303/results/
as to what I did (started >60 mins ago)
Lubuntu 20.04 QA-Test on
dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
This issue was re-created today. Please refer to comments on
http://iso.qa.ubuntu.com/qatracker/milestones/408/builds/204243/testcases/1303/results/
as to what I did (started >60 mins ago)
901 - 1000 of 3989 matches
Mail list logo
