$ journalctl -g 'Linux version'
Apr 27 17:57:21 ub3jj kernel: Linux version 5.15.0-27-generic (buildd@ubuntu)
(gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
#28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 (Ubuntu 5.15.0-27.28-generic
5.15.30)
-- Boot
** Attachment added: "previous (successful) boot logs for comparison"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971095/+attachment/5585653/+files/journalctl_b_-1_g_mpt2sas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
mpt2sas card driver failed to start properly after normal poweroff + restart.
Logs attached.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-27-generic 5.15.0-27.28
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux
As a workaround for this use case may want to try
sudo systemctl stop NetworkManager.service
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898814
Title:
Under netplan with "renderer: networkd",
Added a patch at
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
** Description changed:
- Submitting a patch soon.
+
https://git.launchpad.net/~iheino+ub/ubuntu/+source/bash/commit/?h=bugfix/1960366
- Without fix:
- $ set|fgrep PS1|head -1
+ Expected:
+
+
** Patch added: "0001-Properly-escape-PS1-for-xterm-title.patch"
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1960366/+attachment/5559792/+files/0001-Properly-escape-PS1-for-xterm-title.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Submitting a patch soon.
Without fix:
$ set|fgrep PS1|head -1
PS1='\[\e]0;\u@\h:
\w\a\]${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$
'
With quotation fix applied:
$ set|fgrep PS1|head -1
** Description changed:
Regression to be analyzed further later.
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5)
- Most relevant part of boot logs:
+ Most relevant part of boot logs (more in attachment):
Turning off secondary and tertiary monitors for the duration of the
initial boot appears to work around this issue. Suspend-to-ram works
with all monitors powered (same hardware configuration as in #1926400).
** Attachment added: "journalctl -b -1 -k | egrep -v 'audit|dbus-daemon'"
Public bug reported:
Regression to be analyzed further later.
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] (rev c5)
Most relevant part of boot logs:
Nov 30 13:08:00 ub3ff kernel: microcode: microcode updated early to
Similar symptoms to https://gitlab.freedesktop.org/drm/amd/-/issues/1406
and repeats in some form most of the time when unlocking screen after
screen blanking.
After suspend somewhat more random behaviour (works more often than
after blanking).
** Bug watch added:
** Attachment added: "Possibly related to
https://gitlab.freedesktop.org/drm/amd/-/issues/1406;
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+attachment/5493225/+files/dmesg.20210429.log
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+attachment/5492985/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1926400/+attachment/5492984/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
HWE kernel appears to get more amdgpu MST related WARNINGs and Oopses than
non-HWE, mostly after resume from blanking or suspend.
Kernel logs for most recent one attached.
- $ journalctl -b -1 -k | egrep -v 'audit|dbus-daemon' > /tmp/oops20210428.txt
- $ fgrep RIP
Public bug reported:
HWE kernel appears to get more amdgpu MST related WARNINGs and Oopses than
non-HWE, mostly after resume from blanking or suspend.
Kernel logs for most recent one attached.
$ journalctl -b -1 -k | egrep -v 'audit|dbus-daemon' > /tmp/oops20210428.txt
$ fgrep RIP
Actually
https://git.launchpad.net/ubuntu/+source/apport/commit/apport/ui.py?h=ubuntu/quantal=5080c104ebb3a02c4f16a3f6646449db8c72b545
lists a fix (--hanging) for this being available since quantal.
** Tags removed: focal
** Changed in: apport (Ubuntu)
Status: Confirmed => Fix Released
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
Exact reproduction conditions of bug #1891636 and bug #1891745 unknown.
At least OOPS ID 6647d368-df04-11ea-af91-fa163ee63de6 uploaded to
errors.ubuntu.com now, marking these two as duplicates for now.
**
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
Exact reproduction conditions of bug #1891636 and bug #1891745 unknown.
At least OOPS ID 6647d368-df04-11ea-af91-fa163ee63de6 uploaded to
errors.ubuntu.com now, marking these two as duplicates for now.
**
Also https://errors.ubuntu.com/user/$(sudo cat /var/lib/whoopsie
/whoopsie-id) claims "No errors have been reported from this system",
which is consistent with no ".uploaded" files appearing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891636
Title:
After recent updates Xorg crashes whenever entering Display Settings
To manage notifications about
No longer reproducible by visiting display settings after bug #1891745
crash. Possibly a duplicate of bug #1861609.
** Description changed:
- AssertionMessage Xort: ../../../../../../include/privates.h:121:
+ AssertionMessage Xorg: ../../../../../../include/privates.h:121:
dixGetPrivateAddr:
** Description changed:
[Impact]
1. When trying to send a report manually, you can not
- 2. When next possibly unrelated crash of same process happens, .crash
gets overwritten even if .crash.upload exists (= upload not yet
completed?)
- 3. When trying to copy-paste the stacktrace as text,
** Description changed:
[Impact]
1. When trying to send a report manually, you can not
- 2. When trying to copy-paste the stacktrace as text, you can not
+ 2. When next possibly unrelated crash of same process happens, .crash
gets overwritten even if .crash.upload exists (= upload not yet
Public bug reported:
This instance happened after lockscreen, as such may be suspend-resume
related. On the other hand at least 0 and 10 parts on backtrace appear
similar to bug #1891636
While this appears to be a recent regression, DpkgLog.txt doesn't
contain xorg references. Could it be
Public bug reported:
AssertionMessage Xort: ../../../../../../include/privates.h:121:
dixGetPrivateAddr: Assertion `key-initialized' failed.
Also affected by apport bug #1891634 making filling more information
here somewhat tedious.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
Public bug reported:
[Impact]
1. When trying to send a report manually, you can not
2. When trying to copy-paste the stacktrace as text, you can not
[Test Case]
Start Ubuntu
Open terminal
$ ubuntu-bug /var/crash/.crash does not appear to send anything to
errors.ubuntu.com, when NetworkManager
No such feature seen yet on Focal version of ubuntu-bug either.
** Tags added: focal
** Changed in: apport (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Not reproducible on fresh install on same hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871916
Title:
Navi gpu falls back to vesa/radeon/fbdev/etc drivers instead of amdgpu
To manage
** Patch added: "this patch let me dpkg --configure --pending successfully"
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1872020/+attachment/5351085/+files/grubpostinst.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
(auto)upgrade failed, not analyzed further for now.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: shim-signed 1.40+15+1533136590.3beb971-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
Public bug reported:
Installed (upgraded 16->18->20 beta) ubuntu appears to utilize incorrect
x.org drivers for RX 5500 XT. Those drivers appear to be missing
features like multi-monitor support. On the other hand live-usb of 20.04
beta did manage to utilize all 3 connected monitors (before
*** This bug is a duplicate of bug 1486316 ***
https://bugs.launchpad.net/bugs/1486316
** This bug has been marked a duplicate of bug 1486316
lpc_ich: Resource conflict(s) found affecting gpio_ich
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** 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/1486316
Title:
lpc_ich: Resource conflict(s) found affecting gpio_ich
To manage notifications about this bug go to:
@#9, Supposedly rasdaemon could handle MCEs on bionic+. Have not yet
witnessed it working though, even on hardware that had dozen
reports/year shown with mcelog.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1. appears to depend on snapshot, given cloud images handle the LUNs fine as
additional disks
2. debug symbols part may need more effort than I can spend on this
Also appears to require the following PEBCAK configuration snippet, but
that alone was not enough to reproduce the crash with stock
** Attachment added: "i440fx vm definition (same result with q35 too)"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1773004/+attachment/5143449/+files/ovmf_v02c.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Attempting to boot old 14.04 LTS snapshot in a VM with LUN passthrough
results in segfaults.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: qemu-system-x86 1:2.11+dfsg-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic
As this bug most likely won't ever get fixed (since Unity7 development
was scrapped), it might be useful to document the known workarounds
here, starting with:
1: Start any window manager with working shade support, for example as follows:
$ nohup openbox --replace >/dev/null &
# Warning: If you
Semi-worksforme @ OTA-15, as in symptoms disappeared for now.
But we shall see whether actual bug(s) were addressed as well after
after 10 weeks assuming no OTA-16 before that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirming identical symptoms (symantec sites) to the ones mentioned in
chromium issue linked above. Please consider removing misleading "self-
signed" -part from bug title.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reproduced the issue(*) with Xenial / 1.2.21-2ubuntu4.
Following Zycorax's line of thinking(**), binary-patched virt-aa-helper to get
rid of the error.
$ perl -pi -e s/ovmf/OVMF/ virt-aa-helper
*: selecting UEFI when creating vm with virt-manager fails to create vm and
giving the apparmor
Reproduced on trusty (using just the test124 part of reproduction
instructions above):
Aug 22 13:08:23 gx1 sshd[11844]: pam_unix(sshd:session): session opened for
user test124 by (uid=0)
Aug 22 13:08:23 gx1 systemd-logind[1275]: New session 4 of user test124.
Aug 22 13:09:22 gx1 passwd[11988]:
Removed reference to one client of mine who happens to prefer security
by obscurity over crystal box approaches. Clarified description a little
bit as well and changed report to public. Test cases available on
request, although shouldn't really be needed unless we want to
white/blacklist this
Is this just useragent-sniffing / them mis-identifying the browser as
chrome 35? Or did you get other errors besides them complaining about
browser version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Kernel logs from unattended-upgrades doing mkinitrd resemble Bug
#1253155 symptoms.
Mar 12 06:31:51 network kernel: [213747.796032] Request for unknown module key
'Magrathea: Glacier signing key: c7613364bc2aa19d70bf0c6e59bf8acaff65c879' err
-11
Mar 12 06:31:51 network
Spotted this again on a fresh 14.04.1 LTS server (amd64) installation.
Applied workaround from
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1363519/comments/11
and added it as another post-inst thing to do on all my installations,
along with a verification (dpkg -V/debsums/tripwire/etc).
Public bug reported:
$ swift stat -- container 'åbject'
Traceback (most recent call last):
File /usr/bin/swift, line 1479, in module
globals()['st_%s' % args[0]](parser, argv[1:], thread_manager)
File /usr/bin/swift, line 671, in st_stat
command_helpers.stat_object(conn, options,
Public bug reported:
$ swift stat -- container 'åbject'
Traceback (most recent call last):
File /usr/bin/swift, line 1479, in module
globals()['st_%s' % args[0]](parser, argv[1:], thread_manager)
File /usr/bin/swift, line 671, in st_stat
command_helpers.stat_object(conn, options,
Fyi, crash reporter claimed two instances of running out of space being
DuplicateOf this bug.
In case of running out of inodes or disk space, crash reporter's If you
notice further problems, try restarting the computer. advice sounds
rather harmful. Maybe a topic for another bug report though.
For the record, first ever CE reported by mcelog below on the hardware I
have access to. No UCEs nor even repeating CEs seen. Have not tested
mce-inject and/or apei/einj.ko kernel module.
mcelog: failed to prefill DIMM database from DMI data
Hardware event. This is not a software error.
MCE 0
CPU
Another similar-looking crash file (3.3.8-1ubuntu6.2 as well) in case it
could be useful.
** Attachment added: _usr_lib_squid3_pinger.0.crash
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4306990/+files/_usr_lib_squid3_pinger.0.crash
--
You received this bug
Another similar-looking crash file (3.3.8-1ubuntu6.2 as well) in case it
could be useful.
** Attachment added: _usr_lib_squid3_pinger.0.crash
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1384943/+attachment/4306990/+files/_usr_lib_squid3_pinger.0.crash
--
You received this bug
** Tags added: amd64
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1346828
Title:
eth0 (e1000e): transmit queue 0 timed out
To manage notifications about this bug go to:
Same symptoms on amd64 (trusty lts installation) Testing mentioned
workaround. Vlans in use and vlan offload still on (by default).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1346828
Title:
** Branch linked: lp:~iheino+ub/+junk/nut-upsconf-docfix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1405822
Title:
Default ups.conf should have maxretry setting above examples
** Branch linked: lp:~iheino+ub/+junk/nut-upsconf-docfix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1405822
Title:
Default ups.conf should have maxretry setting above examples section.
To
Merged the changes into 0006-ups-conf-maxretry.patch as requested.
** Patch added:
http://bazaar.launchpad.net/~iheino+ub/+junk/nut-upsconf-docfix/diff/4/2;
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1405822/+attachment/4295435/+files/4_2.diff
** Changed in: nut (Ubuntu)
Merged the changes into 0006-ups-conf-maxretry.patch as requested.
** Patch added:
http://bazaar.launchpad.net/~iheino+ub/+junk/nut-upsconf-docfix/diff/4/2;
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1405822/+attachment/4295435/+files/4_2.diff
** Changed in: nut (Ubuntu)
Public bug reported:
Default/sample ups.conf has maxretry setting at end. Above that are
examples and an empty line.
Uncommenting any of the examples or merging with older configs are
likely to end up with a broken config file, since the parser will
interpret existing maxretries to be inside
Public bug reported:
Default/sample ups.conf has maxretry setting at end. Above that are
examples and an empty line.
Uncommenting any of the examples or merging with older configs are
likely to end up with a broken config file, since the parser will
interpret existing maxretries to be inside
Correction to above: Udevadm-trigger does seem to get fired. Symptoms
looked indentical but might be a different issue this time.
crw-rw-r-- 1 root nut 189, 258 Dec 26 02:00 /dev/bus/usb/003/003
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Reinstalled nut on 14.04.1 with identical changes in config files, got
same issue again.
udevadm trigger does not seem to get activated, not even by replugging ups.
(command used to start it right after install + editing config files: sudo
service nut-server restart)
Bus 003 Device 003: ID
Trusty issue seems to be different from original one, to actually get
the error message printed I had to use:
$ sudo -g nut -u nut upsdrvctl start
... which revealed an unrelated documentation bug in newer ups.conf.
Might file another bug for that unless one is already filed.
** Tags removed:
Correction to above: Udevadm-trigger does seem to get fired. Symptoms
looked indentical but might be a different issue this time.
crw-rw-r-- 1 root nut 189, 258 Dec 26 02:00 /dev/bus/usb/003/003
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Reinstalled nut on 14.04.1 with identical changes in config files, got
same issue again.
udevadm trigger does not seem to get activated, not even by replugging ups.
(command used to start it right after install + editing config files: sudo
service nut-server restart)
Bus 003 Device 003: ID
Trusty issue seems to be different from original one, to actually get
the error message printed I had to use:
$ sudo -g nut -u nut upsdrvctl start
... which revealed an unrelated documentation bug in newer ups.conf.
Might file another bug for that unless one is already filed.
** Tags removed:
FYI neel, current version in 14.04.1 LTS (1.5.4+bzr2294-0ubuntu1.1) does
not seem include a fix for this. A backport (or SRU?) would be nice to
have for this. Or a ReleaseNotes entry at least.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
FYI neel, current version in 14.04.1 LTS (1.5.4+bzr2294-0ubuntu1.1) does
not seem include a fix for this. A backport (or SRU?) would be nice to
have for this. Or a ReleaseNotes entry at least.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I currently don't have access to the hardware, as that system was
decommissioned/repurposed. May have access to it during xmas break. In
any case patrick's observations suggest that next step should be
https://wiki.ubuntu.com/Kernel/KernelBisection between 3.13.0.32-generic
and 3.13.0-34-generic
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002451
Title:
Slow reconfiguration during kernel installation or removal
To manage notifications about this bug go to:
Got matching issue because of /usr full on an old unattended precise setup that
was trying to upgrade firefox.
Almost-interesting part of dpkg log just in case:
Errors were encountered while processing:
/var/cache/apt/archives/firefox_32.0.3+build1-0ubuntu0.12.04.1_amd64.deb
Public bug reported:
Boot hangs if acpi is not entirely disabled on Acer Aspire V3-111P.
Bios 1.05, newer (undocumented) version 1.11 untested so far.
This hang does not occur on Ubuntu 12.04 LTS, but does on 14.04(.1) LTS, unless
using acpi=off.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
** Attachment added: dmidecode.txt
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360731/+attachment/4185639/+files/dmidecode.txt
** Description changed:
Boot hangs if acpi is not entirely disabled on Acer Aspire V3-111P.
- Bios 1.05, newer (undocumented) version 1.11 untested so
** Tags added: quantal raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088081
Title:
udev rules make it impossible to deactivate lvm volume group with
vgchange -an
To manage notifications
http://blog.le-vert.net/?p=24 reports ACPI 5.0 support as being 3.4 kernel
territory.
Got same message on P8B WS myself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1093541
Title:
ACPI Error:
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/890337
Title:
gvfs-gdu-volume-monitor high cpu usage during raid-resync
To manage notifications about this bug go to:
Retried after resync'ing to most recent live image.
When installer got to the
Executing 'grub-install /dev/vda' failed.
This is a fatal error.
Did not press ok this time, but ran the following:
ubuntu@ubuntu:~$ sudo chroot /target apt-get install mdadm
ubuntu@ubuntu:~$ sudo chroot /target
Reproduced during installation of raring as follows, is this same bug or
different?
1. boot to livecd (desktop)
2. a) $ sudo apt-get install mdadm # not certain whether this step was needed
on raring
2. b) $ sudo mdadm -C /dev/md_d2 -l 1 -n 1 -f -x 2 /dev/vd[abc]
3. run installer, tell it to
Public bug reported:
1. boot to livecd (desktop)
2. a) $ sudo apt-get install mdadm # not certain whether this part was needed
2. b) $ sudo mdadm -C /dev/md_d2 -l 1 -n 1 -f -x 2 /dev/vd[abc]
3. run installer, tell it to use entire md_d2 disk for lvm
Results in:
Executing 'grub-install /dev/vda'
** Description changed:
1. boot to livecd (desktop)
- 2. a) $ sudo apt-get install mdadm # not certain whether this part was needed
+ 2. a) $ sudo apt-get install mdadm
2. b) $ sudo mdadm -C /dev/md_d2 -l 1 -n 1 -f -x 2 /dev/vd[abc]
3. run installer, tell it to use entire md_d2 disk for lvm
Error message most likely was a result of mdadm missing from /target.
But UI shouldn't hang then.
$ sudo mount --bind /run/resolvconf/resolv.conf /target/etc/resolv.conf
$ sudo chroot /target apt-get install mdadm
$ sudo chroot /target grub-install /dev/md_d2
Installation finished. No error
Error message also present in Precise.
P.S. noticed the message only when attempting to find out whether bad
page offlining support exists for Ivy Bridge; inconclusive on that so
far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
libqtbamf1 0.2.4-0ubuntu1 fix works for me.
unity-2d-shell 5.12.0-0ubuntu1 has a Depends: ... libqtbamf1 (= 0.1)
though, as does unity-2d-panel; libunity-2d-private0 5.12.0-0ubuntu1 has
a slightly more recent dependancy [libqtbamf1 (= 0.2.1)], but shouldn't
that be updated to = 0.2.4 in whichever
Public bug reported:
Started mumble yesterday, first with pulseaudio but it didn't seem to
work for reason or another, so quit that instance (successfully) and
started another with pasuspender mumble . After using the program
chose quit from menu, but apparently it got in an infinite loop.
** Summary changed:
- infinite loop in mumble at/near exit (ran with pasuspender alsa since
through pulseaudio is too buggy to use)
+ infinite loop in mumble at/near exit (ran with pasuspender alsa)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
reason or another above may have been Bug #911783 since symptoms were
identical, using alsa helped earlier with sound quality issues; whether
it is needed to reproduce this issue is unknown for the time being.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Since pasuspender seems to handle manually sent SEGVs to mumble, there
does not seem to be a straightforward way to get apport-retrace of
this...
Backtrace: /usr/lib/libg15daemon_client.so.1(+0xd59) [0x7f292c3a3d59]
Backtrace: /lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0) [0x7f292aa4ccb0]
Public bug reported:
Wishlist: When ubuntu-bug is asked to send a bug on PID, it should check
whether the PID shows symptoms of being in an infinite loop and if so,
include stack trace of the process to the bug report or ask the user
whether he would like to include details needed for retracing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/986779
Title:
ubuntu-bug lacks an option for collection stack trace of running
process (infinite loop analysis)
To manage notifications about this
I have noticed similar issues with ALC892, please have a look at Bug
#975135. For me alsa-only (with pasuspender) seems to keep sound quality
ok, but that setup has issues mentioned at Bug #986774.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Attempted a reinstallation/cloning of precise as follows:
$ dpkg --get-selections | fgrep -c :i386
237
$ dpkg --get-selections selections.txt
$ sftp clonehost # ...
$ sudo dpkg --set-selections selections.txt
$ sudo apt-get -y update
$ sudo apt-get dselect-upgrade
Ended up with bunch of errors
Seems related to bug #932581
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980502
Title:
update-manager: E:Error, pkgProblemResolver::Resolve generated breaks
To manage notifications about this
Public bug reported:
Seen while attempting to upgrade couple weeks outdated installation of
Precise:
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
Please report this bug against the 'update-manager' package and include the
following error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980502
Title:
update-manager: E:Error, pkgProblemResolver::Resolve generated breaks
To manage notifications about this bug go to:
** Tags added: dist-upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980502
Title:
update-manager: E:Error, pkgProblemResolver::Resolve generated breaks
To manage notifications about this bug
The following packages have unmet dependencies:
gwibber : Depends: gwibber-service (= 3.4.0-0ubuntu2) but 3.4.0-0ubuntu3 is to
be installed
gwibber-service : Breaks: gwibber ( 3.4.0-0ubuntu3) but 3.4.0-0ubuntu2 is to
be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may
Public bug reported:
Some unusual sound usage patterns like seeking streaming media get the driver
into a distorted state, where high-frequency chirps are added to all sound
played.
Seen on natty precise (not tested on others), on natty modprobe-cycled the
driver to workaround the issue, on
** Tags added: natty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975135
Title:
[P8B WS, Realtek ALC892, Black Line Out, Rear] fails after a while
(distortions after seek of streaming media)
To
Public bug reported:
Seen every time when booting Ubuntu 3.2.0-21.34-generic 3.2.13:
[4.090752] asus_wmi: Initialization: 0x0
[4.090904] asus_wmi: BIOS WMI version: 0.9
[4.091026] asus_wmi: SFUN value: 0x0
[4.091131] ADDRCONF(NETDEV_UP): br3: link is not ready
[4.091390]
1 - 100 of 270 matches
Mail list logo
