We discussed this on IRC.
Linux reports (DMI) this is an: ASUSTeK COMPUTER INC. TP202NAS/TP202NAS, BIOS
TP202NAS.209 07/19/2018
This systesm' only internal storage which is not detected here (other than the
error messages quoted above) is a SanDisk DF4064 eMMC.
I recommend testing also with an
** Changed in: linux (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/1818407
Title:
Cant access emmc, error -84
To manage notifications about this bug
Regarding Ubuntu 16.04's "xenial" GA kernel (4.4), I've been told that
the Kernel team ran into some issues with these and are now planning to
release them next week. As Brandon discussed, installing the 4.15
hardware enablement (HWE) kernel - as documented at
https://wiki.ubuntu.com/Kernel/LTSEnab
Will this also make it into Bionic, Xenial (and maybe Cosmic, too)?
--
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 kernel on a luks encrypted volume with Secure
** 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/1835095
Title:
Lubuntu initrd images leaking cryptographic secret when disk
encryption is u
ccooke: As another Ubuntu user, I think I can answer this:
Please check the top of this bug report, where you will see two affected
projects: "Subiquity" and "Subiquity (Ubuntu)". The former is the
'upstream project', or the 'original software', the latter its
integration into Ubuntu. While Subiqu
** Bug watch added: Calamares Issues #1191
https://github.com/calamares/calamares/issues/1191
** Also affects: calamares via
https://github.com/calamares/calamares/issues/1191
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ub
On 18.04, package cryptsetup provides /etc/cryptsetup-initramfs/conf-
hook which states:
# WARNING: If the initramfs image is to include private key material,
# you'll want to create it with a restrictive umask in order to keep
# non-privileged users at bay. For instance, set UMASK=0077 in
# /etc
This is not an issue in Ubuntu (which, for Firefox, follows Mozillas
rolling release model).
You're using https://launchpad.net/~jonathonf/+archive/ubuntu/firefox-esr which
states:
For questions and bugs with software in this PPA please contact Jonathon F
(https://launchpad.net/~jonathonf).
*
** Tags added: disco eoan rls-ee-incoming xenial
--
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 manag
This command was reported to successfully work around this bug:
sudo sed -i 's/^Automatically/# Automatically/g' /var/lib/dpkg/info
/base-files.postinst
It changes any lines starting with "Automatically" into comments, which
lets the script finish properly when you run:
sudo dpkg --configur
Hi.
I am just a fellow Ubuntu user, but I am afraid this bug report is most
likely not something anyone could solve, because so many different
chipsets and issues are being discussed here (I assume this is also why
no developers felt inclined to touch it so far).
I very much recommend that anyone
*** This bug is a duplicate of bug 1801629 ***
https://bugs.launchpad.net/bugs/1801629
** Description changed:
Expected outcome:
After installation, no packages should pend autoremoval (they should have
been apt --purge autoremove'd during the installation) and (if 'install updates
duri
** This bug is no longer a duplicate of bug 1801629
direct dependencies of ubiquity should not be autoremovable
--
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 minimal desktop
I agree this is a separate issue. I just did a fresh Kubuntu 19.04 amd64
UEFI installation (installer ISO downloaded on 2019-04-23) in
Virtualbox, selecting the 'minimal' (set of installed packages) option
and the 'install updates during installation' option set.
After installation, sudo apt updat
** Tags added: disco rls-ee-incoming
--
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 minimal desktop installation has packages pending autoremoval,
pending updates
To manage no
Public bug reported:
I started an Ubuntu 19.04 amd64 Desktop UEFI installation(running under
Virtualbox 6.0.8 on an Ubuntu 18.04.2 amd64 host) with default settings.
I chose automatic partitioning, confirmed this installation screen,
confirmed the popup prompt about writing changes to disk, then t
This package and its open security bugs have not been handled during the
past five years. Debian is no longer shipping it in release for the same
time (Ubuntu is, it is still in sid).
As a result, I recommend dropping this package off any future Ubuntu
releases as well as LTS releases.
** Informa
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802917 discusses how
the version Ubuntu offers to all currently supported Ubuntu releases
reintroduces the vulnerability described in CVE-2013-6890
** Bug watch added: Debian Bug tracker #802917
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
This issue seems to have occurred to me today (and several times
previously) - when I returned to my computer after a while (the screen
had entered power saving mode), the gnome-shell process (on XWayland)
failed.
Neither after logging in to gnome-shell / Xwayland nor after logging out
and back in
When I returned to my computer (AMD RX580 graphics, amdgpu) after a
while (the screen had entered power saving mode), the gnome-shell
process (on XWayland) failed.
Unfortunately this crash was not automatically reported by whoopsie /
apport and required manual re-submission (bug 1792643). If this
Thanks for explaning that it is possible to create a bug report on one
system, then manually copy it to another computer where the bug report
can then be submitted using ubuntu-bug.
This is not exactly as convenient as being able to run apport on one
system to gather debugging info, submit this to
Eric: This issue should only affect Ubuntu running bare metal on Intel
systems, so not Ubuntu running in a VM. Put differently: if you do not
run Ubuntu as the primary operating system on this MacBook Pro then
please file a separate bug report, or (ideally beforehand) see if you
can get this sorted
** Tags added: bionic
--
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
*** This bug is a duplicate of bug 1832801 ***
https://bugs.launchpad.net/bugs/1832801
** This bug has been marked a duplicate of bug 1832801
disco: curl error while loading shared libraries: libssl.so.1.0.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Public bug reported:
fstrim.timer always triggers at 00:00:
$ systemctl list-timers fstrim.timer
NEXT LEFTLAST PASSED
UNIT ACTIVATES
Mon 2019-06-24 00:00:00 CEST 3 days left Mon 2019-06-17 00:00:06 CEST 3 days
ago fstrim.ti
** Summary changed:
- High memory usage by Xorg.
+ High memory usage by Xorg with Kubuntu 18.04, plasma-desktop, nvidia 390
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833829
Title:
High memory
Reproduced as follows on 18.04.1 / Gnome-Shell:
apt-get install photoprint
click on (top left) "show applications" icon and search for "photoprint".
right-click icon, add to favorites.
click icon on panel to start the application.
a separate "broken" icon now shows on the panel for the running app
** Attachment added: "Video playing in Firefox full screen, showing hexchat on
the right, other application windows to the left"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1812394/+attachment/5230291/+files/gnome-shell-screenshot-S5TTVZ.png
--
You received this bug notification b
I'm seeing the same issue on Ubuntu 18.04 x86_64 (upgraded from 16.04),
with AMD RX580 graphics using amdgpu (with amdgpu.dc=1 set), running the
HWE kernel (4.18 ).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
$ lspci -knnv | grep -A10 VGA
2d:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev
e7) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon
RX 4
To clarify, I'm able to reproduce this both with Firefox playing back
the video in windowed mode and when Firefox plays the video back full
screen. As soon as I pause the video (in either mode), the artifact
vanishes, so it only occurs during video playback.
--
You received this bug notification
Setting this option in about:config and restarting Firefox fixes (or works
around?) it for me:
layers.acceleration.force-enabled = true
Source:
https://www.reddit.com/r/firefox/comments/a7epn7/transparent_video_player/
--
You received this bug notification because you are a member of Ubuntu
Bu
Public bug reported:
Bionic's 4.15.0-32-generic #35-Ubuntu (Fri Aug 10 17:58:07 UTC 2018)
fails while probing for efifb on this AMD Ryzen 1800x:
[0.786116] efifb: probing for efifb
[0.786118] efifb: cannot reserve video memory at 0xe000
[0.786120] [ cut here ]-
This issue started happening on 16.04.5 with HWE kernel:
Aug 15 05:51:09 hostname kernel: [0.00] Linux version
4.15.0-32-generic (buildd@lgw01-amd64-038) (gcc version 5.4.0 20160609
(Ubuntu 5.4.0-6ubuntu1~16.04.10)) #35~16.04.1-Ubuntu SMP Fri Aug 10
21:54:34 UTC 2018 (Ubuntu 4.15.0-32.35~1
Still present on 4.18:
$ dmesg | grep -FB3 -A50 ' cut here '
[0.776810] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[0.776847] efifb: probing for efifb
[0.776849] efifb: cannot reserve video memory at 0xe000
[0.776851] [ cut here ]
[
Please ignore the MWAIT comment, this is present ever since I set BIOS option
Advanced > AMD CBS > Zen Common Options > Power Supply Idle Control
to the necessary (for system stability on any Ryzen CPU) non-standard value of
'Typical current' (#1690085).
--
You received this bug notification b
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Confirmed
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Could "[PATCH V2 2/2] efi/fb: Convert PCI bus address to resource if
translated by the bridge" https://lkml.org/lkml/2018/5/18/729 be
related?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787260
Tit
Public bug reported:
On 18.04.1, the 'start network' option on the recovery menu prints this
error on screen
/lib/recovery-mode/recovery-menu: line 75: /etc/default/rcS: No such
file or directory
and gets stuck after
...
[ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill W
apport information
** Tags added: apport-collected bionic
** Description changed:
On 18.04.1, the 'start network' option on the recovery menu prints this
error on screen
/lib/recovery-mode/recovery-menu: line 75: /etc/default/rcS: No such
file or directory
and gets stuck after
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1787696/+attachment/5177010/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1787696/+attachment/5177011/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787696
What this very bug report is about is a little blurry since the focus
changed into different directions over time.
It is my understanding that
https://bugzilla.kernel.org/show_bug.cgi?id=196683 is a hardware
(design) bug, which is not going to be fixed (and could not be fixed or
properly mitigated
The microcode updates AMD had announced https://www.amd.com/en/corporate
/security-updates are going to be availble to AMD customers "by
downloading BIOS updates provided by PC and server manufacturers and
motherboard providers" are now actually available as separate microcode
packages which can be
I observe what is likely the same problem on XUbuntu 16.04.5, running
these commands in xfce4-terminal:
user1@mysystem:~$ lsb_release -ds;cat /proc/version;echo $SHELL;groups;groups
$(whoami)
Ubuntu 16.04.5 LTS
Linux version 4.15.0-29-generic (buildd@lcy01-amd64-024) (gcc version 5.4.0
20160609
TJ is right, I also confirmed this issue on a freshly installed 18.04.1
x86_64 Desktop VM last night. After enabling 'proposed' and installing
all pending updates, 'groups' in a terminal returned just the users
primary group. I then restored a snapshot taken right after the 18.04
installation (but
This also affects my XUbuntu 16.04.5 x86_64 system. When waking the
monitor from sleep, all I get is a blank screen. Switching between TTYs
does not help to restore the session or graphical output, only
restarting the desktop manager helps (but this means loosing the
session).
I have since install
'Artful' users made (and still make, when they somehow notice they are
EOL, such as when requesting support in #ubuntu, or because repositories
are archived) the same 'user experience'. It would be great if this
could be improved for when 14.04 hits EOL.
--
You received this bug notification beca
Definitely, but I do not see this happening anytime soon (do you?).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779443
Title:
esp partitions should be mounted with "discard" option where
applic
You can use the 18.04(.1) alternate server installer if you run into
this situation. Also, I think this situation has improved in the 18.04.1
'server-live' (subiquity) installer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Changed in: subiquity (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/bugs/1776115
Title:
18.04 Subiquity install crashes w/ "no such device" aganist /dev/sda2
This issue still affects 18.04.1. As soon as you try to install with an
unsupported wireless chipset, the chipset name is listed as a wireless
network to connect to (and attempting to connect to it obviously fails,
though without message).
What should instead happen is that a message is displayed
I looked into this a little more. Files on the ESP are not written on
every kernel image update. My current understanding is that they are
only written when grub-install is run.
So, yes, I think discard on ESP is not urgent at all, but still nice to
have.
--
You received this bug notification be
Can you discuss how using the discard option causes performance problems
when there are rare writes (<= once a week) to a partition?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779443
Title:
esp
A 16.04 system I'm looking at shows current modification times on all
files in /EFI/ubuntu/ files:
# ls -l /boot/efi/EFI/ubuntu/
total 3484
drwx-- 2 root root4096 Apr 30 2017 fw
-rwx-- 1 root root 67536 Jan 26 18:07 fwupx64.efi
-rwx-- 1 root root 152 Jul 10 10:40 grub.cfg
-r
*** This bug is a duplicate of bug 1727356 ***
https://bugs.launchpad.net/bugs/1727356
Just a note (mostly to self):
The OP and I discussed this issue today on #ubuntu between 5:30 am and 8:15 am
(UTC).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
This is not fixed. What we have is a reliable workaround to a bug which
apparently affects all Ubuntu 16.04 LTS users with the dbus-user-session
package installed.
Flatpak packages provided by the PPA at
https://launchpad.net/~alexlarsson/+archive/ubuntu/flatpak (and possibly
others) indirectly de
This is possibly a duplicate of bug #95925.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1264342
Title:
Please include ubuntu - DistroRelease spec. data
To manage notifications about this bug go
** Summary changed:
- No network connectivity after upgrade from 16.04 to 16.10
+ No network connectivity (NIC unmanaged) after upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676547
Title:
** Tags removed: patch
** Tags added: trusty
** Changed in: libvirt (Ubuntu)
Assignee: ali salama (alisalama) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667113
Title:
Syste
This is apparently a bug, more precisely a regression (#8) in either Ubuntu's
accountservice or lightdm.
This also affects trusty (as I have tested), so adding tag.
There is no patch, yet, removing tag (set in #21), renaming image in #21.
~alisalama has not handled this bug since April, I assume
I'm on Ubuntu 16.04.3 with mainline kernel
Linux version 4.13.2-041302-generic (kernel@tangerine) (gcc version
7.2.0 (Ubuntu 7.2.0-3ubuntu1)) #201709132057 SMP Thu Sep 14 00:59:32 UTC
2017
and mesa 1:17.3~git170914191100.7ffd4d2~x~padoka0 and X from the Padoka
PPA.
OpenGL renderer string: Radeon
The file I'm testing with has a "H264 - MPEG-4 AVC (part 10) (avc1)"
video track.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574354
Title:
playing .mp4 in VLC freezes machine
To manage notifica
The workaround discussed at http://blog.programster.org/ubuntu-16-04
-compile-custom-kernel-for-ryzen fixes the recurring (roughly once or
twice in 6 hours of operation, during low or idle CPU load periods)
system freezes for this Ryzen 7 1800X (early weeks), AMD microcode
0x8001129, ASRock X370 Ta
Link to correct upstream bug report
** Changed in: linux
Remote watch: Linux Kernel Bug Tracker #196481 => Linux Kernel Bug Tracker
#196683
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Tit
So, to sum up, we have several reports here that Ubuntu's default
kernels freeze on low load situations with Ryzen CPUs (or a subset of
Ryzen CPUs?) up to and including the latest mainline releases. This bug
differs from bugzilla.kernel.org #196481 (user space segfaults only on
high CPU load).
For
Matthew, did you ever get around to work on this?
These (post zesty archive removal / migration) days, no hour passes
without someone joining #ubuntu seeking help with 'broken repositories',
for example:
--- begin quote ---
this just started happening, seemingly without reason: E: The
reposi
Hi Mark, does your network offer IPv4 addressing, or just IPv6?
MegaGlest does not support IPv6 at this time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1639411
Title:
megaglest cannot host game
Thanks, Mark.
I did some testing but have been unable to reproduce the segmentation
fault as of yet. I did succeed in reproducing the part where no LAN IP
address is detected / shown by MegaGlest - using Ubuntu 16.10 x86_64 in
a Virtualbox VM with either the Ubuntu package or our own ("upstream")
Public bug reported:
As of now, it's not possible to install megaglest on 12.04 amd64 (beta1,
fully dist-upgraded as of today) because it depends on the package
megaglest-data in either the same or a higher version. Neither are
available in 12.04 so far.
Debian has a 3.6.0.3 megaglest-data packag
Yes, sounds like it's worth a merge.
I'm new to Ubuntu package management and may have misunderstood the
purpose of a sync request. My intention is to get MegaGlest 3.6.0.3
(which has now entered Debian Testing) into Precise before it's too
late. It is only a bugfix over the version which already
On 15.02.2012 23:03 Stefano Rivera wrote:
> A sync request is a request to take Debian's current package, exactly as
> it is.
Hmm, well, that's different to what I've learnt on IRC, thanks for
clarifying.
> If we need to carry over modifications that we have in Ubuntu, it becomes a
> merge reque
I just spent 3 days trying to understand why the one and only network
interface on a remote server where my only out of band access mechanism
is a netboot recovery system would not come up, and not log any error.
Whoever introduced this new mechanism should maybe have tested it.
Said system runs s
Public bug reported:
Please sync megaglest 3.6.0.3-1 (universe) from Debian testing (main)
Explanation of the Ubuntu delta and why it can be dropped:
* README.txt confirms that this is for x86 architectures only (as forced
by the x86 assembly in the FPU routines). Changed arch field to matc
mathieu-tl:
Thanks for your work on this issue.
Since you nominated it for trusty and state it's in progress - is there a way
to follow this progress?
Are there any test builds you would like to be tested, yet?
In case it's not been sufficiently stated before, this issue does affect
14.04 LTS
check also http://anonscm.debian.org/gitweb/?p=pkg-
multimedia/ois.git;a=commit;h=e538629d4d3709cbe8b2715dc5897eddb4e39070
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1154295
Title:
libois-dev pac
This affects me, too, not on lucid, but on saucy, and soon on trusty,
since apparently Ubuntu has chosen not to ship the /usr/include/OIS
symlink Debian has in today's sid and older releases, effectively
breaking many if not all software which depends on this library.
--
You received this bug not
actually uninstalling and reinstalling libois-dev on this trusty system
converts the earlier /usr/include/OIS *directory* to a symlink pointing
to /usr/include/ois, fixing this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
It's one thing not to provide current documentation. It means another
quality to provide documentation which claims to be up to date but is
actually outdated. On a distribution which not too long ago declared
server installations one of its key features and USP.
An up to date documentation which d
Oneiric is also affected. A SRU would be nice to have.
While it's not clear to me how to reliably reproduce this bug I'll be happy to
test a Oneiric fix if it becomes available before Precise does (and possibly
after).
--
You received this bug notification because you are a member of Ubuntu
Bu
"I/O error, dev sdb, sector 82830936 flags 0" would seem to suggest this
is a hardware error (physically defective storage media sdb), have you
ruled this out, yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Changed in: linux-lts-utopic (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892890
Title:
The eggs were off and it hurts my belly.
To manage notifications
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: [ 241.729
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 bu
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 subscribed
*** 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 Ubuntu
Possible Workaround (untested):
This only applies if you have not rebooted / closed the LUKS volume. Follow
steps 7 to 9 of https://www.thegeekstuff.com/2016/03/cryptsetup-lukskey/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
There are (as of today) 9 unfixed 'medium' criticality CVEs affecting
bionic (many more on xenial, but none of higher severity) according to
https://people.canonical.com/~ubuntu-security/cve/pkg/phpmyadmin.html
Would it be better to remove this package from existing releases
altogether, if such ca
Please also test with the default 19.04 kernel (ideally the installer,
too), can you get graphical output there using amdgpu.dc=0 ?
While running from the installed system, if possible using the default (after
updates) kernel image, with amdgpu.dc=0 set, please run:
apport collect-logs 1837945
Apologies, the correct command is:
apport-collect 1837945
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837945
Title:
AMD RX 570 Black Screen at boot
To manage notifications about this bug go t
The "[drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel
modesetting." was also reported in bug 1837945 where kernel / boot
parameter "amdgpu.dc=0" worked around an otherwise boot to black screen.
There, however, Linux versions 5.1 and 5.2 would also not work with this
parameter set.
Surena: After collecting logs, please continue and report this upstream where
other amdgpu bugs have already been reported:
https://bugs.freedesktop.org/buglist.cgi?product=DRI&component=DRM%2FAMDgpu&list_id=676975&resolution=---
You can file a new bug at https://bugs.freedesktop.org/enter_bug.cg
** Changed in: xserver-xorg-video-amdgpu (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/1837945
Title:
AMD RX 570 Black Screen at boot
To manage notif
Thanks for your feedback. Please post a link here to the upstream bug
report once you filed it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837945
Title:
AMD RX 570 Black Screen at boot
To manag
>From CurrentDmesg.txt:
Linux version 5.4.0-45-generic (buildd@lgw01-amd64-033) (gcc version 9.3.0
(Ubuntu 9.3.0-10ubuntu2)) #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 (Ubuntu
5.4.0-45.49-generic 5.4.55)
[0.00] DMI: Acer Nitro AN515-44/Stonic_RNS, BIOS V1.01 04/16/2020
[Firmware Bug]: AC
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059352
Title:
paramiko 2.12.0-2ubuntu4 fails autopkgtests on all architectures
To manage notifications about this bug go to:
http
I think it would be quite helpful if any of you could file separate bug
reports of testing a fresh 24.04 install of any flavour and could gather
the full kernel log from when the system booted to black screen, with
AMD graphics. That's because this can have many different causes, and we
do not know
Please reproduce the problem (boot to black screen). Then reboot in a way that
you can use the computer and run this without rebooting again:
sudo journalctl -k -b -1 > /tmp/kernel.log
Then attach /tmp/kernel.log to your bug report.
Thanks!
--
You received this bug notification because you ar
*** This bug is a security vulnerability ***
Public security bug reported:
On Ubuntu 22.04 with Wayland, once you activate, from the Settings
application, Sharing, and Remote Desktop Sharing, it is not possible to
permanently deactivate it on the GUI.
While it is still possible to deactivate it
201 - 300 of 319 matches
Mail list logo
