Per coincidence, I worked on this same bug today, as I'm hoping to try
make use of the amdpro legacy OpenCL drivers, which will need amdgpu as
a base.
The issue is Ubuntu is providing newer kernel HWE stacks with amdgpu
driver modules, but failing to keep related Linux firmware packages up
to
I see nothing wrong in these file systems. Only the first one has only
0.16% space left (which is 1.6GB), and probably not shrunkable. As you
were able to extract the metadata, all the file systems are proven to be
at least mountable read-only.
--
You received this bug notification because you
When started with option -i, ntfsresize only evaluates the minimal size
needed for the stored data. There may be a subsequent ntfsresize to
actually do some resizing, which might not be run when you kill the
parent process.
--
You received this bug notification because you are a member of Kernel
Please report what is hinting at ntfsresize and in what conditions it is
started (such as the file system state) ?
Also please start ntfsresize from command line.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1) what are the ntfsresize options ?
2) what are the file system metadata (given by "ntfsinfo -fm device-path"
before resizing)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1945011
Another correction. For the one workaround, switching to discrete
graphics in the BIOS only seemed to get past the initial gnome login.
But resuming from DPMS off/suspend, the same error loop happens even
when hybrid graphics is disabled in the BIOS.
Even worse, seems hardware acceleration ends
Here's the script I run to workaround the intital failure of gnome to
use the external display after unlocking or resuming from DPMS
suspend/off.
** Attachment added: "fix-hdmi-uhd.sh"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365719/+files/fix-hdmi-uhd.sh
--
Apologies, continuing the comment above (mistakenly posted when adding
the log attachment). Let me retry.
Failure loop observed:
- Failed to blit shared framebuffer: EGL failed to allocate resources for the
requested operation.
- Failed to set CRTC mode 3840x2160: No such file or directory
To
Hi, thanks to everyone, especially Daniel for unpacking this issue.
I have had a very similar issue, where gnome shell fails to run my
external 4K/UHD display at 60HZ and I see the following failure loop
triggered in `journalctl -b -p warning _COMM=gnome-shell`:
May 02 20:39:38 JNBA434499PLL
Candidat : 1.173
Table de version :
*** 1.173 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://fr.archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status
Regards,
Jean Pierre.
To manage notifications
/firmware/linux-
firmware.git/commit/?id=fe4a9d49d44c40a7bc32cdd9529e6a5c8ac92519
Regards,
Jean-Pierre.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1772624
Title:
Broadcom BCM4356
/main i386 Packages
100 /var/lib/dpkg/status
Regards,
Jean Pierre.
** Affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https
Apologises, I think I'm conflating a resume from hibernate issue vs a
resume from suspend issue, so the previous comment is probably not that
relevant.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
No sure if this will help, but there are plenty of debian bugs related
to this to check
If you are relying on the `resume=` kernel parameter with
/etc/default/grub, that might well be ignored. According to the message
below, there are various bugs in upstream debian (and I'm not sure if
Ubuntu
I too see this error for Seagate 'ST3500418AS' SATA drives via 88SE9123
PCIe SATA 6.0 Gb/s controller (Ubuntu 16.04.2, latest 4.8 Kernel)
```
exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0
irq_stat 0x4001
failed command: SET FEATURES
cmd ef/05:fe:00:00:00/00:00:00:00:00/40 tag 4
status: {
It's still happening to me on 16.04 (Xenial), fully up to date.
@madbiologist, thanks, good to know where the cause might be.
Still, having to rebuild a kernel with one commit reverted is a fairly
cumbersome work-around and painful given fairly frequent kernel
updates...
As far as I can see, no
Notable upstream bugs with related issues
alegidly patched: https://bugzilla.kernel.org/show_bug.cgi?id=115771
maybe not patched yet: https://bugzilla.kernel.org/show_bug.cgi?id=93521
Workaround (to help other who find this bug)
Add `intel_pstate=disable` to `GRUB_CMDLINE_LINUX_DEFAULT` in
Same, here, this message makes me fear that my system won't be able to
boot with the new kernel.
Setting up linux-signed-image-4.4.0-51-generic (4.4.0-51.72) ...
warning: file-aligned section .text extends beyond end of file
warning: checksum areas are greater than image size. Invalid section
Update on the previous comment, I realised the issue was the the
partition where /var was mounted to hat nosuid set. Seems /var/lib/lxc
must allow for the suid bit to be set. The problem is that people often
have /home mounted with nosuid as a normal security precaution, so this
effects running
It also affected me on Ubuntu 16.04 LTS with /var/lib/lxc mount via
bind.
My original setup only had 8GB for /var, so a bind to directory in /home
was the custom hack I did to give lxc more space.
$ grep lxc /etc/fstab
/home/var/lib/lxc /var/lib/lxc nonebind
*** This bug is a duplicate of bug 1273060 ***
https://bugs.launchpad.net/bugs/1273060
** This bug has been marked a duplicate of bug 1273060
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
--
You received this bug notification because you are a member of
To summarise, there are at least two other related bug reports (which should
add motivation given the wider impact of the issue):
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1082418
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1471380
--
You received this bug notification
*** This bug is a duplicate of bug 1273060 ***
https://bugs.launchpad.net/bugs/1273060
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
** This bug has been marked a duplicate of bug 1273060
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
--
*** This bug is a duplicate of bug 1082418 ***
https://bugs.launchpad.net/bugs/1082418
** This bug has been marked a duplicate of bug 1273060
[Fujitsu LIFEBOOK LH532 (UMA)] Ubuntu EFI install locks out firmware access
--
You received this bug notification because you are a member of
And this bug isn't isolated to just to Fujitsu. The same thing just
happened to me with a Dell.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1273060
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is high risk! It's effectively bricked a Dell Latitude E6540
:-(
My theory is that, somehow, the update caused a change to the firmware
NVRAM settings and boot entries for UEFI, and the Dell code can't handle
something unexpected. And after I've entered BIOS password, the firmware
code
@Chistopher, thanks, the problem is now that my A15 bios can't even
enter setup mode or boot anything, so I'm not sure how to try flash the
most recent A16 version from (released just a month ago)? Searched the
laptop's manual, and no indication of any jumpers to clear/reset NVRAM
:-(
I agree and
It works on Ubuntu 15.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1219560
Title:
Can't pair Logitech K810 using GUI
Status in bluez package in Ubuntu:
Confirmed
Bug
** Attachment added: Nvidia settings screenshot
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1406991/+attachment/4291211/+files/Capture%20d%27%C3%A9cran%20de%202015-01-02%2009%3A45%3A15.png
--
You received this bug notification because you are a member of Kernel
Packages,
The memory corruption was due to a hardware failure detected with memtest86.
Sorry.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
uname -a
Linux CX61-2PC-1298 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
sudo lshw -C display
*-display NON-RÉCLAMÉ
description: 3D controller
produit: GF117M [GeForce 610M/710M/820M / GT
I just :
1) Start Ubuntu.
2) Plug a first HDD on the first USB 3.0.
3) Plug a second HDD on the second USB 3.0.
4) Copy a bunch of files from one disk to the other.
5) Wait 10 seconds...
If you need other information or test, tell me.
** Attachment added: Screen shoot of the kernel panic with
Here is the explained stack of the kernel panic according to the source files
for 3.13.x
--
bio_endio (line unknown) :
http://lxr.free-electrons.com/source/fs/bio.c?v=3.13#L1712
Public bug reported:
I have a new MSI CX61 2PC 2198XFR that I installed today with Ubuntu
14.04 LTS that works fine with my old computer.
Some info for the new one :
Linux JPD-CX61-2PC 3.13.0-43-generic #72-Ubuntu SMP Mon Dec 8 19:35:06 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
When I plugged an
Hello,
I upgraded to the packages in the PPA mentioned in comment #27. I
removed mi Logitech K810 keyboard using the GUI, then restarted the
computer. I managed to pair my keyboard successfully typing the six
characters on-screen. In fact, the GUI showed progression as I typed the
characters by
I do not have the problem in message #4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1219560
Title:
Can't pair Logitech K810 using GUI
Status in “bluez” package in Ubuntu:
File captured while the GUI hung for about a minute, and then failed to
pair the keyboard.
** Attachment added: Hung for a minute, then failed to pair
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1219560/+attachment/3798345/+files/hci.log
--
You received this bug notification
Previous comment contained an attempt to pair that failed. The GUI did
not display a password to type on the keyboard, but the file registered
one, as evidenced in this line:
2013-09-01 21:54:09.899971 HCI Event: User Passkey Notification (0x3b) plen 10
bdaddr 00:1F:20:*:*:* passkey 662178
Public bug reported:
I cannot pair the Logitech K810 keyboard to my computer using the
graphical interface provided by Ubuntu. Whenever I try I get two
possibilities:
1. The GUI will show me a password, which I must type in the keyboard.
After typing the password and pressing ENTER, the pairing
39 matches
Mail list logo
