Public bug reported:
I'm suffering from a series of audio bugs so I'll try my best to
explain.
Out of the box, the output device in GNOME setting is listed as Kaby
Lake something or other. It works in 20.04 but the headset microphone
isn't detected.
In 18.04 the audio didn't work at all, which r
After having intermittent problems booting 4.13.0-32, 4.13.0-36, and
4.13.0-37 I uninstalled those kernels (which also uninstalled linux-
generic-hwe-16.04 and linux-image-generic-hwe-16.04) as well as intel-
microcode. I'm running the 4.4 kernel that comes with 16.04 now with
zero problems. It's n
I don't seem to have this issue on 18.04 either, so it seems to be
limited to 14.04.
$ ps aux | grep [p]olkit
root 1453 0.0 0.0 292924 8796 ?Ssl Oct12 0:01
/usr/lib/policykit-1/polkitd --no-debug
bmaupin 16637 0.0 0.1 323808 19996 ?Sl 08:10 0:00
/us
I saw there was a new BIOS available for my computer, and after
installing it my computer wouldn't boot again. Oddly enough it wouldn't
even boot after downgrading the BIOS back again. The last line in the
boot process was:
ACPI: EC: interrupt blocked
After doing some googling, I was able to get
For what it's worth, I don't seem to have had this issue after upgrading
to Ubuntu 16.04. I recently just upgraded to 18.04 so I'll continue to
keep an eye on things.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Public bug reported:
Sometimes when I first log in, certain items are duplicated in the
panel. For instance, I just logged in, and indicator multiload and
network manager applet are both duplicated in these panel items:
Indicator Plugin
Status Notifier Plugin
See attached screenshot (xubuntu-180
Interesting. I was under the impression it was part of the default
Xubuntu 18.04 installation because it appears to be included in the
default panel configuration if I'm interpreting this correctly:
$ bzgrep -a indicator "/usr/share/xfpanel-switch/layouts/Xubuntu Bionic.tar.bz2"
/plugins/plugin-6
Makes sense, thanks for the clarification!
** Changed in: xfce4-indicator-plugin (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/1801724
Title:
Application indi
In Xubuntu this may be fixable by removing the indicator-application
package:
sudo apt remove indicator-application
xfce4-panel -r
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761606
Title:
Two W
I haven't reformatted my machine in years and was running into some
other issues, so I just did a reinstall of 18.04. With both the install
media and the latest 18.04 kernel (4.15.something), I needed noapic.
So I installed kernel v4.20.4-042004, and it would not boot without
noapic either. Howeve
Here's the kernel log from v4.12.14
$ uname -a
Linux bryan-ThinkPad-T430u 4.12.14-041214-generic #201709200843 SMP Wed Sep 20
12:46:23 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
** Attachment added: "kernel log from v4.12.14"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+attachm
I tested a few kernels, and v4.12.14 is the last kernel that works
without noapic. Starting with v4.13-rc1 my computer will hang on boot
unless I use noapic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Here's the kernel log from v4.12.14 (with apic=debug)
$ uname -a
Linux bryan-ThinkPad-T430u 4.12.14-041214-generic #201709200843 SMP Wed Sep 20
12:46:23 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
** Attachment added: "kernel log from v4.12.14"
https://bugs.launchpad.net/ubuntu/+source/linux/+bu
I don't recall having this issue with 16.04 or 18.04. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389278
Title:
Cannot unlock screen after locking it manually in Xubuntu
To manage notifi
I'm still seeing this same behaviour for the 5.3 kernel.
I'm just now getting back to this, and I think I'm going to need some
hand holding...
> Try changing IRQ configs (CONFIG_GENERIC_IRQ_MIGRATION=y to =n) and
i2c-designware's (CONFIG_I2C_DESIGNWARE_CORE=y to =m).
I copied the 4.13.0 configur
Kristoffer, did you file your bug report yet? I think I'm experiencing
the exact same issue. After Grub, my system hangs with the 4.13.0-36
kernel. I just see a flashing cursor. 4.13.0-32 boots fine.
I'm using Ubuntu 16.04.3 on a Thinkpad T430u with an Intel i5-3317U.
--
You received this bug no
Public bug reported:
My system won't boot with the 4.13.0.36 kernel. Yesterday it hung at a
flashing cursor screen. I updated a few packages yesterday (see below)
and today it hangs at this screen:
Loading Linux 4.13.0.36-generic ...
Loading initial ramdisk ...
_
Booting to the previous kernel
Okay, I filed one:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1751584
I wonder if it's related to this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
** Summary changed:
- Ubuntu doesn't boot with 4.13.0-36 kernel
+ Ubuntu doesn't boot with 4.13.0-36/37 kernels
** Description changed:
+ Edit: the 4.13.0.37 kernel doesn't boot either.
+
My system won't boot with the 4.13.0.36 kernel. Yesterday it hung at a
flashing cursor screen. I update
The weirdest thing just happened yesterday. 4.13.0-37 wouldn't boot, so
I tried 4.13.0-32. The boot process got stuck at this line:
APCI: EC: interrupt blocked
So I tried 4.13.0-37 again and it worked...
I'm definitely confused now.
The only change I made was to do a verbose boot
(https://askub
...and here's my one-liner fix for Xubuntu 16.04 (Gtk 3):
sudo sed -i.bak -E 's/^(\s+-GtkScrollbar.+has.+stepper)/#&/'
/usr/share/themes/Greybird/gtk-3.0/gtk-widgets.css
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
This is *not* fixed for Xenial. I had originally applied the workaround
in the bug description to get my computer to boot again. After seeing a
"fixed" status for this bug, I updated intel-microcode. After I
rebooted, my computer would not boot to the kernel which had the
microcode applied (4.4.0-1
Public bug reported:
I'm experiencing the exact same symptoms as this bug:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920
However, that bug was marked as fixed.
The workaround as desribed in that bug works for me. As soon as I try to
update intel-microcode, my computer w
Since this bug was marked as fixed I'm not sure what the best way to
proceed is. I went ahead and filed a new bug:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1769335
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
In case it helps, I don't believe I've encountered this bug using Ubuntu
18.04. I only use LTS releases so I can't speak for any other versions.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
I just tried kernel v4.20-rc7 and without noapic my computer hangs at a
blank screen. With noapic it boots fine.
Thanks!
** Description changed:
I've used Ubuntu on this specific machine for years without problems,
but starting with the 4.13 kernel that came with the 17.10 HWE and
continui
I'm not sure if this helps, but I removed noapic and added
earlyprintk=efi,keep in an attempt to show some logs. I took a video and
extracted the frames. I've gone through them briefly but I don't see any
errors or warnings:
https://gist.githubusercont
I'm still using v4.20-rc7, and I wanted to try some more kernel
parameters to narrow down the problem. Since the last kernel messages I
got using earlyprintk
(https://gist.githubusercontent.com/bmaupin/b743bb3325e100341c62ee62e713d8a4/raw/7372dddb5704d3f15ff429807355d5d3686165d2/boot7.png)
I tried to boot with an older kernel (4.15.0-43), and it wouldn't boot
without noapic. But v4.20-rc7 seems to boot fine. I guess it must've
been a fluke that it didn't boot for me the first time.
Should I still try to figure out which RC kernel the problem started?
--
You received this bug notif
5.8.0-36-generic was just installed as part of the 20.04 HWE and it does
not boot without intremap=off.
What does that mean? Was this fixed in 5.7 and broken again in 5.8? Do I
need to do another rebase?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
I installed 5.7.0-5 from that link but it looks like the bcmwl module
still fails to compile:
Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.7.0-5-generic -C /lib/modules/5.7.0-5-generic/build
M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build(bad exit status: 2)
ERROR (dkms app
Oh cool. Is there a page I can check to see when that happens so I can
test it? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workarou
I booted 4.13.0-rc1, removing noapic and adding dis_ucode_ldr.
Unfortunately it still doesn't boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noa
After that I tried booting 5.3.0-7642-generic, removing noapic and
adding dis_ucode_ldr. And it booted just fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't bo
Oops, please disregard that last message. I'm multitasking :P
I booted 5.3.0-7642-generic, removing noapic and adding dis_ucode_ldr,
and it wouldn't boot (it froze at ACPI: EC: interrupt blocked)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I'm still tinkering...
I removed noapic and I tried instead with this, and it booted!:
intremap=off
Is this related by any chance to the link I posted in the original bug
report?: https://evilazrael.de/node/401
It's a different model ThinkPad but the symptoms are very similar.
--
You received
The article I linked was for an AMD CPU so it only helped me up to a
certain point.
I'm thinking I must've messed up the second bisect (the one for the
merge point) so I'm going to try to do the bisect again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm hopeful that doing the bisect over again will find a more relevant
commit. While bisecting this time I ran into a weird scenario the I
believe may have affected the previous attempts to do a bisect.
The short version of this is that when the computer has failed to boot a
kernel (without noapic
Due to the aforementioned issue, I believe I was getting a lot of false
negatives and my previous bisects were faulty as a result.
I redid the bisect from the beginning, and this is what I got:
# first bad commit: [c4e1be9ec1130fff4d691cdc0e0f9d666009f9ae] mm,
sparsemem: break out of loops early
Very odd... 5.7 boots (without noapic or intremap=off), but not
consistently.
It boots a number of times just fine (in my tests, anywhere from 3-5
successful boots) and then after that it will hang at boot. Most of the
time after powering off/powering back on it boots fine again, without
needing t
> Maybe the bcmwl-kernel-source package just isn't compatible with 5.7
yet?
I see now in the logs that's the case:
Building module:
cleaning build area...
make -j4 KERNELRELEASE=5.7.0-050700rc2-generic -C
/lib/modules/5.7.0-050700rc2-generic/build
M=/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build.
I just upgraded to 20.04 and I can confirm that this bug affects the
default 5.4 kernel that it ships with.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot wit
I tried booting another half dozen times or so with 5.7 on Ubuntu 20.04
and I didn't have any issues. So maybe it's fixed with that combination?
Unfortunately since the wifi doesn't work I can't continue to use the
5.7 kernel.
--
You received this bug notification because you are a member of Ubun
I finally got around to doing the bisect, and here's the result:
7bf1e44f865523aa16e0eb340a82d643da9215b5 is the first bad commit
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
I followed your instructions exactly as written. How can I use the
mainline release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808418
Title:
Thinkpad T430u won't boot without noapic workaround
This is the correct commit, right?:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7bf1e44f865523aa16e0eb340a82d643da9215b5
It looks to me like there are a lot more than just ARM changes there,
but I don't know anything about kernel development so I might not be .
I
This is what I'm getting:
63db7c815bc0997c29e484d2409684fdd9fcd93b is the first bad commit
But that feels wrong; it looks like it's a fix for XFS?:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=63db7c815bc0997c29e484d2409684fdd9fcd93b
... and I'm not using XFS:
> - First, try latest mainline kernel (v5.0) again, hopefully there's a fix
> already.
No, it looks like it still won't boot (without noapic).
> - Does the issue happen 100% of the time? Otherwise the bisection can be
> inconclusive.
Yes, it happens 100% of the time.
> - Or, take a look kernel
To downgrade openjfx to version 8 and put the packages on hold so they
don't get updated the next time you do a system update:
sudo apt install libopenjfx-java=8u161-b12-1ubuntu2
libopenjfx-jni=8u161-b12-1ubuntu2 openjfx=8u161-b12-1ubuntu2
sudo apt-mark hold libopenjfx-java libopenjfx-jni openjfx
Hmm so I removed indicator-application and now xfce4-indicator-plugin
shows "No indicators" which is pretty annoying...
So if I've uninstalled all indicator-* packages, should I also uninstall
xfce4-indicator-plugin?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Perfect, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801724
Title:
Application indicators sometimes duplicated in panel
To manage notifications about this bug go to:
https://bugs.launchp
...on second thought, I'm not sure updating it would be the best idea
since the end problem appears to be specific to my hardware. I think
it's probably better to mark this bug as invalid and create a new one.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this
After upgrading my BIOS the problem came back again with the 4.15
kernels. I was able to solve the issue by adding noapic to
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"
Once I did that, the kernels worked fine as did intel-microcode.
I'
Public bug reported:
I've used Ubuntu on this specific machine for years without problems,
but starting with the 4.13 kernel that came with the 17.10 HWE and
continuing into 18.04 kernels my computer would no longer boot, hanging
at various screens:
- A blank screen with a flashing cursor
- A scr
I went ahead and filed this new bug that's more specific to my hardware:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751584
Title:
Ubu
** Attachment added: "IMG_20180225_083323505.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+attachment/5222107/+files/IMG_20180225_083323505.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Attachment added: "IMG_20181028_141659821.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+attachment/5222108/+files/IMG_20181028_141659821.jpg
** Description changed:
I've used Ubuntu on this specific machine for years without problems,
but starting with the 4.13 ker
** Description changed:
I've used Ubuntu on this specific machine for years without problems,
but starting with the 4.13 kernel that came with the 17.10 HWE and
continuing into 18.04 kernels my computer would no longer boot, hanging
at various screens:
- A blank screen with a flashing
** Description changed:
I've used Ubuntu on this specific machine for years without problems,
but starting with the 4.13 kernel that came with the 17.10 HWE and
continuing into 18.04 kernels my computer would no longer boot, hanging
at various screens:
- A blank screen with a flashing
I'm assuming I should add apic=debug to a kernel that has the bug (and
not one that boots fine), correct?
Should I used apic=debug with or without noapic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
It looks like I was also suffering from this bug:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920
If anyone's having issues booting, I'd recommend downgrading intel-
microcode as described in the workaround for that bug.
In my case my machine still wouldn't boot with 4.13.
I added the PulseAudio Plugin to the panel and uninstalled
xfce4-volumed. But then I had 2 volume indicators. I had to hide the old
one manually:
gsettings set com.canonical.indicator.sound visible false
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Changed in: xubuntu-meta (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781733
Title:
Hardware volume keys don't work on upgrade to Xubuntu 18.04
To
Ah, I see. It looks like I still had indicator-sound installed.
I reset my panel to the default and it made some other changes in line
with the release notes, like adding the Status Notifier Plugin and
Notification Plugin. I guess I'll need to pay closer attention to the
release notes next time.
I hesitatingly upgraded to 18.04, and the 4.15 kernel that it comes with
booted just fine, so it seems like this issue is limited to the 4.13
kernels that come with 17.10/16.04 HWE.
This is what I have now:
$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
$ uname -a
Linux
I just upgraded to Ubuntu 18.04, and I'm still suffering from this bug.
After upgrading Ubuntu I upgraded to the latest intel-microcode:
$ tail -n 2 /var/log/apt/history.log
Upgrade: intel-microcode:amd64 (3.20180108.0+really20170707ubuntu16.04.1,
3.20180425.1~ubuntu0.18.04.1)
End-Date: 2018-07-1
Same here, on an installed Xubuntu 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761606
Title:
Two Wi-Fi network applets appear after logging back into live-usb
Lubuntu 18.04 session.
To m
Public bug reported:
I just upgraded to Xubuntu 18.04 from 16.04 and my hardware volume keys
(mute, volume up, volume down) weren't working at all. They worked just
fine on 16.04 and 14.04. I'm using a ThinkPad T430u.
Based on the suggestion here I installed xfce4-volumed and that fixed
the probl
For what it's worth, I recently upgraded to 18.04 and this no longer
seems to be an issue. I removed my ~/.xprofile and the compose key seems
to work with the /etc/default/keyboard setting alone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I tried 3.20180425.1~ubuntu0.18.04.1 but my computer wouldn't boot,
which is why I included this instead to indicate the version that didn't
work:
$ tail -n 2 /var/log/apt/history.log
Upgrade: intel-microcode:amd64 (3.20180108.0+really20170707ubuntu16.04.1,
3.20180425.1~ubuntu0.18.04.1)
End-Date:
I'm using Ubuntu 16.04 with Intel graphics.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751584
Title:
Ubuntu doesn't boot with 4.13.0-36 kernel
To manage notifications about this bug go to:
http
Public bug reported:
I first noticed this problem in Ubuntu 16.04. It didn't occur in 14.04.
I don't use non-LTS versions so I'm not exactly sure when it started.
Basically, the display keeps resetting to the default without me doing
anything. So I've customized it like so:
gsettings set de.mh21
** Attachment added: "indicator-multiload-reset-1.png"
https://bugs.launchpad.net/ubuntu/+source/indicator-multiload/+bug/1740751/+attachment/5029723/+files/indicator-multiload-reset-1.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "indicator-multiload-reset-2.png"
https://bugs.launchpad.net/ubuntu/+source/indicator-multiload/+bug/1740751/+attachment/5029724/+files/indicator-multiload-reset-2.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
al 01\ -\ Gregory\ Alan\ Isakov\ -\ Dandelion\ Wine.mp3
Analyzing file "01 - Gregory Alan Isakov - Dandelion Wine.mp3"...
WARNING: "/home/bmaupin/Desktop/Gregory Alan Isakov/This Empty Northern
Hemisphere/01 - Gregory Alan Isakov - Dandelion Wine.mp3": VBR detected, but no
VBR h
Is there any way I can request this bug to be closed? It's for a version
of Ubuntu that's no longer supported (10.10), and I didn't have this
problem in 10.04 LTS or 12.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Bug 945987 is related, which is why I mentioned it in this bug. But I
don't believe it's the same; it seems to me that 945987 is referring to
the inability to change encoding settings from the GUI. But it doesn't
deal specifically with the problem that VBR headers aren't added to MP3.
This problem
Jacob,
Since updating to the latest kernel, I haven't had one single lockup, so
it seems like that did the trick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197869
Title:
Thinkpad T430u randoml
** Attachment added: "/etc/default/keyboard"
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1612951/+attachment/4720184/+files/keyboard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Public bug reported:
I just upgraded Xubuntu 14.04 to 16.04, and I noticed my compose key
wasn't working in any application in X. I verified my compose key was
still set up in /etc/default/keyboard:
XKBOPTIONS="compose:ralt"
I googled around and ran these two commands:
sudo dpkg-reconfigure key
** Description changed:
I just upgraded Xubuntu 14.04 to 16.04, and I noticed my compose key
wasn't working in any application in X. I verified my compose key was
still set up in /etc/default/keyboard:
XKBOPTIONS="compose:ralt"
I googled around and ran these two commands:
sudo
** Summary changed:
- XKBOPTIONS ignored after upgrade to 16.04
+ /etc/default/keyboard ignored after upgrade to 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612951
Title:
/etc/default/keyb
Here's my one-liner fix for Xubuntu 14.04:
sudo sed -i.bak -E 's/(GtkScrollbar.+has.+stepper)/#&/'
/usr/share/themes/Greybird/gtk-2.0/gtkrc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/881472
Title:
I'm game.
1. $ head -n 1 /etc/default/keyboard
# Check /usr/share/doc/keyboard-configuration/README.Debian for
2. In /usr/share/doc/keyboard-configuration/README.Debian, I see this:
"While it will be safe to edit directly the configuration files
(/etc/default/keyboard and /etc/default/console-se
sudo apt-get -y remove empathy && sudo apt-get -y install pidgin
(Type it in the Terminal app)
:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/656900
Title:
Feature request: add "buddy pounce"
T
** Changed in: thunderbird
Importance: Medium => Unknown
** Changed in: thunderbird
Status: Invalid => Unknown
** Changed in: thunderbird
Remote watch: Mozilla Bugzilla #203810 => Mozilla Bugzilla #756984
--
You received this bug notification because you are a member of Ubuntu
Bugs,
For anyone using the remmina-next PPA, I also had to manually upgrade
the libfreerdp-plugins-standard package; for some reason the
dependencies weren't properly set and the drive sharing wasn't working
due to a missing library:
[10:00:37:014] [18886:2095822592] [ERROR][com.winpr.library] -
LoadLib
Public bug reported:
Periodically I install updates on my computer and reboot without logging
in. When I come back to my computer and log in, polkitd is using a large
chunk of memory. At the moment it's using > 2.3 GiB of memory on a
machine with 8 GB RAM:
$ ps aux | grep polkit
root 1229 0
A couple more data points:
Last week, I rebooted my machine and logged in right away. polkitd was
only using 7 MB of memory:
$ ps aux | grep polkitd | grep -v grep
root 1219 0.1 0.0 281164 7244 ?Sl 16:36 0:00
/usr/lib/policykit-1/polkitd --no-debug
Two days later, polkitd wa
As I mentioned in my last comment, yesterday I logged into my computer
after it had been up for 3 days at the login screen. Upon logging in,
polkitd was using nearly 1 GB of memory:
$ uptime
09:09:38 up 3 days, 15:57, 1 user, load average: 0.06, 0.05, 0.05
$ ps aux | grep polkitd | grep -v grep
r
The easiest way to fix this without installing extra packages (like
cheese), is:
1. Downgrade the parts of the enablement stack that caused the problem
sudo apt-get install --install-recommends xserver-xorg libgl1-mesa-glx
libegl1-mesa-drivers
2. (Optional) Clean up extra packages
sudo apt-get
Christopher, do you think there's any chance the upgraded BIOS from bug
1157909 would affect this issue? If so, I can use the default 12.04
kernel instead of the latest and test it out.
My thought is that if the 12.04 kernel triggers this bug, it'd be best
to fix it, especially since 12.04 is an L
Christopher,
There hasn't been any activity because nothing's changed. The bug's
still there.
I tried the version of Ubuntu you mentioned and didn't see the bug. I
was running it from a USB drive, however, because I didn't want to put a
development release of Ubuntu on my computer. So I'm not sur
Marking as Invalid since this bug is for a version of Ubuntu that's no
longer supported
** Changed in: metacity (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/818
** Summary changed:
- Thinkpad T430u randomly locks up/freezes
+ Thinkpad randomly locks up/freezes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197869
Title:
Thinkpad randomly locks up/freezes
** Summary changed:
- Thinkpad T430u reboots twice after suspend then shutdown
+ Thinkpad reboots twice after suspend then shutdown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157909
Title:
Thin
Marking bug as Invalid since Ubuntu 10.04 and 10.10 are no longer
supported.
** Changed in: compiz (Ubuntu)
Status: Expired => Invalid
** No longer affects: compiz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Marking as Incomplete since Ubuntu 10.10 and 11.04 are no longer
supported and no reports that it affects currently supported versions.
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Christopher,
I tried the version of Ubuntu you mentioned for a few hours and didn't
see the bug. I was running it from a USB drive, however, because I
didn't want to put a development release of Ubuntu on my computer. So
I'm not sure if that makes a difference in triggering the bug.
** Changed in
Ha, I can't believe I didn't even think to update my BIOS. At any rate,
that worked! I tried it on these kernels:
3.11.1-031101-generic
3.2.0-53-generic
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
1 - 100 of 140 matches
Mail list logo
