Public bug reported:
I'm currenlty using a Laptop Dell XPS 15 9520 with an Nvidia GPU.
Using a USB Type-C Hub - Model: HD292-Gray. It requires 2 USB-C ports to be use
at the same time to be able to use 2 external monitors.
The Issue Only Happens at Work when I'm using this HUB.
At Home I have
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890061
Title:
MATE Focal "amplified" sound controls do not sync with keyboard
buttons
To manage notifications about this bug
It also affects Ubuntu 20.04 LTS after a recent update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932579
Title:
snap pt_BR locale shows warning every time
To manage notifications about this
Public bug reported:
Hours after installing Ubuntu and getting a message like "Executing
'grub-install /dev/sdaX failed. Fatal error. ", I realized that in the left
corner of the screen there was an icon with the description "Instal RELEASE".
Taking the advice in this post
---
This bug is still alive and well. Every station does it, It plays for about a
minute then throws an error.
It mostly always happens while either closing a window, or alt-tab focus change
on a window.
** Attachment added: "Screenshot from 2021-05-07 09-46-48.png"
Documentation is horribly insufficient in this regard. To quote the link
given, "Ubuntu Desktop flavour now always tracks HWE kernel (hardware
enablement). It means that from 20.04.2 release Ubuntu Desktop will gain
new major kernel versions every 6 months through to summer of 2022".
The words
*** This bug is a duplicate of bug 1910709 ***
https://bugs.launchpad.net/bugs/1910709
** This bug has been marked a duplicate of bug 1910709
DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Upgrading to nvidia-opencl-icd-340:amd64 (340.108-0ubuntu2,
340.108-0ubuntu5.20.04.1) from focal-proposed solves this problem. See
bug #1910709.
I came to this conclusion after testing the focal-daily (20210116) and
finding that nvidia-340 installed just fine. Since LTS daily builds
always have
I changed the package name from "meta" to just linux to get apport-
collect to work. Hope that's OK.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
Nvidia-340 fails to build during
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453636/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453635/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453634/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453633/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453632/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453631/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453630/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453629/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453628/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453627/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453626/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453624/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453623/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453625/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453622/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1912032/+attachment/5453621/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912032
Title:
apport information
** Package changed: linux-meta-hwe-5.8 (Ubuntu) => linux (Ubuntu)
** Tags added: apport-collected
** Description changed:
This is really the result of the 20.04.1 iso images being built with
'linux-generic-hwe-20.04' which shouldn't have been included until
20.04.2 is
Even if that were the only consideration, which it's not, how do you
explain the fact that 20.04.2 has not yet been released?
>From my daily driver:
lance@lance-desktop:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.1 LTS
Release:20.04
Hardware specs can't hurt.
** Attachment added: "hw.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+attachment/5453595/+files/hw.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also may be helpful.
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+attachment/5453586/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks helpful to me.
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+attachment/5453585/+files/history.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I clearly did something wrong based on the lack of attachments to this
and I can't get apport-collect to work so I'll attach a few on my own
but I sure could use some help :^)
** Attachment added: "media-info"
** Information type changed from Private Security 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/1912032
Title:
Nvidia-340 fails to build during Focal install due to upgrade to 5.8
I filed bug #1912032 concerning the failure of nvidia drivers to install
during a fresh installation of Ubuntu 20.04.1 because when download
updates is selected it auto-updates to a 5.8 series kernel during
installation.
--
You received this bug notification because you are a member of Ubuntu
I updated the bug description to better explain why I believe this is a
bug, but I left the original content below the break.
** Description changed:
Beginning about January 8th Focal users that installed Focal using
either the Ubuntu 20.04 or 20.04.1 installation media began getting
I added the packaging tag because this was a packaging error in the
20.04 and 20.04.1 images.
** Tags added: packaging
** Description changed:
+ Beginning about January 8th Focal users that installed Focal using
+ either the Ubuntu 20.04 or 20.04.1 installation media began getting
+ updated to
Unfortunately apport-collect just says "no additional info collected"
(see pic added). I presume because 'ubuntu-meta' is not an installed
package? I struggled a bit trying to decide what the best way was to
report a bug like this because it's not actually a bug in the kernel
itself, it's just
Public bug reported:
Just as the title says, the 20.04 and 20.04.1 images use the HWE version
of linux-generic resulting in upgrades to the 5.8 series kernel. This
seems to effect Ubuntu only, or I should say I checked the Kubuntu,
Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all
Public bug reported:
Cannot install pygame or pip
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
Thanks Alberts. I'd been trying to figure that out for some time now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742193
Title:
nemo-desktop does not show background on GNOME FlashBack session
Bad on me - I didn't realize we now needed an EFI System partition on
ALL installations.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Fairly simple install on non-efi Dell Latitude E6400. Just selected
"something else" and used an existing partition for /. Another OS is
already installed next to it (on sda3 I think).
Installation ended with a grub install warning. Not sure what will
happen when I reboot
Although not intentionally so, this now works fine on both the E6400 and
E6510 laptops. Both initial boots, and subsequent boots. Just works
perfect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Worst case scenario on those older Latitude laptops a DVD still works
fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899308
Title:
failure to boot groovy daily (again)
To manage
http://cdimage.ubuntu.com/ubuntu/daily-live/20201016.1/groovy-desktop-
amd64.manifest still shows casper 1.452
Is that correct or is the manifest just not updated? It's still not
working on the Dell latitude E6510 and E6400 previously mentioned. On
the E6510 I tried both legacy and UEFI modes and
Also seems to effect Dell Latitude E6400 with C2D CPU's and an E6510
with i7 M620 CPU laptops using 20201015 Ubuntu image created with
Startup Disk Creator in 20.04. The same USB with the same image works OK
in my old Intel Desktop so I'm reasonably certain it's hardware
specific.
Typical
Do you have a dual boot setup, if so you may need to disable "Fast Startup"
from windows, as stated in the driver instructions
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hello, my Uuntu 20.04 has a problem, I've formatted it countless times
and this error always occurs.
I'm doing something, the system simply informs that there is no
internet, and it really runs out of internet and if I try to connect in
my hand, it simply locks the entire
** Tags added: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890061
Title:
MATE Focal "amplified" sound controls do not sync with keyboard
buttons
To manage notifications about this
Public bug reported:
I probably have the package wrong but I was grabbing at straws :^)
Just recently testing Ubuntu MATE 20.04.1 release candidates and I
notice that you can increase volume beyond 100% by opening Sound
Settings, and once you've done that you can also increase beyond 100%
using
** Changed in: gnome-control-center (Ubuntu)
Status: Invalid => Confirmed
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
First of all, I need to apologize to respond one month later. Yes, it's
my case. I had installed pulseaudio's plugins before this error appears.
I installed the pipewire lib and Gnome Control Center started work
again.
Even so, I will respond my commands' outputs:
$ dpkg -l | grep
Public bug reported:
When I try to open the Gnome Control Center application, it dies
silently. When I try to open it on the terminal, this error is displayed
on the terminal:
$ gnome-control-center --verbose
can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so:
Why the option "Open new terminals in" not available in GNOME Terminal
3.28.2?
** Changed in: gnome-terminal (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/685814
--
You received this bug notification
Public bug reported:
The option "Open new terminals in" not available in GNOME Terminal 3.28.2
Going Edit > Preferences > General The option is not showing.
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:
Sorry I lumped so much text into one box. I must have been asleep at the
wheel.
I was just setting up another of these today with 18.04.1 and it's also
effected but I know Xenial worked fine out-of-box so I'm just guessing
(with inadequate studying) that the change to GNOME as default resulted
in
Sorry for the delay. I performed a fresh install of 20191014 last night,
then updated it this AM so we'd be working with an out-of-box
experience. After the update and a reboot I opened System Settings >
Devices > Mouse & Touchpad and changed Natural Scrolling and Tap-to-
click to off while also
** Tags added: eoan gnome-panel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743686
Title:
File system folder in nautilus Artful/Bionic flashback session does
nothing
To manage notifications
Public bug reported:
After installing the Eoan Beta on a Dell Latitude E6400 attempting to
set touchpad Edge Scrolling was unsuccessful. It actually seemed to work
as long as the System Settings window was left open but as soon as the
window is closed the Edge Scrolling setting reverts to off.
I
Public bug reported:
Yo solo estaba con lag
yo veia que no lo podia atacar
pero el si podia.
** Affects: apache2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I use Xubuntu operating system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1838215
Title:
I can't log in with my user and password
To manage notifications about this bug go to:
Public bug reported:
First I had the message "No running instance of xfce-4 panel was
found", then I rebooted my computer and the menu bar had disappeared, I
rebooted again but now I try to loggin and password and the computer
returns me to the menu of input user and password as if I had typed
I will follow up ASAP. The plot continues to thicken. I tried a
different set of hardware today with a B43 chipset and it didn't seem to
be effected. But that board has only DVI and VGA outputs whereas the
effected board with a G43 chipset has DVI and HDMI. I'd been using HDMI
so now I ran another
Sadly /var/crash is empty, and errors.ubuntu.com + whoopsie-id just
displays a blank page. Also applying the workaround from bug 994921 does
not result in creating a crash report.
I started testing Ubuntu Disco 20190416 tonight and knowing what I know
now I can say with certainty that the easiest
Based on those most recent results I ran "dpkg-reconfigure grub-pc" and
removed "quiet splash". Now it boots to the gdm3 screen every time. So
maybe something to do with how plymouth hands off the boot process to
gdm3? Or how quickly that hand off is completed?
--
You received this bug
This was tricky but I finally got a successful boot (following several
failed boots) using gdm3 by selecting the kernel with "e" from grub and
then removing 'quiet splash'. So I hope this is more helpful.
** Attachment added: "prevboot.txt"
Method used to collect this info:
(1) Fresh installed 20190413.2 choosing not to auto-login.
(2) Rebooted after install and surprisingly gdm3 appeared as it should so I
booted to desktop and just rebooted.
(3) That reboot failed as had been the previous case - just a black screen,
totally
As requested. Definitely C2D era board (Intel DG43GT) running a Pentium
Dual Core.
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+attachment/5256044/+files/lspcik.txt
--
You received this bug notification because you are a member of Ubuntu
Slight change in behavior testing a fresh install of 20190413.2 - if
installed with auto-login switched on logout did load and give the
expected choices of Ubuntu and Ubuntu w/Wayland. But if auto-login is
turned off I still get a black screen on reboot. I suspect that gdm3 is
not even loading
Public bug reported:
Just testing the 20190413.2 image and after selecting "check disc for
defects" the Ubuntu splash screen appears very briefly, no testing text
is displayed, and a "no errors found" message appears in under one
minute.
As recently as 20190326.2 the test ran as expected
This does appear to be hardware related because I encounter no problem
on a box with Intel G41 graphics but the X4500 is a no-go with gdm3.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824588
I found that turning auto-login off resulted in booting to a black
screen so after unsuccessfully trying the nomodeset boot option I
installed 'lightdm-gtk-greeter' and 'lightdm' from recovery mode which
gives me a working system. I had encountered no problems with desktop
behavior but this box
** Summary changed:
- Ubuntu Disco logs out to black screen
+ Ubuntu Disco boots to or logs out to black screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824588
Title:
Ubuntu Disco boots to
Public bug reported:
Just testing Disco and wanted to see what login options are available
after adding 'gnome-shell-extensions' and found that logging out lands
me on a black screen that's unresponsive to any keyboard input. I'll
test on some slightly different hardware soon.
ProblemType: Bug
** Description changed:
This is intentionally a duplicate of bug #1817485 to collect info on a
fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
default session is also effected. I just wanted to collect all pertinent
logs to prove that this was in fact an unmolested
One more difference between the default and flashback sessions is that
the keyboard hot-keys DO work in the default Ubuntu session, but NOT in
the flashback session. So that makes this even a lower priority, and
passes part of the responsibility onto the flashback devs.
** Tags added: gnome-panel
** Description changed:
This is intentionally a duplicate of bug #1817485 to collect info on a
fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
default session is also effected. I just wanted to collect all pertinent
logs to prove that this was in fact an unmolested
Actually only a logout is necessary for the UI and volume slider to
respond to the amp change. So I'll add steps to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817625
Title:
Bionic
Actually this specific issue effects the default Ubuntu session as well.
I did a fresh install of 18.04.2, installed updates, rebooted, and
checked it out to be sure. Then I filed bug #1817625 so one or the other
needs to be marked a duplicate (and changed back to "new" rather than
"invalid"). I
Public bug reported:
This is intentionally a duplicate of bug #1817485 to collect info on a
fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
default session is also effected. I just wanted to collect all pertinent
logs to prove that this was in fact an unmolested install.
Bionic no longer displays allow above 100% in the sound settings UI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817485
Title:
Bionic "amplified" sound controls do not sync with volume slider
Public bug reported:
I'm just setting up my first Bionic HTPC and I notice that if you select
allow-amplified-volume in dconf that change only applies to the volume
slider, not to the sound control UI. This results in the volume hot-keys
not controlling sound above 100%.
So if you're watching
Would 5.0.0-rc* work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793960
Title:
Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
To manage notifications about this bug go to:
Public bug reported:
Just as the title says, if a usb sound card is in use pavucontol's
settings are ignored. This appears to be an unintended result of the
changes made to address bug #1702794. Specifically if you now look at
/etc/pulse/default.pa you'll find this section:
### Use hot-plugged
Doing
sudo rmmod i2c_hid
sudo rmmod hid
worked for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793960
Title:
Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
To manage
Also, my syslog file took up 1.1 Gb. My computer only has 16.
(Chromebook, s...) Even if I delete it, it comes back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793960
Title:
Lenovo Ideapad
This error happens, but even when I am not touching anything, I do ctrl
alt f5 and it spams the shell. I can’t even put a command in. The only
things I can do are shut down and exit shell.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have also noticed this error on a gl-702vm on archlinux with the 4.19
kernel. I have the same error, with the touchpad jumping around, being
super slow, and getting a repeated error message that says: i2c_hid i2c-
ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535). I can try
the latest
Yeah, I had to update it LAST YEAR.
On Wed, Oct 3, 2018, 08:41 Mathieu Trudel-Lapierre
wrote:
> Should be fixed in 2.02~beta3-4ubuntu7.3; the flashing should be solved
> which should be avoiding the crashes (which are likely due to the
> graphics card really not liking the flickering).
>
> Can
Wily is long past EOL. If anyone is still experiencing this bug with a
supported version it would probably be best to open a new bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1489147
Will we be able to push a patch into gnome-panel 1:3.26 in Bionic since
it's an LTS supported until 2023?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737836
Title:
Standard clock applet is
It seems to me that the most sensible approach would be to just remove
the Computer button from the Places menu. Then you'd just open Home and
select Other Locations. I think that would be more in keeping with the
latest Nautilus redesign.
I'm not at all sure but we may want to do likewise with
Sorry to take so long getting back to this. Disabling "show weather" and
"show temp" helps reduce that dead space but it must be done after each
boot or reboot because the settings don't "stick".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: grub-installer (Ubuntu)
Assignee: (unassigned) => Erick Rafael Vazquez Leyte (leyte)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076351
Title:
Fallo de ubiquity instala
** Summary changed:
- latest Grub2 update causes unbootable system
+ GRUB2 version 2.02~beta3-4ubuntu7.2 causes unbootable system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759099
Title:
GRUB2
Public bug reported:
After updating to Gnu GRUB2 version 2.02~beta3-4ubuntu7.2, any attempts to boot
the system flashes the loader menu for a split second and then crashes to a
black screen with purple top and bottom border with the GRUB version at the top.
I have attempted to repair-boot the
Public bug reported:
Just performing a manual partitioning install using Lubuntu Bionic
20180306.1 amd64 and the installer crashed and generated this report.
The only thing I did that may be "odd" is creating a SWAP partition
during installation.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
This may or may not be worth mentioning but the reason I totally purged
lightdm was just using dpkg to change to gdm3 returns an error:
lance@lance-conroe:~$ sudo dpkg-reconfigure gdm3
[sudo] password for lance:
gdm.service is not active, cannot reload.
invoke-rc.d: initscript gdm3, action
I tested again this AM beginning with a fresh install of 20180227,
applying updates, and then installing gnome-panel. During installation I
chose to auto-login so after initially logging out and selecting
flashback w/metacity I still booted the default DE.
But that was expected behavior based on
Works properly to boot both the flashback w/metacity and GNOME Classic
sessions now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749481
Title:
Wrong session marked as selected in session
Here's mine, it occurs in 16.04.3 with VLC 2.2.8 even, really bad HANG,
VLC unusable!
Code:
$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 21
model : 2
model name : AMD FX-8370 Eight-Core Processor
stepping: 0
microcode :
1 - 100 of 2295 matches
Mail list logo
