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.
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.
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.
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.
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.
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
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.
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
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
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 16.04 (xenial) reached end-of-life on April 29, 2021.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
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
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
You have a number of 3rd party packages that are stopping the upgrade,
eg. mesa-vdpau-drivers:amd64
(21.2.0~rc3+git2108022230.58bf0165ca0~b~mesarc5) which has a package
ver. that prevents upgrade to focal.
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
Sorry, invalid & paste was for a different bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938652
Title:
The new installation crashed
To manage notifications about this bug go to:
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 :-
Aug 2 07:56:18 ubuntu kernel: [
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 1938647
When reporting bugs in the future please use apport by using 'ubuntu-
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 1938635
When reporting bugs in the future please use apport by using 'ubuntu-
focal daily [20210731] BOOTS on
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
Comment as this is the first daily I've noted with 5.11 HWE kernel
(impish daily 20210731 still fails)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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 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.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old
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 1938596
When reporting bugs in the future please use apport by using 'ubuntu-
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Summary changed:
- lubuntu 19.04/19.10 two displays, programs maximized uses only part of 2nd
display
+ lubuntu 19.04-20.04 two displays, programs maximized uses only part of 2nd
display
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- lubuntu 19.04/19.10 xscreensaver runs on single display, other display
continues normally
+ lubuntu 19.04-20.04 xscreensaver runs on single display, other display
continues normally
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- lubuntu 19.04/19.10 - pcmanfm-qt menu won't show(or in wrong position) on 2nd
display
+ lubuntu 19.04-20.04 - pcmanfm-qt menu won't show(or in wrong position) on 2nd
display
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Summary changed:
- lubuntu 19.04 daily - pcmanfm-qt (dolphin..) moves window position on opening
device, folders or adjust size of windows (when on 2nd display only with
vertical placement)
+ lubuntu 19.04-20.04 daily - pcmanfm-qt (dolphin..) moves window position on
opening device,
This is another "what works, what doesn't" Sorry (made b/c of focal
status at top)
But the
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
boots the focal daily without issue, even current (20210729).
I've have only had issues with the impish daily.
(the install the prior comment was
output of `efibootmgr -v` on the sony crapbook
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
https://paste.ubuntu.com/p/z9rn6Kg625/
FYI: the only OS on it is lubuntu; last focal.3 daily I installed
(these commands were operated from that installed focal.3 system)
---
BootNext: 0005
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 1938242
When reporting bugs in the future please use apport by using 'ubuntu-
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 1938221
When reporting bugs in the future please use apport by using 'ubuntu-
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 1938228
Though note: It sounds like your issue is with the `ubiquity`
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
You state "It then has to be restarted the hard way (i.e. by prssing the
power button for several seconds)"
So does this mean even SysRq commands direct to the kernel don't work to
allow a safe reboot, shutdown?
Thank you for taking the time to report this issue and helping to make
Ubuntu better.
It appears you've added 3rd party packages that have prevented the
upgrade, such as
libpython3.9-minimal 3.9.6-1+focal1
libpython3.9-stdlib 3.9.6-1+focal1
I would suggest removing such 3rd party packages and
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 1938098
When reporting bugs in the future please use apport by using 'ubuntu-
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
Ubuntu impish ISO fails to boot again on
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
It fails to boot if ISO is written using mkusb CLONE OR LIVE modes.
(as noted earlier; applies to Xubuntu & Lubuntu too)
--
You received this bug notification because you are a member of Ubuntu
Today's boot contains 4 lines (Lubuntu impish) on
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
invalid image
failed to load
failed to load
... returns unsupported
the message is still very quick; the screen quickly being cleared and
"Attempting to decrypt master key..." from the
Another user has reported issue (yesterday) on askubu
https://askubuntu.com/questions/1353382/any-ubuntu-21-10-iso-download-
that-isnt-corrupted
Picture of screen end-user reported can be seen at
https://i.stack.imgur.com/oeYYg.jpg
The picture fits what @Leok describes I believe; which is
I used the dc7700 in a GNOME QA-test and got a response from vanvugt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930945/comments/5
"Yes this looks like a nouveau kernel driver bug. I recommend using the
proprietary Nvidia driver instead, but it seems your GPU only supports
driver
Likely related -
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919266
(hirsute, kubuntu)
wallpaper issues on same box (used only for QA-tests/support)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Tags added: amd64 impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937115
Title:
Unable to boot/install Impish daily in UEFI boot mode
To manage notifications about this bug go to:
** Description changed:
Ubuntu Desktop Impish daily test on
- - - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
+ - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
Changing display positions in settings. I have two monitors, one above
the other (so not the default).
I made
*** This bug is a duplicate of bug 1930945 ***
https://bugs.launchpad.net/bugs/1930945
the same Ubuntu daily was booted on
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
which shares the identical displays & thus setup (though I think
top/bottom are swapped due to cabling).. but I
This is likely a (duplicate) issue - the top of my lower display has now
become "warped".
GNOME no longer has a Activities/PANEL at the top of the PRIMARY display.
I'm chasing another failure-to-boot issue currently so not spending time on
this sorry.
My display has ONE display (PRIMARY) below
Public bug reported:
Ubuntu impish daily QA-test
Changing screen positions (Settings.Displays) causes the background
wallpaper to be replaced by a strong-blue color.
Opening windows from there causes it sometimes to turn black.
Using the Settings.Background allows me to restore a wallpaper on
** Summary changed:
- Unable to install Impish daily in UEFI boot mode
+ Unable to boot/install Impish daily in UEFI boot mode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937115
Title:
Unable
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
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937126
Title:
bug found
To manage notifications about this bug go to:
Lubuntu impish QA-test install to
- sony vaio svp112a1cw (i5-9400u, 4gb, intel haswell-ULT)
testcase: full disk, uEFI, ... (fails to boot so doesn't matter)
"INVALID IMAGE"
"FAILED TO BOOT"
then quickly boots to "Attempting to decrypt master key..." of the prior
QA-test install located on ssd
*** This bug is a duplicate of bug 1937036 ***
https://bugs.launchpad.net/bugs/1937036
** This bug has been marked a duplicate of bug 1937036
package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed
initramfs-tools package post-installation script subprocess returned
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 1937031
When reporting bugs in the future please use apport by using 'ubuntu-
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 1937024
When reporting bugs in the future please use apport by using 'ubuntu-
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 1937023
When reporting bugs in the future please use apport by using 'ubuntu-
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 1936988
When reporting bugs in the future please use apport by using 'ubuntu-
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 1936910
When reporting bugs in the future please use apport by using 'ubuntu-
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 1936756
When reporting bugs in the future please use apport by using 'ubuntu-
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 1936759
When reporting bugs in the future please use apport by using 'ubuntu-
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
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 1936692
When reporting bugs in the future please use apport by using 'ubuntu-
Lubuntu 20.04.3 QA-test install to
- dell [optiplex] 755 (c2d-e8300, 8gb, amd/ati radeon rv610/radeon hd2400
pro/xt)
testcase: full disk, encryption, BIOS, internet
in setup of box (monitor is portrait-left); a gap opened between
monitors... updated to include focal.
** Tags added: focal
--
*** This bug is a duplicate of bug 1069133 ***
https://bugs.launchpad.net/bugs/1069133
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I see a number of 3rd party packages, esp. from
https://launchpad.net/~oibaf/+ppa-packages
For best results with a
Minor change to title; title wasn't very descriptive I felt on
iso.qa.ubuntu.com list of bugs to look for...
** Summary changed:
- impish-desktop-amd64 25062021 test installation failed
+ impish-desktop-amd64 25062021 "error removing initramfs-tools"
--
You received this bug notification
this issue is not limited to Ubuntu..
I've been suspending debian-bullseye (11) on
- dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd
5000/6000/7350/8350)
lately and when I resume I have this issue. The d780 box has numerous
lubuntu installs (used for QA & support) but I don'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 1935734
When reporting bugs in the future please use apport by using 'ubuntu-
Ubuntu impish daily on
- hp 8200 elite sff (i5-2400, 8gb, nvidia quadro 600)
Settings -> About shows a RED rounded-edge box with lighter-red circle-X
This will be what @EoflaOE refers to.
It's NOT what I saw on my primary install (which was a debian logo).
Either way FIX has been released
Ubuntu impish desktop live QA-test of
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
at the try/install query (maybe-ubiquity) I get video glitches at top of
wallpaper
changing wallpaper gets black background or glitchy-wallpaper (varying
each time) - ignoring that for
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
I don't get a forbidden message, or error.
I get a DEBIAN logo. Given I like debian, I have no issue with it, however
that is not expected, and I bet not intended.
Using impish, but my desktop is Lubuntu/LXQt and I'm running it from
terminal
guiverc@d960-ubu2:/de2900/lubuntu$
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"
** Changed in: qterminal (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/1934616
Title:
qterminal doesn't use correct .bashrc
To manage notifications about
Public bug reported:
Ubuntu MATE impish daily QA-test (live) on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
A number of times, I've had windows open with the top title bar (will be
wrong term, but the close/minimize/maximize, program name etc bar)
hidden by the panel.
This doesn't feel
On initial adjustment of Monitor.Preferences & position of displays
(instead of side-by-side, my top-bottom arrangement) the display
remained mucked up a long while before it settled.. ie. it looked like
this attachment.
Given time - all settled except the Monitor.Preferences issue this bug
is
** Attachment added: "after moving displays around again inside
Monitor.Preferences window - "shadows" still"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1934752/+attachment/5509337/+files/Screenshot%20at%202021-07-06%2008-30-02.png
--
You received this bug notification
Public bug reported:
Ubuntu-MATE impish QA-test (live) on
- hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
Adjusting displays to match my setup (one screen above the other), and
at change the display became warped for a time, before correcting
everywhere BUT the Monitor.Preferences box.
I
UWN publish day today; so earlier today I loaded torbrowser on my impish system
and today it worked :)
apparmor: 3.0.0-0ubuntu9
I have since zsync'd the lubuntu impish daily & it works there too now
summary of https://bugs.launchpad.net/ubuntu/+source/torbrowser-
I was able to load torbrowser on my primary impish desktop today to
enable me to login to fb & paste UWN #690 for ubuntu_news. :) (hours
ago now)
I've since zsync'd the lubuntu impish daily & in a live session; I can
- sudo apt install torbrowser-launcher
- torbrowser-launcher
and select
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
** Changed in: qterminal (Ubuntu)
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/1934616
Title:
qterminal doesn't use correct .bashrc
To manage notifications about
Booted today's impish (canary) daily (live QA-test) on
- dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
Identical result to comment #13
booted with wallpaper shown, however glitches on top though. On changing it, I
get
- no background (usually blocks on small parts of
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.
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 1934616
When reporting bugs in the future please use apport by using 'ubuntu-
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The recommended minimum disk space for a Ubuntu Desktop install is 25GB,
having been so since Ubuntu 17.10
(https://help.ubuntu.com/community/Installation/SystemRequirements).
Your install ran out of space, as
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 1934589
When reporting bugs in the future please use apport by using 'ubuntu-
** Description changed:
Trying to use tor-browser has the program open, then close but is
unusable.
- this issue has existed for a few weeks (3 weeks+?) on my primary box (impish).
- I don't trust facebook, and use tor-browser to access fb to post UWN notice
on my local Tuesday morning
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 1934559
When reporting bugs in the future please use apport by using 'ubuntu-
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Changing ubuntu-release-upgrader -> linux
(install was bionic, it's still bionic so no release-upgrade has occurred; I
believe bot-crichton was wrong)
** Package changed: ubuntu-release-upgrader (Ubuntu) =>
801 - 900 of 3848 matches
Mail list logo
