I'll sum up my view on this (which I had hoped, would be yours, too):
So far, in Ubuntu, mysqld always listened on port 3306 only, and only on
the loopback interface by default. 20.04 introduced a mysql server
version which introduces the MySQL X protocol. The expectation a mysql
server administra
There's no "opera" package in Ubuntu, so filing bugs on the Ubuntu bug
tracker cannot succeed in having these fixed, I'm afraid.
If this is about the Opera web browser, I suggest to look for available
support channels on https://www.opera.com
** Changed in: opera (Ubuntu)
Status: New => In
For gnome-control-center, this bug report was watching
https://bugzilla.gnome.org/show_bug.cgi?id=692666 so far. While still
relevant, the Gnome Project has stopped using this bug tracker and has
since shifted to their Gitlab instance for bug tracking.
A closely related upstream bug report, which
** Bug watch added: gitlab.freedesktop.org/libfprint/libfprint/-/issues #196
https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/196
** Also affects: libfprint via
https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/196
Importance: Unknown
Status: Unknown
--
You r
Hi. Thanks for reporting this issue. However, I think this is not a
software malfunction, and you're rather looking for support:
https://ubuntu.com/support
For free community support, scroll to the very bottom. Personally, I
would recommend real-time IRC support:
https://wiki.ubuntu.com/IRC/Chann
Public bug reported:
This is a bug report / feature request about Ubuntu installations
created by either the Ubuntu Desktop or Server (both 'live' and
classic/alternative) installer. 'ubiquity' may be the wrong package.
Currently, when you install any variant of Ubuntu to a storage type
which sup
What you're looking at there is probably unicode character 🌈
maybe Dimitri can confirm this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779569
Title:
thunderbird showing weird images in some mai
On some Ubuntu systems I manage, I see regular writes to the /EFI/ubuntu
location with current file modification timestamps. On a multi boot
system, the content of the ESP can also change more often. So I would
say there seem to be regular writes, which means discard would make
sense.
Changing the
Bionic live server dailies:
http://cdimage.ubuntu.com/ubuntu-server/bionic/daily-live/current/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783129
Title:
Only "main" component enabled after insta
*** This bug is a duplicate of bug 1764417 ***
https://bugs.launchpad.net/bugs/1764417
Public bug reported:
This is a duplicate of #1764417 (and probably also of #1663839), I'd
like to provide extra logs and not clutter the existing report.
Roughly two minutes after logging in, I was confron
Public bug reported:
Pointing ubuntu-bug to a non-existing X window makes apport-gtk
segfault:
myrestricteduser@ubuntu1804amd64~$ DISPLAY=:1 ubuntu-bug ubiquity
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
Segmentation f
Off-topic but possibly necessary context:
Ubuntu (major) releases are time based. The time of the release is indicated in
the release version. As such, Ubuntu 18.10 will be released in year (20)18,
month 10.
More precise release dates are provided at https://wiki.ubuntu.com/Releases
Point rele
While I'm not Andrew (@at-fresh), I can confirm that installing using
the amd64 image at http://cdimage.ubuntu.com/ubuntu-server/bionic/daily-
live/current/ provide the expected sources.list file.
It would be nice to update / refresh / replace the 18.04.1 release
images using these, if this is an
Public bug reported:
'proposed' is enabled by default on bionic server-live amd64 daily
images via /etc/apt/sources.list.d/proposed.list. This is unexpected.
These images were downloaded at
http://cdimage.ubuntu.com/ubuntu-server/bionic/daily-live/current/bionic-live-server-amd64.iso
I tested tw
Public bug reported:
Ubuntu 18.04.1 amd64 server-live installer:
It would be nice to offer a UI to cancel the installation. So far while
following the menu navigation users can click "back" several times but
then only end up on the first installer prompt (language selection).
There is no way to '
Hi Dimitri,
I'm not 'validating SRUs' per se, I just use the daily builds (I am aware these
are unsupported, I was not aware these can come with non release
configurations) to overcome some of the (sometime serious) issues the released
18.04.1 server-live installer has, some of which have thank
I was wrong. the 18.04.1 server-live installer (as well as daily ISOs
until today) have not improved upon this (tested on an UEFI booted
system only). The alternative (debian-installer based) server installer
works fine.
--
You received this bug notification because you are a member of Ubuntu
Bug
This may have been a BIOS bug, does not occur after BIOS upgrade (BIOS
P4.70 04/17/2018 -> BIOS L4.81 08/16/2018):
# dmesg -t | grep ^DMI:
DMI: To Be Filled By O.E.M. To Be Filled By O.E.M./X370 Taichi, BIOS L4.81
08/16/2018
# dmesg | grep -A5 'efifb: probing for efifb'
[0.81] efifb: pro
# cat /proc/version
Linux version 4.15.0-34-generic (buildd@lgw01-amd64-047) (gcc version 7.3.0
(Ubuntu 7.3.0-16ubuntu3)) #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018
# cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/vg-slash ro
Before the BIOS upgrade, the same kernel v
** Changed in: gvfs (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/1752091
Title:
gvfsd-metadata[1703]: g_udev_device_has_property: assertion
'G_UDEV
I'd be very happy to help testing cryptodisk / luks / lvm / md raid
configurations as part of a joint SRU effort.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565950
Title:
Grub 2 fails to boot a
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824546
Title:
Intel N3060 booting into black screen with 5.0 kernel
To manage notifications about this bu
It is yet unclear what the root cause of this issue is - libpam, crypt,
passwd and sudo seem like primary suspects. The 256 character password
is hashed to a value which still allows a TTY login to succeed. Also,
passwd run by a different user in the context of the affected user
(using sudo) still
This seems to be an issue with network namespaces, which I assume may
point to Linux. This report is about Ubuntu Kylin, a supported Ubuntu
flavor.
** Project changed: ubuntu-ubuntu-server => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
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.
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: B
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 receive
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 instal
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.
https://bugs.launchpad.net/bugs/
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 additio
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
*** 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.
https
*** 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 installat
** 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
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 th
*** 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.
https://bugs.la
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
** Cha
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 ma
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.
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
Command
** 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 osprober-linux-
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: device-ma
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
drivers/gpu/drm/amd/amdgpu/../display/dc/dcn10/dc
** 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 Ryze
** 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
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
Related links:
https://lore.kernel.org/patchwork/project/lkml/list/?series=419906&state=*
https://github.com/torvalds/linux/blob/master/drivers/platform/x86/hp-wmi.c
https://wiki.ubuntu.com/Kernel/Reference/WMI
https://lwn.net/Articles/391230/
** Bug watch added: Linux Kernel Bug Tracker #201981
~esserre This is not the same bug - please report it separately (run
"ubuntu-bug linux").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804577
Title:
ACPI BIOS Error (bug): Failure creating [\_SB.S
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
https://bugzill
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
o
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
on
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 because
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 b
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 t
~emmenlau: Try setting up a serial console to or netconsole from this
system to get a better idea of why / how it's freezing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
Ryzen 1800X
Public bug reported:
After installing rasdaemon and starting the service (sudo systemctl
start rasdaemon) on this amd64 16.04.4 system, running "ras-mc-ctl
--summary" fails:
Can't locate DBI.pm in @INC (you may need to install the DBI module)
(@INC contains: /home/myuser/.opam/4.04.2/lib/perl5 /e
Public bug reported:
parallel-rsync's man page states that it is a "parallel process kill
program":
http://manpages.ubuntu.com/manpages/bionic/man1/parallel-rsync.1.html
This seems incorrect - it was likely copied and pasted from 'parallel-
nuke'.
The upstream URL is also incorrect (now), upstr
Steve: That's more of a support question (https://ubuntu.com/support -
see also the references to community support to the bottom). However,
other Ubuntu users wondering about this same question may end up on this
bug report, so here's a quick reply:
Please read up on the support policy which appl
See comment 26 if you're still interested in seeing this fixed. After
sending mail there, be sure to mention it here, ideally with some kind
of reference (mailing list name and (message id) or (date and time of
message send, sender's e-mail address, subject line)) so others will not
send duplicate
Image referenced in comment 31 by _doom (duso315-gmail) - cropped + scaled down:
"mmc0: mmc_hs400_to_hs200 failed, error -84"
** Attachment added: "mmc0: mmc_hs400_to_hs200 failed, error -84"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407/+attachment/5285942/+files/9q7jRYx.jpg
-
@ovari: It's good that you contacted these mailing lists. Note, however,
that the developers subscribed to these lists are extremely overwhelmed
with e-mail. They will likely not respond to e-mails which do not
(concisely) state the actual issue by means of error messages, version
number and furthe
I just reported it upstream at
https://gitlab.gnome.org/GNOME/nautilus/issues/1243
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1243
https://gitlab.gnome.org/GNOME/nautilus/issues/1243
** Also affects: nautilus via
https://gitlab.gnome.org/GNOME/nautilus/issues/1243
Import
Thanks, Seb. I have reported this upstream at
https://gitlab.gnome.org/GNOME/nautilus/issues/1244
** Bug watch added: gitlab.gnome.org/GNOME/nautilus/issues #1244
https://gitlab.gnome.org/GNOME/nautilus/issues/1244
** Also affects: nautilus via
https://gitlab.gnome.org/GNOME/nautilus/issues
As a potential workaround, please try to boot a current kernel (one that
was also tested to not work otherwise) with kernel parameter
sdhci.debug_quirks=32832 as per https://forums.xilinx.com/t5/Embedded-
Linux/Linux-Kernel-4-6-mmc-issue/td-p/727465
--
You received this bug notification because y
Public bug reported:
I just installed Ubuntu 19.10 desktop daily 20191009 on VirtualBox
6.0.12 r133076 (virtualbox.org packages) running on Ubuntu 18.04.3.
18ebdad23234e617c7f33dec4cc6346ec443a3cc7edf004275483c63832791cf eoan-
desktop-amd64.iso
Both host and guest are amd64, both are configured
** Attachment added: "grub.cfg of installed system"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1847469/+attachment/5295833/+files/grub.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
*** This bug is a duplicate of bug 1847457 ***
https://bugs.launchpad.net/bugs/1847457
This is indeed a duplicate of bug 1847457.
** This bug has been marked a duplicate of bug 1847457
No /cdrom mounted on live
--
You received this bug notification because you are a member of Ubuntu
Bugs
Please disregard my above comment. Further testing shows the default
installer option can also cause /cdrom to be empty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847457
Title:
No /cdrom mounte
I tested installing using the 20191009 daily installer in UEFI mode
several times today.
Using the default (boot to live system/desktop) grub menu option, /cdrom was
always mounted.
Using the grub menu option to immediately run the installer, /cdrom was never
mounted.
Of course, this could stil
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 po
** 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 e
https://launchpadlibrarian.net/423140934/VarLogDistupgradeAptlog.txt
seems to suggest you have packages from multiple Ubuntu releases
installed. If this can be confirmed, then this is more of a support case
than a bug in the software.
This said, more robust handling by the release upgrader (detect
** Summary changed:
- Error installing default-mysql-server on fresh ubuntu 18.04.3 install
+ Error installing default-mysql-server on fresh ubuntu 18.04.2 install
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Thanks for filing this bug report, Jack.
I'm one of the IRC support volunteers who tried to help here, but I'm mostly
out of ideas.
As suggested on IRC, trying a mainline kernel may be a good idea (only if you
can still reproduce the issue).
I should mention that a "USB-C Triple-4K Dock" (Serial
Possibly related to bug 699802. See comments 24 and 101 for potential
workarounds.
If you'll test these, please test them thoroughly, doing multiple warm
and cold boots with each changed setting, since successful boots are
currently non-deterministic.
--
You received this bug notification becaus
Also, before you do the testing, please attach your current
/boot/grub/grub.cfg
/boot/efi/EFI/ubuntu/grub.cfg
files to this bug report. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829402
** Summary changed:
- Crash in first phases of Ubuntu 19 Installing from USB
+ Crash in first phases of Ubuntu 19.04 Installing from USB
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829742
Title:
The way I understand Mustafa's report this is about the general lack of
a caps lock state indicator on (so primarily post-login, in gnome-
shell). Bug #1734887 rather discusses the lack of an indicator pre-login
(gdm), so is a different issue.
** This bug is no longer a duplicate of bug 1734887
Could you explain what seems to be the security impact here?
Cross Site Scripting (XSS) is an attack which may be possible when data
is interpreted by a HTML renderer without ensuring that data is properly
escaped / encoded. The "whois" command does not render HTML, it is a
command line utility.
** Summary changed:
- upgrade to ubuntu 16 from 14 failed
+ LTS Upgrade from Ubuntu 14.04 to 16.04 failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829767
Title:
LTS Upgrade from Ubuntu 14.04
Please note that Kubuntu 14.04 LTS is no longer supported:
https://wiki.ubuntu.com/Releases
The Ubuntu community documentation describes a means of upgrading from an EOL
release:
https://help.ubuntu.com/community/EOLUpgrades
The technical reason your upgrade attempt failed is that due to a
com
*** This bug is a duplicate of bug 1725017 ***
https://bugs.launchpad.net/bugs/1725017
** This bug has been marked a duplicate of bug 1725017
file-roller crashed with SIGSEGV in g_action_map_lookup_action()
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Bug watch added: gitlab.gnome.org/GNOME/file-roller/issues #31
https://gitlab.gnome.org/GNOME/file-roller/issues/31
** Changed in: file-roller
Importance: Medium => Unknown
** Changed in: file-roller
Status: Confirmed => Unknown
** Changed in: file-roller
Remote watch: GNOME Bug
I assisted (or tried to) oikasd on IRC with this a little today.
initially, oikasd ran "sudo apt-get upgrade" and apt seemed to get stuck
(no further lines of output for several minutes) after these lines (full
output not available):
snapd.failure.service is a disabled or a static unit, not sta
Thanks for the credit, but it is not mine. This rather unspecific
workaround, which will likely increase power draw, was not initially
reported by me, but at
https://bugs.freedesktop.org/show_bug.cgi?id=109215#c9
** Bug watch added: freedesktop.org Bugzilla #109215
https://bugs.freedesktop.org/
I tested version 19.01.3-1~ubuntu19.04.1 (from -proposed) on a fully
updated 19.04, and can no longer reproduce this issue: The terminal
window opens - as expected - in directory ~/Desktop/aaa'bbb/. Injecting
commands as discussed in comment 2 appears to be no longer possible.
** Tags removed: ver
** Bug watch added: Linux Kernel Bug Tracker #199035
https://bugzilla.kernel.org/show_bug.cgi?id=199035
** Also affects: udev via
https://bugzilla.kernel.org/show_bug.cgi?id=199035
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #901965
https://bugs.d
Thanks for your report. I'm not a developer, just having a quick glance
on your logs:
Your system log shows I/O errors on /dev/sdb, a 1.00 TB storage. This
can be due to bad cabling / connectors or due to a bad disk.
Additionally, the USB connection to the WD My Passport 25E1 drive was
reset twice
Please consider testing this:
1. Add this to /etc/default/grub :
GRUB_GFXPAYLOAD_LINUX="text"
2. Add this to the GRUB_CMDLINE_LINUX_DEFAULT option in /etc/default/grub :
earlyprintk=efi,keep
3. Run: sudo update-grub
4. Try all of the following combinations of kernel boot parameters by editing
Thank you for taking the time to report this bug and helping to make
Ubuntu better. While we appreciate the difficulties you are facing, it
would appear that the image (ISO file) you downloaded could be corrupt.
There is an easy way to verify the integrity of the Ubuntu ISO files you
download. Coul
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, you seem to be using packages from PPAs. PPAs
are unsupported by Ubuntu, and packages (and package versions) installed
from those need to be removed before upgrading to a new Ubuntu release.
This PPA, whic
Diederik: Ubuntu 14.04 reached end of life, is no longer supported.
Max, and anyone else affected by this issue with identical symptoms as
Max on Ubuntu 16.04 with kernel 4.4.0-148, please consider testing this:
1. Add this to /etc/default/grub :
GRUB_GFXPAYLOAD_LINUX="text"
2. Add this to the G
Possible duplicate of bug #1829620.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829402
Title:
Purple screen hangup during boot
To manage notifications about this bug go to:
https://bugs.launchpa
*** This bug is a duplicate of bug 1829620 ***
https://bugs.launchpad.net/bugs/1829620
Thanks for testing, Jackneill.
To explain, the "dis_ucode_ldr" option disables loading of microcode
updates by Linux. Microcode updates are are binary blobs (no source code
is available) which modify operat
** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues
#22
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/22
** Also affects: gnome-shell-extension-desktop-icons via
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/22
Impor
Possible duplicates: #1813441 #858913
** Also affects: gnome-shell-extension-desktop-icons via
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/22
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Possible duplicates: #1822254 #858913
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813441
Title:
Can no longer drag and drop files from desktop into applications
To manage notifications about thi
Possible duplicates: #1813441 #1822254
** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues
#22
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/22
** Also affects: gnome-shell-extension-desktop-icons via
https://gitlab.gnome.org/World/ShellExt
Dear Adam,
the log you provided does not seem to indicate an issue with acquiring
data from http://ppa.launchpad.net/jtaylor/keepass/ubuntu but from
http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu - a PPA which does
not support your Ubuntu release (18.04 / bionic).
So this appears to not be a
1 - 100 of 313 matches
Mail list logo
