--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1037370
Title:
iwlagn or iwlcore oops, adaptor inactive on ACPI resume
To manage notifications about this bug go to:
Public bug reported:
This machine suspends/resumes several times a day, and uptimes measure
in weeks. This is the first or second time I've encountered this
symptom in months.
On resume, the WLAN LED didn't light up again. Looking at the kernel
log I see the stack trace below. After modprobe
FWIW, I have the exact same symptom with Lucid on a amd64 Thinkpad with:
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
Subsystem: Lenovo Device 20e4
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989134
Title:
aptitude/apt-get update error: BADSIG 40976EAF437D05B5
To manage notifications about this bug go to:
Public bug reported:
I've tried aptitude clean, removing /var/lib/apt/lists followed by mkdir
-p /var/lib/lists/partial and used the -o Acquire::http::No-Cache=True
-o Acquire::BrokenProxy=true options. There is no difference in that in
the end of an apt-get or aptitude update operation I get:
Some more information: This machine is not behind an apt-cacher-ng
proxy. Another Lucid x64 machine (a VM guest which incidentally runs on
the same host where the problem is occuring), also without any package
cache and with the same country-specific package server
(us.archive.ubuntu.com) is
...and, just tried aptitude clean followed by aptitude update once
again. Looks like something was sorted out server-side:
Get:1 http://archive.canonical.com lucid Release.gpg [198B]
Ign http://archive.canonical.com/ lucid/partner Translation-en_US
Get:2 http://archive.canonical.com lucid
Public bug reported:
This is a regression from Oneiric:
Steps:
- Pair Nokia BH-503 stereo BT headset to the laptop.
- Verify headset is connected: Headset LED slow-blinks blue, device appears as
connected under BT settings.
- Open sound settings.
- Sources listed: Digital SPDIF out, Analog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985116
Title:
A2DP headset does not appear in sound settings output list.
To manage notifications about this bug go to:
Done, see attachment. Symptoms are the same.
** Attachment added: verbose PulseAudio log
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/985116/+attachment/3091807/+files/pulseverbose.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
When logging into an Ubuntu (compiz/unity) session, I get heavy
flickering whenever new windows are created or when windows are moved on
screen. I also get a dark band that gradually appears under the top
panel and gradually obscures any content under it.
The attached video
** Attachment added: video showing flicker and dark band
https://bugs.launchpad.net/bugs/965557/+attachment/2942710/+files/VID_20120326_104435.mp4
** Description changed:
When logging into an Ubuntu (compiz/unity) session, I get heavy
flickering whenever new windows are created or when
I fixed this before seeing comment #2:
run-parts was returning an error code (2 IIRC) because I had removed,
but not purged, update-manager-core from these systems a few days ago.
That resulted in /etc/update-motd.d/91-release-upgrade being left
behind, which would attempt to run
Root cause is update-manager-core removal does not clear no-longer-
functional /etc/update-motd.d script, breaking MOTD. Requires purge.
** Package changed: pam (Ubuntu) = update-manager-core (Ubuntu)
** Summary changed:
- /var/run/motd is not created even though /var/run/motd.new is created
+
Public bug reported:
Starting a few days ago, all of my 10.04.4 servers ceased printing the
MOTD when I SSH'd into them. /etc/motd is a symlink to /var/run/motd
which doesn't exist. /var/run/motd.new is being created correctly on
each login, e.g.:
Linux hostname 2.6.32-39-generic-pae
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949256
Title:
/var/run/motd is not created even though /var/run/motd.new is created
To manage notifications about this bug go to:
Please disregard #23; I mis-traced the call hierarchy, plus the failure
is more subtle when the specified fix is applied to the Licid package.
I'll add the info in later comments once I have it all gathered.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
FWIW, the fix in:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/ecryptfs-
utils/oneiric/revision/70/src/utils/ecryptfs-mount-private#src/utils
/ecryptfs-mount-private
doesn't prevent ecryptfs_insert_wrapped_passphrase_into_keyring() from
inserting both fek and (a) fnek into the
18 matches
Mail list logo
