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 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 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 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 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 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.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 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 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 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 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 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 941457
When reporting bugs in the future please use apport by using 'ubuntu-
bug
Sorry I should have said "Confirmed", not "New".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/941457
Title:
startlubuntu is not a registered x-session-manager option
To manage notifications about
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 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 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 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 1217813
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.
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 do
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 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 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 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 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 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 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, and thank you for the mea
culpa on issue that resolved itself :)
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 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 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
Changed status from incomplete to "Fix Released" based on comments #7 &
#8. Thank you phillw @ john.hupp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309698
Title:
Lubuntu does not handle /etc/xd
Public bug reported:
Xubuntu hirsute daily installation QA-test on
- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400
pro/xt)
At completion of install, it suggested I reboot so I was accepted. I
then got the Xubuntu plymouth screen, and it sat there ... for >60 mins
** E
I booted a recent (20201122) Lubuntu hirsute daily, and it shows the
message on that box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905383
Title:
Xubuntu hirsute live system, on shutdown no "Pl
QA-test (live) using Xubuntu hirsute daily on
- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400
pro/xt)
this issue occurred, top panel wasn't expected color, menu items were
lacking icons (just greyish-display).. `xfsettingsd --replace &` fixed
this as usual. ctrl+alt+T
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
I see squashfs errors -
Nov 24 21:43:54 ubuntu kernel: [ 538.269782] SQUASHFS error: zlib
decompression failed, data probably corrupt
Nov 24 21:43:54 ubuntu kernel: [ 538.269788] SQUASHFS error:
squashfs_rea
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 1905483
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.
Ubuntu 20.10 was released in 2020-October (thus it's 20.10) and there
have been no Ubuntu releases in
Great find Rik
My intention today was to try and boot each of the grub options
available
* Kubuntu failed on
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
* Kubuntu (safe graphics failed on fail on
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
* OEM install
Great find Rik
My intention today was to try and boot each of the grub options
available
* Kubuntu failed on
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
* Kubuntu (safe graphics failed on fail on
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
* OEM install
Great find Rik
My intention today was to try and boot each of the grub options
available
* Kubuntu failed on
dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400 pro/xt)
* Kubuntu (safe graphics failed on fail on
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
* OEM install
> Your comments about invoking "apport-collect" .. the issue is with the
> fourth screen of a system install. Is apport
accessible at that time
Yes `apport-bug` is available on all Ubuntu and flavor of Ubuntu (eg.
Lubuntu) media for that exact purpose (I don't know about netboot). In
`calamares
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 1905778
When reporting bugs in the future please use apport by using 'ubuntu-
bu
This bug is also discussed at
https://discourse.lubuntu.me/t/lubuntu-20-04-and-20-10-libreoffice-font-
of-some-dialog-windows-is-too-small/1834/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905778
T
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 1905821
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Public bug reported:
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
** background
QA-test install, login to a ~recent hirsute install (untouched) to
verify nothing has changed, screens aren't in correct orientation?? yet
command history from my validation post-install is present (I always
ad
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 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. But
Lubuntu hirsute daily QA-test install on
- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400
pro/xt)
testcase: install alongside
..
reboot, login to new system, .. adjust displays to match my setup ..
on logout, I logged back in and displays returned to default (as it was
on
Lubuntu hirsute daily QA-test on
- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
this box shares displays with prior comment (d755-8) so
landscape+portrait, though opposite order due cables
saved & applied monitor.settings
logout & login again.
Monitor.setti
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 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. Support however is aimed at helping
you.
If you would like support, you can use
https://answers.launchpad.ne
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 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. But
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.
If you want a support site ("how do I track down..") you can use
https://answers.launchpad.net/ubuntu
Message (upgrade to 20.04 is available) is still occurring on i386
Thinkpad t43 running Lubuntu 18.04... I still see occasional report by
end-user on support sites (again few in number, 2-3 a week maybe)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
*** This bug is a duplicate of bug 1906162 ***
https://bugs.launchpad.net/bugs/1906162
** This bug has been marked a duplicate of bug 1906162
Lubuntu 20.04 and 20.10: Libreoffice: font of some dialog-windows is too
small
--
You received this bug notification because you are a member of U
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I see the following in your logs
Nov 29 23:17:07 ubuntu-studio ubiquity: Processing triggers for
hicolor-icon-theme (0.17-2) ...#015
Nov 29 23:17:07 ubuntu-studio ubiquity: Processing triggers for libc-bin
(2.31
A recent Lubuntu 20.04.2 QA-test install
`micro` was installed
`micro --version` reports
"Version: 0.0.0-unknown"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906235
Title:
Micro thinks that it'
I was asked to test this
Recent Lubuntu 20.04.2 QA-test install, thus clean system.
`sudo apt install micro`
I started micro, played with editor entering & changing text.
On exit (without save) I did have a `micro.txt` in my $HOME, it contained
"2020/11/30 20:47:25 Micro started" as contents.
I
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906316
Title:
Xorg crash
To manage notifications about this bug go to:
https://bugs.launchpa
I'm adding my primary box running a morning & night updated hirsute system
(heavily modified & bloated...)
- dell [optiplex] 960 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
It occurs on reboot, or if I logout & login again, my monitor.settings
go back to a left-right setup; whe
lenovo thinkpad x201 (i5-m520, 4gb, i915) LIVE session using hirsute
primary purpose is exploration of http://launchpad.net/bugs/1905947
boots up with laptop monitor on left, external monitor on right... panel on
external monitor..
for this test, I'll swap external & internal monitor around, left
lenovo thinkpad x201 (i5-m520, 4gb, i915) hirsute daily
primary purpose is exploration of http://launchpad.net/bugs/1905947
boots up with laptop monitor on left, external monitor on right... panel on
external monitor..
for this test, I'll swap external & internal monitor around, left-right
becom
I repeated the steps in #6 using a recent focal/20.04.2 daily, and I can logout
& login and changed settings survive on a live system using
- lenovo thinkpad x201 (i5-m520, 4gb, i915)
focal.2 booted with laptop on left, external on right by default too.
(a groovy comparison would have been bett
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
In the title, & package the bug is reported against, you have said
`pcmanfm-qt`, but in the description your refer only to `pcmanfm` which
is a different program/package.
This maybe just a mistake, but pleasPcmane
Lubuntu daily QA-test [2020-02-22.1 using LXQt 0.16)
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
in live session, display config was changed, I logged out & logged in again
(testing for another bug), and matching this bug
"the wallpaper appears to have been misplaced; the top.of.wallpaper
Lubuntu daily QA-test (2020-10-22.1) on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
and this issue was NOT re-created in a live session.
Install performed on that (dc7700) box, monitor.settings changed, logout
& login again and this issue was again NOT re-created
I'll do more testing as
I've experienced this today on
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
which is a uEFI box.
I note @Leokolb noted reports as being uEFI+Secure OR uEFI (as this box
is)
I did NOT have the issue earlier today on a BIOS box (dc7700)
Error report reminds me of
https://bugs.launchp
A later QA-test install (Manual partitioning, no internet, no encryption) on
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
or box in comment #5 worked as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Fresh Lubuntu hirsute (2020-02-22.1) QA-test install on d755-8 box
this issue is still occurring on LXQt 0.16
guiverc@d755-8:~$ lxqt-about --version
lxqt-about 0.16.0
liblxqt 0.16.0
Qt5.15.2
The image shows the actual Monitor positions relative to each other (left
display), yet when
** Also affects: lxqt via
https://github.com/lxqt/lxqt/issues/1709
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810075
Title:
lxqt-panel: menu-butt
Another QA-test on
- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400
pro/xt)
and this issue was NOT re-create on live session, nor after install.
- dc7700 has two monitors, one above the other (comment #20)
- d755-8 or this box has left & right but right-monitor is portr
I've tried to re-create this on Lubuntu's hirsute daily (using LXQt
0.16) installed on dc7700 & d755-8 and been unable to.
I won't currently change New->Fix.Released as I only see mention of hp
8200 & d960 being boxes.
Note: mention of dc7700 is made in this report, but it was using
different scr
I just swapped my TOP & bottom display positions (a few times) in
Monitor.Settings on the dc7700 (which shares displays with 8200 this bug
was filed on) which is more confirmation that I believe this is solved,
but I'll endeavour to test on either hp 8200 or d960
--
You received this bug notific
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 1916590
When reporting bugs in the future please use apport by using 'ubuntu-
bu
Login today on my primary box and YIPPEE (d960)
Display configuration doesn't require re-setting.
No changes made (since last reboot/login whenever that was)
Yep - all fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://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 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 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/bugs
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 1916670
When reporting bugs in the future please use apport by using 'ubuntu-
bu
You just made me laugh, thank you :) Hisenburg... LOL.
The correct package is not really your job, ideally a *bug triager*
would have detected a filing against a imperfect package & corrected...
I'm not a GNOME user, but if was GNOME related `gnome-shell` is likely
what I'd have used (alas I don
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 1916801
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 1916800
When reporting bugs in the future please use apport by using 'ubuntu-
b
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I don't see the Launchpad question you refer to, if I did, I would have
looked up what you asked there and possibly made a comment.
I do see refer to Qt4 requirements, Qt5 was introduced in Dec-2012 and
programs t
2021-feb-23 QA-test installs
I've experienced this on a QA-test install on d755-8 (same box bug is
filed against). I was attempting to explore other 'older' bugs on new
LXQt 0.16
Report details can be seen at https://bugs.launchpad.net/ubuntu/+source
/lxqt-panel/+bug/1810075/comments/14
Uploade
I just re-created this on
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
using Lubuntu hirsute daily (live QA-test).
To achieve it I have
- two monitors (DVI-I-1 & DP-1 listed in Monitor.Settings)
- Monitor.Settings, my DP-1 is left, DVI-I-1 is right
- right monitor or my DVI-I-1 which
I tested for this today using Lubuntu hirsute daily.
I could NOT re-create it on
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
I couldn't always re-create it anyway; it only occurs with certain
screen positions, and it seems to be luck if depending on how the
screens 'snapped' together..
I've attempted to re-create this 3 times in last few days and failed to
RE-CREATE this bug using
lubuntu hirsute dailies using LXQt 0.16 (not all today)
boxes tested include
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd
I've attempted to re-create this (again) today using Lubuntu hirsute daily
(LXQt 0.16) on
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
I was UNABLE TO RE-CREATE (again) on hirsute.
If it's still an issue, it appears to be in focal/20.04 only.
--
You received this bug notification beca
I tested for this today on
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
using Lubuntu hirsute daily (LXQt 0.16) and was UNABLE TO RE-CREATE IT.
If this issue still occurs on focal, it doesn't on hirsute I believe.
(iso.qa.ubuntu.com reports only show up to focal)
--
You received this b
Repeat of comment #9 on Lubuntu daily hirsute, on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
Again, I was testing for other bugs, and the logout/login step used to
prove that caused this issue to re-appear.
PLEASE NOTE:
I don't consider this bug an issue with regards Lubuntu.
Yeah it's
Right clicking black top.monitor
screengrab is achieve via quick combination of PRINTSCREEN then right-
click on mouse being pressed... works on these slower boxes :)
contrast MENU with menu when right click is pressed on bottom.monitor
(next comment)
** Attachment added: "screen_top_menu.jpg"
Right clicking black bottom.monitor
contrast MENU with menu when right click is pressed on top.monitor (prior
comment #11)
** Attachment added: "screen_bottom_menu.jpg"
https://bugs.launchpad.net/ubuntu/+source/lxqt-session/+bug/1845756/+attachment/5467410/+files/screen_bottom_menu.jpg
--
** Description changed:
- Lubuntu 19.10 daily
+ 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 exact
*** This bug is a duplicate of bug 1845756 ***
https://bugs.launchpad.net/bugs/1845756
this is almost the same as 1845756 so marking as duplicate
** This bug has been marked a duplicate of bug 1845756
lubuntu - strange movement of wallpaper on monitor.settings change (or next
login)
--
1 - 100 of 3989 matches
Mail list logo
