[Bug 78673] Re: edgy->feisty dist-upgrade only works if ~/.gnupg file is there
BTW, I found that existance of ~/.gnupg isn't enough. I uncommented keyserver-options auto-key-retrieve and then ran gpg --verify /tmp/blah/blah.gpg so by the time I tried update-manager again, my keyring already included the key. This was on an edgy laptop that hadn't been updated for a few weeks. Presumably the latest update-manager would have worked. -- edgy->feisty dist-upgrade only works if ~/.gnupg file is there https://bugs.launchpad.net/bugs/78673 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 76500] Re: doesn't manage local machine
On Mon, Apr 30, 2007 at 05:47:02PM -, Jd wrote: > Can u please confirm that you can use Xen with xm command line. There > seems to be some problem with Xen itself. /proc/xen/privcmd seems to be > xc_handle critical for xen operation. Yes, Xen itself worked. I was able to create a couple paravirtualized domains. I'm not using Xen now, though, because I couldn't get it to give a PCI video card to a hardware-virtualized domain. (I wanted to build a multi-seat system, with Windows seeing a real PCI vid card.) I got the impression there's no MMU code for doing that yet. I haven't tried Xen at all since upgrading to Feisty. -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , des.ca) "The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces!" -- Plautus, 200 BC -- doesn't manage local machine https://bugs.launchpad.net/bugs/76500 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 87422] I think I fixed this.
On Sun, May 27, 2007 at 01:39:39PM -, Brandon wrote: > How 'bout now? Try xevil-2.02r2-7 from the debian unstable archives. > Gentoo users were experiencing this problem, and someone uploaded a > patch to them. I took it from them, and applied it to the debian > package. It compiles ok on feisty now, and runs fine. I can't install the binary package directly, because Debian's now using a libc version > than Feisty's. -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , des.ca) "The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces!" -- Plautus, 200 BC -- crash on load on AMD64 https://bugs.launchpad.net/bugs/87422 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 88585] Re: dga corrupts its pagetable
On Sun, May 06, 2007 at 08:57:41PM -, Timo Aaltonen wrote: > Have you tried this on Feisty? > > ** Changed in: xf86dga (Ubuntu) >Status: Unconfirmed => Needs Info Ok, now is a good time to possibly lockup X, since I just had to reboot anyway. I'm now running feisty, with feisty's kernel and X drivers (except mesa 6.5.3 from git, and kernel-side drm from git, but they shouldn't matter here). Feisty uses the "intel", not "i810" driver, and I've updated my xorg.conf to use it. The intel driver doesn't do DGA. [EMAIL PROTECTED]:~$ sudo dga Xlib: extension "XFree86-DGA" missing on display ":0.0". Unable to query video extension version This is even without SubSection "extmod" Option "omit xfree86-dga" EndSubSection So dga still doesn't work, but it isn't a land-mine anymore. -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , des.ca) "The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces!" -- Plautus, 200 BC -- dga corrupts its pagetable https://bugs.launchpad.net/bugs/88585 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 88585] Re: dga corrupts its pagetable
On Tue, May 29, 2007 at 03:19:48PM -0300, peter wrote: > On Sun, May 06, 2007 at 08:57:41PM -, Timo Aaltonen wrote: > > Have you tried this on Feisty? > > > > ** Changed in: xf86dga (Ubuntu) > >Status: Unconfirmed => Needs Info > > So dga still doesn't work, but it isn't a land-mine anymore. Silly me, I ended up with extmod commented out, so that's why DGA was disabled. With extmod, I get the same pagetable corruption as before. [ 2330.559844] PGD 4a2d0067 PUD 4cdeb067 PMD 4d051067 PTE 80040027 [ 2330.559850] Bad pagetable: 000f [1] SMP [ 2330.559853] CPU 1 ... As before, I can ssh in and reboot. -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , des.ca) "The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces!" -- Plautus, 200 BC -- dga corrupts its pagetable https://bugs.launchpad.net/bugs/88585 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64863] Re: It would be nice if k3b could automatically fetch mp3 decoder (package libk3b2-mp3)
Wait, why can't k3b just recommend libk3b2-mp3. Is it because the library is in universe while k3b is in main? It does already suggest it. And how is it better for k3b to pull it in when you want to run it instead of when you're installing it? I guess that lets it pull it in if you enable a universe repository after installing k3b. -- Peter -- It would be nice if k3b could automatically fetch mp3 decoder (package libk3b2-mp3) https://bugs.launchpad.net/bugs/64863 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for k3b in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 56168] Re: k3b should *not* calculate md5 sum of images by default
k3b should now only md5sum an ISO image once, although I guess it still starts doing it by default before burning. See the SVN commit at the end of the thread yamal linked to. -- k3b should *not* calculate md5 sum of images by default https://bugs.launchpad.net/bugs/56168 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for k3b in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 99715] Re: k3b crash pc
> It will crash when an updater like adept synaptics (could be dpkg?) will install ,configure an package and at the same time i start k3b. Ok, now that sounds like it might be bad hardware. Try rebooting to memtest86+, and letting it run overnight. If it finds any memory errors, try relaxing your memory timings a little. If the problem only happens when there's disk access, that won't help, though. However, k3b locks my whole machine hard (ALT+SYSRQ+B does nothing, I can't ping it, let alone ssh in) when I insert a blank DVD+R. But not otherwise; I can burn CDs, and I can start k3b with the disk in the drive. I'll report it as a separate bug. -- k3b crash pc https://bugs.launchpad.net/bugs/99715 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for k3b in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 104673] drm lockups on g965 hardware
Public bug reported: Binary package hint: linux-source-2.6.20 All Feisty needs to support 3D on Intel g965 hardware without frequent crashes or lockups is to use a newer version of the kernel drm drivers. It has i915 drm 1.6.0, but libdrm from git is currently at 1.9.0. Running feisty's AMD64 2.6.20-14-generic, and with X started in an AMD64 feisty chroot, some openGL programs can trigger a bug, and get a message like: Apr 8 03:34:25 tesla kernel: [133430.971457] [drm:i915_wait_irq] *ERROR* i915_wait_irq: EBUSY -- rec: 16309404 emitted: 16312306 And the X server exits, leaving the image on screen unchanged. re- starting X fails, because the hardware is confused. (A reboot, or at least a suspend/resume to re-POST the video is needed.) How frequently this happens depends on the program. Some games seem to trigger this within 15 minutes to an hour. Others not at all. I think it depends on what graphics effects are enabled, too. Anyway, currently feisty on g965 hardware will, I think, give the average gamer crashes on the order of once in an hour of gameplay. Using kernel-side drm modules compiled from the latest git makes Feisty's mesa work great. (i915 version 1.9.0). I played nexuiz for > 8 hours on it :) With Feisty's kernel drm modules, nexuiz sometimes made the video lock up, as above. So as I said, kernel drm modules are the only thing holding Feisty back from working fairly solidly out of the box on g965 hardware. (2D support is ok already). It might not be necessary to go all the way to 1.9.0. I've been compiling the latest drm and mesa on edgy for months now, with quite good results. ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed -- drm lockups on g965 hardware https://bugs.launchpad.net/bugs/104673 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75702] Re: ~/.drirc is not read
The bug is still present in feisty, as of libgl1-mesa-dri 6.5.2-3ubuntu7. I installed feisty in a chroot, and I'm using Feisty's kernel anyway. BTW, there's only one serious problem with Feisty's support for g965 hardware: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/104673 not counting this bug as serious, although it might be for people who want to enable force_s3tc, for a game with pre-compressed textures. -- ~/.drirc is not read https://bugs.launchpad.net/bugs/75702 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 191620] Re: stormbaancoureur segfaults
I think the problem is with libode. A while ago I compiled stormbaan 1.5.2 from source, and I had to compile my own libode. IIRC, Deb/Ubuntu's libode isn't configured with something stormbaan needs. LD_PRELOAD=/usr/local/lib/libode.so /usr/games/stormbaancoureur worked for me. (AMD64 Ubuntu Hardy) -- stormbaancoureur segfaults https://bugs.launchpad.net/bugs/191620 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251002] [NEW] man page wrong about default text encoding for pdftotext
Public bug reported: The man page for pdftotext(1) says -enc defaults to Latin1, but my testing shows that I get identical output with no -enc and with -enc UTF-8. -enc Latin 1 gives different output. I'm using a French PDF, and viewing the text with less(1). In an LANG=en_CA xterm, the -enc Latin1 text looks right. In a LANG=en_CA.utf8 gnome-terminal, the default/-enc UTF-8 output looks right. When it's mismatched, you see an inverse-video question-mark sort of glyph, or less's highlighting of control characters, depending on what locale less is using. xpdfrc(5) says the default for textEncoding is Latin1. pdftotext(1) says this config option corresponds to -enc. Anyway, UTF-8 output seems to work properly, it's just the documentation that says it's not the default. ** Affects: poppler (Ubuntu) Importance: Undecided Status: New -- man page wrong about default text encoding for pdftotext https://bugs.launchpad.net/bugs/251002 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219391] [NEW] xv doesn't work on ATI ES1000
Public bug reported: Binary package hint: xserver-xorg-video-ati I'm testing the Hardy beta desktop i386 live cd (from a USB stick wth isotostick.sh) on a Dell Poweredge 1950: dual Harpertown CPUs, Intel 5000X chipset, ATI ES1000 graphics. Everything works fine so far, except Xv. totem just shows a black rectangle instead of the video (playing the Experience Ubuntu.ogg video.) This looks exactly like Debian bug #413694. http://bugs.debian.org/413694 The command gst-launch-0.10 videotestsrc ! xvimagesink gives me a black window. It doesn't say anything about not being able to get an XV port, so this isn't like another bug report on launchpad. I tried xvattr -a XV_CRTC -v 0 and -v 1, but that made no difference. (setting to 1 resulted in a setting of -1, FWIW). At least one other ES1000 bugs report I saw turned out to revolve around the fact that it has only one CRTC. My Xorg.0.log is attached below. The monitor EDID "AVO" is a Dell 2161DS KVM[-over-IP] switch made by Avocent. I'm physically sitting at the console, with the VGA signal going through the KVM to an LCD. There's no -over-IP happening here. I even tried connecting the LCD directly to a VGA port, and it looks the same. (I didn't restart X to get a different EDID though.) lspci -vv 0e:0d.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Unknown device 01b3 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop+ ParErr- Stepping+ SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/219391 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219391] Re: xv doesn't work on ATI ES1000
** Attachment added: "Xorg log from i386 desktop hardy beta" http://launchpadlibrarian.net/13567385/Xorg.0.log -- xv doesn't work on ATI ES1000 https://bugs.launchpad.net/bugs/219391 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207209] Re: {Hardy} Xorg not loading "nv" driver
I have the same problem, but with a different PCI ID: an AGP 7600GT
nv supports this card; putting Driver "nv" in xorg.conf brings up a 1680x1050
desktop with the size (in mm) detected correctly by DDC. With the default
xorg.conf not specifying a driver, X chooses VESA.
sudo lspci -vvnn:
01:00.0 VGA compatible controller [0300]: nVidia Corporation GeForce 7600 GT
[10de:02e0] (rev a2) (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Unknown device [1682:2249]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
SERR-
I've attached my Xorg.0.log, in case it will somehow be useful.
I'm running from the Hardy beta i386 Desktop liveCD (on a USB stick w/
isotostick.sh) with updates installed on the livesystem tmpfs:
/var/log/aptitude snippets:
[UPGRADE] xserver-xorg 1:7.3+10ubuntu7 -> 1:7.3+10ubuntu10
[UPGRADE] xserver-xorg-core 2:1.4.1~git20080131-1ubuntu5 -> 2:1.4.1~git20080131-
1ubuntu9
[UPGRADE] xserver-xorg-video-nv 1:2.1.7-1 -> 1:2.1.8-1ubuntu1
[UPGRADE] grub 0.97-29ubuntu18 -> 0.97-29ubuntu21
[UPGRADE] hdparm 7.7-1ubuntu1 -> 8.6-1ubuntu1
[UPGRADE] hwtest 0.1-0ubuntu6 -> 0.1-0ubuntu8
[UPGRADE] hwtest-gtk 0.1-0ubuntu6 -> 0.1-0ubuntu8
[UPGRADE] initramfs-tools 0.85eubuntu34 -> 0.85eubuntu36
[UPGRADE] libuuid1 1.40.3-1 -> 1.40.8-2ubuntu2
[UPGRADE] lshw 02.12.01-2 -> 02.12.01-2ubuntu1
[UPGRADE] pciutils 1:2.2.4-1.1ubuntu2 -> 1:2.2.4-1.1ubuntu3
[UPGRADE] python-central 0.6.0ubuntu2 -> 0.6.1ubuntu2
[UPGRADE] udev 117-4 -> 117-8
[UPGRADE] upstart 0.3.9-1 -> 0.3.9-2
[UPGRADE] upstart-compat-sysv 0.3.9-1 -> 0.3.9-2
[UPGRADE] upstart-logd 0.3.9-1 -> 0.3.9-2
[UPGRADE] util-linux 2.13.1-2ubuntu1 -> 2.13.1-5ubuntu1
[UPGRADE] util-linux-locales 2.13.1-2ubuntu1 -> 2.13.1-5ubuntu1
[UPGRADE] x-ttcidfont-conf 26 -> 27
[UPGRADE] xbase-clients 1:7.3+10ubuntu7 -> 1:7.3+10ubuntu10
[UPGRADE] xkb-data 1.1~cvs.20080104.1-1ubuntu2 -> 1.1~cvs.20080104.1-1ubuntu5
[UPGRADE] xorg 1:7.3+10ubuntu7 -> 1:7.3+10ubuntu10
[UPGRADE] xserver-xorg-video-vesa 1:1.3.0-4ubuntu3 -> 1:1.3.0-4ubuntu4
Then I restarted X with CTRL+ALT+backspace.
/usr/share/doc/xserver-xorg-video-nv/changelog.Debian.gz shows the
change that fixed the original submitters problem, but it doesn't fix my
problem.
I already have Debian installed on this machine (where I use nvidia's
binary-only stuff), but I could find a spare partition to do an Ubuntu
install if you think this really was already fixed for my hardware. I'd
rather not, because Ubuntu's kernels don't include the badram patch, and
one of the memory sticks in this machine has a couple bad bytes. So I'd
have to take out the flaky memory stick until I had a badram kernel
ready to boot the Ubuntu system to avoid the risk of disk corruption.
(not an issue running from the livecd.)
Thanks
** Attachment added: "Xorg.0.log without Driver "nv"."
http://launchpadlibrarian.net/13570321/Xorg.0.log
--
{Hardy} Xorg not loading "nv" driver
https://bugs.launchpad.net/bugs/207209
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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253165] [NEW] mpeg3cat: fails on amd64
Public bug reported: Binary package hint: mpeg3-utils AMD64 $ mpeg3cat DEAD_LIKE_ME_S1_D1_US/VIDEO_TS/VTS_01_1.VOB > foo64.mpeg Segmentation fault x86 $ mpeg3cat DEAD_LIKE_ME_S1_D1_US/VIDEO_TS/VTS_01_1.VOB > foo.mpeg Hit end of data in DEAD_LIKE_ME_S1_D1_US/VIDEO_TS/VTS_01_1.VOB -rw-r--r-- 1 peter peter 1.0G Jul 30 00:16 foo.mpeg -rw-rw-r-- 1 peter peter0 Jul 30 00:30 foo64.mpeg The other tools aren't 64bit clean, either: AMD64 $ mpeg3dump DEAD_LIKE_ME_S1_D1_US/VIDEO_TS/VTS_01_1.VOB have_mmx=0 total_astreams=0 total_vstreams=0 total_titles=1 Title path=DEAD_LIKE_ME_S1_D1_US/VIDEO_TS/VTS_01_1.VOB total_bytes=3ffc4800 cell_table_size=0 Total PIDs=0 x86 $ mpeg3dump DEAD_LIKE_ME_S1_D1_US/VIDEO_TS/VTS_01_1.VOB have_mmx=0 total_astreams=2 Stream 0x0080: channels=6 rate=48000 samples=0 format=AC3 total_sample_offsets=0 Stream 0x0081: channels=2 rate=48000 samples=0 format=AC3 total_sample_offsets=0 total_vstreams=1 Stream 0x: w=720 h=480 framerate=29.970 frames=0 coding=420 total_frame_offsets=0 total_keyframe_numbers=0 total_titles=1 Title path=DEAD_LIKE_ME_S1_D1_US/VIDEO_TS/VTS_01_1.VOB total_bytes=3ffc4800 cell_table_size=0 Total PIDs=0 And FYI, the AMD64 architecture includes MMX, so it can be enabled without runtime checks on amd64. even on x86, mpeg3cat still segfaults on a file produced by mplayer -dumpstream dvd://42: x86 $ mpeg3cat -a0 s1.t42.dump > s1.t42.ac3 Segmentation fault Although that file isn't empty, it isn't a proper ac3 file either. mplayer says a52: CRC check failed! repeatedly. ** Affects: libmpeg3 (Ubuntu) Importance: Undecided Status: New -- mpeg3cat: fails on amd64 https://bugs.launchpad.net/bugs/253165 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253186] [NEW] user mplayer config file can break ogmrip
Public bug reported: Binary package hint: ogmrip my ~/.mplayer/config has afm=hwac3, because I have a digital (TOSLINK) connection to my speakers. I have to comment that line to use ogmrip, otherwise when it runs something like mplayer > fifo & faac < fifo, mplayer fails and faac is left blocked opening the named pipe file. (mplayer -afm hwac3 -ao pcm:... is what breaks.) possible solutions include mplayer -noconfig user, or mplayer -afm -hwac3. ** Affects: ogmrip (Ubuntu) Importance: Undecided Status: New -- user mplayer config file can break ogmrip https://bugs.launchpad.net/bugs/253186 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253194] [NEW] audio encoding inefficient
Public bug reported: Binary package hint: ogmrip ogmrip encodes audio by running mplayer -ao pcm:file=named.pipe faac named-pipe... While this is happening, top shows faac using 33% CPU, fluxbox using 20% CPU, and Xorg using ~15% CPU. (This is on a Core 2 Duo E6600, so there's 200% total available.) Switching to another virtual desktop reduces the CPU usage of fluxbox and Xorg to ~0, but faac still only gets ~33%. I've found when writing my own encoding scripts that for video data, putting a buffer in the pipe is necessary to keep the reader working at full CPU usage. Maybe the same thing is going on here for audio data. I use bfr -b 11m pipe.y4m | x264 ... stdin.y4m bfr is like cat, but uses a buffer of 11MB in this case. I'm assuming that faac is starved for data. Maybe mplayer is being slowed down by the same sillyness that results in so much CPU usage for the window manager and X server when the progress dialog is visible. ** Affects: ogmrip (Ubuntu) Importance: Undecided Status: New -- audio encoding inefficient https://bugs.launchpad.net/bugs/253194 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75174] Re: runaway kacpi_notify
This bug happened for me on an Acer desktop machine: Veriton 7200 (mobo S81M, even after upgrading to latest bios revision: R01-F3). The machine has Debian on its hard drive, and Debian's 2.6.18-6-686 doesn't have the problem. Debian's 2.6.24-etchnhalf.1-686 _does_ have the problem. It's very repeatable by running burnP6 or burnK7. yacpi hangs until burnK7 is stopped and the temp comes down, while kacpi_notify uses lots of CPU... Debian's 2.6.25 backport (linux-image-2.6.25-2-68 2.6.25-6~bpo40+1) doesn't have the problem, so that's what I'm going to run here. Intrepid's i386 Desktop alpha 4 (kernel 2.6.26-5.15-generic) doesn't have the problem. I don't think I've tried Hardy. (The machine's CDROM drive door is stuck closed, and it doesn't boot from its USB1.1 ports. I booted intrepid by copying vmlinuz and initrd.gz to the HD, and loading them with GRUB, with iso-scan/filename=... Whoever though of and implemented iso-scan/filename=, nice job!) So this is a good sign that this bug is in fact going away in newer kernels. If I had found the problem with Intrepid's kernel, I would have followed up on bugzilla.kernel.org. -- runaway kacpi_notify https://bugs.launchpad.net/bugs/75174 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 158976] Re: Casper doesn't wait for USB hard disks to come up
This is a problem for iso-scan/filename=, too. It gets the list of block devs on the system at the start, and goes through that list, then drops you to a shell. On a fast machine, the boot scripts get to /scripts/casper/20iso-scan before USB devices have shown up. Even the internal hard drive maybe hadn't read its partition table yet. (dual quad-core Harpertown server. :) I worked around it by adding break=mount to the kernel command line. Then I wait for my USB stick to be detected before pressing ^D at the (initramfs) shell prompt to continue the boot. break=premount is no good, because USB keyboard drivers haven't been loaded yet, AFAICT! I tried this with Intrepid alpha 4, AMD64 and i386. -- Casper doesn't wait for USB hard disks to come up https://bugs.launchpad.net/bugs/158976 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219391] Re: xv doesn't work on ATI ES1000
I tried Intrepid alpha 4 (desktop amd64 and i386). xv still gives just a black rectangle. No apparent improvement. :( Much more serious is that compiz needs to be blacklisted: (I just reported https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/258469). -- xv doesn't work on ATI ES1000 https://bugs.launchpad.net/bugs/219391 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258469] Re: need to blacklist software direct rendering, e.g. ATI ES1000
** Attachment added: "Xorg log from Intrepid alpha 4 (amd64 desktop) on a Dell PE1950 (ATI ES1000)" http://launchpadlibrarian.net/16862496/Xorg.0.log -- need to blacklist software direct rendering, e.g. ATI ES1000 https://bugs.launchpad.net/bugs/258469 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258469] [NEW] need to blacklist software direct rendering, e.g. ATI ES1000
Public bug reported: Binary package hint: compiz The ES1000 chipset doesn't support 3D at all. It's found on server mobos, for example. It's not too slow with gnome and firefox, although it (currently?) doesn't support RENDER acceleration. Anyway, Intrepid Alpha 4 (desktop amd64 and i386) boots up to a light gray screen with only a mouse cursor visible. This only happens after the "ubuntu" user logs in: the gdm screen is fine. I was able to switch to a text console and killall compiz.real, and then I could see the gnome desktop. There didn't seem to be a window manager, but I was able to rectify that by going into properties->appearance and turning compiz on (graying out the screen), then I think blindly clicking effects back to none. I did switch to tty1 and kill compiz.real again, though. So maybe it was just not killing compiz that was the trick. Anyway, ATI ES1000 needs to be blacklisted for compiz. Xorg.0.log: ... (II) PCI: 0e:0d:0: chip 1002,515e card 1028,01b3 rev 02 class 03,00,00 hdr 00 ... Probably you should blacklist anything where glxinfo shows: direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 ... OpenGL vendor string: Mesa Project OpenGL renderer string: Software Rasterizer OpenGL version string: 2.1 Mesa 7.1 rc3 ... Xorg apparently sets up a software direct renderer or something, so looking for direct rendering: Yes no longer tells you whether you have hardware 3D. ** Affects: compiz (Ubuntu) Importance: Undecided Status: New -- need to blacklist software direct rendering, e.g. ATI ES1000 https://bugs.launchpad.net/bugs/258469 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 215497] [NEW] "disable networking" leaves ipv6 enabled
Public bug reported: Binary package hint: network-manager In Ubuntu Hardy (i386), using the Network Manager applet's "Disable Networking" button only disables IPv4. I was still able to ping6 another machine using a v6 address received from radvd. Similarly, other machines could make v6 UDP and TCP connections to the local machine when the user thought networking was disabled (although I didn't test that). I was tempted to mark this a security bug, but I didn't because the security breach is only based on an expectation of what unticking "Enable Networking" should do. Some users might well use that do disable networking while they configure a firewall or something, though. Also, disabling networking to prevent local programs accessing the network only works for IPv4 because of this. So there are obvious security implications, but I'm not sure if it's the sort of thing to bug the Security team about. My expectation for the behaviour of the tickbox that says "Enable Networking" was that unticking it would bring all the network interfaces down (except loopback), so ifconfig wouldn't show them without -a. Same as ifdown eth0; ... would if the interfaces were configured in /etc/network/interfaces. I've seen a comment that maybe N-M keeps the ifaces UP and RUNNING so it can check for link activity. It doesn't make sense to do that if all networking is supposed to be disabled anyway. I see this behaviour on the the i386 Hardy Beta livecd, and with up-to- date Hardy installed on a Toshiba A70 laptop (rtl8139, madwifi). I doubt it's hardware-specific, though. I'll provide more info if this isn't easily reproducible for everyone. network-manager version: 0.6.6-0ubuntu5. network-manager-gnome 0.6.6-0ubuntu2. ifconfig # networking disabled ath0 Link encap:Ethernet HWaddr 00:90:96:b4:99:aa inet6 addr: fe80::290:96ff:feb4:99aa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth0 Link encap:Ethernet HWaddr 00:02:3f:d4:2c:44 inet6 addr: 3ffe:bc0:112:1:202:3fff:fed4:2c44/64 Scope:Global inet6 addr: fe80::202:3fff:fed4:2c44/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:40383 errors:0 dropped:0 overruns:0 frame:0 TX packets:22416 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:60715796 (57.9 MB) TX bytes:1554946 (1.4 MB) Interrupt:18 Base address:0xa000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1582 errors:0 dropped:0 overruns:0 frame:0 TX packets:1582 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:79260 (77.4 KB) TX bytes:79260 (77.4 KB) wifi0 Link encap:UNSPEC HWaddr 00-90-96-B4-99-AA-00-00-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6637 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:0 (0.0 B) TX bytes:305302 (298.1 KB) Interrupt:19 ifconfig # networking enabled ath0 Link encap:Ethernet HWaddr 00:90:96:b4:99:aa inet6 addr: fe80::290:96ff:feb4:99aa/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) eth0 Link encap:Ethernet HWaddr 00:02:3f:d4:2c:44 inet addr:10.1.0.207 Bcast:10.255.255.255 Mask:255.0.0.0 inet6 addr: 3ffe:bc0:112:1:202:3fff:fed4:2c44/64 Scope:Global inet6 addr: fe80::202:3fff:fed4:2c44/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:40393 errors:0 dropped:0 overruns:0 frame:0 TX packets:22462 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:60717173 (57.9 MB) TX bytes:1561469 (1.4 MB) Interrupt:18 Base address:0xa000 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1582 errors:0 dropped:0 overruns:0 frame:0 TX packets:1582 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:79260 (77.4 KB) TX bytes:79260 (77.4 KB) wifi0 Link encap:UNSPEC HWaddr 00-90-96-B4-99-AA-00-00-00
[Bug 215497] Re: "disable networking" leaves ipv6 enabled
To clarify, it doesn't "leave" ipv6 enabled, because the interface does have to get it's autoconfigured addresses again. Even if it doesn't see a router advertisement, it will still get a link-local address. sshd and exim4 both default to listening on a v6 socket, so they could be connected to. So the threat isn't purely theoretical. -- "disable networking" leaves ipv6 enabled https://bugs.launchpad.net/bugs/215497 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 176003] Re: defaults to deactivating NICs that don't support carrier detection
I tried on the same old machine. This time the NIC in it is an old tulip (21140-based Cogent EM-110 or 100), which doesn't support carrier detection either. I used the Hardy i386 beta livecd (nice Heron wallpaper, BTW): Everything is the same as before. The daemon.log messages from NetworkManager are the same as I copied/pasted in the initial bug report. eth0 is detected, but n-m decided not to run DHCP on it until instructed. It turns out that the network connectivity applet has a left-click menu which (in this case) has a radio button for "Wired Network", and a "manual configuration" option. Selecting "wired network" gives connectivity (since the machine is on an ethernet segment with a DHCP server). So it's really trivial to tell n-m to use the interface _if you know how_. Left clicking on something to bring up a different menu wasn't obvious to me, but what do I know; I usually use fluxbox and mostly run stuff from bash in a gnome-terminal. I probably only right-clicked it before, which just gives an "Enable Networking" on/off, which is already enabled. I would still suggest that at least for the live CD, defaulting to trying to activate the connection would be a good thing. I'd rate this as a wishlist bug. AFAIK, only really old NICs don't support carrier detection. This tulip NIC was old 8 years ago. People with old hardware usually have some computer experience, at least in this part of the world (Canada). Thanks, -- defaults to deactivating NICs that don't support carrier detection https://bugs.launchpad.net/bugs/176003 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 213040] [NEW] update-manager: spelling errors in hardy.tar.gz
Public bug reported: Binary package hint: update-manager I spell-checked the files in hardy.tar.gz that update-manager downloads when upgrading from gutsy to hardy. (I was originally looking at it to see if I was missing anything by just using aptitude, so I could remove instead of upgrade some packages, and choose different ways of resolving conflicts.) Anyway, I noticed enough typos that I thought it would benefit from spell checking by a native English speaker. I used emacs's ispell mode, which works pretty well for doing a batch of files, since you can just let it add all the python variable and function names to the local temporary local dictionary. That highlighted cases where a function/variable name was typoed in a comment, or even in code in one case. I fixed many typos, and some grammar and awkward language, in error and dialogue strings. I fixed on typo in an environment variable name, and another in a variable name that was mis-typed in an error-handling block. There were many spelling errors in the code comments, which I fixed, but I didn't try to re-word many of the comments, since they're not user-visible. I haven't tried to verify that the code still works, since I'm done upgrading to Hardy beta (using aptitude, which worked nicely). I do know a little Python, and most of the changes are in comments and logging strings, not in anything that other code looks at. Anyway, I hope this helps. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- update-manager: spelling errors in hardy.tar.gz https://bugs.launchpad.net/bugs/213040 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 213040] Re: update-manager: spelling errors in hardy.tar.gz
** Attachment added: "correct spelling in hardy.tar.gz" http://launchpadlibrarian.net/13154590/hardy.spellcheck.patch.gz -- update-manager: spelling errors in hardy.tar.gz https://bugs.launchpad.net/bugs/213040 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125687] Re: Samba does not start on boot.
> Upstream has made some adjustments to nmbd in samba 3.0.28a so that it will wait when the interfaces have gone away, but I don't know if this affects the behavior on startup. This doesn't solve the problem for the ntpdate init script, for example. There's a general problem that numbering scripts with numbers higher than rcS.d/S40networking doesn't mean that dhcp will have an IP by the time they run. That's why I wrote that little init script that waits until it can ping something before it returns, so the firestarter and ntp init scripts could work properly. If this problem goes away for samba because of something samba-specific way, this bug should be duplicated or a new one reported. -- Samba does not start on boot. https://bugs.launchpad.net/bugs/125687 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268005] Re: live cd from nfsroot breaks the nfs mount during bootup
I had thought this was bug 92338, but that was fixed by Hardy's N-M's support for iface eth0 inet manual The fact that that no longer works is a different bug (this one, in fact). On bug 92338, --- Alexander Sack wrote on 2008-09-22: (permalink) since gutsy we dont manage interfaces configure in /etc/network/interfaces anymore. ifupdown and network-manager are mutually exclusive. So given that nfsroot uses something in /etc/network/interfaces, all should be fine for you. --- So some people think casper's workaround should still be enough, and I agree it looks like bug 256054. Maybe removing the auto eth0, and just keeping iface eth0 would do the trick? No idea. Ansgar, casper doesn't parse any ip= options. boot=nfs does, but not boot=casper. How would ip=up work? You want Linux to get the DHCP lease from the pxelinux that booted it? I don't think there's any mechanism for that, other than encoding the ip, netmask, gateway, and dns into kernel command line options for either Linux itself or the initramfs to parse. If you want Linux to parse it, probably your ethernet drivers need to be compiled into the kernel. The trend is always to move things out of the kernel and into user-space, so parsing complex kernel params is probably not going to get added, and if it already exists it will probably get removed sometime! -- live cd from nfsroot breaks the nfs mount during bootup https://bugs.launchpad.net/bugs/268005 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255559] Re: awn-applet-activation crashed with SIGSEGV in awn_title_hide()
I hit this on the Intrepid i386 livecd daily build (Sept30, 2008). I had compiz running with some extra stuff turned on (e.g. installed ccms and enabled ezoom plugin). HW: Toshiba A70 laptop: ATI IXP chipset, integrated ATI graphics (quite slow with AWN) 00:00.0 Host bridge: ATI Technologies Inc RS300 Host Bridge (rev 02) Subsystem: Toshiba America Info Systems Device ff00 00:01.0 PCI bridge: ATI Technologies Inc Radeon 9100 IGP AGP Bridge -- awn-applet-activation crashed with SIGSEGV in awn_title_hide() https://bugs.launchpad.net/bugs/29 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155655] Re: gnome-terminal does not honor display setting when using xephyr-xserver
I tried to reproduce this, but it works for me on a pre-Intrepid system. I'm going to mark this fix-released, rather than invalid, on the assumption that there was something going on. If anyone can reproduce this, or knows exactly what the submitter meant by "only the first gnome-terminal honors the display setting" they should re-open this bug. It sounds like Heikki is saying that one of the gnome-terminals opens outside Xephyr, even though DISPLAY=:1. That sounds very unlikely, unless gnome-terminal talks to an already-running gnome-terminal that it found with something other than X, and asked it to open a new window. I tested on a dual-core system with hot caches, and gnome-terminal running outside Xephyr, so there was plenty of chance for any race conditions to happen. Both gnome-terminals appear at opposite corners of the Xephyr window. The combined stdout/stderr of it all is: Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list! unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed unrecognised device identifier! (EE) config/hal: NewInputDeviceRequest failed Failed to retrieve terminal server from activation server ** Changed in: gnome-terminal (Ubuntu) Status: New => Fix Released -- gnome-terminal does not honor display setting when using xephyr-xserver https://bugs.launchpad.net/bugs/155655 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 277988] [NEW] man page not parseable for man -k
Public bug reported: Binary package hint: gucharmap man -k guchar gucharmap (1)- (unknown subject) I couldn't find it when I was looking for it earlier with man -k unicode and man -k character, etc. I don't know nroff so I can't tell what's wrong with the page that makes it not parseable by the indexer, sorry. ** Affects: gucharmap (Ubuntu) Importance: Undecided Status: New -- man page not parseable for man -k https://bugs.launchpad.net/bugs/277988 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278454] [NEW] [r200] multihead lockups with textured video Xv adaptor
Public bug reported: Binary package hint: xserver-xorg-video-ati driver version 1:6.9.0+git20081003.f9826a56-0ubuntu2 Running GNOME with metacity (not compiz for this bug...) on pre-Intrepid i386. Toshiba A70 laptop (ATI IXP chipset: mobility radeon 9100IGP). Using Xinerama on internal and VGA CRT. machine booted with CRT plugged in, so that was the default display. X started without being told to set up xinerama. GNOME does that with xrandr when I log in. ran mplayer -nosound ... and paused it to keep the Radeon Video Overlay Xv adaptor occupied. ran another mplayer (on a 720p video that this machine doesn't quite have the horsepower to play with no skips), and dragged the window over to the CRT. During the dragging back and forth, and resizing, X dies, but gdm is able to restart it cleanly. X crashed even more easily with Xv in the previous Intrepid version of -video-radeon, so this isn't a recent regression. If anything, it's an improvement. :) BTW, compiz is totally b0rked on multihead on this GPU. I'll report that separately if/when I get around to it, if it hasn't been already. ProblemType: Bug Architecture: i386 Date: Sun Oct 5 02:39:10 2008 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: ath_hal Package: xserver-xorg-video-radeon 1:6.9.0+git20081003.f9826a56-0ubuntu2 PackageArchitecture: i386 ProcEnviron: SHELL=/bin/bash PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 ProcVersion: Linux version 2.6.27-5-generic ([EMAIL PROTECTED]) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu8) ) #1 SMP Fri Oct 3 00:38:23 UTC 2008 SourcePackage: xserver-xorg-video-ati Uname: Linux 2.6.27-5-generic i686 xkbcomp: ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- [r200] multihead lockups with textured video Xv adaptor https://bugs.launchpad.net/bugs/278454 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278454] Re: [r200] multihead lockups with textured video Xv adaptor
** Attachment added: "Xorg.log from the crash" http://launchpadlibrarian.net/18229548/Xorg.0.log.old ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/18229549/Dependencies.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/18229550/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/18229551/LsPci.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/18229552/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/18229553/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/18229554/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/18229555/Xrandr.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/18229556/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/18229557/xdpyinfo.txt -- [r200] multihead lockups with textured video Xv adaptor https://bugs.launchpad.net/bugs/278454 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278954] [NEW] read-only bind mounts cause spurious EROFS
Public bug reported:
I installed the Intrepid kernel (linux-image-2.6.27-5-server on an
otherwise-Hardy x86-64 server (I do have Intrepid's initramfs-tools, and
a non-current-Intrepid module-init-tools).
/dev being read-only bind mounted on /dev/.static/dev somehow causes
Linux to return EROFS for only some operations on the root filesystem.
(My root filesystem is XFS. Yes, this works, you just can't setup grub
on it from linux, so I boot grub from USB or PXE after the initial
install of Ubuntu.)
I don't have this problem on my pre-Intrepid desktop at home running
2.6.27-4-generic, with a JFS root filesystem (and /dev read-only bind
mounted). And I didn't notice it on my pre-Intrepid laptop with
2.6.27-5-generic (IIRC), with an ext3 rootfs. It's not on, so I can't
check it's status right now. So either a server kernel bug, or an XFS
bug, I'd guess.
symptoms:
# strace touch /etc/bar # /etc/bar doesn't exist beforehand
close(0)= 0
open("/etc/bar", O_WRONLY|O_CREAT|O_NOCTTY|O_NONBLOCK, 0666) = 0
syscall_280(0, 0, 0, 0, 0x2, 0, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2,
0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2, 0x2,
0x2) = -1 (errno 30)
utimes("/etc/bar", NULL)= -1 EROFS (Read-only file system)
close(0)= 0
touch: setting times of `/etc/bar': Read-only file system
exit_group(1) = ?
/etc/bar now exists.
# strace chmod 644 /etc/mtab
stat("/etc/mtab", {st_mode=S_IFREG|0600, st_size=794, ...}) = 0
fchmodat(AT_FDCWD, "/etc/mtab", 0644) = -1 EROFS (Read-only file system)
/proc/mounts showed that / was mounted rw, but /dev/.static/dev was mounted ro.
mount /dev /dev/.static/dev -o remount,rw makes metadata ops work again on the
root filesystem.
/proc/mounts (after remount)
rootfs / rootfs rw 0 0
/dev/disk/by-uuid/dc2372d6-5ae9-4b28-8fe5-108c779e82fb / xfs
rw,relatime,noquota 0 0
/dev/disk/by-uuid/dc2372d6-5ae9-4b28-8fe5-108c779e82fb /dev/.static/dev xfs
rw,noquota 0 0
/etc/fstab
# /dev/sda1
UUID=dc2372d6-5ae9-4b28-8fe5-108c779e82fb / xfs
relatime,inode64,noikeep0 1
It's a 10GB filesystem, so I probably don't need inode64...
Let me know if you have any problem reproducing this, and I can get more
details on my server.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: linux-2.6.27
** Tags added: linux-2.6.27
--
read-only bind mounts cause spurious EROFS
https://bugs.launchpad.net/bugs/278954
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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278954] Re: read-only bind mounts cause spurious EROFS
I was able to reproduce this on another server. It happens on XFS with relatime,inode64,noikeep. It does not happen on 2.6.27-5 with just relatime. I haven't checked which of inode64 or noikeep is the problem. -- read-only bind mounts cause spurious EROFS https://bugs.launchpad.net/bugs/278954 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263747] Re: linux 2.6.27-2.3: pcspkr should be enabled too, now that snd-pcsp is blacklisted by default
** Changed in: linux (Ubuntu) Status: Won't Fix => Fix Released -- linux 2.6.27-2.3: pcspkr should be enabled too, now that snd-pcsp is blacklisted by default https://bugs.launchpad.net/bugs/263747 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 282425] [NEW] openoffice.org-thesaurus-en-us provides en_GB, but not en_CA or anything else
Public bug reported: oowriter's thesaurus feature doesn't work well for me. I have to mess with document languages to get it to open. Being in Canada, I run Ubuntu (pre-Intrepid, AMD64) with LANG=en_CA.utf8. I have openoffice.org-thesaurus-en-us and ...-en-au installed. (but not language-support-writing-en, or the en-au and en-za myspell dicts it wants to pull in. I'd rather play with aptitude than have lots of pkgs I don't need, esp. when I'm tracking Intrepid's relatively frequent package updates...) Anyway, oowriter won't open the thesaurus (grayed-out thesaurus item under tools->language) unless I use tools->language->for... to change the doc language to en_US (or en_GB). For one thing, it would be nice if it offered to let you use a thesaurus for another variant of English. Better would be if the en-us thesaurus just claimed to apply to all the other variants of English, since it already lists itself as en_US and en_GB. If a thesaurus can be useful for both en_US and en_GB, it is certainly useful for en_CA, since our spellings are usually the GB spellings, but our word usage is usually closer to US. (e.g. we write neighbour (with the "our" ending), but we put gas in our trucks more often than petrol in our lorries.) So please add some lines to /usr/share/myspell/infos/ooo/openoffice .org-thesaurus-en-us, to make it apply to all the en variants that aren't covered by the ...-en-au package (which is in fact only en_AU). Or perhaps to the en_AU thesaurus, since it says it just has the US spellings removed, should be the thesaurus for en_CA, en_ZA, en_whatever, as well as en_AU, unless it's full of "blimey", "crikey", and "throw another shrimp on the barbie". :) The package description for openoffice.org-thesaurus-en-us should also say what en variants it provides dictionaries for, since en-us isn't an obvious name to find an en_GB thesaurus under, esp. when OO won't just use them as a general English thesaurus. ** Affects: openoffice.org-dictionaries (Ubuntu) Importance: Undecided Status: New -- openoffice.org-thesaurus-en-us provides en_GB, but not en_CA or anything else https://bugs.launchpad.net/bugs/282425 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 196076] Re: Seagate ST980813ASG on Dell Vostro 1700 HD stops
I was going to reply on the forum thread I originally started, but it's locked now. sigh. http://ubuntuforums.org/showthread.php?t=625076 Anyway, the solution to my problem was an updated firmware for my WD5000YS hard drive. http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1493&p_created=1168299631&p_sid=mN5O5Wsi&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9NDkmcF9wcm9kcz0mcF9jYXRzPSZwX3B2PSZwX2N2PSZwX3NlYXJjaF90eXBlPXNlYXJjaF9mbmwmcF9wYWdlPTEmcF9zZWFyY2hfdGV4dD1yYWlk&p_li=&p_topview=1 or a shorter URL that also has a link to it: http://www.3ware.com/KB/article.aspx?id=15065 --- [...] Cause: WD hard drives have an internal routine that is periodically executed as part of the internal “Data Lifeguard” process that enhances the operational life expectancy. While the drive is running this routine, if the drive encounters an error, the drive’s internal host/device timer for this routine is NOT cancelled causing the drive to be locked in this routine, never becoming accessible to the host computer/controller. This condition can only be reset by a Power Cycle. [...] --- sounds exactly like what I was seeing. I upgraded my firmware several months ago, and I haven't seen the problem since. -- Seagate ST980813ASG on Dell Vostro 1700 HD stops https://bugs.launchpad.net/bugs/196076 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262550] Re: WARNING: Intrepid might burn down MacBook Pro
Is something using a lot of CPU time? run top, and look at the load averages at the top right. (number of tasks waiting running/waiting to run averaged over the last 5/10/15 minutes). If it's not close to zero, something's keeping your CPU busy. Is your CPU idling at low speed, like it should be? run cpufreq-info, or if it's not installed, look at /proc/cpuinfo (the clock speed there is updated by the kernel's cpufreq framework). And cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor (ondemand is good, userspace is ok too if there is a userspace daemon checking the load and deciding what speed to set the CPU to.) Core 2 CPUs have a built-in temp sensor that reports a relative temp, relative to the max temp. e.g. on my desktop $ sensors coretemp-isa- Adapter: ISA adapter Core 0: +59.0°C (high = +86.0°C, crit = +100.0°C) coretemp-isa-0001 Adapter: ISA adapter Core 1: +58.0°C (high = +86.0°C, crit = +100.0°C) (sensors is in lm-sensors, and you have to configure it. You can just modprobe coretemp, and do grep . -n /sys/devices/platform/coretemp.0/temp1_* (I use grep here as an easy way to combine file names with file contents). I get: /sys/devices/platform/coretemp.0/temp1_crit:1:10 /sys/devices/platform/coretemp.0/temp1_crit_alarm:1:0 /sys/devices/platform/coretemp.0/temp1_input:1:59000 /sys/devices/platform/coretemp.0/temp1_label:1:Core 0 /sys/devices/platform/coretemp.0/temp1_max:1:86000 ) see bug 264290 for more info about core 2 temp sensors, and a problem that seemed like it was caused by high temps, but has gone away for me with 2.6.27-3. -- WARNING: Intrepid might burn down MacBook Pro https://bugs.launchpad.net/bugs/262550 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92338] Re: NetworkManager takes over already used nfsroot interface
On more careful reading of this bug (#92338), it seems to be reporting the problem that your main network interface can't be in /etc/network/interfaces if you want to boot with nfsroot. The fix for that is support for the "manual" setting in interfaces(5) to stop ifupdown breaking the nfsroot. e.g. auto eth0 iface eth0 inet manual So I was wrong earlier, and this isn't a dupe of bug 268005, even though they basically cause the same problem. I had been going to send email asking why you closed this even though it was still a problem. But as I discovered, this bug is fixed, and the regression in n-m in Intrepid is a different problem. I'm pretty sure bug 268005 will be a problem for nfsroot in general, not just boot=casper. It prevents nfsroot netbooting the Ubuntu Intrepid alpha6 live cd (except with a workaround hack). -- NetworkManager takes over already used nfsroot interface https://bugs.launchpad.net/bugs/92338 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 219391] Re: xv doesn't work on ATI ES1000
still present in Intrepid alpha6 i386. I discovered that the "Textured Video" adaptor works, but not the used-by-default video overlay. xvinfo: Adaptor #0: "ATI Radeon Video Overlay" 1 port at 57. supports a bunch of attributes. Adaptor #1: "Radeon Textured Video" 16 ports at 58 no port attributes defined I can attach a complete xvinfo output if someone wants it. If something is already using the vid overlay, then anything else will have to use the next available adaptor. e.g. with totem running on the video overlay (displaying a black rectangle), gst-launch-0.10 videotestsrc ! xvimagesink does produce its video test pattern. Its debug output confirms it's using the textured video adaptor. However with videotestsrc ! xvimagesink producing a black rectangle on the video overlay, totem makes a mess of the Experience Ubuntu (ogg theora in /usr/share/example-content) video. It's displayed as streaks of colour, not the correct video at all. Maybe the XV adaptor has bugs with the colour space it's using, but not videotestsrc's colourspace. The colours are the same in a screenshot, so they're screwy before getting to the framebuffer. In Hardy, I'm not sure there was a textured video adaptor, so this sounds like a separate bug. The vid overlay is still broken, so even if xv textured video sometimes works, this bug isn't gone. (esp. since the xv vid overlay is the default adaptor.) -- xv doesn't work on ATI ES1000 https://bugs.launchpad.net/bugs/219391 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105538] Re: Setting capslock to control in gnome keyboard preferences leaves capslock stuck on
MountainX, you don't need sudo in /etc/rc.local. It runs as root on bootup, like all init scripts. Are you sure your loadkeys method even works? loadkeys is a totally different way to change your keymap: It changes the Linux kernel keymap. I though X put the kbd in raw mode, and got keycodes which weren't affected by Linux's keymap, but maybe I'm remembering wrong or it's changed in the few years since I've used loadkeys instead of just xkb options. I don't think loadkeys even accepts the same syntax as xmodmap; loadkeys(1) and keymaps(5) don't say anything about "add" lines. The easiest way to swap ctrl and caps (for X11, doesn't affect the text consoles like loadkeys) is to set the xkb option ctrl:swapcaps. The defaults can be set in xorg.conf, or you could arrange for your X session startup scripts to include setxkbmap -option ctrl:swapcaps. I like having my capslock as an extra control (ctrl:nocaps), since some of muscle memories send my finger to the key labeled Ctrl, but capslock is right there on the home row so it's easier to reach, and where Control is on e.g. Sun and original VT100 keyboards. :) Plus, I find the Caps Lock feature useless and annoying. Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" # Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "us" Option "XkbOptions""ctrl:nocaps" Option "Autorepeat""200 40" #Ubuntu default: lv3:ralt_switch ISO level 3 shift EndSection Anyway, none of this has anything to do with the bug report, which was that if caps-lock is on _when_ you enable ctrl:nocaps (either with setxkbmap or with gnome), you won't be able to turn caps-lock off again, because you don't have a caps-lock key. This has happened to me, and I had to re-enable capslock, turn off capslock, then re-do the setting. (setxkbmap -option '' clears all options, BTW. Get that into your command history before you try to test this, unless you really like clicking your mouse. setxkbmap -print is interesting...) Strangely, X turns off the capslock LED when you hit capslock while ctrl:nocaps is set. If you hit numlock a couple times, it will sort itself out and eventually display the correct set of LEDs. I was going to say this isn't a gnome-keyboard-preferences bug, since it's the same problem when you use setxkbmap. But then I realized that I couldn't imagine anybody wanting caps-lock to be stuck on, so it would be a nice feature for g-k-p to turn off caps-lock if it's on before applying any setting that leaves the keyboard without a caps-lock key. That would make it more than a straight GUI equivalent of setxkbmap (with persistence, now that that works properly...) The X people probably wouldn't see it as a bug, either. They probably wouldn't be willing to make setting xkb options have side effects, like turning off caps-lock, since you never know what weird things people might want. GNOME should be putting the user-friendly do what almost- everyone-wants wrapping on top of thing, vs. the direct uncooked interface you get with setxkbmap. OTOH, I personally would like it if setxkbmap -option ctrl:nocaps turned off caps-lock, just in case. e.g. maybe put that in a script you can run with a mouse click, if you're using some other window manager. I can't think of any situation where I'd want to cripple a console by leaving it stuck in caps-lock on mode. Although you can hold shift to reverse caps-lock, so you could type setxkbmap, or anything else in lower case, unless that feature was disabled (with another xkb option, I think). BTW, leaving caps-lock on is an easy mistake to make (once, anyway), because turning it on when you wanted ctrl (if that's the layout you're used to) is what might make you run g-k-p in the first place, before you touch the keyboard again. (That's what I did.) -- Setting capslock to control in gnome keyboard preferences leaves capslock stuck on https://bugs.launchpad.net/bugs/105538 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138920] Re: Matrox Millennium G200 AGP fails 1024x768 resolution
** Summary changed: - Matrox Millennium G200 AGP fails 1074x768 resolution + Matrox Millennium G200 AGP fails 1024x768 resolution -- Matrox Millennium G200 AGP fails 1024x768 resolution https://bugs.launchpad.net/bugs/138920 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 138920] Re: Matrox Millennium G200 AGP fails 1024x768 resolution
Ubuntu can't detect what resolutions your monitor supports, and the Monitor section of your xorg.conf doesn't list any. I would mark this "invalid", but one could consider it a bug that Ubuntu doesn't have a better way to deal with situations where it can't autodetect things. I don't think there's anything wrong with editing a text config file, or using sudo dpkg-reconfigure xserver-xorg but if there is a tool to do it better, Ubuntu should use that. (The monitor resolution detection stuff is here in your log file: (II) MGA(0): I2C Monitor info: (nil) (II) MGA(0): end of I2C Monitor info (--) MGA(0): No DDC signal DDC is the signaling method for computers to ask monitors about themselves, etc. Since Xorg can't get any info from the monitor, it falls back on very conservative defaults for horizontal and vertical refresh rate limits, which only allow up to 800x600 resolutions. Your log says your vid card has 8MB of RAM, so your card definitely supports 1024x768. If your monitor does too, go look up its specs (hsync and vsync, aka horizontal and vertical refresh range, or whatever.) on my system, my Xorg.0.log has lines like ... (II) intel(0): Printing DDC gathered Modelines: (II) intel(0): Modeline "1680x1050"x0.0 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync (65.3 kHz) (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) ... Here's an example "Monitor" section: Section "Monitor" Identifier "opti" Option "DPMS" DisplaySize 320 240 # 32x24 cm HorizSync 30-70 VertRefresh 50-120 EndSection HorizSync is in khz, VertRefresh is in Hz. google for more info if you need it. It's only in the last couple years that you didn't always have to put your refresh rates in your xorg.conf (or previously /etc/X11/XF86Config). There is a ton of old and new info about configuring X... -- Matrox Millennium G200 AGP fails 1024x768 resolution https://bugs.launchpad.net/bugs/138920 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268005] Re: live cd from nfsroot breaks the nfs mount during bootup
** Also affects: casper (Ubuntu) Importance: Undecided Status: New -- live cd from nfsroot breaks the nfs mount during bootup https://bugs.launchpad.net/bugs/268005 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 182940] Re: network NFS DHCP boot fails on multiple NIC machine
-t 7 is too short for my setup. -t 60 should be safe. I was able to netboot the Hardy livecd (which detects my interfaces such that eth1 is the one with the cable plugged in to it). (It does boot=casper, not boot=nfs, so it doesn't normally look at ip= at all.) I booted with break=mount, and started shells on tty2 and tty3, then did ipconfig -t 60 all. I had to kill an ipconfig eth0 /tmp/..., but then the boot worked fully. -- network NFS DHCP boot fails on multiple NIC machine https://bugs.launchpad.net/bugs/182940 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268005] Re: live cd from nfsroot breaks the nfs mount during bootup
I marked this as also affecting casper, since it's with boot=casper, not boot=nfs. Also, most nfsroot systems probably wouldn't have N-M installed. In Hardy and Intrepid, scripts/casper-bottom/23networking builds a /etc/network/interfaces with auto lo iface lo inet loopback auto eth0 iface eth0 inet manual auto eth1 iface eth1 inet manual In Hardy, this apparently prevents N-M from bringing the interface down then up. nm-applet's dropdown just shows "manual..." In Intrepid, this doesn't stop N-M. So unless there's some other way of asking N-M to back off (which casper should use), this is a regression in N-M in Intrepid. N-M's changelog shows that 21_manual_means_always_online was dropped or not needed anymore. Maybe that's when the regression happened. Or maybe not, but I'm not going to debug this further myself. -- live cd from nfsroot breaks the nfs mount during bootup https://bugs.launchpad.net/bugs/268005 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 92338] Re: NetworkManager takes over already used nfsroot interface
casper in Hardy (and maybe earlier) writes a /etc/network/interfaces with auto eth0 iface eth0 inet manual for each interface. This keeps N-M from touching it. Except in Intrepid; see bug 268005 which is a dupe of this bug, since I didn't see this before reporting it. scripts/nfs doesn't rewrite interfaces, of course, since you can edit it yourself on the NFS server. -- NetworkManager takes over already used nfsroot interface https://bugs.launchpad.net/bugs/92338 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269715] [NEW] sysctl.conf has a bad commented-out entry for sys.kernel.maps_protect
Public bug reported: Binary package hint: procps sysctl keys don't start with sys. This is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494655 ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Affects: procps (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #494655 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494655 ** Also affects: procps (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=494655 Importance: Unknown Status: Unknown -- sysctl.conf has a bad commented-out entry for sys.kernel.maps_protect https://bugs.launchpad.net/bugs/269715 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264290] Re: linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive
The coretemp scale change is normal, and is explained here: http://kerneltrap.org/mailarchive/linux-kernel/2008/4/29/1661864 --- The thing is, the temperature is stored as a relative value in the CPU. Relative to what, depends on the CPU model, can be 85°C or 100°C. Up to kernel 2.6.24 we had a set of rules to find out, in 2.6.25 we have a presumably better heuristic. So some people have seen their CPU temperature climb by 15°C and others drop by 15°C, that's expected. --- I don't think it explains the keyboard hangs and blocked tasks at all, so maybe that's something else. I'll try 2.6.27-3 soon. -- linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive https://bugs.launchpad.net/bugs/264290 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264290] Re: linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive
I've been running 2.6.27-3 for the past couple days without problems. Maybe the problems I had before really were due to overheating, since I did knock over the case sometime shortly before trying 2.6.27-2.3 :(, and I re-applied thermal paste on my CPU heatsink before trying 2.6.27-3. Still, even before that it ran fine with 2.6.24. And my CPU temps are only a couple degrees lower. I don't really think it was a physical thermal problem, but I can't rule it out. Anyway, I think the long-delay bug is no longer happening for me. Maybe something in 2.6.27-3 was a fix for my hardware. Can launchpad clone a bug, so I can mark the freezing part of this as fixed, and the coretemp part as a sort of non-bug? The coretemp reading is of course still 15C higher than with Hardy, and doesn't agree with the BIOS, but that's meant to happen. ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive https://bugs.launchpad.net/bugs/264290 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175960] Re: "clock appears to be wrong" dialog prevents gnome session from starting
It's fixed in Hardy. The time-admin gui runs with root privs, so I can set the clock and then get to the normal gnome desktop. -- "clock appears to be wrong" dialog prevents gnome session from starting https://bugs.launchpad.net/bugs/175960 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 199923] Re: evdev grabs all devices even if it's disabled
> The upstream developers realize this is a bug in evdev 1.2, which is why it's been fixed in evdev 2.0. I think Jeffrey was talking about just the lack of Emulate3Buttons, which is now present in evdev in Intrepid. I don't see anything in its man page about disabling evdev entirely. I'd still like to be able to disable evdev so my keyboard will use the old X keycodes for compatibility with programs that depend on them; they're different for the arrow keys: evdev: left = 113 right = 114 up = 111 down = 116 kbd: left = 100 right = 102 up = 98 down = 104 I have a Dell DS2161-2 kvm-over-ip switch, and it's over-ip function works by loading a java program that talks to the switch over an encrypted connection. I assume the java program makes use of the keycodes (not keysyms) the viewer gets from X to generate scancodes for the USB keyboard the remote computer sees. When I press up-arrow on my evdev keyboard, Ubuntu on the remote machine runs the gnome screenshot applet. :( So the Java program doesn't seem to be portable to other keyboard layouts, or something. I guess I should report it to Dell, but in the meantime I'd rather just be able to kludge around it by using the kbd driver. (Intrepid on my laptop insists on loading evdev when hal sees the touchpad and apparently a ps/2 mouse, and I haven't figured out what devices to put in Xorg.conf to handle everything and thus hopefully prevent X from deciding to use evdev. If I could, I'd just disable HAL or whatever.) My Hardy desktop still uses kbd and mouse, not evdev. I'm with Jeffrey on this; it would be really nice if new pieces of system infrastructure were as non-mandatory as possible. e.g. you can still avoid udev if you don't like it. -- evdev grabs all devices even if it's disabled https://bugs.launchpad.net/bugs/199923 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 105519] Re: livecd clock is (inevitably) wrong
dhcp has a timezone option. I might not be widely used, but dhclient on the livecd should be configured to request timezone or location or whatever the option is. Then if the server does support it, you're all set. DHCP also supports a list of NTP servers, although that's not so necessary since Ubuntu seems to have a default for that anyway. It would be much better to use people's ISP's NTP servers, though. Many machines will have their BIOS clocks set to local time, so if you can get the difference between that and NTP time, that would be a good default for a timezone (although there are multiple timezones with the same time offset). Probably you'd have to record hwclock time, then do ntpdate, if ntpdate modifies the hwclock, too. On machines with BIOS clock = UTC, which is good if you never boot any silly OSes that don't support that, the livecd will just default to timezone = UTC, like before. -- livecd clock is (inevitably) wrong https://bugs.launchpad.net/bugs/105519 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 274264] [NEW] lvcreate --type undocumented
Public bug reported: Binary package hint: lvm2 Ubuntu Hardy. lvcreate --help shows ... [-t|--test] [--type VolumeType] [-v|--verbose] ... AFAICT, --type isn't documented in the man page or in /usr/share/doc/lvm2. And I didn't have any luck with google. lvcreate works fine without it, but I'm curious about what it lets you do... upstream's man page currently doesn't have it either: http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/LVM2/man/lvcreate.8?cvsroot=lvm2 so this won't be fixed in Intrepid either, unless it's not in the --help output. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- lvcreate --type undocumented https://bugs.launchpad.net/bugs/274264 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275299] [NEW] ubuntu-mobile-default-settings: better descriptions describing target MIDs
Public bug reported: Binary package hint: ubuntu-mobile-default-settings It's not obvious from the package descriptions that Ubuntu Mobile targets small-screen netbooks. Although that does sound familiar from reading news items, it would be appropriate to make it clear in the package descriptions that Ubuntu Mobile is for netbooks, not laptops in general. (I was wondering if Ubuntu had decided to make ubuntu-desktop be for desktops, and ubuntu-mobile be the equivalent for laptops, so pcmcia, wireless, and that sort of thing could be left out of ubuntu- desktop, or at least only be Recommended or Suggested for desktops.) anyway, I installed ubuntu-mobile-default-settings on my 15" screen laptop (no palm pilot, so I didn't want to pull in gnome-pilot-sync with ubuntu-mobile), and was unpleasantly surprised by how intrusive it was. Among other things, u-m-d-s installs devilspie with a config file that causes every new X11 window to be maximized and undecorated. The windows aren't re-decorated after moving or resizing, and I don't see an obvious way to do anything with them (other than reading up on devilspie). So what I'm trying to say is that u-m and u-m-d-s need descriptions like: -- u-m: Description: The Ubuntu mobile system This package depends on all of the packages in the Ubuntu mobile system. Ubuntu Mobile is an alternative to ubuntu-desktop, intended for use on Mobile Internet Devices (MIDs). See http://www.ubuntu.com/products/mobile. MIDs typically have: * 4 to 7 inch touch screen * Physical and/or virtual keyboard * 2GB to 8GB Flash or disk storage, 256MB+ memory (512MB+ recommended) It is also used to help ensure proper upgrades, so it is recommended that it not be removed. --- u-m-d-s: This package contains GConf and application default settings as well as the panel configuration for an Ubuntu Mobile desktop, intended for use on Mobile Internet Devices with < 7" screens. By default, every newly-opened window will be maximized and undecorated, so you probably don't want this on a machine with a larger screen. --- That MID feature list is from the URL I included, with the obvious or not-really-relevant ones pared out. ** Affects: mobile-meta (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-mobile-default-settings (Ubuntu) Importance: Undecided Status: New ** Also affects: mobile-meta (Ubuntu) Importance: Undecided Status: New -- ubuntu-mobile-default-settings: better descriptions describing target MIDs https://bugs.launchpad.net/bugs/275299 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275304] [NEW] wrong ownership of .Xauthority and /tmp/libgksu-xxx
Public bug reported: Binary package hint: gksu [EMAIL PROTECTED]:~$ gksudo xterm [EMAIL PROTECTED]:/home/peter# ll $XAUTHORITY -rw--- 1 peter peter 150 2008-09-27 20:20 /tmp/libgksu-3t0ebS/.Xauthority The directory is also owned by the user who ran gksudo, so they could modify .Xauthority during the gksudo session. This isn't really a security problem, because anyone who runs gksudo is root-equivalent in the first place. An attacker gaining access to their account could do lots of things besides try to exploit root X processes by writing to their .Xauthority. e.g. capture user's password and sudo themselves. The problem this does cause is that gksudo only works for sudo-to-root. gksudo -u other-user xterm fails, because xterm can't open .Xauthority, because it doesn't have read permission on it or even exec permission on the dir it's in. ** Affects: gksu (Ubuntu) Importance: Undecided Status: New -- wrong ownership of .Xauthority and /tmp/libgksu-xxx https://bugs.launchpad.net/bugs/275304 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275304] Re: wrong ownership of .Xauthority and /tmp/libgksu-xxx
sorry, this is on an updated Intrepid i386 with gksu 2.0.0-5ubuntu3 libgksu2-0 2.0.7-1ubuntu2 -- wrong ownership of .Xauthority and /tmp/libgksu-xxx https://bugs.launchpad.net/bugs/275304 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 275299] Re: ubuntu-mobile-default-settings: better descriptions describing target MIDs
On Mon, Sep 29, 2008 at 12:07:46PM -, Oliver Grawert wrote: > well, what you describe in your description seems to actually be ubuntu-mid Ah, I see. ubuntu-mobile and ubuntu-mid are both built from the mobile-meta source package. I hope you'll update it's description, too. It currently doesn't say what MID stands for, or have any URLs. It should probably point to http://www.ubuntu.com/products/mobile, but maybe ubuntu-mobile shouldn't. > i will change the description of ubuntu-mobile to: > > Description: The Ubuntu mobile system > This package depends on all of the packages in the Ubuntu mobile system. > Ubuntu Mobile is an alternative to ubuntu-desktop, intended for use on > 7 - 9 inch touchscreen equiped Ultra Mobile PCs (UMPCs). Yeah, that's what a curious sysadmin needs to know when seeing this package available in aptitude. control files can have a Homepage: field, right? That would be a good idea. thanks. -- Peter Cordes -- ubuntu-mobile-default-settings: better descriptions describing target MIDs https://bugs.launchpad.net/bugs/275299 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 261190] Re: problems witht cell!=default
** Also affects: gridengine (Debian) Importance: Undecided Status: New -- problems witht cell!=default https://bugs.launchpad.net/bugs/261190 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262858] [NEW] typo in package description
Public bug reported: Binary package hint: firefox-3.0 It says: ... Install this firefox package too, [for auto upgrades] It should say: Install the firefox ... I had to re-read it a couple times to figure out it was a typo and not trying to say something about this (firefox-3.0) package! This is related to https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/88232 but that's about the editorial decisions on the content of the message. (BTW, I think the current description is pretty good. esp. just saying it's designed to be light weight, not claiming that it actually is. :) ** Affects: firefox-3.0 (Ubuntu) Importance: Undecided Status: New -- typo in package description https://bugs.launchpad.net/bugs/262858 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 261190] Re: problems witht cell!=default
sent email to Debian Grid Engine Maintainers <[EMAIL PROTECTED]> to notify them of this and the csh dep bug. The bugs are too small to be worth filing on the Debian BTS too. BTW, I'm now sure that the chmod thing was the cause of my problems with CELL != default. It would be good if the prompts told you that most people do use CELL=default, not their hostname or anything. -- problems witht cell!=default https://bugs.launchpad.net/bugs/261190 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263747] [NEW] linux 2.6.27-2.3: pcspkr should be enabled too, now that snd-pcsp is blacklisted by default
Public bug reported: linux 2.6.26-3.9 changes: ... * config: Disable pcspkr (in favor of snd-pcsp) module-init-tools 3.3-pre11-4ubuntu9 changes: * Blacklist snd_pcsp by default. When I upgraded my Hardy system to the Intrepid kernel (with Hardy's module-init-tools), snd-pcsp was alsa card0. :( So yeah, blacklist it. But my machine doesn't beep, because pcspkr isn't built anymore. :( I don't want my system beeps to come out my speakers. I haven't checked the config of -server kernels, but it would definitely be appropriate for them to use the pcspkr beep. In Hardy, snd-pcsp is in linux-ubuntu-modules-...-generic, and pcspkr is in linux-image-...-generic possibly related bug: kernel loads pcspkr module even when blacklisted (maybe someone decided to not build pcspkr even as a module) https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/83512 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- linux 2.6.27-2.3: pcspkr should be enabled too, now that snd-pcsp is blacklisted by default https://bugs.launchpad.net/bugs/263747 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263747] Re: linux 2.6.27-2.3: pcspkr should be enabled too, now that snd-pcsp is blacklisted by default
> We simply do not want pcspkr enabled by default. Couldn't you build it and blacklist it, like with snd-pcsp? Or is that open bug about not obeying the blacklist why it's not built at all? (hmm, is it maybe getting loaded in the initramfs, which doesn't have the blacklist? Because it's an "input" module?) > Too many people complain about it. I guess I'm pretty old-school, liking my computers to beep. But not having it come out my main speakers means that the volume setting on my speakers doesn't matter, and it works even when my speakers are in optical input mode, and mplayer is sending them DTS audio over TOSLINK. I'll try snd-pcsp again, but before I upgraded module-init-tools, snd- pcsp became alsa card0, which is horrible. Probably it won't be too hard to config things so that's not the case, but I'd rather alsa didn't know about it at all. happy hacking, -- linux 2.6.27-2.3: pcspkr should be enabled too, now that snd-pcsp is blacklisted by default https://bugs.launchpad.net/bugs/263747 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264290] [NEW] linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive
Public bug reported: I tried Intrepid's kernel on my Hardy C2Duo system. I ran into a serious problem: sometimes the kernel would stop receiving keyboard events. I think this behaviour is related to CPU load and a faulty temperature reading. e.g. after pressing "+" in aptitude (triggering some dependency calculations), the key release event would go unnoticed. I was in X running gnome-terminal, so I could click on another tab (the mouse was unaffected), and the "+" characters would be visible. (That's how I'm sure it wasn't some other sort of hang.) The kernel log shows messages like INFO: task xfsdatad/0:7209 blocked for more than 120 seconds. ...stack backtrace ... INFO: task java:11768 blocked for more than 120 seconds. ... (full log attached, see below). I've never seen anything like that before, in over 2 years of stable operation on this hardware. 2.6.27... ran fine overnight and through a day (without interactive use except a big soon after boot) just running azureus (java bittorrent). I only started to notice problems after 7-zipping something, and making the CPU work. After I noticed the pausing behaviour, I thought the machine might be overheating, and sensors (reading the coretemp module) showed my idle CPU temp at ~60, and my load CPU temp at ~80, even when I turned up my CPU and case fans to full speed. Normally I max out at 70 with fans at slow speed, running two instances of burnP6. In case it matters, I hadn't updated module-init-tools to the Intrepid version yet. I'm pretty sure I was able to reproduce the key sticking after doing that and booting again, though, but I didn't run long enough to see any backtraces in the kernel log. It turns out that Hardy's 2.6.24 reads 15C cooler than Intrepid's 2.6.27, and that the BIOS on my mobo agrees with the lower number: idle at ~45C. There was a big update to the coretemp driver between Hardy and Intrepid, and I bet it's the cause of the change in behaviour. (Changelog-2.6.25) commit bfe38ccf8d0b541f387f65267f6f3794be59233a Merge: 20f8d2a... 25e9c86... Author: Linus Torvalds <[EMAIL PROTECTED]> Date: Thu Feb 21 16:37:42 2008 -0800 Merge branch 'release' of git://lm-sensors.org/kernel/mhoffman/hwmon-2.6 * 'release' of git://lm-sensors.org/kernel/mhoffman/hwmon-2.6: hwmon: normal_i2c arrays should be const hwmon: New driver for Analog Devices ADT7473 sensor chip hwmon: (coretemp) Add Penryn CPU to coretemp hwmon: (coretemp) Add TjMax detection for mobile CPUs hwmon: (applesmc) sensors set for MacBook2 hwmon: (thmc50) Storage class should be before const qualifier hwmon: (coretemp) fix section mismatch warning hwmon: (coretemp) Add maximum cooling temperature readout hwmon: (adm1026) Properly terminate sysfs groups hwmon: (vt8231) Update maintainer email address hwmon: (vt8231) Add individual alarm files hwmon: (via686a) Add individual alarm files hwmon: (smsc47m1) Add individual alarm files hwmon: (max1619) Add individual alarm and fault files hwmon: (lm92) Add individual alarm files (coretemp has to guess how to interpret the temp number it gets from the hardware, hence the coretemp coretemp.0: Using relative temperature scale! With 2.6.24, the output includes: coretemp-isa- Adapter: ISA adapter Core 0: +42.0°C (crit = +85.0°C) On 2.6.27, the output was something like : Core 0: +60.0°C (high = +86°C) (crit = +100.0°C) and similar for Core 1. I don't know why a bogus temp reading would make the system go crazy and hang for a long time, unless this temp is somehow communicated to ACPI, or Linux does something to try to throttle. My BIOS doesn't have ACPI thermal support: /proc/acpi/thermal_zone/ is empty, even though thermal.ko is loaded. My hardware is an Intel DG965WH motherboard (g965 chipset) with BIOS Version: MQ96510J.86A.1751.2008.0811.0002Release Date: 08/11/2008 E6600 CPU (C2D @ 2.4GHz, 4MB cache). 4GB of RAM. It's late and I might be forgetting something. I'll look over this later... ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive https://bugs.launchpad.net/bugs/264290 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264290] Re: linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive
** Attachment added: "kern.log with two boots of 2.6.27-2-generic" http://launchpadlibrarian.net/17260679/kern.log.0 -- linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive https://bugs.launchpad.net/bugs/264290 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264290] Re: linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive
BTW, this is _not_ like https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/158585 That bug seems to be machines that actually are running too hot. cpufreq with the ondemand governor idles my CPU at 1.6GHz. And like I said, 2x burnP6 only takes me up to 72C, as reported by sensors/coretemp on 2.6.24. -- linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive https://bugs.launchpad.net/bugs/264290 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 261190] Re: problems witht cell!=default
fixed in Debian's 6.2-2, along with a documentation bug I reported to Debian's BTS. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497103 The depend-on-csh bug isn't fixed, though. -- problems witht cell!=default https://bugs.launchpad.net/bugs/261190 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 261190] Re: problems witht cell!=default
Debian released the fix for this in 6.2-2 ** Changed in: gridengine (Debian) Status: New => Fix Released ** Changed in: gridengine (Ubuntu) Status: New => Confirmed -- problems witht cell!=default https://bugs.launchpad.net/bugs/261190 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 261247] Re: gridengine-execd should depend on csh
** Bug watch added: Debian Bug tracker #497839 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497839 ** Also affects: gridengine (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497839 Importance: Unknown Status: Unknown ** Changed in: gridengine (Ubuntu) Status: New => Confirmed -- gridengine-execd should depend on csh https://bugs.launchpad.net/bugs/261247 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264866] [NEW] qrsh doesn't work
Public bug reported: see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497855 Intrepid probably shouldn't release this gridengine without another update from Debian, given this and the other packaging bugs that have been fixed recently. The new upstream version (beta2 -> stable) doesn't hurt either. ** Affects: gridengine (Ubuntu) Importance: Undecided Status: New ** Affects: gridengine (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #497855 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497855 ** Also affects: gridengine (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497855 Importance: Unknown Status: Unknown -- qrsh doesn't work https://bugs.launchpad.net/bugs/264866 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 266935] [NEW] mkbootserver broken: uses old unsupported cut(1) syntax
Public bug reported: systemimager-server3.2.3-3 on AMD64 Hardy. $ sudo mkbootserver --interface=bond0 --tftpdir=/srv/tftpboot This script may modify the following files: /etc/services /etc/inetd.conf /etc/xinetd.d/tftp You should already have a kernel and ramdisk to use. Do you wish to continue (y/[n])? y Ok, continuing... Checking for a tftp server... found. Checking if tftp server is H. Peter Anvin's tftp server... doesn't look like it. Checking if tftp server is atftpd... yup - right on! Checking for a running inetd... cut: fields and positions are numbered from 1 Try `cut --help' for more information. Not found. Checking for a running xinetd... cut: fields and positions are numbered from 1 Try `cut --help' for more information. Not found. Looking for update-inetd... found. Updating inetd.conf... done. No superserver found, so nothing to reload Attempt to configure inetd failed. ** Affects: systemimager (Ubuntu) Importance: Undecided Status: New ** Description changed: + systemimager-server3.2.3-3 on AMD64 Hardy. + $ sudo mkbootserver --interface=bond0 --tftpdir=/srv/tftpboot This script may modify the following files: /etc/services /etc/inetd.conf /etc/xinetd.d/tftp You should already have a kernel and ramdisk to use. Do you wish to continue (y/[n])? y Ok, continuing... Checking for a tftp server... found. Checking if tftp server is H. Peter Anvin's tftp server... doesn't look like it. Checking if tftp server is atftpd... yup - right on! Checking for a running inetd... cut: fields and positions are numbered from 1 Try `cut --help' for more information. Not found. Checking for a running xinetd... cut: fields and positions are numbered from 1 Try `cut --help' for more information. Not found. Looking for update-inetd... found. Updating inetd.conf... done. No superserver found, so nothing to reload Attempt to configure inetd failed. -- mkbootserver broken: uses old unsupported cut(1) syntax https://bugs.launchpad.net/bugs/266935 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 252174] Re: gvfsd-trash crashed with SIGSEGV in g_main_context_dispatch()
I hit this on a clean boot of the Intrepid alpha5 desktop i386 livecd. (from a USB drive with isoscan/filename=...) It looks identical to Steve's original report, except mine receives the segv in g_main_context_prepare(). I also get segvs in fast-user-switcher-applet whenever I click on it. It looks like https://bugs.launchpad.net/ubuntu/+source/fast-user-switch-applet/+bug/262532 The stack trace is 0x08056366 in ?? () ... (3 more times, with different addresses that I'm not going to type out) 0xb7881cda in g_cclosure_marshal_VOID__OBJECT () from /usr/lib/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 -- gvfsd-trash crashed with SIGSEGV in g_main_context_dispatch() https://bugs.launchpad.net/bugs/252174 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 266935] Re: mkbootserver broken: uses old unsupported cut(1) syntax
The Debian package is orphaned by the maintainer, so this may be a lost cause. see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=417911 -- mkbootserver broken: uses old unsupported cut(1) syntax https://bugs.launchpad.net/bugs/266935 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128492] Re: Please upgrade to latest version
The Debian package is orphaned. see http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=417911 AMD64 Hardy has version 3.2.3-3 un systemimager-bin-i386 (no description available) ii systemimager-boot-i386-sta 3.2.3-3SystemImager boot binaries for i386 client nodes un systemimager-boot-ia64-sta (no description available) un systemimager-boot-standard (no description available) ii systemimager-common3.2.3-3Utilities and libraries common to both the server and client un systemimager-initrd-i386(no description available) un systemimager-kernel-i386(no description available) ii systemimager-server3.2.3-3Automate GNU/Linux installs and upgrades over a network ii systemimager-server-flamet 3.2.3-3SystemImager boot binaries for i386 client nodes I haven't even gotten it to work yet... -- Please upgrade to latest version https://bugs.launchpad.net/bugs/128492 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125687] Re: Samba does not start on boot.
> This should be already fixed in hardy. It isn't totally fixed, unless samba is supposed to start before interfaces are configured by DHCP, and that doesn't count as a bug. my smb.conf has interfaces = 127.0.0.1/8 10.255.255.255/8 bind interfaces only = true so eth0 _has_ to be up and configured by DHCP before smbd starts, or it will end up listening only on the loopback interface. I put this hack at the end of my /etc/rc.local (sleep 60 && /etc/init.d/samba restart)& After every boot, one of smbd and nmbd has already exitted by the time the restart happens. Sorry I don't remember which. My hack does get both started properly, though, since networking is always up by then. debsums -a samba shows that my /etc/init.d/samba is the Ubuntu package version (3.0.28a-1ubuntu4.4). ** Changed in: samba (Ubuntu) Status: Fix Released => In Progress -- Samba does not start on boot. https://bugs.launchpad.net/bugs/125687 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 267987] [NEW] blobandconquer: non-free.
Public bug reported: Binary package hint: blobandconquer also, v1.0 is released upstream, but with non-free data files from http://www.parallelrealities.co.uk/blobAndConquer.php: --- License Source code is distributed under the GNU General Public License. Resources are Non Free. This game should not be added to Linux distributions or respositories. --- see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495531 ** Affects: blobandconquer (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: blobandconquer (Debian) Importance: Unknown Status: New ** Bug watch added: Debian Bug tracker #495531 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495531 ** Also affects: blobandconquer (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495531 Importance: Unknown Status: Unknown ** Changed in: blobandconquer (Ubuntu) Status: New => Confirmed -- blobandconquer: non-free. https://bugs.launchpad.net/bugs/267987 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268005] [NEW] live cd from nfsroot breaks the nfs mount during bootup
Public bug reported: Binary package hint: network-manager I'm half guessing that this is N-M's bug, so it may need to be reassigned. I've been trying to boot the Intrepid Desktop i386 (alpha5) LiveCD from a NFS/TFTP/DHCP server (i.e. PXE). I can netboot the Intrepid live CD, accessing filesystem.squashfs over nfs (mounted by the initramfs, so not nfsroot by all definitions). The problem is that after the init scripts are done, the NFS mount is dead, and all I/O hangs forever. cat is usually in the cache, so I can even cat /var/log/kern.log, and files in /proc, like /proc/mounts, but if tab-completion accesses anything from filesystem.squashfs, the tty is tied up permanently. /etc/init.d/NetworkManager runs late in the boot sequence, so it's possible that all the scripts after it are already cached locally. Or that it doesn't break the network until later. Or maybe it's not N-M's fault at all. So you only get 6 tries after switching away from X (which manages to start up far enough to show a blank orange screen and start spinning the cursor). Running things in the background in case they hang works, but tab-completion will still hang your shell. /proc/mounts doesn't indicate any problems, and the NFS mount looks up. I don't know what to cat in /proc or /sys to duplicate the info I'd get from ifconfig. (neither it nor ip(8) are in the cache.) This is a really hard problem to debug... TORAM=yes might help, but it doesn't seem to do anything. (There is code that looks for that env var, even if toram isn't parsed by /init.) Probably the thing to do would be to mount a local filesystem somewhere and run binaries from it. It's definitely an init script that breaks the NFS mount, because booting with init=/bin/bash drops me to a shell after the initramfs does its thing. Then I can run find over the whole squashfs filesystem with no problems. My client machine (holly) PXE boots, and my pxelinux.cfg/default looks like DEFAULT menu.c32 SAY press return for menu prompt 1 LABEL intrepid-i386 kernel intrepid-i386/vmlinuz append boot=casper netboot=nfs nfsroot=10.0.0.17:/mnt/GP1TB/srv/intrepid-a5-i386 initrd=intrepid-i386/initrd.gz -- # other useful args: text to not start gdm ...other LABELs Everything is set up properly so it loads vmlinuz and initrd.gz that were unpacked from /casper in the intrepid iso image. I've been netbooting Debian installers and whatnot for years, and I'm sure I didn't get that part wrong. BTW, I had to search for a while and eventally read /init to figure out the right boot args, if those even are all the boot args needed. I found lots of older docs, e.g. for feisty and Gutsy. I guess I should have looked at initramfs(8), although it doesn't say what combination you need exactly for NFS root to work. 10.0.0.17:/... is where I unpacked the whole ISO (with 7z x intrepid- desktop-i386.iso). casper/filesystem.squashfs exists under that. /mnt/GP1TB is exported to the subnet that the client is on. I unpacked the CD instead of exporting a loopback mount of the iso image to rule out any possibility of problems on the NFS server side. Unsurprisingly, I get the same results if I boot the same kernel and initrd with the same args, but from syslinux on a USB stick instead of pxelinux. I've tried this on two different clients with identical results: a Dell PE1950 server at work (dual bnx2 gigE onboard), and an Asus K8V (Marvell Yukon gigE onboard, no other NICS) at home. So it's not a eth0/eth1 confusion problem, because my home machine only has an eth0. I use NFS all the time between my home machines, so I'm confident there's nothing wrong with the network or my NFS setup. (NFS server (tesla) is running linux Ubuntu 2.6.24-21.42-generic, boot server (llama) is running dnsmasq 2.43-1~bpo40+1 on Debian Etch. Etch's pxelinux, too, except Hardy's at work and when booting syslinux from USB...) LiveCD netbooting used to work as late as Gutsy. see https://wiki.ubuntu.com/LiveCDNetboot. It doesn't work with Hardy, either, but I haven't tried as hard to see if maybe a different combination of kernel params would work. I haven't managed to get Hardy as far as NFS mounting the squashfs, so it's problems aren't due to any init scripts. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- live cd from nfsroot breaks the nfs mount during bootup https://bugs.launchpad.net/bugs/268005 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268005] Re: live cd from nfsroot breaks the nfs mount during bootup
I thought of a way to debug this: hit alt+sysrq+e to send a sigterm to all tasks while init scripts are running, but before NetworkManager starts. I tried it after booting with TORAM=yes, since it seemed to be hung there. It actually works, and I'm running from a filesystem.squashfs that was loaded to tmpfs. So I manually ran some sudo /etc/rc2.d/whatever start, and after starting dbus then NetworkManager, I see that ifconfig shows eth0 go down for a short while after N-M's start script runs. For netbooting the livecd to work, we need a way to prevent N-M from running, or at least from doing this. Or we need NFS mounts that survive the interface going down then up. In fact I'm a bit surprised it doesn't seem to survive. (since I booted with TORAM=yes, I didn't have any NFS mounts when I was running the init scripts.) -- live cd from nfsroot breaks the nfs mount during bootup https://bugs.launchpad.net/bugs/268005 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264290] Re: linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive
I tried this again: I booted the i386 Intrepid alpha5 CD, and installed lm-sensors. My idle temps are still 59C, which doesn't agree with the BIOS or 2.6.24, which idles at ~42C (coretemp sensor).2x burnP6 only gets me up to 72C on each core. Ambient temp is somewhat lower than before... I haven't seen the keyboard-sticking behaviour at all, so it's either the lower reported temps or maybe i386 kernels don't show that problem. -- linux 2.6.27-2.3: coretemp reads 15C too hot, and keyboard is occasionally unresponsive https://bugs.launchpad.net/bugs/264290 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25496] Re: toRam or copy2Ram (run ubuntu live from ram)
It sort of works to boot Intrepid's livecd with TORAM=yes, but you have to give it a kick with ALT+SYSRQ+E when it gets stuck after the message from the squashfs module. The code for doing stuff if $TORAM is set (to non-zero length, IIRC) is there, but nothing sets $TORAM. So do it yourself from the kernel command line. /init inherits kernel params as env vars, and /scripts/casper inherits them too. I have booted an i386 with 1.5GB of RAM from Intrepid alpha5 on a USB stick, with TORAM=yes + a sysrq kick, and it did work. -- toRam or copy2Ram (run ubuntu live from ram) https://bugs.launchpad.net/bugs/25496 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268005] Re: live cd from nfsroot breaks the nfs mount during bootup
The Hardy netboot issues can be debugged by booting with break=mount debug=y, then running t=/dev/tty2; sh <$t >$t 2>$t & # repeat for tty3 if you want exit boot will continue, and hang because the network is down. You can debug by switching to another console and looking at /casper.log (where stdout and stderr are redirected). Some script tries to switch to manual mode when nfsroot booting, so ifup doesn't screw it up later. I guess if you don't put ip=something (other than dhcp) on the commandline, Hardy won't nfsroot boot. This is not the NetworkManager issue, and is not present in Intrepid. I only mention it because Hardy is an LTS release, so it people may be trying to mess around with it on servers for a while... Hmm, Hardy might be failing because it tries to use eth0, while the network cable is plugged in to eth1, according to its detection order. (I haven't tried netbooting Hardy at home, only on a Dell PE1950 with dual bnx2 NICs.) Intrepid detects the ports in the opposite order, with eth0 as the port marked GbE 1 (of 2) on the back, and which has the lower MAC address. I plugged my cables into GbE 1 since the BIOS defaults to netbooting from that interface, but not the other one, among other reasons. So anyway, maybe it's just Hardy's bad luck, and Intrepid would have the same problem if it needed to use eth1. -- live cd from nfsroot breaks the nfs mount during bootup https://bugs.launchpad.net/bugs/268005 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258469] Re: need to blacklist software direct rendering, e.g. ATI ES1000
I wasn't able to try this again until now, since I had limited time in the machine room and I had trouble netbooting a livecd. (see https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/268005...) This bug doesn't seem to be present on this hardware anymore in the i386 Hardy alpha5 livecd. I've booted i386 Hardy alpha5 without compiz problems on a machine with a NVidia 7600GT AGP, too. (nice UI for suggesting the non-free drivers for desktop-effects, BTW.) On the Dell PE1950 (ATI ES1000): $ xdriinfo driver 0 Xlib: extension "XFree86-DRI" missing on display ":0.0". Screen "0" is not direct rendering capable. and indeed, xdpyinfo doesn't show XFree86-DRI among the loaded extensions. Even though Xorg.0.log has a line that says "(II) Loading extension XFree86-DRI". It does still have all the stuff about setting up the swrast dri provider, though. glxinfo says "direct rendering: Yes" (Mesa Project Software Rasterizer), just like on my NVidia desktop. The SGI-GLX extension is present. I booted Intrepid i386 alpha4 again, and the gray-screen bug is still there. It shows the same thing for xdriinfo, and XFree86-DRI is not present. I can easily boot Intrepid with nfsroot now. Actually, I'll just leave it running on perun03 until I make some more progress cloning my Ubuntu server install onto the rest of the nodes. So now's a great time to ask me for any info... Do you need the Xorg.0.log from alpha5? I didn't see any diffs that looked important... -- need to blacklist software direct rendering, e.g. ATI ES1000 https://bugs.launchpad.net/bugs/258469 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 229732] Re: USB Keyboard drivers not loaded in initramfs
This is only a problem with break=premount or earlier. break=mount happens after hal/udev have loaded drivers for everything. Note that some servers don't _support_ ps/2 keyboards anymore. e.g. I have a rack of Dell PE1950 machines with a KVM-over-IP that connects to 1 USB port and their VGA out. I don't think the PE1950 even has a PS/2 port anywhere. The best fix for this is probably in scripts/functions:panic(). It already does modprobe i8042 modprobe atkbd before dropping to a shell. So just add maybe modprobe ehci-hcd modprobe hid to that. I think that's right. I'll see if I can boot a machine with a ps/2 and usb kbd attached, and load modules until the USB kbd starts working at break=premount. Hmm, I don't know how to detect the right USB controller module. ehci- hcd is for usb2.0 machines, and older hardware only has uhci-hcd or ohci-hcd. There might be laptops with no ps/2 ports, broken internal keyboards, and only USB1.1 support. Other than that, this fix would be enough for most people, since USB keyboards are most often used on newer computers. At least USB1.1 computers will have PS/2 ports... ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- USB Keyboard drivers not loaded in initramfs https://bugs.launchpad.net/bugs/229732 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268005] Re: live cd from nfsroot breaks the nfs mount during bootup
I have a workaround for nfsroot booting Intrepid: boot with break=init touch /cow/etc/init.d/NetworkManager exit You will boot normally, but N-M won't run (because files in /cow take precedence over files in filesystem.squashfs, so it's init script is empty). -- live cd from nfsroot breaks the nfs mount during bootup https://bugs.launchpad.net/bugs/268005 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268005] Re: live cd from nfsroot breaks the nfs mount during bootup
Any way of preventing NetworkManager from starting (or from bringing your interface down and then up) is sufficient. Or maybe just pre- caching the files it will try to access while the network is down, if N-M gets stuck trying to access some files while the network is down. -- live cd from nfsroot breaks the nfs mount during bootup https://bugs.launchpad.net/bugs/268005 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 25496] Re: toRam or copy2Ram (run ubuntu live from ram)
> I have booted an i386 with 1.5GB of RAM from Intrepid alpha5 on a USB stick, with TORAM=yes + a sysrq kick, and it did work. Actually, what worked was PXE booting with TORAM=yes. TORAM=yes doesn't work with isoscan/filename=, which is how I had my USB drive set up. -- toRam or copy2Ram (run ubuntu live from ram) https://bugs.launchpad.net/bugs/25496 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 229732] Re: USB Keyboard drivers not loaded in initramfs
I booted a machine with a USB and a PS/2 keyboard from an i386 Intrepid alpha5 USB drive, with break=premount. panic() should run (after the modprobe for ps/2 keyboards): if ! grep -q '^H:.*kbd' /proc/bus/input/devices ; then # no keyboard? Try USB. modprobe uhci-hcd modprobe ohci-hcd modprobe usbhid fi The line we want to match with grep is H: Handlers=kbd (that line has a trailing space.) In a fully running kernel, the line is e.g. H: Handlers=kbd event1 It's ok to load both USB modules, esp. since this only happens with break=whatever, or some other panic. So they won't be loaded for most people's normal boots. When we're trying handle errors, it's better to be safe. And it won't load anything extra if a keyboard of any kind is known to the kernel, thanks to grep on /proc/bus/input/devices. I'm not aware of USB host drivers other than ohci and uhci; They should work for almost all hardware ever. ehci-hcd isn't needed for keyboards, and is not sufficient for using them. I guess it _only_ handles USB2.0 HighSpeed devices. After modprobing both USB HCD drivers, I exitted from the break=premount shell, and the boot continued normally from my USB drive. ehci-hcd was loaded properly and both keyboards work after boot. (K8V mobo, Via K8T800 chipset.) -- USB Keyboard drivers not loaded in initramfs https://bugs.launchpad.net/bugs/229732 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 229732] Re: USB Keyboard drivers not loaded in initramfs
** Tags added: patch ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => In Progress -- USB Keyboard drivers not loaded in initramfs https://bugs.launchpad.net/bugs/229732 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 268005] Re: live cd from nfsroot breaks the nfs mount during bootup
Hardy does not suffer from this bug. The problems I was having with Hardy were https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/182940, because as I said, Hardy's kernel detected interfaces in opposite order to how they're labeled on the chassis. I netboot Hardy at home on my single-NIC desktop with no problems. -- live cd from nfsroot breaks the nfs mount during bootup https://bugs.launchpad.net/bugs/268005 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258469] Re: need to blacklist software direct rendering, e.g. ATI ES1000
It's not running. ps axuw | grep compiz doesn't return anything. And the visual effects radio button on gnome-appearance-properties is set to "none". Setting it to "normal" makes the screen go gray, then ~10 seconds later back to normal with the radio button switched back to "none". I didn't see the gray during bootup, so I don't think compiz even tried then. There was no mention of compiz in any log files, or .xsession-errors, until after trying to enable it. Then it does have some compiz log messages. stuff like: compiz.real (video) - Warn: No 8 bit GLX pixmap format, disabling YV12 image format and a bunch of failures to init things. -- need to blacklist software direct rendering, e.g. ATI ES1000 https://bugs.launchpad.net/bugs/258469 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258469] Re: need to blacklist software direct rendering, e.g. ATI ES1000
unless this is a problem on other video cards that don't do 3D, this is fixed. ** Changed in: compiz (Ubuntu) Status: Incomplete => Fix Released -- need to blacklist software direct rendering, e.g. ATI ES1000 https://bugs.launchpad.net/bugs/258469 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 5944] Re: init script disregards NFSROOT=auto option in some cases
This bug is a feature request for backward-compatible cmdline parsing. NFSROOT is not a documented parameter in initramfs-tools(8), only nfsroot. IMHO, people who have old ROMs that append stuff that's no longer compatible with current initramfs should do a two stage boot: have their ROM load pxelinux or something that can boot linux with the right parameters. AFAIK, this is possible. If it wasn't, I'd be more inclined to agree with the backward compat request. ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Invalid -- init script disregards NFSROOT=auto option in some cases https://bugs.launchpad.net/bugs/5944 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104697] Re: Include filesystem checking utilities into initramfs
posted to brainstorm as http://brainstorm.ubuntu.com/idea/13027/ -- Include filesystem checking utilities into initramfs https://bugs.launchpad.net/bugs/104697 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93471] Re: /bin/sh:can't access tty; job control turned off
submitter says it's fixed for him. BTW, it's ok to change the status of your own bugs. just click on the status line on launchpad, etc... ** Changed in: initramfs-tools (Ubuntu) Status: New => Fix Released -- /bin/sh:can't access tty; job control turned off https://bugs.launchpad.net/bugs/93471 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263745] Re: ubuntu intrepid Alpha 4 64bit live cd-no ide disks only sata
> ... but listed in /dev/disk/by-uuid and id but not when doing ls -l /dev/disk/by-uuid ... huh? Are you saying there are entries for your PATA disks in /dev/disk /by-uuid, but ls -l doesn't list them? What kind of PATA controller? post lspci output. (sorry, I don't feel like reading MSI's web site to find out what kind of PATA controller your mobo has.) Intel southbridges since ICH8 have no PATA ports, so mobos usually include a third-party controller. What driver does the hardy kernel use to for your PATA controller? probably Intrepid's kernel isn't detecting your controller. Also, please try again with with Intrepid alpha5, since it has a new kernel (linux 2.6.27). -- ubuntu intrepid Alpha 4 64bit live cd-no ide disks only sata https://bugs.launchpad.net/bugs/263745 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 263745] Re: ubuntu intrepid Alpha 4 64bit live cd-no ide disks only sata
This is a linux bug, if linux doesn't detect your hard drives. The linux package encompasses all the modules and config for loading them. except blacklists in module-init-tools. upgrade that and initramfs- tools to intrepid, too. ** Changed in: linux (Ubuntu) Sourcepackagename: casper => linux -- ubuntu intrepid Alpha 4 64bit live cd-no ide disks only sata https://bugs.launchpad.net/bugs/263745 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 162594] Re: audacity does not play a sound since Gutsy upgrade
AFAIK, Ubuntu wants everything that outputs sound to go through pulseaudio. (a software mixing daemon). Not everything supports pulse, though, and will find the audio device unavailable if something else already has it open through pulse. sudo lsof /dev/snd/* will almost always tell you what process you need to stop to free up the audio device, if you don't want to convert everything to pulseaudio. Or I think it's appropriate to report bugs on any program that doesn't/can't use pulseaudio by default. -- audacity does not play a sound since Gutsy upgrade https://bugs.launchpad.net/bugs/162594 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
