Laptop: HP Spectre x360 Convertible 14-ea0xxx
Graphics: Intel TigerLake-LP GT2 [Iris Xe Graphics]
Resolution: 3000x2000
Mostly uncustomized out-of-the-box Ubuntu, the one notable choice being
to use the gnome-xorg session type (declining to use the Ubuntu
customisations to gnome-session,
Sorry, I am opposed to Canonical forcing snap on Ubuntu users and do not
wish to spend my personal time on supporting that.
I'll just use a non-snap distribution mechanism instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I just upgraded to jammy, and the mouse cursor now becomes comically
huge whilst it's over a Firefox window.
I suspect this might be something to do with this being a HiDPI laptop.
I'm also fairly upset about the overcomplicated - and apparently broken - snaps
being
No, the mic-mute keyboard key does not work - neither with the old (-27)
or new (-28) kernel.
My mention of bug 1955691 is based upon having tested by rolling back to
the -27 kernel and seeing the mic-mute LED stay off, rolling forward to
the -28 kernel and seeing it illuminate at boot again,
I've reported a related regression in bug 1959970
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1955691
Title:
audio mute/ mic mute are not working on a HP machine
To manage notifications about
Public bug reported:
The bug 1955691 kernel update introduces undesirable behaviour on the HP
Spectre x360 - the mic-mute LED is now lit at system startup, even
though the microphone is NOT MUTED.
This is undesirable because it is giving the user incorrect information;
and also because the LED
I've just been bitten by this.
It seems this was broken by
https://sourceware.org/git/?p=glibc.git;a=commit;h=429029a73ec2dba7f808f69ec8b9e3d84e13e804
and it has recently been realised that was a bad idea:
(It took 30 seconds on the next boot)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
Title:
HP Spectre x360 14-ea0xxx Tiger Lake Keyboard does not work until
~30-60 seconds after boot
To
In the apport-collected CurrentDmesg.txt, the keyboard is detected at:
[ 11.664651] input: AT Translated Set 2 keyboard as
/devices/platform/i8042/serio0/input/input44
That's sooner than it usually takes!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468228/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468227/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468226/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468225/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468224/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468223/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468222/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468221/+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/1916314
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468220/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468219/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468218/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
Title:
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468217/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468216/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468215/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
Title:
HP
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468214/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468213/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
Title:
HP
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468212/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468211/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1916314/+attachment/5468210/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916314
Title:
HP
apport information
** Tags added: apport-collected groovy
** Description changed:
On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is
inoperable for ~30-60 seconds after system boot.
Kernel logging reveals that it did not detect the keyboard during this
time.
An
> Have you compiled kernel with that patch?
No, I haven't. The workaround of setting i8042.nopnp is satisfactory for
me, and the patch creator has done a thorough write up of the problem.
My objective in filing this bug is to raise awareness that the current
version of Ubuntu has this problem -
Public bug reported:
On the HP Spectre x360 14-ea0xxx (Tiger Lake), the keyboard is
inoperable for ~30-60 seconds after system boot.
Kernel logging reveals that it did not detect the keyboard during this
time.
An analysis of this and a patch can be found at:
I also have this exact model of laptop.
I have installed kernel 5.11 from https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.11/
Following a cold boot to Ubuntu, sound can be made to work via the
workaround GPIO commands detailed in
https://bugzilla.kernel.org/show_bug.cgi?id=210633#c13
The
** Also affects: 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/1765911
Title:
Major performance regression from Ubuntu 17.10 with i915
To
Similar/same issue observed on HP Spectre 13 (2017 model) which has
exactly the same Intel HD 520 graphics. Bad enough that I had to
reinstall 17.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Touchpad handling appears to have been refactored somewhat in bionic -
which led to the surprise of having my settings changed on upgrade
but even when I tracked down the new gsettings property of
org.gnome.desktop.peripherals.touchpad click-method, it fails to behave
as
It is expected that the -22.ucode file is missing because it was
deliberately removed per https://lists.ubuntu.com/archives/kernel-
team/2017-July/085667.html
The -27.ucode file was added in linux-firmware 1.165 and updated in
1.168
None of the other versions were ever released by Intel
Adding linux-firmware as an affected package - on further investigation,
it turns out that the real problem here appears to be firmware
incompatibility between the Wifi and Bluetooth parts of the 8260
package.
Relevant bug in Kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=197807
** Also affects: linux-firmware (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/1719210
Title:
Bluetooth audio to A2DP headset no longer works
The exact manifestation of this seems to have changed (now the gnome
settings UI claims that my hardware doesn't have bluetooth support at
all - despite CLI bluetoothctl still being aware of it) but the basic
issue still very much remains: 4.13 from artful => bluetooth inoperable;
4.10 from zesty
It is not possible to test the latest upstream kernel. It appears to
introduce further problems apparently related to apparmor which prevent
dhclient running, preventing a wifi connection from being successful at
all, as well as apparently causing display flickering, which is barely
perceptible at
Unfortunately as the issue is intermittent, it is difficult to pinpoint
a starting version exactly, but here's my best attempt:
Ubuntu zesty 4.10 series: definitely not affected
Ubuntu artful 4.12 kernels: problem not observed, though other iwlwifi
issues (bug 1719210) observed - probably not
Public bug reported:
Recently I have been experiencing intermitted total packet loss over
wifi.
I've already been looking at another issue in which Bluetooth
coexistence seems to be causing controller hardware to crash - bug
1719210 - so I'm rather suspicious of the updated iwlwifi microcode
I also seem to now be having Bluetooth-unrelated issues with iwlwifi,
filed in bug 1722109
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719210
Title:
Bluetooth audio to A2DP headset no longer
Confirming this is very much *not* fixed - the last linux-firmware
upload doesn't seem to have touched anything iwlwifi-related at all:
https://launchpadlibrarian.net/339888041/linux-
firmware_1.168_1.169.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs,
OK, I think I finally found the real trigger, helped by John Tanner's
comment and Googling the bt_coex_active option. It's trying to
simultaneously use bluetooth and a *2.4GHz* wifi network.
Trying that on my hardware results in lots of iwlwifi kernel logging
reporting that the device microcode
Or so I thought :-(I got set up for bisecting again, and now I can't
reproduce the problem at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719210
Title:
Bluetooth audio to A2DP headset
Hmm... empirically, I seem to have discovered a factor related to why
this sometimes works and sometimes does not with 4.13 - for me, the bug
only occurs if my laptop is booted *without* AC power applied.
Which makes no sense. But seems to be happening anyway.
--
You received this bug
I am seriously confused.
As requested, I tested out a 4.14-rc - actually, I tested -rc2 since
that had come out - and the problem was present - audio playback would
freeze after around 40-50 seconds.
Then I went back to various 4.13 versions and attempted to get the start
of a bisection going -
Mainline ppa 4.12.14 is working OK
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1719210
Title:
Bluetooth audio to A2DP headset no longer works following upgrade from
4.12 to 4.13 in artful
To
Lack of functionality also a problem in mainline-ppa 4.13.3 version. The
following messages are logged to the journal:
Sep 24 21:44:05 spectre bluetoothd[826]: Unable to get Headset Voice gateway
SDP record: Connection timed out
Sep 24 21:44:46 spectre bluetoothd[826]: connect error: Connection
Public bug reported:
Using artful kernel 4.12.0-13.14, Bluetooth audio works great.
Upgrading to artful kernel 4.13.0-11.12, there are severe Bluetooth
audio issues which have manifested in a variety of weird ways:
1) Playback would stall after 10-20 seconds
2) Upon removing the device and
Still a problem in artful upgraded from zesty right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714301
Title:
systemd-networkd hangs my boot (wireless)
To manage notifications about this
Public bug reported:
Code in /lib/systemd/system/systemd-resolved.service seeks to populate
/etc/resolv.conf if it is empty:
ExecStartPre=-+/bin/sh -c '[ ! -s /etc/resolv.conf ] && ln -snf
../run/systemd/resolve/stub-resolv.conf'
However the code is just wrong, and writes a symlink to
Public bug reported:
In Zesty, inactive Terminator tabs now have a transparent background,
which makes the app look pretty broken.
It appears there's a default of full transparency configured in the CSS
in the code, which isn't being overridden for everything which actually
*needs* to not be
Additionally, if I hover over the gnome-terminal title bar to show the
menus, the application menu is titled "Unknown Application Name".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629138
Title:
Public bug reported:
On current yakkety:
* Open the dash
* Search for the Terminal application (gnome-terminal)
* Drag-drop it to the launcher
* Click the newly added application launcher
Observe that a gnome-terminal window opens, but rather than the
application launcher having a steady
Concerning this update... ibus-mozc seems to have stopped displaying its
suggestions window on upgrading to yakkety, which is a rather major
fault.
Upgrading to a local build of this version restores it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
maxb@altimeter:~$ ls -lA /usr/bin/sieveshell
lrwxrwxrwx 1 root root 13 Jul 25 13:19 /usr/bin/sieveshell -> ../sbin/cyrus
maxb@altimeter:~$ ls -lA /usr/sbin/sieveshell
ls: cannot access '/usr/sbin/sieveshell': No such file or directory
maxb@altimeter:~$ ls -lA
Acting on Cyril's suggestion above, I downloaded the Debian 8.0-2 source
package, rebuilt it locally, and installed it. It seems to have fixed
the problem for me. So perhaps the problem really is in the Ubuntu
delta?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
"SRU: backport python 2.7.12 to 16.04 LTS" (bug 1591895) has caused a
regression in (at least) python-cassandra. Any attempt to connect to a
cluster fails due to:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/cassandra/cluster.py", line 1894, in
I'm not sure if this helps, but I see pulseaudio logging an "Operation
Not Authorized" message when things do not work:
Apr 26 01:46:52 zenbook pulseaudio[3346]: [pulseaudio] module-bluez5-device.c:
Acquiring transport /org/bluez/hci0/dev_20_74_CF_02_DB_F2/fd0
Apr 26 01:46:52 zenbook
This is fairly serious, as python-googleapi in Xenial is unusable as a
result.
Since updating Xenial to an new upstream version is unlikely to be
approved post-release, please see this upstream Git commit for the one-
line fix to this problem:
https://github.com/google/google-api-python-
** Summary changed:
- Totem goes to background when full-screen and out of focus
+ Totem/VLC etc. goes to background when full-screen and out of focus
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see this with VLC too, so it's probably with any fullscreen app.
However, at least on 15.04, ticking the 'Always on top' option via the
right-click titlebar menu of the video window is an effective
workaround.
This seems to suggest it ought to be easy to fix? It's clear Unity can
draw things
Public bug reported:
Since upgrading from trusty to vivid, it appears that smartd has started
sending 'SMART error (FailedOpenDevice) detected' alert emails each time
a USB external hard drive is attached and then removed (subject to it
being attached long enough to be caught by smartd's polling
Public bug reported:
Since upgrading from trusty to vivid, it appears that smartd has started
sending 'SMART error (FailedOpenDevice) detected' alert emails each time
a USB external hard drive is attached and then removed (subject to it
being attached long enough to be caught by smartd's polling
Public bug reported:
The command 'pip3 list' is broken on vivid:
maxb@altimeter:~$ pip3 list
[snip]
Exception:
Traceback (most recent call last):
File /usr/lib/python3/dist-packages/pip/basecommand.py, line 122, in main
status = self.run(options, args)
File
No, I have no Thunderbolt hardware in this computer, nor will any ever
be installed.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17.4-vivid/ has so far
been successfully running for an uptime of 2 days. So far so good,
though I didn't always experience a crash within this time on the utopic
I've just looked back through my /var/log/kern.log and I've noticed
something strange - I can't tell for certain which reboots are due to a
system lockup (since /var/log/syslog has rotated away too much, so I
can't look for rsyslogd shutting down to identify a clean reboot), but
it looks very much
Dell's release notes for this BIOS update state We do not recommend you
to upgrade to A10 BIOS if your system doesn't support Thunderbolt
hardware.
I decline to install a BIOS update that the manufacture recommends
against.
--
You received this bug notification because you are a member of
Public bug reported:
Since upgrading to utopic, I've been experiencing occasional system
lockups - when this occurs, nothing at all is responsive including the
mouse pointer and Alt-SysRq combinations.
Lockups only occur infrequently - perhaps once every day or two days -
so testing this is
Public bug reported:
My trusty-utopic upgrade failed due to:
Removing syslinux-themes-debian (12-3) ...
/var/lib/dpkg/info/syslinux-themes-debian.postrm: 15:
/var/lib/dpkg/info/syslinux-themes-debian.postrm: extlinux-update: not found
dpkg: error processing package syslinux-themes-debian
This appears to be a coding error. If you look at the file and line
referenced, you see the local variable 'e' being referenced, but it is
not in scope there.
It looks like the code is expecting the captured exception variable from
a previously exited 'except' block to still be in scope after the
Further note on reproducability:
The bug is only directly visible if the previous loop attempting
multiple retries to update the APT cache fails on all attempts.
One way to make this happen is to have a third party PPA in sources.list
which doesn't have anything published for utopic, and have
ooshlablu is correct. You cannot preseed network settings in a preseed
file which the installer is loading from a network location, because the
network needs to be configured before the preseed can be fetched.
The solution here is to pass the appropriate options on the kernel
command line.
You
Public bug reported:
Scenario: d-i EFI netboot with oem-config/enable=true
Problem: After the install completes and reboots into the OEM
configuration temporary user, there is no icon on the desktop to invoke
oem-config-prepare - indeed, oem-config is not even installed.
Cause: oem-config-udeb
Public bug reported:
Program appears to not support ID3 format version 2.4 - it reports no
tags present when run on such a file
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: id3v2 0.1.12-2.1
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
Uname: Linux 3.13.0-20-generic x86_64
** Branch linked: lp:~j/bash-completion/bug1289597
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1289597
Title:
bash: words: bad array subscript
To manage notifications about this bug go to:
Public bug reported:
On trusty, with bash-completion installed, I can't tab-complete paths to
files beginning with ~/
Only directories are offered as completion candidates.
This completion works correctly when the bash-completion package is
purged, reverting to basic built-in completion.
Public bug reported:
Open several terminator windows by repeatedly pressing Ctrl+Shift+I
For me, they open at a seemingly random variety of different sizes,
e.g.:
79x21
78x20
76x18
77x19
76x18
The size should be:
1) Constant
2) Based on a standard 80 character width
ProblemType: Bug
Public bug reported:
Recently, within trusty, evince has broken so that the zoom selector in
the top right of the window is inoperable.
Clicking its dropdown arrow does not cause any UI to open.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: evince 3.10.3-0ubuntu9
ProcVersionSignature:
I observe that the menu access keys are correctly disabled if
UBUNTU_MENUPROXY=0 is set in the environment, disabling the global menu
to revert to menu bar drawn within the gnome-terminal window.
Therefore, I've marked the bug as also affecting unity, as it seems
highly likely that at least some
Public bug reported:
I installed android-tools-adbd, and was surprised when totem stopped
working.
It turns out that libhybris installs its own implementation of the
alternative /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf at a higher
priority than the one from mesa, but the libhybris one is
I have just experienced the same manner of pointer corruption using the
upstream 3.10-rc5 kernel
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have spent some time trying to better quantify how often the problem
reproduces in daily use with the raring kernel, and ironically I only
experienced the problem a couple of times in a week now that I'm
actually trying to reproduce it.
I have now switched to the 3.10-rc5 mainline build, and
Public bug reported:
debian-keyring was promoted from a Suggests to a Recommends as a result
of a user report in bug 717245.
However, either behaviours of tools have changed since then, or there
was confusion between errors and warnings - if I use pull-debian-source
without having
Public bug reported:
Since upgrading from quantal to raring, I am experiencing corruption of
my mouse pointer around once per day.
I am using a dual-head setup on an ATI RV730 GL [FirePro V3750].
When corruption occurs, the mouse pointer is usually some garbled
rearrangement of the pointer's
Should the Ubuntu bugtask really be marked Fix Committed when it looks
like the fix has only landed into Unity upstream branches at present?
Also, when might this reach raring-proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi. Sorry for taking so long to get back on this one. I failed to see
the emails due to some mail rules filing things into folders too
aggressively, which I've now fixed.
I've bisected, and come up with a hopefully useful result: the
regression occurred between 3.8.2 and 3.8.3 !
--
You received
It would appear that 9f677cf27341b7a53915ad0e018912dc022a2a24 is almost
certainly the issue (based on examining the efi commits between 3.8.2
and 3.8.3). To quote its commit message:
efi: be more paranoid about available space when creating variables
commit
Public bug reported:
I am seeing a repeatable crash in gnome-disks when unplugging a SATA HD
whilst the SMART Data window for the HD in question is open.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gnome-disk-utility 3.6.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic
Public bug reported:
Hardware: Asus Zenbook Prime UX21A
Runing quantal, I can set boot parameters using efibootmgr as expected.
Running raring, any attempt to write EFI vars fails.
dmesg says:
[ 248.382221] efivars: set_variable() failed: status=8009
strace of efibootmgr says:
The bug also occurs with upstream 3.9-rc6 from the kernel-ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1167622
Title:
Cannot change EFI variables using efibootmgr (raring regression)
To
Public bug reported:
In quantal, the network-manager indicator progressed straight from
connecting (pulsing/rippling wifi symbol) to connected (static wifi
signal level indicator) when successfully connected.
In raring, it shows the disconnected (outlined empty lack of wifi
symbol) symbol for a
It should be noted that this isn't just a backend issue. There are a
couple of user visible weirdnesses as a result:
1) USB sticks mounted by usb-creator show up at /media/deviceuuid not
/media/user/deviceuuid like removable media generally does in raring
2) Attempting to unmount via the Unity
*** This bug is a duplicate of bug 689593 ***
https://bugs.launchpad.net/bugs/689593
** This bug has been marked a duplicate of bug 689593
2x100% CPU and memory usage growth when performing partition modifications
via udisks
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 689593 ***
https://bugs.launchpad.net/bugs/689593
** This bug has been marked a duplicate of bug 689593
2x100% CPU and memory usage growth when performing partition modifications
via udisks
--
You received this bug notification because you are a member
** Summary changed:
- 2x100% CPU and memory usage growth when setting bootable flag in palimpsest
+ 2x100% CPU and memory usage growth when performing partition modifications
via udisks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The other option for people on Quantal is to upgrade to Raring. There's
still no fglrx, but the open source radeon driver has improved a *lot*.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058040
Public bug reported:
The menu option to open the Totem Preferences UI appears to have gone
missing.
There's evidence in the source code that there's supposed to be a
preferences UI, and the online help states there should be an Edit
Preferences menu item, but it does not appear.
ProblemType:
1 - 100 of 969 matches
Mail list logo
