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 1831301
--
You received this bug notification because you are a member of U
OP had also tested this with linux-image-generic-hwe-18.04 / linux-
image-4.18.0-20-generic, where dmesg looked very similar to that of this
hwe-18.04-edge kernel.
Gabriele:
(1) Please do as discussed in comment 2.
(2) Please also re-run alsa-info as discussed at
https://wiki.ubuntu.com/Audio/A
Public bug reported:
There are some situations where it is desirable to gather debugging
information on a system affected by a bug, but to login (to
Launchpad/Ubuntu SSO) and complete editing this bug report from a
different system.
This is already implemented for situations where the affected sy
Possibly related to https://bugzilla.mozilla.org/show_bug.cgi?id=1553422
where non user owned files in $HOME/.cache/mozilla/firefox caused it.
As reported there, pressing Ctrl-Shift-J revealed file access errors
within the Firefox profile directory, due to incorrect file ownerships.
You could run
I do not know how priorities in bug handling are set, but I do wonder
what may be the reason to not handle this rather common (30 dupes)
critical (crash) bug on a 'main' package for the past three years -
could someone explain this to me? Thanks in advance.
--
You received this bug notification b
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
https://gitlab.gnome.org/GNOME/nautilus/issues/12
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 o
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 wi
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:
Thanks for the notice, I updated the link.
https://wiki.ubuntu.com/ARM/RaspberryPi?action=diff&rev2=104&rev1=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
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: Medium
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
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 wireles
** 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 o
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:
https://bugs.launchpad.
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 tracking
Public bug reported:
Running (up to date) 18.04 LTS I'm trying to import a public key from
the somewhat new but OpenPGP key spamming resistant key server at
keys.openpgp.org:
$ curl -s
'https://keys.openpgp.org/vks/v1/by-fingerprint/723E343AC00331F03473E6837BE5A11FA37E8721'
| gpg --import
gpg:
Some more context:
"New" keys.openpgp.org key server:
https://keys.openpgp.org/about/news#2019-06-12-launch
Isses with SKS keyservers:
https://medium.com/@mdrahony/are-sks-keyservers-safe-do-we-need-them-7056b495101c
OpenPGP certificate (key signature) flooding / spam:
https://www.vice
*** This bug is a security vulnerability ***
Public security bug reported:
According to https://people.canonical.com/~ubuntu-
security/cve/2019/CVE-2019-13050.html mitigating CVE-2019-13050 was
deferred, however mitigation is needed.
Reading the comments listed there, I am unable to determine th
See also related bug 1844059.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844055
Title:
Importing public key from keys.openpgp.org fails with "no user ID"
To manage notifications about this bug
** 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/1764417
Title:
Unrecoverable failure in required component
org.gnome.SettingsDaemon.Color.desktop
To manage notifications about
Thanks for clarifying this here and on the CVE tracker, Alex + Marc!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1844059
Title:
Please apply mitigations for CVE-2019-13050
To manage notifications
This apparently made it into 19.10 beta1, my UEFI booted 19.04 beta1 VM
(running on VirtualBox 6.0.12, Ubuntu 18.04.3 / Linux 5.3 host) reported
a duplicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
On the 19.10 beta, deleting a starred file leaves behind a file named ""
in Starred.
It does not matter whether the file is first moved to trash, then trash
expunged, or whether the file is immediately deleted using Shift-Delete.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Public bug reported:
While in "Starred" right-clicking on a FSO¹ and selecting "Copy to.." brings up
a new window to choose the destination, but this window shows an error message:
The folder contents could not be displayed
The specified location is not supported
Steps to reproduce:
1. Star
Confirming the error message enables the user to continue. If the user
then chooses to create a new folder, Nautilus crashes with:
https://errors.ubuntu.com/bucket/?id=/usr/bin/nautilus%3A11%3Acheck_valid_child_name%3Anew_folder_name_changed%3Ag_closure_invoke%3Asignal_emit_unlocked_R%3Ag_signal_e
Please ignore the previous comment, this wa snot meant to be posted
here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845703
Title:
Deleting starred files leaves behind starred file named ""
To
Confirming the error message enables the user to continue. If the user
then chooses to create a new folder, Nautilus crashes with:
https://errors.ubuntu.com/bucket/?id=/usr/bin/nautilus%3A11%3Acheck_valid_child_name%3Anew_folder_name_changed%3Ag_closure_invoke%3Asignal_emit_unlocked_R%3Ag_signal_e
Public bug reported:
According to
nautilus --help
there is an option
-c, --checkPerform a quick set of self-check tests.
Running 'nautilus --check' on the 19.10 beta or on 18.04.3 prints:
running nautilus_self_check_file_utilities
running nautilus_self_check_file_operation
Please refer to the duplicate bug 1845750 for a reproducer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845749
Title:
/usr/bin/yelp:11:yelp_uri_get_document_uri:action_new_window:g_closure_invok
*** This bug is a duplicate of bug 1845749 ***
https://bugs.launchpad.net/bugs/1845749
Public bug reported:
Steps to reproduce:
1. Run "yelp :"
2. Yelp opens with an empty document / no document.
3. From the menu, select "New Window"
4. Yelp crashes with a segmentation fault.
This happens o
** Summary changed:
- Ubiquity crashes at the bootloader installation phase
+ Bootloader installation fails on UEFI systems with FDE (incl. /boot)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762988
This also affects the 18.04.1 "alterantive installer (debian-installer),
where I reproduced it today.
This error will not occur on the current default server installer
(Subiquity) at this time since it does not support dmcrypt-luks at all.
To my knowledge, the desktop installer (Ubiquity) does not
The root cause of this is discussed at bug #1565950.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762988
Title:
Bootloader installation fails on UEFI systems with FDE (incl. /boot)
To manage noti
See bug #1762988 for a discussion of how
(a) this also affects Ubuntu installers and
(b) a non secureboot full disk encryption installation can be achieved with the
alternative server installer (AKA debian-installer).
--
You received this bug notification because you are a member of Ubuntu
Bug
$ journalctl --list-boots 2>/dev/null | head -n1 && journalctl --disk-usage
2>/dev/null
-37 64975ef449c34cdc828feb0197d7a2f5 Mon 2018-09-10 02:00:47 CEST—Mon
2018-09-10 08:05:57 CEST
Archived and active journals take up 1.8G in the file system.
My interpretation is my systems' situation is that
This issue also affects 18.04.1.
$ lsb_release -ds; cat /proc/version; cat /proc/cmdline
Ubuntu 18.04.1 LTS
Linux version 4.18.0-13-generic (buildd@lcy01-amd64-024) (gcc version 7.3.0
(Ubuntu 7.3.0-16ubuntu3)) #14~18.04.1-Ubuntu SMP Thu Dec 6 14:09:52 UTC 2018
BOOT_IMAGE=/vmlinuz-4.18.0-13-generi
Possibly related: bug #1517491
See also:
https://askubuntu.com/questions/1088662/npm-depends-node-gyp-0-10-9-but-it-is-not-going-to-be-installed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809828
Public bug reported:
If storage is hot-added during installer runtime, this results in the
installer incorrectly stating the amount of available storage.
Steps to reproduce:
I booted the Ubuntu 20.04.1 Desktop installer in a VM from a (virtual) CD-ROM
drive, in BIOS mode. No other storage was at
Attaching screenshot previously stored at imgur.com
** Attachment added: "ubiquity_incorrect_fs_allocation_display.png"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1900274/+attachment/5423474/+files/ubiquity_incorrect_fs_allocation_display.png
** Description changed:
If storage
Relevant lines from DpkgTerminalLog.txt:
Setting up linux-firmware (1.187.3) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-51-generic
[..]
cp: cannot stat '/etc/ykluks.cfg': No such file or directory
E: /usr/share/initramfs-tools/hooks/yubikey-luks failed with return 1.
update-initramfs:
https://packaging.ubuntu.com/html/fixing-a-bug.html probably still
applies.
However, expanding the version numbers for recent releases on
https://launchpad.net/ubuntu/+source/dstat shows, in "Publishing details",
shows:
"Copied from debian sid in Primary Archive for Debian GNU/Linux."
So this i
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
However, this bug report was filed against ubuntu-release-upgrader,
while the bug report seems to be about "Lotus Approach v 98", a software
which (to my knowledge) is not part of Ubuntu. I amn therefore changing
t
This is probably a 'feature' of your Sophos AV software.
talpa_* modules are part of it:
https://support.sophos.com/support/s/article/KB-37103
See also the various 'talpa' error messages in your kernel log:
https://launchpadlibrarian.net/516159223/CurrentDmesg.txt
** Changed in: linux (Ubun
Possible duplicate report: bug 1910738
This is most likely a support topic, not a bug - please provide further
information if you are convinced it is a bug. Support options (incl. free
community support - on the bottom) are listed on
https://ubuntu.com/support
** Changed in: linux (Ubuntu)
Possible duplicate report: bug 1904724
Thanks for reporting. This is more likely a support topic, not a bug - please
provide further information if you are convinced it is a bug. Support options
(incl. free community support - on the bottom) are listed on
https://ubuntu.com/support
** Changed i
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1396379
Title:
installer uses first EFI system partition found even when directed
otherwise
To manage notifications about this b
*** This bug is a duplicate of bug 1897299 ***
https://bugs.launchpad.net/bugs/1897299
Linux version 5.4.0-48-generic (buildd@lcy01-amd64-010) (gcc version 9.3.0
(Ubuntu 9.3.0-10ubuntu2)) #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 (Ubuntu
5.4.0-48.52-generic 5.4.60)
dmesg shows repeat occur
Also related: https://bugzilla.kernel.org/show_bug.cgi?id=206109
** Bug watch added: Linux Kernel Bug Tracker #206109
https://bugzilla.kernel.org/show_bug.cgi?id=206109
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Summary changed:
- High I am having issues on Xubuntu 20.04 revolving around WiFi
+ iwl3945: Low throughput on focal / Linux 5.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902421
Title:
iwl3
The current installer version is 20.04.1, which comes with different
proprietary nvidia drivers.
Another problem is that your DNS resolver failed. It would be nice if
Ubiquity could detect this and re-try getting the packages which failed
to download. Maybe this makes this a wishlist bug.
For sup
There is no easy way to gracefully handle weak crypto. It has been known
for more than five years that 1024 bit (or rather <2048 bit) DH primes
need to be considered weak and should not be used - https://weakdh.org/
- GnuTLS > 3.2 does the right thing in having services which still have
not taken a
Thanks for the bug report. I'm reassigning this to (the proper?) package
- calibre is an e-book library manager.
** Project changed: calibre => linux-meta (Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
TJ wrote this:
https://help.ubuntu.com/community/Full_Disk_Encryption_Howto_2019
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773457
Title:
Full-system encryption needs to be supported out-of-the-
Possibly related? https://bugzilla.kernel.org/show_bug.cgi?id=204343
** Bug watch added: Linux Kernel Bug Tracker #204343
https://bugzilla.kernel.org/show_bug.cgi?id=204343
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
There is support for tasks in apt for a while now, tasksel is considered
deprecated.
sudo apt-get -V --assume-no install server^
apt-cache show server^ | awk -F: '/^Package/ {print $2}'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is not a software bug, please contact support.
Quoting UbiquitySyslog.txt:
mce: [Hardware Error]: Machine check events logged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877881
Title:
Can't
Please update this bug report in case you have reason to believe this
status is incorrect.
** Changed in: ubiquity (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/bu
Thanks for the fast fix of Subiquity. Personally, I continue to consider
Ubuntu installers to be affected. To me, the ability to live upgrade
Subiquity (where Internet access is available) is a nice workaround.
Could we clarify which Ubuntu releases (or their installers) are (not)
affected in that
** Bug watch added: GCC Bugzilla #96130
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96130
** Also affects: gcc via
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96130
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs
It is my impression that specifying "mtrr_gran_size/mtrr_chunk_size" when
"mtrr_cleanup: can not find optimal value" is still useful on some systems.
The latest system where I helped identifying good values (according to
https://github.com/tomreyn/linux_mtrr_size_fix) was a
Gigabyte Z97X-Gamin
So, as has been previously stated here, and as is documented in section
5 of the journald.conf man page (install man-db, run 'man 5
journald.conf'), journald will, by default, limit the journals' disk
allocation to either a maximum of 10% of available disk space, or to the
absolute size of 4GB, whi
** Package changed: ubuntu => linux-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888070
Title:
latest update freezes system on boot
To manage notifications about this bug go to:
htt
I can't reproduce any issues with grub2 booting off a fully updated (as
of today) 19.04 amd64 pre-release in BIOS boot mode.
Some of what was posted previously was about boot issues with
(apparently incompatible) non Ubuntu versions of Grub 1 (0.99), probably
installed by one of the other OS insta
As discussed on IRC:
A package being dropped as unsupportable isn't really a functional bug (which
you'd file a bug report on). According to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917831 'pdfshuffler' is going
to be replaced by an actively maintained fork, 'pdfarranger', in Debian. Th
Not breached here:
$ journalctl -b -u systemd-journald.service -n 1
-- Logs begin at Sat 2018-09-29 05:03:28 CEST, end at Thu 2019-03-21 18:18:38
CET. --
Mar 20 13:32:03 debby2017 systemd-journald[699]: System journal
(/var/log/journal/f8b692c8bb791fe2804f3d5a5905148b) is 1.8G, max 1.8G, 0B free
So I wasn't aware of this size hard limit on persistent storage - I just
noticed that it is 'already' allocating 1.8GB, but this is indeed less
than the 10% of the file system the man page says it will consume. So
from my personal point of view this is a non-issue then (ideally
Benjamin will also p
See also #1798992
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802337
Title:
Please apply security updates during Ubuntu install
To manage notifications about this bug go to:
https://bugs.launchp
The reason I had filed this against ubuntu-manual-tests was that someone
(I did forget who since this was back in October) asked me to file this
bug exactly against his (pseudo) package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
s/asked me/recommended to/ - sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798992
Title:
Fresh desktop installation has packages pending autoremoval, pending
updates
To manage notificatio
** Package changed: subiquity (Ubuntu) => ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798992
Title:
Fresh desktop installation has packages pending autoremoval, pending
update
*** This bug is a duplicate of bug 1816846 ***
https://bugs.launchpad.net/bugs/1816846
Marc also reported on IRC (#ubuntu, 2018-02-22 ~17:20 UTC) that this report
refers to the mini.iso with MD5SUM ed2bbe59e5dac40b92e0ddeb6b206ef8
While Marc uses Xen, Jesse uses a different HV technology.
Ma
Public bug reported:
I'm installing Ubuntu 18.04.2 amd64 server on a BIOS booted VirtualBox
VM. It has two storages, on which I previously installed Ubuntu using
the same installer. Then, I created an MD RAID-1 backed by a total of
two component devices, which are partitions, one on each of the tw
Reported upstream on the Gnome projects' new 'bug tracker' (Gitlab) - for which
no bug watch exists in Launchpad (to date):
https://gitlab.gnome.org/GNOME/file-roller/issues/31
** Bug watch added: GNOME Bug Tracker #746829
https://bugzilla.gnome.org/show_bug.cgi?id=746829
** Also affects: fil
Public bug reported:
Affects:
* Ubuntu 19.04 amd64 Desktop installer (main flavour, UEFI booted)
Does not affect:
* Ubuntu 18.04.2 amd64 Desktop installer (main flavour, UEFI booted)
When installing on 19.04, keeping the default English installer language, but
setting the keyboard layout
Quick summary (from my POV, after discussing this with Marco in #ubuntu-
bugs):
The issue described here is that the keyboard layout chosen during the
Ubuntu 19.04 amd64 (default flavour) installer step does not carry to
the installed system, where only the US-English keyboard will be
available no
Workaround:
Before starting the installation (or after cancelling it during the first
steps), click on "Activities" (top left corner of the screen), then type
"settings" and press enter to bring up the "Settings" application. There, click
on "Region & Language" on the left column menu, then, und
Thanks Sebastien, I've filed it at Gnome's Gitlab and added the bug
tracker.
** Bug watch added: gitlab.gnome.org/GNOME/gvfs/issues #395
https://gitlab.gnome.org/GNOME/gvfs/issues/395
** Also affects: gvfs via
https://gitlab.gnome.org/GNOME/gvfs/issues/395
Importance: Unknown
Stat
UbiquitySyslog.txt reports (timestamps/hostname removed):
efi: EFI v2.31 by American Megatrends
efi: ACPI=0xd9ae ACPI 2.0=0xd9ae SMBIOS=0xf04c0 MPS=0xfd430
secureboot: Secure boot could not be determined (mode 0)
SMBIOS 2.7 present.
DMI: Gigabyte Technology Co., Ltd. To be filled by O
Public bug reported:
On Ubuntu 19.04 (amd64):
Removing fonts-liberation2 (2.00.5-1) ...
dpkg: warning: while removing fonts-liberation2, directory
'/usr/share/fonts/truetype/liberation2' not empty so not removed
Removing fonts-opensymbol (2:102.10+LibO6.2.2-0ubuntu2) ...
dpkg: warning: while rem
~seb128: Since this also affects 18.04.2 via #1827295, is an SRU
possible / needed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795372
Title:
gnome-control-center crashed with SIGSEGV in
net_de
To clarify (thanks teward!), setting static IPv4 or IPv6 addresses is
possible.
However, selecting the "Info" option from the NIC context menu or
setting a domain name will cause the 18.04.2 installer to fail. Running
"snap refresh subiquity" from another TTY works around this (as mwhudson
clarifi
Chris (~iplayfast): You're not running the latest HWE kernel image:
linux-image-generic-hwe-18.04 | 4.18.0.18.68 | bionic-updates
"cat /proc/version" would report:
Linux version 4.18.0-18-generic (buildd@lcy01-amd64-006) (gcc version 7.3.0
(Ubuntu 7.3.0-16ubuntu3)) #19~18.04.1-Ubuntu SMP Fri A
I think the other bug report you meant to point to is actually bug
#1825227.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825224
Title:
gnome-calendar cannot add credentialed web ics calendars
To
It is an issue for me on 18.04.2, see my recent duplicate reports.
What happened to the upstream 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/1716940
Title:
gvfsd-trash crashed with si
Public bug reported:
While sure useful as a way to remedy the add-on intermediate signing
certificate expiry issue Mozilla has created
(https://bugzilla.mozilla.org/show_bug.cgi?id=1548973), I really think
Normandy should be disabled in Ubuntu by default:
Normandy is a collection of servers, wo
Normandy can remotely change the functionality and behavior and
preferences of Firefox installations, though. It can silently install
extensions which may not be listed at about:addons. I agree that is not
remote root access (not immediately, anyway), but the fact that such a
powerful remotely cont
** Also affects: subiquity (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/1824852
Title:
linux-firmware package not available in server installer
Public bug reported:
The desktop folder context menu option "Open in Terminal" opens a new
terminal, but the working directory is the home directory when it should
be the folder context.
To reproduce:
1. Create a folder "test" on the Desktop
2. Right-click on the "test" folder icon on the Deskto
Public bug reported:
Attempting to open a Desktop folder named "aaa'bbb" (without double
quotes) using the "Open in Terminal" option from the context menu
produces a notification message stating:
Execution of "x-terminal-emulator --working-directory=/home/...
Text ended before matching quote was
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825396
Title:
"Open in Terminal" returns "Text ended before matching quote was found
for '
As discussed on IRC, command injection is actually possible here.
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues
#111
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/111
** Also affects: gnome-shell-extension-desktop-icons via
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/111
Im
*** This bug is a duplicate of bug 1825396 ***
https://bugs.launchpad.net/bugs/1825396
** Bug watch added: gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues
#105
https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/issues/105
** Also affects: gnome-shell-extension-deskto
Public bug reported:
During the past days, questions about Secure Boot initialization
repeated on IRC.
This is what this screen looks like on 16.04 (I don't have an 18.04 or
19.04 screen available, but the users' questions seem to suggest it
still looks similar):
https://i.stack.imgur.com/cCTiK.
** Attachment added: "Secure Boot Inintialization on Ubuntu 16.04 installer,
step "Preparing to install Ubuntu""
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1826026/+attachment/5258297/+files/secure_boot_init.png
** Description changed:
During the past days, questions about Sec
Public bug reported:
Some of us had a discussion on what happens to systems running former
Ubuntu flavours (which no longer exist) when they are upgraded. It was
understood that the upgrade path will lead to (vanilla) Ubuntu. However,
packages which used to be installed from the previous flavour,
** Description changed:
- Some of us had a discussion on what happens to systems running former
- Ubuntu flavours (which no longer exist) when they are upgraded. It was
- understood that the upgrade path will lead to (vanilla) Ubuntu. However,
- packages which used to be installed from the previou
** Changed in: ubuntu-release-upgrader (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/1826044
Title:
Packages unavailable in target release should be removed
Considering that this is a regression, with major impact (TTY login no
longer possible, often no graphical login either), many affected users
on (amongst other) the latest LTS release, and both this fact and how to
fix it has been known since at least January 30, I am puzzled as to why
this is bein
101 - 200 of 319 matches
Mail list logo
