Will this likely make it into 20.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831789
Title:
Add "dis_ucode_ldr" to linux boot options for Recovery Mode
To manage notifications about this bug
It affects disco. Was a fix released?
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583801
Title:
No sound via headphones (headset) when Ubuntu boots with them plugged
in
Public bug reported:
I did a test install using
$ sha256sum focal-live-server-amd64.iso
28c4e38588dd3ecfe2b8b3ec9ecb9e09057671fdd362b4732dc6cb5ff0f8a539
focal-live-server-amd64.iso
(which was published at
http://cdimage.ubuntu.com/ubuntu-server/daily-live/current/focal-live-server-amd64.iso
A screenshot of the installer update step is attached.
** Attachment added: "Installer update screen"
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1860360/+attachment/5321768/+files/installer_update_available.png
** Tags added: focal
--
You received this bug notification
Since no later than 18.04.3 the installer offers to encrypt an LVM which
is configured during manual partitioning. I assume this solves this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1750645
Public bug reported:
I did a test install using
$ sha256sum focal-live-server-amd64.iso
28c4e38588dd3ecfe2b8b3ec9ecb9e09057671fdd362b4732dc6cb5ff0f8a539
focal-live-server-amd64.iso
(which was published at
http://cdimage.ubuntu.com/ubuntu-server/daily-live/current/focal-live-server-amd64.iso
Watch existing bug on GNOME Gitlab. Previously, this was
https://bugzilla.gnome.org/show_bug.cgi?id=753678
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #332
https://gitlab.gnome.org/GNOME/gnome-shell/issues/332
** Bug watch added: bugzilla.gnome.org/ #753678
Public bug reported:
This seems similar to https://bugs.launchpad.net/ubuntu/+source/xubuntu-
default-settings/+bug/1754888
4 files affected:
/usr/share/applications/org.kde.mobile.okular_chm.desktop,
/usr/share/applications/org.kde.mobile.okular_djvu.desktop,
I'm experiencing the same bug since 2 weeks. Using Ubuntu 19.10,
Libreoffice Calc 6.3.4.2 Build ID: 1:6.3.4-0ubuntu0.19.10.1.
Please help!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852183
This can be a duplicate of bug 1849542 - do you agree?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859043
Title:
thunderbird completely broken after upgrade
To manage notifications about this
Hi,
I seem to have the same problem. I have no experience with linux kernels or bug
reports, but I am a computer engineer so with guidance I will be able to
contribute to debugging.
I am running "Ubuntu 4.15.0-46.49-generic 4.15.18" on an HP zbook the
lspci output is attached.
Both 4.15.0-72
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 4 21:17:05 ubuntu kernel: [
Public bug reported:
MySQL Server 8.0 (on Eoan) binds to / listens on *:33060/tcp (MySQL X
protocol) by default. For the classic shell it binds to
localhost:3306/tcp only, as users will have gotten used to expect.
This seems like a potentially dangerous change of defaults - users may
not expect
** Changed in: ubuntu
Status: Opinion => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1482430
Title:
report a bug button failure
To manage notifications about this bug go to:
While installing ESP on top of mdadm (metadata version <= 1.0) RAID-1 is
practically possible, supporting this is not: The UEFI specification
(version 2.8, sections 13.3.1.1, 13.3.3) defines the ESP as a FAT32 file
system which is located (directly) on a GPT partition. While this does
not seem to
The format you are complaining about is American NOT English. I have
noticed the same problem, running Gnome Flashback under Ubuntu 18.04,
today. System settings show the correct English regional format (eg Thu
12 Dec 2019 18:29:30) but, in the indicator, I get Thu Dec 12 2019
18:29:30. Extremely
Ok, maybe some progress. It appears I can search among a maximal number
of hits. So that depends per folder. And as soon as Nautilus start to
crash, I have to start all over by rebooting, as even small searches
then crash. (Logging out/in does not make a difference.)
For what it is worth, I:
1 -
*3 Sorry, " sudo cat /proc/sys/fs/inotify/max_user_watches " now gives:
524288
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852053
Title:
Nautilus Crashes when opening search field and entering
Well, it definitely is not gsconnect, as I disabled a week ago and the
crashing is back in full force.
I am trying to find some kind of pattern to make it predictable. But
it's mind-boggling so far. I wish few others had same issue ;)
--
You received this bug notification because you are a
You can run snap --help (or man snap) to get all the availabel commands.
However to install is "snap install ".
Tom
On Mon, 9 Dec 2019, Vojtěch Šmiro wrote:
Hello.
How to install these types of packages? I have some apps in snap format
and I don't know how to install them.
e is: "None"
amarok: loading layout "No Grouping (Single Line)"
amarok: grouping mode is: "None"
amarok: loading layout "Verbose"
amarok: grouping mode is: "Album"
amarok: END__: void Playlist::La
The problem is back. But not frequent enough yet to let me catch it
properly, I did get after running 'nautilius -q":
Traceback (most recent call last):
File
"/home/tom/.local/share/nautilus-python/extensions/nautilus-gsconnect.py", line
49, in
localedir=LOCALE_DIR)
Hmm, sorry for putting you on the wrong path there.
We'll now need to wait for a developer / package maintainer to have a
look at this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854395
Title:
I'm not sure why I missed this when we were looking into it on IRC, but
this is apparently something involving the openssl and nss crypto
libraries / frameworks. I'm not enough of a developer to understand what
exactly seems to be the problem, though, but knowing that apache httpd
supports HTTPS
Just a side note: An unsupported, experimental build of xiccd 0.3.0-1 is
currently available at
https://launchpad.net/~xubuntu-dev/+archive/ubuntu/experimental
If you are considering to use this PPA, please make sure to read its
description first. Consider using APT pinning to only allow this
To my surprise, the bug stopped happening few days ago so I cant
replicate. Search works again as intended.
It might have been an update but I am not even sure which one could have
fixed the issue;
So, until further notice, for me it seems solved...
--
You received this bug notification
Verified fix in proposed 4.15.0-71-generic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1843487
Title:
UIO:
It's now also filed at
https://gitlab.gnome.org/GNOME/nautilus/issues/1290 - thanks Sebastian.
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1290
https://gitlab.gnome.org/GNOME/nautilus/issues/1290
** Also affects: nautilus via
I'm currently traveling for work, but will verify the fix this evening
hopefully.
Thanks
On Thu, Nov 14, 2019, 10:41 Dan Streetman
wrote:
> @drdabbles can you please verify the fix in systemd in proposed
>
> --
> You received this bug notification because you are subscribed to the bug
>
Public bug reported:
I'm using Ubuntu 16.04.6 LTS
GTG version 0.3.1-3
GTG crashes when I close application.
GTG reported the following:
GTG0.3.1 has crashed.
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File
Can't even work around this by using Akonadi Console to ('configure
remote') set the Authentication to "1" instead of "9" because it's reset
shortly after Kmail starts, and you get the popup of doom from Google
again :(
--
You received this bug notification because you are a member of Ubuntu
Work around isn't possible.
As soon as you set the IMAP server to imap.gmail.com you can see the password
field goes disabled and the advanced connection settings are disabled and
"gmail" type is forced.
This "helpful" would seem easy to undo, and then at least there would then be a
way to
Workaround doesn't work in Kmail v5.7.3 because both password and connection
settings (to set to "plain") are disabled.
Even for a freshly created IMAP connection.
Something in KDE is disabling these because the email is @gmail ?
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1764417 ***
https://bugs.launchpad.net/bugs/1764417
Please note that I have unsubscribed off this bug report because I am no
longer experiencing it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I did that:
- In Nautilus I press Ctrl-F and a character and then N freezes and gdb reports
segmetation fault. -(gdb) backtrace
[...]
(org.gnome.Nautilus:12326): Gtk-WARNING **: 11:34:57.526: Duplicate child name
in GtkStack: icons
(org.gnome.Nautilus:12326): Gtk-WARNING **: 11:34:57.579:
Randomly tried this :
apport-retrace --gdb _usr_bin_nautilus.1000.crash
But that gave me: "ERROR: report file does not contain one of the
required fields: Package"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is it possible the crash report auto-uploaded ( cb12411a-045e-11ea-
afb5-fa163e983629 ) ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852053
Title:
Nautilus Crashes when opening search field and
Sorry I spend about 30 minutes trying to understand how to open a crash
report program. I followed your link and Googled, but these
"explanations" are so unclear that I cant get any further. I use Ubuntu
since version 11 I think and it's remarkable how complex that crash
reporting remained...
In
@Khurshid-alam
I have confirmed this bug on a standalone install of compiz on Ubuntu
server 18.04 - no unity, no mate, nothing.
Same results with both the application switcher and static application
switcher - can't change the background color or opacity. Some of the
other settings do work.
--
Public bug reported:
Upgraded to 19.10 one week ago. Then all worked fine. Nothing major
changed as far as I know. But now:
- click in Dock on the file stack icon to open Nautilus
- stay in Home or browse to any folder
- click Ctrl-F to open search field at the top of window
- enter any
Until this may get mitigations in Ubuntu, this approach can be used to
(temporarily) clean up a poisoned key ring:
https://tech.michaelaltfield.net/2019/07/14/mitigating-poisoned-pgp-
certificates/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Don't know what I managed to screw up in the previous experiment, but I
just tried again and I can install a working virtual machine by first
formatting the virtual disk, then telling the installer to use the
partition without reformatting. I used the system rescue CD iso and
gparted this time
Just tried a new experiment: I attached the new qcow2 image to a
different virtual machine, used gnome-disks to create a MSDOS partition
table, one large ext4 partition and a small swap area, then detached the
image from that VM and used it for the install of the new ubuntu 19.10
virtual machine.
Public bug reported:
I'm trying to install a KVM virtual machine using the ubuntu 19.10 live
iso. It always gets as far as the step where it is going to format the
blank disk (in this case a newly created qcow2 image with a 20G size
limit). I then see the virtual machine go to 100% cpu usage and
For me, the fix is to change line 812 of /usr/sbin/dkms from:
[ -z $kernels_module ] || return 0
to
[ -z $kernels_module ] && return 0
This was fixed upstream here:
https://github.com/dell/dkms/commit/b95779938805aca8e98d57492b18dee07d35d285
--
You received this bug notification
According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943569,
this is fixed in debian dkms=2.7.1-5.
** Bug watch added: Debian Bug tracker #943569
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943569
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm still seeing this on Eoan, which has dkms 2.7.1-4ubuntu2 - the
symptom is that virtualbox-dkms does not correctly build and install its
kernel modules with the message `modinfo: ERROR: missing module or
filename.`
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thank you for your report.
$ host kr.archive.ubuntu.com
kr.archive.ubuntu.com is an alias for ftp.kaist.ac.kr.
ftp.kaist.ac.kr has address 103.22.220.133
This mirror server is currently unavailable. This is likely a temporary
issue. I have notified the relevant team at Canonical, who are
@Kamal yes this seems to fix it. I was able to run my device stress
test for over 15 minutes. With the bug I was lucky if I could make it
15 seconds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Kamal thanks for the quick response. I tried the files you sent over
but it looks like I need some additional packages in order to rebuild my
kernel module for that kernel. I tried to tell modprobe to force load
my module built against 4.15.0-66 and it would not load it.
--
You received this
The commit for "uio: fix crash after the device is unregistered" in this
bug introduces another bug which is fixed upstream in the kernel. It
adds an illegal mutex_lock in uio_interrupt() in uio.c. This completely
breaks interrupt handling in UIO.
I opened the following bug to track this:
This bug is buggy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850174
Title:
This is not a bug, please ignore - just testing
To manage notifications about this bug go to:
** Changed in: gnome-terminal
Importance: Medium => Unknown
** Changed in: gnome-terminal
Status: Confirmed => Unknown
** Changed in: gnome-terminal
Remote watch: GNOME Bug Tracker #780622 => bugzilla.gnome.org/ #780622
--
You received this bug notification because you are a member
Asus UX330 here.
After upgrade to 19.10 failed because of mysql-core update error, I also had
the TPM error even though I disabled secure boot in the BIOS.
Comment #13 fixed for me, thank you ! Do you know if there's a way to make it
permanent in a boot option ?
Not sure if a more permanent fix
Kodi devs-team were very conservative they would not help and asked me
to wait Ubuntu fix the bug.
Kodi is a reference to a bug that affects every graphical software
installed.
I'm observing every new mesa and kernels upgrades, I'll keep informing.
--
You received this bug notification because
No, Kodi does not crash anymore with x-swat and since official mesa
19.0.8-0ubuntu0~18.04.2
But it's followed by another problem, it's not 100% solved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just tested your ppa with mesa 19.2.1-1ubuntu1~18.04.1~ppa2, thank you
Since mesa 19.0.8-0ubuntu0~18.04.2 the image produced by Ubuntu with all
media players and browsers is very dark, like the contrast and black
levels were adjusted at a very low value. It became worse than before,
including
Is this something which could be supported by now?
gnome-control-center -> power seems to offer a setting to manage wi-fi
power saving but in the end this is just a wi-fi on/off switch which
immediately brings the device down/up (bug 1751954).
Looking through the details of an existing NM
This appears to have been partially fixed upstream at
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/53
However, the description is still ambiguous as reported at
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/681 (now tracked
here)
It would be nice to see this fixed in
Point to currently open bug on GNOME Gitlab (which has further
references to related bug reports)
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #681
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/681
** Changed in: gnome-control-center
Importance:
Public bug reported:
I've just installed Ubuntu 19.10 on a Lenovo Thinkpad P1. I can't get GStreamer
to display any video - no window appears. Even the test case:
gst-launch-1.0 videotestsrc ! videoconvert ! autovideosink
fails.
My colleague suggested removing gstreamer1.0-vaapi:
sudo apt-get
Thanks for the notice, I updated the link.
https://wiki.ubuntu.com/ARM/RaspberryPi?action=diff=104=103
** Package changed: ubuntu => ubuntu-docs
** Changed in: ubuntu-docs
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Is yours failing? Mine is displaying the error message with lz4, but
still booting and finding the root filesystem, that's what I thought
this bug is about. You must not be failing either, as you have a boot
time to measure. In the olden days, the other people who got this error
weren't able to
Boot lz4
Startup finished in 6.907s (firmware) + 8.338s (loader) + 2.595s (kernel) +
3.705s (userspace) = 21.547s
graphical.target reached after 3.695s in userspace
Boot gzip
Startup finished in 7.799s (firmware) + 8.070s (loader) + 3.562s (kernel) +
10.306s (userspace) = 29.739s
Switching back to lz4, now I don't get the error! Maybe it's the newest
kernel (.19 out today), or maybe it's just tweaking the decoding to gzip
and back? Very strange.
Booting lz4 again
Startup finished in 7.775s (firmware) + 7.947s (loader) + 2.136s (kernel) +
9.105s (userspace) = 26.965s
Boot lz4
Startup finished in 6.907s (firmware) + 8.338s (loader) + 2.595s (kernel) +
3.705s (userspace) = 21.547s
graphical.target reached after 3.695s in userspace
Will come back with gzip and see.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Still in 19.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767995
Title:
Horizontal scroll doesn't honor Natural Scrolling preference
To manage notifications about this bug go to:
** Summary changed:
- Intel wifi 3165 not working properly in Ubuntu 18.10
+ Intel wifi 3165 not working properly in Ubuntu 19.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848953
Title:
Intel
** Attachment added: ""journalctl -b -1" (failed boot) for other user"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1848900/+attachment/5298524/+files/jj9k.log
** Summary changed:
- blank display with Eoan Ermine live DVD on Rysen 2200G
+ Blank display with Eoan Ermine live DVD on
I was supporting another Xubuntu 19.10 user on AMD Ryzen 3 2200G
(Gigabyte Technology Co., Ltd. B450 AORUS M/B450 AORUS M, BIOS F2
08/08/2018) today, whose log of a failed (standard) boot (to black
screen) showed
kernel: WARNING: CPU: 2 PID: 255 at
Related logs from journalctl -b:
os-prober[6348]: debug: running /usr/lib/os-probes/10zvol-test on /dev/sda5
os-prober[6351]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/sda5
50mounted-tests[6361]: debug: creating device mapper device
/dev/mapper/osprober-linux-sda5
kernel:
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848496
Title:
[zfs-root] device-mapper: reload ioctl on
Public bug reported:
On a 19.10 (pre-release, 20191016 daily) zfs installation, running 'os-
prober' (as 'update-grub' does by default) triggers the following error
message:
x@x:~$ sudo os-prober; echo $?
device-mapper: reload ioctl on osprober-linux-sda5 failed: Device or resource
busy
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 1848225
This is needed since the source package assignment has been updated.
Target Netplan package
** Package changed: plan (Ubuntu) => netplan.io (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848225
Title:
netplan fails to configure wifi on rpi4 with eoan
To
** Changed in: evince (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847633
Title:
19.10 wifi networks menu doesn't respect natural scrolling
Changing to gzip is bad. 19.10 switched over to lz4 because it's way
faster decompressing, which makes for faster boots!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835660
Title:
initramfs
At https://gitlab.gnome.org/GNOME/nautilus/issues/1244 it was determined
that this is a duplicate report for upstream bug
https://gitlab.gnome.org/GNOME/nautilus/issues/162
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #162
https://gitlab.gnome.org/GNOME/nautilus/issues/162
**
*** This bug is a duplicate of bug 1847826 ***
https://bugs.launchpad.net/bugs/1847826
** This bug has been marked a duplicate of bug 1847826
ZFS installer crashes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Related OOPS:
https://errors.ubuntu.com/oops/0bfbfd74-ed21-11e9-aef8-fa163e983629
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847826
Title:
ZFS installer crashes
To manage notifications about
** Summary changed:
- ZFS installer crashes (Xubuntu)
+ ZFS installer crashes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847826
Title:
ZFS installer crashes
To manage notifications about this
*** This bug is a duplicate of bug 1847826 ***
https://bugs.launchpad.net/bugs/1847826
** This bug has been marked a duplicate of bug 1847826
ZFS installer crashes (Xubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1847826 ***
https://bugs.launchpad.net/bugs/1847826
Public bug reported:
Desktop installation on a 4 GB RAM system. The following non default options
were selected:
* minimal installation
* 3rd party (proprietary) software
* ZFS
Shortly after the
As seen on the duplicate bug 1847848, 2 GB can trigger the installers'
OOM killer. With 3 GB, installation (with ZFS) succeeded for me (but 3
GB is probably still too little for a ZFS Desktop system, so I agree
more is much better there).
Maybe the easiest way to fix this for the 19.10 release is
Public bug reported:
Doing a default installation with the ZFS option enabled, on a system
with 2.0 GB physical RAM (actually a Virtualbox VM), the installation
went out of memory and OOM killer kicked in, stopping the desktop and
leaving me with a shell which just printed OOM messages for
Based on the events in UbiquitySyslog.txt (first error seems to be
"ubiquity: cannot resolve path '/dev/sda4'"), this is likely a duplicate
of bug 1847826
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I don't seem to be able to reproduce this, so I hope the log files allow
for concluding something.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847843
Title:
eoan-desktop-amd64 20191011 zfs
eoan-live-server-amd64.iso daily 20191011 lacks the /lib/firmware path.
eoan-desktop-amd64.iso daily 20191011 has the /lib/firmware path as well as
bnx2/bnx2-mips-09-6.2.1b.fw.
Rob Thomas: Could you confirm that you tested the live-server installer?
** Tags added: amd64 eoan
--
You
Public bug reported:
I just did a default installation. Had switched back and forth between
not enabling (default) and enabling 3rd party drivers a bit, but in the
end decided to go with the default. Then, after selecting ZFS install,
the installer crashed with a message saying so.
ProblemType:
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
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.
@ddstreet any configuration that ships lots to a remote host will
trigger this. The server always responds with the bug, so the
configuration effectively doesn't matter. As long as one host is
attempting to send journals to another in Disco, this bug will be
triggered.
Examples configs:
re: evince -->
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1847647
Screenshot attached. The Select Network screen, just like I originally
reported.
** Attachment added: "Screenshot from 2019-10-10 14-13-03.png"
Public bug reported:
1. You can't easily go to report a bug on launchpad.net.
Go to https://bugs.launchpad.net/ubuntu/
Click Report a Bug
Expected Behavior: report a bug
Actual behavior: Taken to stupid words
Fix: Put a link on ALL major launchpad.net pages where you can click on "Report
a Bug"
Screenshot -- I promise I just clicked submit IMMEDIATELY after this
screenshot, no funny business like retyping "evince" in the unselected
radio button text field and selecting it...
** Attachment added: "Screenshot from 2019-10-10 14-10-29.png"
I'm experiencing this in 19.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1073669
Title:
Bluetooth won't stay disabled after reboot due to early upstart job
To manage notifications about this
Public bug reported:
Steps to reproduce
Be in 19.10
Set natural scrolling to on/true/yes for mouse/touchpad
Go to select network
on the list of wifi SSIDs, scroll down. It won't move. Scroll up. It scrolls
down.
I've only tested this with touchpad, but I'm guessing it affects mice
too? Can
For those that may try to search for this bug in the future, the error I
received was
Error 411: gth required
The issue is that libmicrohttpd exhibits a bug when Content-Length is
omitted, even if Transfer-Encoding is set to "chunked". The HTTP/1.1
spec allows Content-Length to be omitted when
Public bug reported:
I'm requesting that systemd 240 receive the fix in upstream PR 11953
found here https://github.com/systemd/systemd/pull/11953
This fixes remote journal shipping using systemd components. I believe
only Disco (19.04) is impacted by this issue.
** Affects: systemd
** Tags added: amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788702
Title:
package snapd (not installed) failed to install/upgrade: subprocess
installed post-removal script returned error
Potential dupe of bug 1788702?
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805874
Title:
package snapd (not installed) failed to install/upgrade: installed
snapd package
301 - 400 of 11183 matches
Mail list logo
