I've talked to four people over the last two days that are affected by
this too. On the ubuntu-server mailing list Sean Darcy is also trying to
solve the issue.
https://lists.ubuntu.com/archives/ubuntu-
server/2009-February/002645.html
--
upgrade from 7.04 to 7.10 fails
https://bugs.launchpad.ne
** Tags added: kernel-oops resume
--
request_firmware() fails on resume from suspend
https://bugs.launchpad.net/bugs/331415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
** Tags added: resume
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Tags added: regression-potential
--
request_firmware() fails on resume from suspend
https://bugs.launchpad.net/bugs/331415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
Ooops :)
Maybe we could add documentation to the package to make creating routed
connections easier for end-users to avoid the need for vde?
--
Should it Build-Depends on libvdeplug2-dev?
https://bugs.launchpad.net/bugs/253230
You received this bug notification because you are a member of Ubuntu
Jeff, thanks for that update.
I'm focusing on the via-rhine issue as you know. I'm confused by your
report that via-rhine failed after resume on Hardy even though acpi-
support was unloading the module. That doesn't seem to make sense since
there should be no difference between boot-time loading
The hollow/blank on mouse-over is still occuring with metacity, multiple
X-screens, nvidia.
apt-cache policy notify-osd
notify-osd:
Installed: 0.9ubuntu2
Candidate: 0.9ubuntu2
--
Notification is blanked on mouse over in vmware
https://bugs.launchpad.net/bugs/336108
You received this bug noti
This also affects multiple X screens.
1. Notification always appears on screen 0.
2. When focus is on screen 1+, the notification 'flashes' briefly (1/10th
second) on screen 0.
3. When focus is on screen 0, the notification appears. If the focus is moved
to another screen the notification disapp
Public bug reported:
Binary package hint: notify-osd
The current package doesn't include a man-page.
apt-cache policy notify-osd
notify-osd:
Installed: 0.9ubuntu2
Candidate: 0.9ubuntu2
** Affects: notify-osd (Ubuntu)
Importance: Undecided
Status: New
--
No man-page
https://b
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it without more information.
Please include the following additional information, if you have not already
done so (pay attention to lspci's additional options), as required by the
Ubunt
There is also a change to mac80211 to fix a problem with ath9k that
might cause this since both ath5k and ath9k depend on mac80211:
git log Ubuntu-2.6.27-9.19..Ubuntu-2.6.27-11.27 --pretty=format:"%h %ci %s" |
egrep 'ath5k|mac80211'
1e2bc95 2008-11-20 18:35:12 -0700 ath5k: Fix reset sequence for
1 in particular
8875bb4 2008-11-20 18:35:12 -0700 ath5k: fix suspend-related oops on rmmod
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
--
Kernel 2.6.27-11 in 8.10 has no WiFi support
https://bugs.launchpad.net/bugs/327237
You received this bug notification becaus
s
1 S root 4623 1 4623 01 80 0 - 4083 fuse_d 928 0 01:37 ?
00:00:01 /sbin/mount.ntfs /dev/sda1 /media/WindowsRecovery -o rw
4 S root 7628 7371 7628 01 80 0 - 8953 unix_w 1436 0 02:11
pts/200:00:00 sudo killall mount.ntfs
0 S tj7771 7694
I've also experienced this. Since there doesn't appear to be bluez bug-
tracker I asked in the IRC Freenode #bluez channel and it was suggested
that the current git HEAD solved it. I built and installed it but,
although it now writes the trusts to /var/lib/bluetooth//trusts it doesn't seem that the
>From dmesg.log:
[ 13.812844] ath_hal: module license 'Proprietary' taints kernel.
[ 13.814201] ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112,
RF2413, RF5413)
[ 13.863078] wlan: 0.9.4
[ 13.876291] ath_pci: 0.9.4
[ 13.913152] ath_pci :02:00.0: PCI INT A -> GSI 17 (level,
jiribb is correct - not sure what I was doing saying Confirmed!
Although the debian kvm-79 package appears to have VDE enabled, kvm-83
has reverted to the kvm-72 status. I'll upload VDE-enabled versions into
my PPA.
** Changed in: kvm (Ubuntu)
Status: Fix Released => Confirmed
--
Should
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
--
Kernel 2.6.27-11 in 8.10 has no WiFi support
https://bugs.launchpad.net/bugs/327237
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
If you'd like to try it out the package is now in my PPA for Hardy,
Intrepid and Jaunty.
kvm (1:83+dfsg-0ubuntu2~tj~ppa2j) jaunty; urgency=low
* Add build-depends on libvdeplug2-dev which will cause qemu's configure
script to enable vde support (LP: #253230).
-- TJThu, 12 F
** Attachment added: "Jaunty debdiff"
http://launchpadlibrarian.net/22552201/kvm_83%2Bdfsg-0ubuntu2.debdiff
--
Should it Build-Depends on libvdeplug2-dev?
https://bugs.launchpad.net/bugs/253230
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
cryptsetup (2:1.0.6-7ubuntu3) jaunty; urgency=low
* debian/initramfs/cryptroot-hook: fix support for UUID and LABEL correlation
between fstab and crypttab (LP: #287879).
-- TJ Thu, 12 Feb 2009 16:45:00 +
** Attachment added: "Jaunty debdiff"
http://launchpadlib
Confirmed here on x86_64 with nvidia 180.29 and GeForce Go 7600.
I run dual-screen with separate X sessions. The primary (screen 0)
exhibits the horizontal pixel-offset/wraparound and sometimes corrupted
top 1 or 2 rows too (1280x800x24).
Adjusting the GPU Scaling momentarily seems to solve the o
Confirmed here too. Jaunty amd64 with nvidia 180.29. Switching to VTs
results in a black screen with no console.
uname -a
Linux hephaestion 2.6.28-7-generic #20-Ubuntu SMP Mon Feb 9 15:42:34 UTC 2009
x86_64 GNU/Linux
lspci -nn | grep nVidia
01:00.0 VGA compatible controller [0300]: nVidia Corpor
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
--
uvcvideo: camera IDs that should be added
https://bugs.launchpad.net/bugs/264948
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
--
ACPI: Abit IX38 QuadGT fails to boot without acpi=off
https://bugs.launchpad.net/bugs/264358
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
--
OOPS: "Unable to handle kernel NULL pointer dereference"
https://bugs.launchpad.net/bugs/258450
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: xulrunner-1.9 (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
--
wrong permissions on /tmp files makes it impossible to directly view with
external viewer
https://bugs.launchpad.net/bugs/254169
You received this bug notification because you are a member of Ubu
** Changed in: xulrunner-1.9 (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
Status: In Progress => Confirmed
--
firefox - the associated helper application does not exist
https://bugs.launchpad.net/bugs/239952
You received this bug notification because you are a mem
** Changed in: mythtv (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
--
Sound goes bad when changing channels
https://bugs.launchpad.net/bugs/210852
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
** Changed in: qemu (Ubuntu Jaunty)
Assignee: TJ (intuitivenipple) => (unassigned)
--
Could not open /proc/bus/usb/devices
https://bugs.launchpad.net/bugs/156085
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
** Changed in: kdemultimedia (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
--
kmid doesn't send note on/note off on Kubuntu Gutsy 64bits
https://bugs.launchpad.net/bugs/154892
You received this bug notification because you are a member of Kubuntu
Bugs, which is subsc
** Changed in: ubuntu
Assignee: TJ (intuitivenipple) => (unassigned)
--
Bus error when running Firefox or Epiphany
https://bugs.launchpad.net/bugs/133786
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Updated the debdiff to be based off 7ubuntu3:
cryptsetup (2:1.0.6-7ubuntu4) jaunty; urgency=low
* debian/initramfs/cryptroot-hook: fix support for UUID and LABEL correlation
between fstab and crypttab (LP: #287879).
-- TJ Thu, 12 Feb 2009 16:45:00 +
** Attachment removed: "J
Occurred here too. As it seems to be in-progress I won't file the apport
reports.
--
evolution-alarm-notify crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/328981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Copying is clear enough:
"I was copying an NTFS partition image using dd from an external USB
hard-drive to /dev/sda2 (after replacing the laptop's internal hard-
disk)."
E.g. dd if=/media/mobile120/vista.img of=/dev/sda2
The file being copied was 29GB.
I mentioned it simply because it might be
Thanks for the explanation, Szabolcs.
I can't remember the exact details now of course, but I do remember that
the 'dd' copy from USB to /dev/sda2 had finished when I spotted the CPU
monitor showing the I/O wait.
I hadn't spotted mount.ntfs in the process list previously, although
admittedly I'd
Just got caught out by this on Jaunty. Wasn't aware of the -R option
since the man page is, it seems, out fo date quite significantly.
--
apport generates crash files that are incomplete according to apport-retrace
https://bugs.launchpad.net/bugs/145358
You received this bug notification because
Notes:
We discussed this in #ubuntu-kernel on Friday (13th February 2009) and
it looks as if the problem is related to blacklisting the 'madwifi'
(ath_pci, ath_hal) driver (in the linux-restricted-modules package) to
stop it conflicting.
--
Kernel 2.6.27-11 in 8.10 has no WiFi support
https://bu
This still affects the Jaunty release.
mettle, I've modified your patch slightly (to avoid the need for awk)
and removed some of the indent (so that the debdiff only shows the lines
we've actually changed - not indents) and am attaching it here.
** Attachment added: "Jaunty debdiff"
http://la
Interesting. This is something I reported and posted a patch to mainline
for back in early 2006. I thought it was eventually sorted out.
--
dmraid & attempt to access beyond end of device
https://bugs.launchpad.net/bugs/329880
You received this bug notification because you are a member of Ubuntu
See my original bug #77734 report "Disk Read Errors during boot-time
caused by probe of invalid partitions"
--
dmraid & attempt to access beyond end of device
https://bugs.launchpad.net/bugs/329880
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
Status: Fix Released => Confirmed
--
Disk Read Errors during boot-time caused by probe of invalid partitions
https://bugs.launchpad.net/bugs/77734
You received this bug notification becau
Public bug reported:
Binary package hint: pbuilder
This is a by-product of the fix I created for bug #278213 "Does not
accept multiple --debbuildopts options" which resulted in "pbuilder
(0.181ubuntu6)".
The problem is that when using pdebuilder and passing --debbuildopts to
both 'sides' (host a
** Summary changed:
- pdebuild --debbuildopts inherited by target pbuild
+ pdebuild host --debbuildopts inherited by target pbuild
** Description changed:
Binary package hint: pbuilder
- This is a by-product of the fix I created for bug #278213 "Does not
- accept multiple --debbuildopts opt
** Attachment added: "Jaunty debdiff"
http://launchpadlibrarian.net/22050276/pbuilder_0.183ubuntu2.debdiff
--
pdebuild host --debbuildopts inherited by target pbuild
https://bugs.launchpad.net/bugs/326216
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
It would be helpful to backport this change to Intrepid and Hardy since
they have received automated backports of the recent Jaunty package.
** Attachment added: "Intrepid debdiff"
http://launchpadlibrarian.net/22050237/pbuilder_0.183ubuntu2.debdiff
** Attachment removed: "Intrepid debdiff"
** Bug watch added: Debian Bug tracker #514358
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514358
** Also affects: pbuilder (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514358
Importance: Unknown
Status: Unknown
--
pdebuild host --debbuildopts inherited by t
This was caused by a problem with kvm-72. I've just back-ported kvm-83
(and installed the kvm-source DKMS package to update the kernel modules)
and it boots correctly.
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
Status: In Progress => Inval
This is a symptom of bug #324987 "Kernel *loses* partitions at
partitioning stage; installer fails"
--
Ubiquity silently fails during file-system preparation
https://bugs.launchpad.net/bugs/324976
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Tested with Jaunty alpha-4 live-CD (amd64) in a kvm-83 virtual machine
with one 5368MB qcow2 disk image with empty partitions pre-defined using
fdisk -u /dev/nbd0.
I decided to check the partition table created by fdisk using cfdisk. It
reported problems. Unfortunately the exact message scrolled o
As per the resolution of bug #324987, this issue should be dealt with by
ensuring that ubiquity reports the partitioner failure to the user
rather than silently returning to the advanced partitioning page.
--
Ubiquity silently fails during file-system preparation
https://bugs.launchpad.net/bugs/3
relatime,errors=remount-ro 0 1
== /etc/crypttab: ==
c5321f6e-05c0-43a7-8757-03aa29c44b04
/dev/disk/by-uuid/ae87e7a1-b65b-4586-9e0a-bfc6d60cebc9
/home/tj/Media/theme-song.mp3 luks,keyscript=/usr/local/sbin/crypto-usb-key.sh
The patch required is:
diff -Nu a/usr/share/initramfs-tool
Confirmed: I've also back-ported Jaunty's kvm-83 for Intrepid, Hardy,
and Gutsy. They are available from my PPA. The only one I've not tested
is Gutsy since I'm in the midst of debugging various Jaunty installation
bugs.
** Changed in: kvm (Ubuntu)
Status: New => Fix Released
--
Should it
I've been seeing the same symptoms with the Jaunty alpha-4 amd64 live-CD
with iwl3945 and a hidden SSID. The encryption on the network is WPA2
TKIP+AES.
I've tried defining a new connection, and setting the details directly
via the "Connect to hidden network..." option.
When it fails the resultin
Here are instructions to reproduce the issue in a KVM/QEMU virtual
machine using a live-CD ISO image. They create a qcow2 image, mount it
using nbd, create the 'faulty' partition table using 'fdisk -u', and
then start the VM guest with the live-CD.
qemu-img create -f qcow2 ubuntu-jaunty-install-te
The proposed fix causes the dialog-box:
ERROR!!!
Error informing the kernel about modifications to partition /ev/sda5 --
Device or resource busy. This means Linux won't know about any changes
you made to /dev/sda5 until you reboot -- so you shouldn't mount it or
use it in any way before rebooting
My previous suggested patch would cause unwanted side effects when
device aliases/symlinks are used for non-crypt disks.
This patch should provide the desired result without causing a
regression:
diff -Nu cryptsetup-1.0.6/debian/initramfs/cryptroot-hook
/target/usr/share/initramfs-tools/hooks/cr
Ooops! The patch in comment #7 was premature. This is how it should be:
diff -Nu cryptsetup-1.0.6/debian/initramfs/cryptroot-hook
/target/usr/share/initramfs-tools/hooks/cryptroot
--- cryptsetup-1.0.6/debian/initramfs/cryptroot-hook2009-02-09
18:42:15.358063612 +
+++ /target/usr/share/in
Turns out it is a problem with Compiz.
Disabling Compiz and returning to Metacity clears the problem.
** Also affects: compiz (Ubuntu)
Importance: Undecided
Status: New
--
Out-of-bounds areas for multiple X screens with different dimensions
https://bugs.launchpad.net/bugs/331918
You r
Conversation with Compiz developers on #compiz-fusion-dev confirming
this is an issue with the latest release:
With the Ubuntu Jaunty (1:0.7.9+git20090211-0ubuntu4)
package, using two X screens of different dimensions, there is an out-of-bounds
(black) region on the 2nd screen where desktop and
The conversation moved on to a different but related issue, multiple
screen scenarios, and I thought it worth recording here for future
reference:
IntuitiveNipple: out of curiousity, is there any reason to use
multi-screen instead of multi-output?
smspillaz: I'm not sure... what's the differenc
Using the advice I tried using:
DISPLAY=:0.1 compiz --only-current-screen
which, because 'compiz' is a script, results in the final command:
/usr/bin/compiz.real --ignore-desktop-hints --loose-binding --replace
--only-current-screen core ccp
The result is that the screen is taken over but the s
** Attachment added: "Photograph #4 - Screen 0 losing decoration/keyboard input"
http://launchpadlibrarian.net/22933587/Photograph_%234.jpg
--
Out-of-bounds areas for multiple X screens with different dimensions
https://bugs.launchpad.net/bugs/331918
You received this bug notification because
Changed upstream bug-track reference to the MTRR bug.
** Changed in: linux
Bugwatch: Linux Kernel Bug Tracker #11714 => Linux Kernel Bug Tracker
#11541
Status: Invalid => Unknown
--
Kernel panic on boot if SMP (ASUS M3A-H/HDMI)
https://bugs.launchpad.net/bugs/292619
You received thi
Public bug reported:
prepare-compat-wireless.sh has a typing error in the usage of the
variable ${WT} - the leading $ is missing.
** Affects: linux-backports-modules-2.6.27 (Ubuntu)
Importance: Undecided
Status: New
--
prepare-compat-wireless.sh - incorrect shell variable
https://
** Attachment added: "Patch to correct missing $ variable prefix"
http://launchpadlibrarian.net/22949808/linux-backports-modules-2.6.27.patch
--
prepare-compat-wireless.sh - incorrect shell variable
https://bugs.launchpad.net/bugs/332576
You received this bug notification because you are a me
as delayed.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
Status: Triaged => In Progress
--
WARNING: at /build/buildd/linux-2.6.27/kernel/power/main.c:176
suspend_test_finish+0x74/0x80()
https://bugs.launchpad.net/bugs/286672
You received this bug notifica
Tormod: I'm not sure that it blocks SysRq but I think so. When I first
observed it I tried to sync the disks (Alt+SysRq+S) and then power off
(Alt+SysRq+O) and if I recall correctly it didn't respond.
--
request_firmware() fails on resume from suspend
https://bugs.launchpad.net/bugs/331415
You re
d.
If the logs confirm it I'll mark this as a duplicate of that bug.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => TJ (intuitivenipple)
--
kernel warning while suspending
https://bugs.launchpad.net/bugs/287453
You received this bug notification because you are a member of Ubu
I've put a test package in my PPA that may resolve this:
https://edge.launchpad.net/~intuitivenipple/+archive/ppa/
udev (138-2~tj~ppa1j) jaunty; urgency=low
* Revert "Revert "rules: add "watch" option to dm and md rules" to prevent
slow down due to inot
On Sat, 2009-02-21 at 17:44 +, zippidy_josh wrote:
> Attached a kern.log. I'm running:
> Linux redstone-desktop 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC
> 2009 i686 GNU/Linux
I don't *think* your issue is caused by firmware. The tell-tail is
kernel time-stamps that delay for 60 sec
I've been doing some bisect and other testing via git.
I also took the hardy package that works correctedly with the Hardy
installation - compiz (1:0.7.4-0ubuntu7) - and after making some minor
changes (build dependencies) to enable it to build, built and tested it
on Jaunty.
It suffers the same
The updated fix is now available in my PPA. Instead of reverting
selected patches I reset to the commit before the watch rules were added
and then cherry-picked the two non-watch-rules:
udev (138-2~tj~ppa2j) jaunty; urgency=low
* Revert "watch" option rules to prevent slow d
If you're still seeing this problem, please try reinstalling the
package:
sudo apt-get --reinstall install libc6
--
package libc6 2.8~20080505-0ubuntu8 failed to install/upgrade: package libc6 is
already installed and configured
https://bugs.launchpad.net/bugs/330348
You received this bug notif
** Changed in: grub (Ubuntu)
Sourcepackagename: linux => grub
Status: New => Fix Released
--
ext4 fail with kernel 2.6.28-8
https://bugs.launchpad.net/bugs/331163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
If you can get past the udev inotify storm there's a quick way to remove
the "watch" entries instead of reverting the package:
sudo -i
for rule in /lib/udev/rules.d/*; do sed -i 's/watch//g' $rule; done
/etc/init.d/udev restart
exit
I'm attaching a udev_log=debug captured via serial console at bo
** Attachment added: "Gzipped boot log with udev_log=debug"
http://launchpadlibrarian.net/22975815/boot-log-udev-debug.log.gz
--
[jaunty] doesn't boot anymore after udev upgrade
https://bugs.launchpad.net/bugs/332270
You received this bug notification because you are a member of Ubuntu
Bugs,
Attached is another udev_log=debug captured via serial console. Only
lvm2 installed, and one partition with a VG in it. No boot devices are
mounted from the LVM.
** Attachment added: "udev_log=debug via serial console"
http://launchpadlibrarian.net/22981279/boot-udev_log%3Ddebug.log.gz
--
[ja
I've finally managed to catch the event storm in the act in a log.
First, I built udev 138-1 with "--enable-debug". I had to apply a fix to
the udev/Makefile.in and udev/lib/Makefile.in because both were failing
to pass $(DEBUG_CFLAGS) to the compiler and linker.
With the package installed on the
Further analysis of event storm log.
The crux of the problem is when the LVM VG partition is detected. A
cascade of duplicate synthesised 'change' events begins. This is where
it starts. This sequence is the first. I've cut-out the intervening log
messages:
run
/sys/devices/pci:00/:00:0
More analysis. I grep-ed out just the handle_inotify reports. In this
5-minute log there were 777. Analysing them for uniqueness I get:
sort boot-udev-storm-handle_inotify.log | uniq -c
1 [829] handle_inotify: [1385] util_run_program: '/lib/udev/watershed'
(stdout) ' Reading all physical
Having left the problem alone overnight it occurred to me this morning
that maybe the issue here is the *multiple* watches being created by
similar devices (block + lvm, block +md) in the same event run that is
at the heart of this. This would explain why only systems with some
combination of LVM,
ge so you don't have to go through
+ this procedure at every boot:
+
+ To update just the kernel version that is currently running:
+
+ update-initramfs -u -k `uname -r`
+
+ or to update for all installed kernels:
+
+ update-initramfs -u -k all
+
+ Now restart the PC and hopefully the
n: openjdk-6 (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => TJ (intuitivenipple)
Status: New => Confirmed
--
applet fails to load with nullpointerexception
https://bugs.launchpad.net/bugs/199732
You received this bug notification because you are a member o
** Changed in: icedtea-gcjwebplugin (Ubuntu)
Importance: Medium => Low
Status: Confirmed => Invalid
--
applet fails to load with nullpointerexception
https://bugs.launchpad.net/bugs/199732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Work-around is to unload ALSA modules prior to suspend. Updated report
using latest kernel is needed to determine if this is still an issue.
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
--
suspend works on tribe 5, fails with updates since t
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
--
Screen flickering
https://bugs.launchpad.net/bugs/24270
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing l
: Eric Sandeen
Signed-off-by: "Theodore Ts'o"
Committed via bug #346194
** Changed in: linux (Ubuntu)
Assignee: TJ (intuitivenipple) => (unassigned)
Status: In Progress => Fix Committed
Target: None => ubuntu-9.04-beta
--
kernel bug corrupts filesystem on h
On Fri, 2009-03-20 at 20:23 +, TomasHnyk wrote:
> But how it comes that when I boot up the computer wifi works? Is it set
> by bios, which is not used while resuming? So we need a driver that will
> emulate this bios behaviour?
>
That's it precisely. For a cold-boot or return from hibernation
Philip, did you test it with the current Ubuntu Jaunty alpha which is
also based on the 2.6.28 kernel?
The kernel version you report the issue against might not have had
support for the device(s) at the time 2.6.24 was developed.
Please attach two reports using:
sudo lspci -vvnn >/tmp/report.txt
I've created a DKMS package containing the iwlwifi drivers (iwl3945.ko,
iwlcore.ko, iwlagn.ko) with debugging enabled. The package "iwlwifi-
debug-dkms" is available from my PPA for Jaunty.
After installation see the man-page ("man iwlwifi") for instructions on
enabling and using debugging. The lo
On Sat, 2009-03-21 at 10:48 +, Scott James Remnant wrote:
> It isn't trivial, it's extraordinarily expensive - we run modprobe
> several hundred times during a normal boot, having to check the module
> options against the module would add a significant penalty!
I've not been able to detect eve
botp
lsub output does not represent what the kernel drivers handle. The names
of devices reported are taken from the file /var/lib/misc/usb.ids in the
usbutils package which might not have that information (see man lsusb).
When the device is connected look in /var/log/kern.log and you'll see
some
I'm still seeing the multiple-cursors effect. I had thought I'd posted a
bug report about it previously to this one but I can't find it now. That
might be because I'd put it down to an issue with the Nvidia drivers.
--
Multiple X screens launch apps on screen 0
https://bugs.launchpad.net/bugs/336
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/24198996/xorg.conf
--
Cursor image left behind with multiple X screens
https://bugs.launchpad.net/bugs/346579
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Public bug reported:
Binary package hint: xserver-xorg
With multiple X screens and Nvidia drivers moving the cursor from one
screen to another leaves a copy of the cursor image at the edge of the
screen the cursor leaves.
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/24199035/xorg.conf
--
Multiple X screens launch apps on screen 0
https://bugs.launchpad.net/bugs/336721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/24198979/Xorg.0.log
--
Cursor image left behind with multiple X screens
https://bugs.launchpad.net/bugs/346579
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/24199038/Xorg.0.log
--
Multiple X screens launch apps on screen 0
https://bugs.launchpad.net/bugs/336721
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I've opened a new bug # 346579 "Cursor image left behind with multiple X
screens"
I realised also this bug is probably assigned to the wrong package so
correcting that.
** Changed in: xorg (Ubuntu)
Sourcepackagename: xorg-server => xorg
--
Multiple X screens launch apps on screen 0
https://bugs
** Attachment added: "xorg.conf"
http://launchpadlibrarian.net/24199067/xorg.conf
--
Touchpad cursor trapped on screen 1
https://bugs.launchpad.net/bugs/333732
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
401 - 500 of 2922 matches
Mail list logo
