[Bug 446329] Re: udev output at bootup: NAME=%k is superfluous
I see the message too. lvm2 is the wrong package, though. pe...@tesla:~$ dpkg -S /etc/udev/rules.d/50-kvm.rules kvm: /etc/udev/rules.d/50-kvm.rules ** Package changed: lvm2 (Ubuntu) = kvm (Ubuntu) -- udev output at bootup: NAME=%k is superfluous https://bugs.launchpad.net/bugs/446329 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 472080] [NEW] Installs symlinks to files in non-dependency libkadm5clnt6
Public bug reported: Binary package hint: libkrb5-dev Found with cruft(8). $ find -L $(dpkg -L libkrb5-dev) -maxdepth 0 -type l -ls 168769880 lrwxrwxrwx 1 root root 19 Oct 31 15:35 /usr/lib/libkadm5clnt.so - libkadm5clnt.so.6.0 $ apt-file search libkadm5clnt.so.6.0 libkadm5clnt6: /usr/lib/libkadm5clnt.so.6.0 So probably libkrb5-dev should depend on libkadm5clnt6 as well as libkadm5srv6. Or maybe not, I don't know how this is supposed to work. I only have libkrb5-dev installed because libcurl4-openssl-dev pulls it in. ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New -- Installs symlinks to files in non-dependency libkadm5clnt6 https://bugs.launchpad.net/bugs/472080 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 472969] [NEW] installs a broken man-page symlink
Public bug reported: Binary package hint: qemu-kvm found with cruft(8) $ find -L $(dpkg -L qemu-kvm) -maxdepth 0 -type l -ls 31129340 lrwxrwxrwx 1 root root 10 Oct 31 15:41 /usr/share/man/man1/kvm-nbd.1 - qemu-nbd.1 correct target is /usr/share/man/man8/qemu-nbd.8.gz ii qemu-kvm0.11.0-0ubuntu6.1 Full virtualization on i386 and amd64 hardware ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- installs a broken man-page symlink https://bugs.launchpad.net/bugs/472969 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 472080] [NEW] Installs symlinks to files in non-dependency libkadm5clnt6
On Tue, Nov 03, 2009 at 06:34:23PM -, Sam Hartman wrote: -Source: krb5 +8Source: krb5 Is that a typo? happy hacking, -- #define X(x,y) x##y Peter Cordes ; e-mail: X(pe...@cor , 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 -- Installs symlinks to files in non-dependency libkadm5clnt6 https://bugs.launchpad.net/bugs/472080 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1395269] [NEW] ethtool -t eth0 offline loses routing table
Public bug reported: ethtool -t eth0 offline does the tests, but leaves the routing table with only the entry for the local network. I had to sudo route add default gw 10.0.0.1, in my case. The online test didn't do this. Ubuntu 14.04, ethtool 1:3.13-1 Linux tesla 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ethtool -i eth0: driver: e1000e version: 2.3.2-k firmware-version: 1.1-0 bus-info: :00:19.0 relevant kernel log: [637008.472410] e1000e :00:19.0 eth0: offline testing starting [637009.077985] e1000e :00:19.0 eth0: testing unshared interrupt [637022.468941] e1000e :00:19.0: irq 45 for MSI/MSI-X [637022.572094] e1000e :00:19.0: irq 45 for MSI/MSI-X [637022.572257] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [637037.432893] e1000e: eth0 NIC Link is Up 10 Mbps Full Duplex, Flow Control: Rx/Tx [637037.433003] e1000e :00:19.0 eth0: Link Speed was downgraded by SmartSpeed [637037.433005] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO [637037.433035] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [637037.982611] net_ratelimit: 3 callbacks suppressed [637037.982623] IPv4: martian source 10.0.0.17 from 80.73.161.44, on dev eth0 [637037.982628] ll header: : 00 19 d1 11 b4 9b 00 03 6d 11 34 1b 08 00 m.4... (the martian packets are from TCP connections that my router is still NATing to this machine, even though without its routing table, it's not happy to see them.) And yes, my e1000e is autonegotiating to 10baseT/Full on the same cables and switch that still works at 1000baseT with another machine, hence running self-tests... I thought this machine used to run at 1000baseT, weird if I went 5 years without noticing my desktop being slow. Not what this bug report is about, though. The e1000e hardware is on a DG965WH Intel mobo (ICH8 / g965 graphics, first-gen core2) 00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 02) Subsystem: Intel Corporation Device 0001 Flags: bus master, fast devsel, latency 0, IRQ 45 Memory at e030 (32-bit, non-prefetchable) [size=128K] Memory at e0324000 (32-bit, non-prefetchable) [size=4K] I/O ports at 20e0 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: e1000e $ ethtool eth0 Settings for eth0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Full 100baseT/Full 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Speed: 10Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: on (auto) Cannot get wake-on-lan settings: Operation not permitted Current message level: 0x0007 (7) drv probe link Link detected: yes Appears to be the same problem as someone reported to Redhat a while ago, which got marked as fixed for the igb driver https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=661976 Not very useful info in their BTS, because the bug that it's a dup of is now flagged private, so nobody can even look at it. Possibly this is a per-driver thing, unless the right fix is to have ethtool save/restore the routing table entries for that iface. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ethtool 1:3.13-1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Sat Nov 22 03:00:35 2014 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.3 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.3 SourcePackage: ethtool UpgradeStatus: Upgraded to trusty on 2014-07-14 (130 days ago) ** Affects: ethtool (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ethtool in Ubuntu. https://bugs.launchpad.net/bugs/1395269 Title: ethtool -t eth0 offline loses routing table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ethtool/+bug/1395269/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1095180] Re: incorrect bash-completion for sudo
It's a corner case of a directory in the current directory having the
same name as a command. The directory entry is superseding the command
completion.
If you sudo ettab you get a list of completions. In /etc, the only
entry for etckeeper is with a trailing /, rather than having an entry
for the command AND an entry for the directory. If you are cded to
somewhere without an etckeeper directory present, etckeeper is fine.
This happens with completion for any commands flagged to take another command
as their first argument. simple testcase:
mkdir apt-g{,et}
nice apt-gtab = lists apt-g/ apt-get/
nice apt-getab = nice apt-get/
Probably fixable without disabling completing filenames as a fallback,
IDK. _command_offset() is pretty complex, I'm prob. not going to try to
fix it myself.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to etckeeper in Ubuntu.
https://bugs.launchpad.net/bugs/1095180
Title:
incorrect bash-completion for sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1095180/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1095180] Re: incorrect bash-completion for sudo
The bug is in the core code of bash_completion, in the functions that handle commands that take other commands as their arguments, e.g. sudo, nice, and so on. Marked invalid for the etckeeper package, but still confirmed for bash-completion. (I hope I'm doing this right. If there's a way to un-assign it from etckeeper altogether, that would be best). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1095180 Title: incorrect bash-completion for sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1095180/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1095180] Re: incorrect bash-completion for sudo
reported upstream as https://alioth.debian.org/tracker/index.php?func=detailaid=314893group_id=100114atid=413095 ** Bug watch added: alioth.debian.org/ #314893 http://alioth.debian.org/support/tracker.php?aid=314893 ** Changed in: etckeeper (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1095180 Title: incorrect bash-completion for sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1095180/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 106975] Re: mysqldump lacks bash completion script
reassigning this to mysql. Packages can provide their own completion rules and install them with dh_bash-completion. Not every tool needs to have its completions shipped in bash-completions to be installed on every system regardless of whether the tool is installed or not. There's already a script that someone wrote, just toss that into the mysql packaging, or submit it upstream. ** Tags added: patch ** Package changed: bash-completion (Ubuntu) = mysql-5.5 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.5 in Ubuntu. https://bugs.launchpad.net/bugs/106975 Title: mysqldump lacks bash completion script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.5/+bug/106975/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1095180] Re: command / directory mixup for completion of args to meta-commands like sudo
** Summary changed: - incorrect bash-completion for sudo + command / directory mixup for completion of args to meta-commands like sudo -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to etckeeper in Ubuntu. https://bugs.launchpad.net/bugs/1095180 Title: command / directory mixup for completion of args to meta-commands like sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1095180/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 66278] Re: Bug#393079: update-grub: savedefault can cause problems
On Sun, Oct 15, 2006 at 12:02:14PM +0200, Robert Millan wrote: Btw, your Mail-followup-to header screwed my reply. Please don't use that header when submitting bugs to BTS. Sorry; I used Ubuntu's reportbug and then changed some headers without realizing all the headers it sets. Hopefully I'm not causing more problems by CC'ing Ubuntu's BTS on this. : Also sorry for the delay; enough computer problems at work that I didn't want to look at this one again :( On Sun, Oct 15, 2006 at 12:00:39PM +0200, Robert Millan wrote: On Sat, Oct 14, 2006 at 06:08:03PM -0300, Peter Cordes wrote: So I don't know where grub could save defaults to, and I'm not shocked that savedefault doesn't work. I've always been suspicious about by default writing to the hard drive while booting, but this is the first time savedefault has ever actually caused a problem. My opinion is that it's not such a great default. The standard grub menu.lst doesn't use the saved default anyway. I would suggest making savedefault another automagic-comment configurable item, defaulting to off. Yes indeed, savedefault is implemented by writing into MBR. Unfortunately, we had to diverge from upstream on this, and it resulted into a handful of problems I'd rather not get into. Given that it's not enabled by default, though, I think it's safe to do another release with it. It actually is enabled by default. It's the savedefault in every entry that's the problem, not when reading it by specifying default saved. update-grub always writes savedefault in every entry (except the alternate ones), right? Maybe update-grub could have an option for including savedefault or not, or it could include it only if it sees a default saved or fallback saved? That sounds likely to confuse anyone who actually wanted to figure out what was going on, but might just work for more people. The error message I included was for Ubuntu's default boot menu, which has no noticeable difference from Debian's. (no surprise there...) For etch+1 this will all be taken over by GRUB 2. Happy hacking :) -- #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 -- update-grub: savedefault can cause problems https://launchpad.net/bugs/66278 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 104673] Re: drm lockups on g965 hardware
Peter, now that the 7.10 Gutsy Gibbon release of Ubuntu is out, we were wondering if you can still reproduce this issue. I haven't tried, since I'm still using the latest git mesa and drm (kernel and userspace). Next time I'm planning to reboot anyway, I'll try to remember to switch back to the shipped kernel drm modules, and all that. Brian fixed in Gutsy I don't think that thread sheds any light on this. g965 usually worked even in Feisty, but some GL apps triggered bugs. Peter F lockups with gm965 If you haven't tried using the latest git drm and mesa, you might want to try. I'll attach a script I use to run git-pull, compile and install drm and mesa. Run it from a directory where you have a drm and a mesa directory, from doing a git-clone something://whatever You'll need kernel headers, e.g. linux-headers-[versionnumber]-generic There's some good info on freedesktop.org about building things from git. I hope that's enough info to get you started. ** Attachment added: a script I keep in /usr/local/src/g965 http://launchpadlibrarian.net/10158135/update-build -- 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 104673] Re: drm lockups on g965 hardware
I checked out the git trees, ran you script (had to comment out the 64 bit mesa stuff) I'm glad you figured it out, since I created it for my own use and didn't take time to clean it up before posting it. Did your mesa get compiled with -fno-strict-aliasing? It needs that, maybe especially if you use a higher level of optimization than -O1. I'll attach a patch for configs/linux-dri-x86 (which again you'll have to clean up, because it changes lib_dir to lib32, for use on amd64 Ubuntu.) i915 identifies itself as 20070209 version, according to dmesg. good. Check your other mesa versions with LIBGL_DEBUG=verbose MESA_VERBOSE=1 glxgears (and/or glxinfo) Leann I'm flipping the status to Incomplete until we hear a report back from you regading stock Gutsy drm modules. Also marking Importance to Medium. I have been unable to cause any lockups on Gutsy (kernel version sig Ubuntu 2.6.22-14.46-generic. I hadn't noticed that /proc file before :). I booted with just the Ubuntu version of the drm kernel modules, and ran stuff with LD_LIBRARY_PATH=/usr/lib LIBGL_DEBUG=verbose MESA_VERBOSE=1 nexuiz so I could verify that it was using /usr/lib/dri/i965_dri.so, not /usr/local/lib/dri. I checked with lsof that it's using the /usr/lib versions of all the libraries. Anyway, using stock Gutsy everything, I ran nexuiz and enabled all the eye candy (including HDR and dynamic lighting/shadows) at 1680x1050. timedemo demos/demo3 runs at 3 fps, and sometimes down to 1 fps (on a g965, E6600, 4GB of DDR2-800). On edgy and feisty (with the previous version of Nexuiz, though), really low framerates would fairly consistently lock up my g965. I ran all five demos probably a couple times each. So I think it's fair to say that on desktop g965 hardware (Intel DG965WH motherboard), Gutsy no longer has problems. Or at least it's much better than Feisty. I'll try openarena, in case it reveals problems. Leann However against the linux-source-2.6.20 package this is being marked as Won't Fix as it does not meet the criteria for a stable release update. I agree. I think I replied to this bug on the 2.6.20 page without thinking. The Debian BTS just has bug numbers... Although they probably do something special for kernel bugs, because they use package names with the kernel version in it, too. ** Attachment added: tweak mesa configs by adding -fno-strict-aliasing http://launchpadlibrarian.net/10170793/mesa-config.diff -- 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 104673] Re: drm lockups on g965 hardware
libGL: OpenDriver: trying /usr/lib/dri/i965_dri.so Unless you replaced that file yourself, then your attempt to install mesa from git was not successful... You should be basically applying the changes I make to the 64bit config to your 32bit config, since you're running a 32bit system. I get [EMAIL PROTECTED]:~$ LIBGL_DEBUG=verbose MESA_DEBUG=1 glxgears libGL: XF86DRIGetClientDriverName: 1.8.0 i965 (screen 0) libGL: OpenDriver: trying /usr/local/lib/dri/i965_dri.so ... because I changed the config file to make it look for the dri library in /usr/local/lib/dri. Good idea using Debian's packages. That's probably sufficient. It's surprising it doesn't work. I didn't know if there are any major differences between the g965 and the mobile gm965, but I would be surprised. OTOH I'm not trying ut2004. I'll try something that uses texture compression, since in the past I've found that always locked up. (even FXT1, not just DXTn with the external library). BTW, I played openarena for a couple hours this afternoon with no problems on my system (with Gutsy's mesa and drm). Of course, I'm using a g965, not an 855GM. I've found lockups are more common at lower frame rates, and openarena doesn't have enough eye candy to slow down a g965. -- 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 104673] Re: drm lockups on g965 hardware
this is a hard freeze :-( usually what happens is the X server exits, leaving the video hardware displaying whatever it was at the time. So the mouse doesn't move the cursor, and you can't ctrl+alt+f1 (because no X server is listening for that key combo.) However, it's only X that's affected. If you have another computer you can ssh in from, you can shut down cleanly. Or Alt+sysrq+r to take the keyboard out of raw mode, so e.g. ctrl+alt+delete should shut down cleanly. or hold alt+sysrq and hit s, then u, then b. (to sync, umount, and reboot.) The power button should also shut down cleanly. When X crashes like this, restarting it is no good. The video hardware is in some weird state and only re-POSTing will help, which only happens on a reboot or when coming back from a suspend/resume. -- 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 124644] Re: mount only uses last fstype from fstab
This is fixed in Gutsy (util-linux 2.13-8ubuntu1). UDF+iso9660 dvds are mounted as udf. iso9660-only discs are mounted as iso9660. -- mount only uses last fstype from fstab https://bugs.launchpad.net/bugs/124644 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 104673] Re: drm lockups on g965 hardware
You could fetch the ut2004 demo The demo only has one level per game type, so I couldn't try the map you suggested... I was able to reproduce the lockups with ut2004 on my system. So although gutsy is much better than feisty or edgy were, it's still not perfect. I got lockups most quickly on the bombing run match type. It locked up within a minute on that, after ~half an hour of the assault. This was at 1024x768, dynamic lights disabled. Lockups seemed equally frequent with all three combinations I tried: gutsy kernel and userspace; gutsy kernel + git libdrm and mesa; git kernel drm + git libdrm and mesa. The error messages were always the same. [14217.783425] [drm:i915_wait_irq] *ERROR* i915_wait_irq: EBUSY -- rec: 15060137 emitted: 15060382 The end of Xorg.0.log (after killing ut2004-bin, since X didn't exit or log errors until ut died): Error in I830WaitLpRing(), timeout for 2 seconds pgetbl_ctl: 0xcff80001 pgetbl_err: 0x0 ipeir: 0 iphdr: 780a0101 LP ring tail: 1bbe8 head: 1a448 len: 1f001 start 0 Err ID (eir): 0 Err Status (esr): 1 Err Mask (emr): ffdf instdone: ffe5fafd instdone_1: c instpm: 0 memmode: 0 instps: 8001e023 HW Status mask (hwstam): fffedffe IRQ enable (ier): 82 imr: fffe iir: 40 acthd: 5e9c044 dma_fadd_p: 5e9c140 ecoskpd: 307 excc: 0 cache_mode: 6800/180 mi_arb_state: 44 IA_VERTICES_COUNT_QW 0/0 IA_PRIMITIVES_COUNT_QW 0/0 VS_INVOCATION_COUNT_QW 0/0 GS_INVOCATION_COUNT_QW 0/0 GS_PRIMITIVES_COUNT_QW 0/0 CL_INVOCATION_COUNT_QW 0/0 CL_PRIMITIVES_COUNT_QW 0/0 PS_INVOCATION_COUNT_QW 0/0 PS_DEPTH_COUNT_QW 0/0 WIZ_CTL 0 TS_CTL 0 TS_DEBUG_DATA b365895b TD_CTL 0 / 0 space: 125016 wanted 131064 (II) intel(0): [drm] removed 1 reserved context for kernel (II) intel(0): [drm] unmapping 8192 bytes of SAREA 0x1efff000 at 0x2af313ecd000 Fatal server error: lockup Those messages don't look familiar, so I think they must have fixed one thing, and ut2004 is uncovering another problem. So gutsy still has problems, but so does the latest git kernel+userspace. :( So at this point backporting the kernel drm into the gutsy kernel won't help anything, AFAIK. This might be more of a mesa dri bug, not a drm bug. I'm having fun with ut2004 on my old s754 athlon64 + 7600gt, though. :) I'll report this on freedesktop.org. -- 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 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=1493p_created=1168299631p_sid=mN5O5Wsip_accessibility=0p_redirect=p_lva=p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9NDkmcF9wcm9kcz0mcF9jYXRzPSZwX3B2PSZwX2N2PSZwX3NlYXJjaF90eXBlPXNlYXJjaF9mbmwmcF9wYWdlPTEmcF9zZWFyY2hfdGV4dD1yYWlkp_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 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 112837] Re: funny menu after install of emacs-extra
not fixed in intrepid either, and has no maintainer in Debian. The package doesn't even exist on the PTS (http://packages.qa.debian.org/e /emacs-extra.html - 404). So it's not exactly actively maintained. I like the colour scheme it provides for light on dark, but it's probably pretty obsolete. The only two entries in changelog.Debian.gz are May 2002 and June 2007! -- funny menu after install of emacs-extra https://bugs.launchpad.net/bugs/112837 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 112837] Re: funny menu after install of emacs-extra
BTW, happycoders-emacs conflicts with emacs-extra, and is from the same Debian maintainer. It's version number is 2004.08.14, so it's old, too. -- funny menu after install of emacs-extra https://bugs.launchpad.net/bugs/112837 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 273601] Re: 8.10 intrepid alpha 6 - root file system mounted read only (XFS) with2.6.27-4-generic
Leann, thanks for the reply on my bug that's a dup of this. I thought I'd already posted my workaround, but it turns out I only posted it on bug 253786 (/dev/.static/dev is left read-only). Since I found a workaround, this bug hasn't caused me any problems. Anyway, you can convince the init scripts to remount the bind mount read-write as well as the main root filesystem with this in fstab /dev/dev/.static/dev bind remount,rw 0 0 That avoids triggering the bug with XFS root filesystems. And it makes /dev/.static/dev read-write, so MAKEDEV works, so I'll be keeping this in my fstab even after the XFS bug is fixed. see bug 253786 for more discussion on ro/rw, and how it gets that way in the first place. If you don't want to break the kernel freeze, you could possibly add this workaround to update-manager's collection of quirks. (e.g. test if xfs_info / shows that the root filesystem is xfs, then append a line to /etc/fstab.) Hmm, reading the fix description, XFS has a per-FS read-only flag? That doesn't sound like it would interact well with various combinations of read-only and read-write bind mounts... Could be a security hole if you think you have a ro bind mount for a chroot, but some FS ops are allowed. I'll test this and report a bug if I remember and have time, and it's not already known. -- 8.10 intrepid alpha 6 - root file system mounted read only (XFS) with2.6.27-4-generic https://bugs.launchpad.net/bugs/273601 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 87422] Re: crash on load on AMD64
version 2.02r2-8 works on pre-Intrepid. This might well have been fixed in Hardy, but I didn't check. ** Changed in: xevil (Ubuntu) Status: Incomplete = Fix Released -- 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 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
looks like this is fixed in Linux 2.6.27.3: commit c068663ae65e507814545b59a8e2090f48a85613 Author: Christoph Hellwig [EMAIL PROTECTED] Date: Sun Oct 12 14:30:44 2008 +0200 xfs: fix remount rw with unrecognized options [...]otherwise we may skip clearing the xfs-internal read-only flag. This will only show up on some operations like touch because most read-only checks are done by the VFS which thinks this filesystem is r/w. [...] -- 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 229732] Re: USB Keyboard drivers not loaded in initramfs
USB module loading order: Linux 2.6.27.3's changelog says that Linux will now warn if ehci isn't loaded before o/uhci. And that it has always been better to load ehci first. So panic() should load ehci-hcd first, then try the other two, in case the user works around a problem and goes on to boot up. -- 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 253786] Re: /dev/.static/dev is mounted ro in intrepid
I was looking into this because it triggered bug 278954. initramfs bind-mounts /dev to /dev/.static/dev before the init scripts remount / read-write. I've been working around the XFS bug with a line in fstab: /dev/dev/.static/dev bind remount,rw 0 0 This has the side-effect of making /dev/.static/dev writeable again, also enabling things that want to run MAKEDEV to work successfully. Some packages do want to run MAKEDEV in their postinst, IIRC, and fail because of that. So if you get rid of /dev/.static/dev, you need to change MAKEDEV so it always returns true, or change all the packages, or something. Or just have the /etc/rcS.d/S20checkroot.sh make the bind mount read-write, just after remounting the root fs. mount -n /dev /dev/.static/dev -o remount,rw (-n because my fstab workaround puts it in mtab, but that's not the default.) I think (the real, on root fs) /dev would be needed by people who build their own non-initramfs not-so-modular kernel. You need a /dev/null until /etc/rcS.d/S10udev, probably. I don't know if that's still supported, either. I used to do that, before I had too many different machines to customize kernels for (and plenty of RAM in most of them :). Oh, the good old days of worrying about kB used by the kernel. -- /dev/.static/dev is mounted ro in intrepid https://bugs.launchpad.net/bugs/253786 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 287948] [NEW] gawk-doc: example doesn't match actual output
Public bug reported:
Binary package hint: gawk-doc
in (gawk.info.gz)Records, this example is given:
$ echo | awk 'BEGIN { RS = a } ; { print NF }'
1
But that's wrong: real results
[EMAIL PROTECTED]:~$ echo | gawk 'BEGIN { RS = a } ; { print NF }'
0
[EMAIL PROTECTED]:~$ echo | gawk --posix 'BEGIN { RS = a } ; { print NF }'
1
gawk 1:3.1.6.dfsg-0ubuntu1 on AMD64 pre-Intrepid.
I'm not sure what the best thing for the docs to say would be. I assume it's a
bug in the docs, not in awk, but I'm not sure.
I'm still trying to figure out what the most concise way to read lines
from stdin, and feed them in batches of e.g. 10 lines to the stdin of
separate invocations of another command. Probably perl, since awk's RS
mechanism doesn't seem to be flexible enough. (I can do it in a perl
one-liner, but I was trying to shorten it, and awk's print | command
looks useful.)
** Affects: gawk-doc (Ubuntu)
Importance: Undecided
Status: New
--
gawk-doc: example doesn't match actual output
https://bugs.launchpad.net/bugs/287948
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- TAbort- MAbort- SERR- PERR- Latency: 32 (2000ns min), Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 6 Region 0: Memory at d800 (32-bit, prefetchable) [size=128M] Region 1: I/O ports at cc00 [size=256] Region 2: Memory at fc2d (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at fc10 [disabled] [size=128K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- ** Affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New -- 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 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-
TAbort- MAbort- SERR- PERR-
Latency: 64 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at fc00 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at c000 (32-bit, prefetchable) [size=256M]
Region 2: Memory at fb00 (32-bit, non-prefetchable) [size=16M]
Expansion ROM at fd00 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [44] AGP version 3.0
Status: RQ=256 Iso- ArqSz=0 Cal=3 SBA+ ITACoh- GART64- HTrans-
64bit- FW+ AGP3+ Rate=x4,x8
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW-
Rate=none
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 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 175918] Re: Automatic mode can be disabled, but not reenabled
I think Paul is talking about what Network Manager calls Roaming Mode. In the properties for an interface, there is a tickbox for Roaming Mode, which re-enables that drop-down of nearby wireless networks. So this is fixed at least in Hardy. Haven't tried with Gutsy. -- Automatic mode can be disabled, but not reenabled https://bugs.launchpad.net/bugs/175918 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 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
[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 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 75726] Re: DRI broken on r128 on dual head r128 + i965 (non Xinerama)
yeah, I submitted it upstream, too. I didn't mention it here, sorry. -- DRI broken on r128 on dual head r128 + i965 (non Xinerama) https://bugs.launchpad.net/bugs/75726 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 187552] [NEW] mhwaveedit: can't handle files with spaces
Public bug reported: Binary package hint: mhwaveedit /usr/bin/mhwaveedit uses an unquoted $@, so the shell word-splits the args. The correct way to pass on args in a wrapper script is $@, not just [EMAIL PROTECTED] ** Affects: mhwaveedit (Ubuntu) Importance: Undecided Status: New -- mhwaveedit: can't handle files with spaces https://bugs.launchpad.net/bugs/187552 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 187552] Re: mhwaveedit: can't handle files with spaces
also, the wrapper should use exec. i.e. exec /usr/lib/mhwaveedit/mhwaveedit.real $@ -- mhwaveedit: can't handle files with spaces https://bugs.launchpad.net/bugs/187552 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 104673] Re: drm lockups on g965 hardware
This did turn out to look the same as the lockups I had seen before with SPECViewperf. See https://bugs.freedesktop.org/show_bug.cgi?id=7962, where I've mentioned this bug, and passed along the info about the ut2004 lockups. -- 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
Re: [Bug 164486] Re: nfsd oops after a disk disappears
On Fri, Dec 28, 2007 at 05:55:06AM -, Leann Ogasawara wrote: Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks! -- nfsd oops after a disk disappears I'll probably upgrade my regular system to run the kernel from Hardy at some point. This is not an easily testable bug, because I don't think it's the same thing as unplugging a disk's SATA connector. The SATA controller doesn't think it's gone, just not responding to commands. Maybe sometime I'll test hot-unplugging a drive to see if I get the same oopses. If I do, then I'll test the same thing with Hardy's kernel. Otherwise, I'll mostly hope I never see my hard drive mysteriously disappear again! I posted on the forums about that, since I'm not sure it's a kernel bug (possibly a hardware problem). http://ubuntuforums.org/showthread.php?t=625076 -- #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 -- nfsd oops after a disk disappears https://bugs.launchpad.net/bugs/164486 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 165213] Re: ghex truncates large files when saving
On Fri, Jan 04, 2008 at 01:08:10AM -, Gianni Tedesco wrote: I also noticed problems with ghex and large files. Is it a 32 or 64 bit CPU that you're using? 64bit: AMD64 Ubuntu Gutsy. I'm not sure ghex is designed to handle that big a file at all. Besides it ought to save to a temporary file and rename it over the original, just to be safe and avoid chomping your data anyway. Yeah, as long as it always re-writes the whole file anyway, that's a good plan. It's not really useable on block devices of any significant size anyway, with its current design. As for the performance with big files, mmap is the way to go. The attached patch demonstrates this. I tried it out on some fairly modestly sized files (600MB sort of ballpark) and the results were predictably spectacular. This patch is a bug-ridden hack but it might work for your case. I started work on doing all this portably with glib. There's a way to do it without changing the UI behaviour but it's not a trivial one-nighter and my school homework + other things got in the way for now so... I don't really have time to spend on this either. :( -- #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 -- ghex truncates large files when saving https://bugs.launchpad.net/bugs/165213 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 164486] nfsd oops after a disk disappears
Public bug reported: Binary package hint: linux-image-2.6.22-14-generic I run AMD64 Ubuntu Gutsy on a Core 2 Duo (Intel DG965WH mobo, 4GB RAM) I sometimes see sda stop responding on my machine. (I'm starting to think this may well be a driver bug, not a hardware problem, but I'll report it separately.) I run an AMD64 system with /, /usr and /home on RAID1, but /var/tmp, /data on non-raid evms block devices. /home and /data are NFS-mounted by another computer in the house. /home is an XFS filesystem on an evms volume made from an lvm2 logical volume with one physical volume: my RAID1 of partitions on sda and sdb. /data is an XFS filesystem on an evms volume on an lvm2 logical volume in a volume group with two physical volume: other partitions on sda and sdb. This time, I noticed the drive disappear when I ran df. I think the I/O reading /bin/df from disk was the I/O that made the kernel notice that sda was out to lunch. processes blocked on disk I/O for ~30 seconds, then md decided to fail the reads over to the other half of the block device. In case that matters. I imagine the result on the system outside the ahci driver would be the same as pulling the power cord on the hard drive. (although udev doesn't remove /dev/sda*, while it might if the drive has hot-unplugged.) anyway, I'm trying to just report the NFSd oops bug here. Note that I have no idea what filesystem was being read when nfsd oopsed. It was either /data or /home. I do have a Nov 22 05:29:47 llama kernel: nfs: server tesla not responding, timed out message with the right timestamp on the machine that has the filesystems mounted, so I know there was an NFS request happening. Nov 22 05:28:44 tesla kernel: [714786.172320] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x2 frozen Nov 22 05:28:44 tesla kernel: [714786.172329] ata1.00: cmd 61/01:00:df:73:99/00:00:03:00:00/40 tag 0 cdb 0x0 data 512 out Nov 22 05:28:44 tesla kernel: [714786.172331] res 40/00:ff:00:fa:00/00:00:00:00:00/40 Emask 0x4 (timeout) Nov 22 05:28:44 tesla kernel: [714786.172337] ata1.00: cmd 60/28:08:1a:8d:95/00:00:26:00:00/40 tag 1 cdb 0x0 data 20480 in Nov 22 05:28:44 tesla kernel: [714786.172339] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 22 05:28:45 tesla kernel: [714786.484245] ata1: soft resetting port Nov 22 05:28:50 tesla kernel: [714791.743090] ata1: port is slow to respond, please be patient (Status 0xc0) Nov 22 05:28:55 tesla kernel: [714796.558036] ata1: softreset failed (device not ready) Nov 22 05:28:55 tesla kernel: [714796.558042] ata1: hard resetting port Nov 22 05:29:00 tesla kernel: [714802.072821] ata1: port is slow to respond, please be patient (Status 0x80) Nov 22 05:29:05 tesla kernel: [714806.607826] ata1: COMRESET failed (errno=-16) Nov 22 05:29:05 tesla kernel: [714806.607834] ata1: hard resetting port Nov 22 05:29:10 tesla kernel: [714812.122615] ata1: port is slow to respond, please be patient (Status 0x80) Nov 22 05:29:40 tesla kernel: [714841.676126] ata1: COMRESET failed (errno=-16) Nov 22 05:29:40 tesla kernel: [714841.676135] ata1: limiting SATA link speed to 1.5 Gbps Nov 22 05:29:40 tesla kernel: [714841.676138] ata1: hard resetting port Nov 22 05:29:45 tesla kernel: [714846.687024] ata1: COMRESET failed (errno=-16) Nov 22 05:29:45 tesla kernel: [714846.687032] ata1: reset failed, giving up Nov 22 05:29:45 tesla kernel: [714846.687034] ata1.00: disabled Nov 22 05:29:45 tesla kernel: [714846.687049] ata1: EH complete Nov 22 05:29:45 tesla kernel: [714846.687431] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST _OK Nov 22 05:29:45 tesla kernel: [714846.687438] end_request: I/O error, dev sda, sector 647335194 Nov 22 05:29:45 tesla kernel: [714846.687456] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST _OK Nov 22 05:29:45 tesla kernel: [714846.687460] end_request: I/O error, dev sda, sector 60388319 ... Nov 22 05:29:50 tesla kernel: [714851.486244] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK Nov 22 05:29:50 tesla kernel: [714851.486248] end_request: I/O error, dev sda, sector 164108026 Nov 22 05:29:50 tesla kernel: [714851.520009] Unable to handle kernel NULL pointer dereference at RIP: Nov 22 05:29:50 tesla kernel: [714851.520014] [_end+132959939/2130332920] :nfsd:encode_fsid+0x9b/0xb0 Nov 22 05:29:50 tesla kernel: [714851.520031] PGD 1234b3067 PUD 122c24067 PMD 0 Nov 22 05:29:50 tesla kernel: [714851.520036] Oops: [1] SMP Nov 22 05:29:50 tesla kernel: [714851.520039] CPU 0 Nov 22 05:29:50 tesla kernel: [714851.520042] Modules linked in: joydev xpad nfs nls_cp437 vfat fat nls_utf8 usb_storage ide_core libusual isofs udf loop af_packet binfmt_misc vboxdrv nfsd exportfs lockd sunrpc ppdev autofs4 ipv6 video sbs container button dock ac battery cpufreq_userspace cpufreq_stats cpufreq_powersave cpufreq_conservative cpufreq_ondemand
[Bug 125687] Re: Samba does not start on boot.
I was just going to report the same bug. I've seen this on Ubuntu Feisty, and I still see it on Gutsy. The problem I've seen seems to be that on DHCP client machines, it can take some time for network interfaces other than loopback to come up. The networking init script (which runs ifup -a) doesn't seem to wait for DHCP to finish getting an IP before letting later stuff run. This is a problem for programs which depend on specific interfaces existing. I have e.g. samba configured with interfaces = 127.0.0.1/8 10.255.255.255/8 bind interfaces only = true so if those interfaces aren't up, nmbd doesn't start at all. smbd can start but only be listening on loopback because eth0 didn't have an IP when it started. I hacked around it in the past once on a desktop I installed for a colleague with a script that waited for the network to come up: #!/bin/sh # sleep long enough for networking to come up before ntp, firestarter, etc. # /sbin/ifconfig echo waiting for network timeout=20 while ! /sbin/ifconfig | grep -q '129\.173';do sleep 1 timeout=$(( $timeout - 1 )) if [ $timeout -lt 1 ];then echo timeout waiting for network return 1 fi done echo done waiting for network --- I think I sourced it from some other init script, hence the return instead of exit. On my home server/desktop, which gets an IP via DHCP from my firewall/other server, I use /etc/rc.local as a convenient place to put (sleep 60 /etc/init.d/samba restart) I have to say restart, not just start, because smbd can start bound to the loopback interface only, and start will just leave it running. Obviously these are not proper solutions, but I hope this helps understand the problem. I don't think I've seen the problem when I've changed /etc/network/interfaces to use a static IP for the machine. -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 104673] Re: drm lockups on g965 hardware
On Fri, Nov 23, 2007 at 12:12:29PM -, nbubis wrote: I seem to have the same problem with a fresh install of gutsy as well. running 3d apps (blender, k3d) locks up X. I'm running on a dell 1420n with a 965 GMA. Is this really an error with the kernel modules? is there a solution \ workaround for this problem? AFAIK, gutsy is as stable as the latest git versions of libGL (and /usr/lib/dri/i965_dri.so), libdrm, kernel-side drm. Also AFAIK, the fix for the graphics lockups could be in any of those pieces of software. When I say as stable, I don't mean perfectly stable. e.g. ut2004-demo locks up my g965 quite easily. So does SPECviewperf 9.0.3's tcvis. It is better than e.g. Edgy, where even some screensavers could lock it up. -- #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 -- 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 165213] ghex truncates large files when saving
Public bug reported: Binary package hint: ghex I was using ghex2 to look at the beginning of an 8.6GB .wav file. I changed a byte and saved the file, and now it's only 612MB. (I think it's no coincidence that ghex2 is using just a bit more RAM than that: RSS=626MB). I really like ghex2's UI, with interpretations of the next 1, 2 and 4 bytes as signed or unsigned integer, which is why I put up with it's memory wastage. Hex editors are not supposed to rewrite the whole file. They're supposed to edit in place. And mmap() the file if you want, but don't load it all into RAM! ** Affects: ghex (Ubuntu) Importance: Undecided Status: New -- ghex truncates large files when saving https://bugs.launchpad.net/bugs/165213 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 172479] Re: xxdiff doesn't work when run with stdin and stdout closed
This is on AMD64 Ubuntu Gutsy, BTW. -- xxdiff doesn't work when run with stdin and stdout closed https://bugs.launchpad.net/bugs/172479 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 172479] xxdiff doesn't work when run with stdin and stdout closed
Public bug reported: Binary package hint: xxdiff rapidsvn makes you choose a diff tool, so I told it to use xxdiff. It apparently runs xxdiff with stdin and stdout closed, which leads to it running diff with stdin and stdout closed. There's no way that can work, because diff writes the diff to stdout. To reproduce this outside of rapidsvn, use the shell's redirection operators to close the file descriptors: touch foo bar xxdiff foo bar 0- 1- strace -f will show that /usr/bin/diff ends up doing 12022 open(foo, O_RDONLY) = 0 12022 open(bar, O_RDONLY) = 1 12022 read(0, , 4096) = 0 12022 read(1, , 4096) = 0 12022 close(0) = 0 12022 close(1) = 0 12022 close(1) = -1 EBADF (Bad file descriptor) 12022 write(2, diff: , 6) = 6 12022 write(2, standard output, 15) = 15 12022 write(2, : Bad file descriptor, 21) = 21 12022 write(2, \n, 1) = 1 12022 exit_group(2) = ? xxdiff pops up a dialog box. ** Affects: xxdiff (Ubuntu) Importance: Undecided Status: New -- xxdiff doesn't work when run with stdin and stdout closed https://bugs.launchpad.net/bugs/172479 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 162594] Re: audacity does not play a sound since Gutsy upgrade
Check if anything else has the sound device file open. less /proc/asound/card0/pcm0p/info and look at subdevices_avail (at the end of the file) If avail is 0, then something already has your sound card open. (This might not be a problem, depending on the drivers/hardware; e.g. My Intel HDA, w/ Sigmatel STAC9271D codec, shows 1 subdevice, and 0 avail when anything is playing. It allows apparently unlimited stereo output streams (at 48kHz only), or a single multichannel stream at any sample rate.) You can check what processes have the card open, with lsof /dev/snd/pcmC0D0p I found audacity kept switching to using the digital output of my sound card, which isn't hooked up. But you did say you set it to Alsa (default), which should work. Other ALSA programs work for you, right? e.g. aplay, or mplayer -ao alsa, or whatever. (check with lsof while the programs running to make sure it's opened the sound device directly instead of starting artsd or something) -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 157457] Re: Cannot trim or export a selection in Audacity 1.3.3.-1build1, Ubuntu Gutsy Gibbon 7.10 64-bit
The double gray arrow is not the same as the selection region. Using the selection tool, click+drag over the waveform, not in the time bar. You'd have to read the docs to find out what the gray arrow thing is. -- Cannot trim or export a selection in Audacity 1.3.3.-1build1, Ubuntu Gutsy Gibbon 7.10 64-bit https://bugs.launchpad.net/bugs/157457 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 122098] Re: audacity 24bit quantization noise in feisty
What hardware/drivers? And do other recording programs have the same problem? e.g. try with arecord, which is part of ALSA, so it should be using the interface correctly. Sorry if this isn't helpful, but you didn't say anything to rule out sound driver bugs. BTW, audacity is the same package in Ubuntu/Xubuntu/Kubuntu. There is only one Ubuntu package namespace. Kubuntu is Ubuntu with the kubuntu- desktop package installed, which depends on a bunch of KDE stuff. So the diff is just the set of packages installed by default, and pulled in by the *ubuntu-desktop package. -- audacity 24bit quantization noise in feisty https://bugs.launchpad.net/bugs/122098 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 175806] dhclient tries to chmod /etc/resolv.conf only before it creates it
Public bug reported: Binary package hint: dhcp3-client I booted the Ubuntu Gutsy i386 livecd on an old machine, and switched to tty1 to run dhclient, because NetworkManager apparently didn't want to bother. This uncovered a funny corner-case in dhclient: ... DHCPREQUEST on eth0 to 255.255.255.255 port 67 DHCPACK from 10.0.0.1 chown: failed to get attributes of `/etc/resolv.conf': No such file or directory chmod: failed to get attributes of `/etc/resolv.conf': No such file or directory bound to 10.0.0.18 -- renewal in 18184 seconds. ... /etc/resolv.conf was created fine, with mode 644, but owned by root:dhcp instead of root:root. This is a very minor bug. ** Affects: dhcp3 (Ubuntu) Importance: Undecided Status: New -- dhclient tries to chmod /etc/resolv.conf only before it creates it https://bugs.launchpad.net/bugs/175806 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 164507] Re: misleading error message in terminal when trying to chmod on fat32
This is one of those parts of Unix that you're probably just going to have to get used to. Unfortunately, there are standards (e.g. POSIX.1) that say what possible error codes a system call is allowed to return, and what they imply for that system call. run man 2 chmod to see the manual for the chmod system call (which the chmod(1) program is built around). Or online at e.g. http://linux.die.net/man/2/chmod It's unfortunate, because none of them are really appropriate for the situation. EIO could make sense, but it usually implies serious/unexpected problems (e.g. hard drive failure or network outage). EROFS (read only filesystem) is only true in so far as file permissions aren't modifiable. So for chmod(1) (the program) to print a better error message: 1. it would have to try to find out if the filesystem was FAT or similar if it saw an EPERM error code. Not going to happen; Programs usually just print the standard text for an error message and print what they were trying to do when it happened. The user can tell exactly what's going on (even in a program more complicated than chmod). If programs tried to diagnose problems further, they'd all print different error messages, so it would be hard to tell what actually happened in the probably common case that the program misdiagnosed the problem. (and programs would be twice as big, and people would have to spend lots of time fixing bugs in the error-diagnosing code, esp. since most error handling code in most programs doesn't get much testing even currently. Think about how bad it would be if lots of programs tried to have special handling for strange corner cases. (I realize you weren't arguing for this whole strawman I've put up, I'm just trying to explain why Unix is how it is. The point is that chmod would have to be a much fancier program to do what you suggest, but Unix (esp. traditional command line) is all about small, sharp tools that do one thing well.)) or 2. Linux (the kernel) could return an error code not allowed by the standards for chmod(2) (the system call). This could happen; GNU = GNU is Not Unix, so they're not afraid to violate Unix standards when the standards suck. (Linux tries pretty hard to conform to most standards, though.) fat isn't POSIX compliant, (e.g. it doesn't support chmod), so one could argue that Linux doesn't need to be POSIX-compliant when using it. ENOTSUP (Operation not supported) would seem the most appropriate error code. EINVAL (Invalid argument) would work too. (see the errno(3) manpage) Yeah, that's actually not a bad idea. I can hardly imagine it breaking anything to return ENOTSUP from chmod, since almost everything deals with errno by just looking up the associated string and printing it. Since there is just one global table, not per-system call or anything, programs would just print out operation not supported. So I vote for changing fat's chmod handler function. This bug should be assigned to the linux-source package, since that's the only sensible place to change anything to fix it. -- misleading error message in terminal when trying to chmod on fat32 https://bugs.launchpad.net/bugs/164507 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 175960] clock appears to be wrong dialog prevents gnome session from starting
Public bug reported: Binary package hint: gnome-control-center I'm not sure this is the right package: maybe gnome-session is really at fault here. I have an old AMD K7 machine with a probably-dead CMOS battery, so it often boots up with the hw clock set to the year 2000. I just put Ubuntu Gutsy (i386) onto it. After logging in through gdm (or booting from the Gutsy live CD), Ubuntu's default desktop session pops up a dialog that reads: The computer clock appears to be wrong ... Ignore / Adjust the Clock. All is well if I select Ignore. However, selecting adjust fails: You get a dialog that says: The configuration could not be loaded You are not allowed to access the system configuration. [close] After closing the dialog, it just sits there doing nothing, with the orange background and a mouse cursor, but _nothing_ else. All I can do is switch to a text console to debug it: gnome-settings-daemon is still running. Neither x-window-manager nor metacity are running. Maybe gnome-session is waiting for gnome-settings to exit... In case it matters, hw is Athlon (original) 650MHz, 256MB RAM, ATI AIW Radeon 7200 (32MB RAM) plugged into a CRT that supports DDC properly, so that's all good. IDE hard drive, XFS root filesystem (yes, I had to install grub manually). An ne2kpci ethernet card is installed, but NetworkManager doesn't even try to bring it up because it can't detect whether there is a link. (This is a separate bug that I'll report...) So the machine has eth0 UP BROADCAST RUNNING MULTICAST, but with no IP. netstat doesn't show any socket activity, so I don't think anything's just waiting for a net timeout. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 47848] Re: should warn at partitioning stage if /boot is on XFS
I just installed i386 Gutsy from the desktop livecd on an old AMD K7 650MHz, 256MB RAM, that I use for messing around. 1 IDE hard drive: hda1: win98 hda2: failed installed of winxp hda5: swap hda6: / (XFS) Right after partitioning, the installer warns if you /boot will be on XFS. It pops up a dialog that warns you about grub-install not working properly on an XFS /boot, giving you options of [go back] an [continue]. The actions of the buttons are opposite to their text: [go back] continues, and vice versa. At the end of the install, a similar (or identical) dialog comes up before running grub-install. This time, the buttons are mapped correctly. I hit continue, and grub-install failed. To install grub manually, I made a grub floppy (cat /usr/lib/*-pc/stage[12] /dev/fd0) This machine is so old that floppy booting works better than USB. :P Then root (hd0,5) setup (hd0) did the trick. I think there's a way to get it to work from the grub shell running under Linux, maybe using install instead of setup. Anyway, Gutsy still has the warnings, and still needs them. -- should warn at partitioning stage if /boot is on XFS https://bugs.launchpad.net/bugs/47848 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 175960] Re: clock appears to be wrong dialog prevents gnome session from starting
just noticed my .xsession-errors contains: (process:12519): Gtk-WARNING **: This process is currently running setuid or setgid. This is not a supported use of GTK+. You must create a helper program instead. For further details, see: http://www.gtk.org/setuid.html Refusing to initialize GTK+. (process:12523): Gtk-WARNING **: This process is currently running setuid or setgid. This is not a supported use of GTK+. You must create a helper program instead. For further details, see: http://www.gtk.org/setuid.html Refusing to initialize GTK+. /etc/gdm/Xsession: Beginning session setup... SESSION_MANAGER=local/quixote:/tmp/.ICE-unix/12516 processes 12523 and 12519 are not running any more (at the empty screen stage.) -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 163708] Re: n-m doesn't recognize ethernet on bootup
It would probably also help to know what hardware you have. Maybe attach a copy of your /var/log/dmesg, which will contain all the messages about your kernel detecting your ethernet hardware. If you can poke around with mii-tool or ethtool (see if they show the NIC has a link when it boots up, or if the kernel doesn't know what's going on, not just network manager). Some drivers log to the kernel log (which syslog saves in /var/log/kern.log) when an ethernet link appears/disappears. -- n-m doesn't recognize ethernet on bootup https://bugs.launchpad.net/bugs/163708 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 176003] defaults to deactivating NICs that don't support carrier detection
Public bug reported: Binary package hint: network-manager I just tested i386 Gutsy on an old K7 desktop with an RTL8029 (ne2k-pci) NIC installed. (I was messing around with a win98 game on that machine, and I knew win98 would have drivers for it... heh, it's such a bad NIC that I feel the need to make excuses for using it. :) The Gutsy live CD (and Gutsy after installing) doesn't get an IP address automatically, because NetworkManager decides not to try. I'm not impressed. It's better to run dhclient in vain, esp. on the livecd. (If you don't think this is a bug in n-m, then I think it's a bug in the livecd to not try all options for getting connectivity.) daemon.log shows: Feb 7 16:02:15 quixote NetworkManager: debug [949953735.305326] nm_hal_device_added(): New device added (hal udi is '/org/f reedesktop/Hal/devices/net_00_02_44_06_ba_e7'). Feb 7 16:02:15 quixote NetworkManager: info eth0: Driver 'ne2k-pci' does not support carrier detection. ^IYou must switch to it manually. Feb 7 16:02:15 quixote NetworkManager: info nm_device_init(): waiting for device's worker thread to start Feb 7 16:02:15 quixote NetworkManager: info nm_device_init(): device's worker thread started, continuing. Feb 7 16:02:15 quixote NetworkManager: info Now managing wired Ethernet (802.3) device 'eth0'. Feb 7 16:02:15 quixote NetworkManager: info Deactivating device eth0. After bootup, eth0 is UP BROADCAST RUNNING MULTICAST, but with no IP. Neither ethtool nor mii-tool can get any information at all. Simply running dhclient eth0 gets me an IP. But in the network manager gnome gui, it's not even obvious how to enable eth0. (I'm a first time network-manager user, but a long-time Debian and Ubuntu admin. So this would really be a problem for a first-time user of Ubuntu.) So, IMHO, the bug is that network manager defaults to not using some interfaces. I should mention that there is a pci and and ISA modem in the machine. I was going to test them to see if they actually work and have Linux drivers. Network Manager has an entry for one of them. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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 the bug contact for 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
ok, disabling roaming mode and enabling dhcp in n-m worked on this setup, so it's not terrible, but I'd still rather see the default be to try DHCP before deciding not to use the interface, _esp_ in the live cd. -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 75726] Re: DRI broken on r128 on dual head r128 + i965 (non Xinerama)
On Wed, Jan 23, 2008 at 03:40:29PM -, Bryce Harrington wrote: Hi Peter, It's been a while since you reported this, and I wanted to check if it's still an issue? Have you had a chance to test it against Hardy? No. I haven't been using dual-head any more. I can give it a try if I have some spare time and I'm rebooting my machine anyway. We definitely will need your /etc/X11/xorg.conf, /var/log/Xorg.0.log, and the output from lspci -vvnn. ** Changed in: xorg-server (Ubuntu) Status: New = Incomplete -- #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 -- DRI broken on r128 on dual head r128 + i965 (non Xinerama) https://bugs.launchpad.net/bugs/75726 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 224507] [NEW] should suggest pdf-viewer
Public bug reported: Binary package hint: pdfcrack pdfcrack used to suggest xpdf-reader. Now it suggests on pdf-reader, which doesn't exist and is not a virtual package provided by any Ubuntu packages. pdf-viewer is a virtual package provided by evince, xpdf-reader, and others. This seems like a better choice. ** Affects: pdfcrack (Ubuntu) Importance: Undecided Status: New -- should suggest pdf-viewer https://bugs.launchpad.net/bugs/224507 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 224562] [NEW] pdfcrack description/docs should mention other ways to access pdfs
Public bug reported: Binary package hint: pdfcrack The pdf encryption key only depends on the user password (and information that is stored in the file, like the hash of the owner pwd.) e.g. see http://www.cs.cmu.edu/~dst/Adobe/Gallery/anon21jul01-pdf-encryption.txt If it's not illegal[1], pdfcrack should point out that if you don't need a password to view the pdf, it can be completely decrypted by e.g. pdftk with the password checking commented out. Enforcing the owner password in PDF encryption is entirely optional, in a technical sense. The legal sense is another matter, and even talking about things, let alone distributing software that ignores restrictions, might be illegal in some parts of the world. I wish I'd known this; I wouldn't have tried pdfcrack, since I just want to merge some user pass= PDFs. [1] DMCA in the US, and all those garbage laws spreading to other countries too. ** Affects: pdfcrack (Ubuntu) Importance: Undecided Status: New -- pdfcrack description/docs should mention other ways to access pdfs https://bugs.launchpad.net/bugs/224562 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 224563] [NEW] pdfcrack doesn't try the empty string first for user password
Public bug reported: Binary package hint: pdfcrack pdfcrack with no options tries to brute force the user password. It seems to start with 4-character strings. It should try the empty string first! Most pdfs have empty user passwords (so they're publicly viewable), and running pdfcrack with no options on a file will probably be the first thing a lot of people try. Ubuntu's /usr/share/dict/words (from wcanadian) starts with a blank line, so wordlist mode starts sensibly. ** Affects: pdfcrack (Ubuntu) Importance: Undecided Status: New -- pdfcrack doesn't try the empty string first for user password https://bugs.launchpad.net/bugs/224563 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 227240] Re: apt-cacher-ng should allow more file types to be downloaded
*(changelog|copyright)$ If that's supposed to be a regex, then you probably mean '.*' instead of '*'. . matches any character, * matches 0 or more of the preceding character. So .* is like the glob wildcard *. -- apt-cacher-ng should allow more file types to be downloaded https://bugs.launchpad.net/bugs/227240 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 190227] Re: ia32 apps look for libs on the wrong place
Mesa in ia32-libs has the same problem. ~/bin32/gears is /usr/lib/xscreensaver/gears from xscreensaver on an ia32 Debian Etch system, IIRC. Any 32bit openGL program, even medibuntu's googleearth package, is affected. $ LIBGL_DEBUG=verbose MESA_DEBUG=1 ~/bin32/gears libGL: XF86DRIGetClientDriverName: 1.9.0 i965 (screen 0) libGL: OpenDriver: trying /usr/lib/dri/i965_dri.so libGL error: dlopen /usr/lib/dri/i965_dri.so failed (/usr/lib/dri/i965_dri.so: wrong ELF class: ELFCLASS64) libGL error: unable to load driver: i965_dri.so (runs with software rendering) Fortunately, mesa has an env var for the driver path: $ LIBGL_DEBUG=verbose MESA_DEBUG=1 LIBGL_DRIVERS_PATH=/usr/lib32/dri ~/bin32/gears libGL: XF86DRIGetClientDriverName: 1.9.0 i965 (screen 0) libGL: OpenDriver: trying /usr/lib32/dri/i965_dri.so drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: Searching for BusID pci::00:02.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 4, (OK) drmOpenByBusid: drmOpenMinor returns 4 drmOpenByBusid: drmGetBusid reports pci::00:02.0 Mesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable (runs with hardware rendering) -- ia32 apps look for libs on the wrong place https://bugs.launchpad.net/bugs/190227 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
This problem looks different than what I reported in that forum thread. On my system, I see the problem every few months. On my system, everything will be working fine, and then out of the blue sdb stops responding to SATA commands completely, and not even a shutdown -r now fixes it. A power cycle is needed. Before a reboot, the kernel doesn't notice anything even if I hot-unplug the hard drive. I think this means that port on the SATA controller isn't giving any results at all, not even link detection. In the log above, after every port reset Linux detects a drive with the right size. On my system, there is no response at all from the drive when the problem is happening. -- 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 55706] python-uncertainities python2.3/2.4 breakage.
Public bug reported: Binary package hint: python-uncertainities On a fresh install of Dapper Drake (i386), installed from the live DVD: $ sudo aptitude install python-uncertainities ... Setting up python-uncertainities (0.001-3.1ubuntu1) ... /var/lib/dpkg/info/python-uncertainities.postinst: line 20: /usr/bin/python2.3: No such file or directory dpkg: error processing python-uncertainities (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: python-uncertainities E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up python-uncertainities (0.001-3.1ubuntu1) ... /var/lib/dpkg/info/python-uncertainities.postinst: line 20: /usr/bin/python2.3: No such file or directory dpkg: error processing python-uncertainities (--configure): subprocess post-installation script returned error exit status 1 The package claims Depends: on python2.4, but installs into /usr/lib/python2.3. The postinst checks whether it should run python2.3 or python2.4, or whatever, by using dpkg --listfiles and seeing what python directory it uses. I guess a package with a typo in its name doesn't have much to live up to... ** Affects: python-uncertainities (Ubuntu) Importance: Untriaged Status: Unconfirmed -- python-uncertainities python2.3/2.4 breakage. https://launchpad.net/bugs/55706 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 13851] ubiquity
ubiquity doesn't handle the grub+xfs thing at all, it just crashes. I booted the i386 live DVD on a laptop, and shrunk the windows partition, then used the install menu item. I don't think I did anything to confuse ubiquity, but I hadn't used it before. (I'm used to installing Debian with the debian-installer menu interface, but I wanted to try this install thing in the menu...) Anyway, I made / and /home XFS, and I didn't use a /boot. Ubiquity died right at the end, with no warning that I could have a GRUB+XFS problem. (At least I don't think it warned. Maybe it did, but it wasn't very emphatic about it, so it sounded like it wouldn't hurt to try.) In any case it shouldn't crash, it should recognize that grub failed. I saved the error logs and stuff, so I can create a new bug # if you want. I thought there looked like plenty of bugs open already about the installer crashing. -- Grub will not install to XFS Formatted Partition https://launchpad.net/bugs/13851 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 75702] Re: ~/.drirc is not read
On Wed, Mar 07, 2007 at 05:47:18PM -, Timo Aaltonen wrote: can you try with Feisty Herd5, which has mesa-6.5.2 It's fixed in mesa-6.5.3 (current git), which is what I'm using now. g965 is new enough hardware that it's worth keeping up... If I can update just my mesa package, I'll try it. Otherwise, well, maybe. ** Changed in: mesa (Ubuntu) Status: Unconfirmed = Needs Info -- ~/.drirc is not read https://launchpad.net/bugs/75702 -- #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 -- ~/.drirc is not read https://launchpad.net/bugs/75702 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 75702] Re: ~/.drirc is not read
On Thu, Mar 08, 2007 at 10:06:09AM -, Timo Aaltonen wrote: can you find the changeset which fixed this? git-blame src/mesa/drivers/dri/i965/intel_context.c shows 9f344b3e (Eric Anholt2006-08-09 19:14:05 + 333)intel-sarea = saPriv; 9f344b3e (Eric Anholt2006-08-09 19:14:05 + 334) 844e5610 (Zou Nan hai2007-01-24 16:07:43 +0800 335)driParseConfigFiles (intel-optionCache, intelScreen-optionCache, 844e5610 (Zou Nan hai2007-01-24 16:07:43 +0800 336) intel-driScreen-myNum, i965); 844e5610 (Zou Nan hai2007-01-24 16:07:43 +0800 337) 844e5610 (Zou Nan hai2007-01-24 16:07:43 +0800 338)intel-vblank_flags = (intel-intelScreen-irq_active != 0) 844e5610 (Zou Nan hai2007-01-24 16:07:43 +0800 339)? driGetDefaultVBlankFlags(intel-optionCache) : VBLANK_FLAG_NO_IRQ; 9f344b3e (Eric Anholt2006-08-09 19:14:05 + 340) 9f344b3e (Eric Anholt2006-08-09 19:14:05 + 341) ctx-Const.MaxTextureMaxAnisotropy = 2.0; 9f344b3e (Eric Anholt2006-08-09 19:14:05 + 342) That might be it. Does that help? I'd have to go read the git docs some more to dig any deeper. -- #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 -- ~/.drirc is not read https://launchpad.net/bugs/75702 -- 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 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 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 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 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 261190] [NEW] problems witht cell!=default
Public bug reported: I built the Intrepid source packages (6.2~beta2-2) on a Hardy AMD64 system. After installing, I configured with debconf. I chose the cell name equal to my cluster's name. Something must still be assuming SGE_CELL=default, though: $ sudo -u sgeadmin qconf -au peter users error: cell directory /var/lib/gridengine/default doesn't exist I do have a /var/lib/gridengine/perun directory, though. I'm in a hurry, so I'm just going to reinstall SGE with cell=default I haven't seen a good tutorial about setting up grid engine, although I have used it on a Sun cluster. ** Affects: gridengine (Ubuntu) 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 261190] Re: problems witht cell!=default
This is probably because gridengine-common.postinst does
chown 644 ${TMPFILE}
instead of
chmod 644 ${TMPFILE}
so other tools can't read /etc/default/gridengine
--
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] [NEW] gridengine-execd should depend on csh
Public bug reported: With gridengine 6.2~beta2-2 (with the chmod bug fixed), compiled on Ubuntu Hardy, I got this error in /var/spool/gridengine/execd/perun02/messages: 08/25/2008 15:27:16| main|perun02|E|08/25/2008 15:27:16 [1054:10399]: unable to find shell /bin/csh So I installed csh and now qhost can see the resources on perun02. ** Affects: gridengine (Ubuntu) Importance: Undecided Status: New -- 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 105563] Re: usb stick not mounted after hibernate
On Hardy (2.6.24), there are still problems. CONFIG_USB_PERSIST=y, in /boot/config-2.6.24-16-generic. I don't have time right now to test a lot of stuff, for one thing because my Toshiba A70 is really slow to boot. (kernel seems to stick for a while before before detecting hard drives...) I hibernated with a Patriot brand USB stick mounted (by gnome/nautilus), and when I came back there seemed to be two mount points. /media/Patriot on /dev/sda1, and /media/Patriot_ on /dev/sdb1. I didn't notice until I'd unmounted one of them, but I think the kernel detected the USB stick again, instead of realizing that it was the same one present when it hibernated. I did remove and reinsert the USB stick, after a while, so that's in the kernel log, too. My kern.log shows this. Note the sda insertion on May 7, 23:50, then the hibernate. After the resume on May 8, 14:15, the USB stick is detected as sdb. There are some FAT directory read errors, which makes it look like the kernel really did get something crossed up. This might have been the original mount which became stale after resume from hibernation? I don't know if there ever was a /dev/sda1 block dev after the resume. Eventually just umount and pumount, and clicking on unmount in nautilus, got rid of /media/Patriot*, and the mount entries, so I didn't have to hack mtab or anything. ** Attachment added: kern.log http://launchpadlibrarian.net/14371322/kern.log -- usb stick not mounted after hibernate https://bugs.launchpad.net/bugs/105563 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 72886] Re: Burning CD/DVD, starvation, doesn't use burn-proof
newegg doesn't sell that item number anymore. Better to give a model number. Have you had this happen with CDs and DVDs? I thought DVDs were smarter about recovering, and were supposed to be able to. It didn't take a special feature like burn proof. I'm not sure if I've ever had a buffer underrun while burning, but I think so, and my discs come out ok. (I've sometimes seen single-bit errors on them, though, which is why I always make par2 files to put on the disc with the files. This is easy if its a few big files, which is what I'm always burning.) -- Burning CD/DVD, starvation, doesn't use burn-proof https://bugs.launchpad.net/bugs/72886 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 110484] Re: k3b causes system freeze
I also have a DG965WH motherboard (and a Pioneer DVR-111D, firmware 1.29). It uses the Intel g965 chipset, which doesn't include any IDE ports. The board has a Marvell IDE controller chip, which is driven by the pata_marvell kernel module. This is a relatively new driver in the kernel, and I think not totally bug-free yet. e.g. running AMD64 Feisty with the stock kernel, my system would lock up if k3b was running while I closed the tray with a blank dvd-r (or was it +r) in it. I'm currently running Gutsy's kernel (and the latest git versions of DRM and mesa for better g965 support; I made a script to download and hack linux-headers...-generic so they don't depend on gutsy's libc, because the headers themselves don't. I guess some of the shipped progs in /usr/src/.../scripts do. BTW, Gutsy's xorg isn't a big improvement for opengl performance or stability if you were using Feisty with mesa from git. They still haven't fixed the tearing (no vsync). I think Feisty's mesa still crashed sometimes on g965, though, and gutsy's mesa is newer and better.) Anyway, I can burn DVDs all day without any problems, and the crash while k3b recognized a freshly inserted disc doesn't happen anymore. (I used to have to quit k3b, load a disc, and run it again.) So some people's lockups might be the fault of their PATA driver. Try a newer kernel if you have a motherboard with an Intel 965 chipset and a funky PATA controller. BTW, SATA burners are not much more expensive these days, if you're in the market for a new one anyway. Usually system lockups are not directly k3b's fault. Locking up the whole system requires messing with hardware (usually), so it's more often a driver or the X server or something else that directly controls hardware that needs to be fixed. Or other software can avoid doing whatever makes the driver cause a lockup. -- k3b causes system freeze https://bugs.launchpad.net/bugs/110484 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 138760] xdelta 1.1.3-7_i386 has bad md5sums
Public bug reported: Binary package hint: xdelta Ubuntu feisty i386 ships a wrong md5sum for /usr/bin/xdelta. debsums -c xdelta /usr/bin/xdelta The package file is a42682a708e2af3895406977f5100f71 xdelta_1.1.3-7_i386.deb Its control.tar.gz contains an md5sums file: 84370c941410078bc68cb0c543ee7d74 usr/bin/xdelta 6527027195e1c381d02ff118d53b7ff3 usr/share/man/man1/xdelta.1.gz 916dc487ac6afebc89d3200bc7e38a84 usr/share/aclocal/xdelta.m4 9d2bca71143999e4521e1893aa586220 usr/share/doc/xdelta/copyright 760f5a04e2178c8eb405136edade622c usr/share/doc/xdelta/changelog.gz 5cd01030b5eb36c6d32ae423b2df3598 usr/share/doc/xdelta/NEWS.gz 95571fadb8ce320d4295a3ceb8cdc254 usr/share/doc/xdelta/README.gz 51e786f8cd79c7d978be75f3325e7efd usr/share/doc/xdelta/AUTHORS 4b72daeb5d4247e75342f02063efd58f usr/share/doc/xdelta/changelog.Debian.gz The usr/bin/xdelta file in the data.tar.gz doesn't match. 821ead0494e6e84bf4f22aa6b18d60e8 usr/bin/xdelta (and I unpacked this with ar x, and tar xzf, so there's no way the postinst did anything to this copy of it.) I wouldn't go so far as to say this is a security vulnerability, but it does raise red flags when checking things with debsums. ** Affects: xdelta (Ubuntu) Importance: Undecided Status: New -- xdelta 1.1.3-7_i386 has bad md5sums https://bugs.launchpad.net/bugs/138760 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 135680] Re: evince chokes on absolute paths that include a #
Launching from Nautilus shows the same problem for me. You probably need an NFS mount, or maybe even an autofs-mounted NFS mount, to reproduce this. Like I said, it only happens in /net for me. I just tried copying my file to bar.pdf. Then evince /net/llama/home/peter/bar.pdf works. (It makes a copy in /tmp/evince-8626/document-5-bar.pdf). I tried ln -s ACTInc_Quote#1722076.2.pdf foo.pdf, then evince /net/llama/home/peter/foo.pdf fails, with the message Unable to open document Unhandled MIME type: application/octet-stream /tmp/evince-8626 contains lrwxrwxrwx 1 peter peter 26 2007-08-30 16:28 document-6-foo.pdf - ACTInc_Quote#1722076.2.pdf (i.e. it copied the symlink, and the symlink is broken because it is a relative link.) And sorry, I forgot I wasn't using reportbug... I'm running AMD64 feisty (with gutsy's kernel, but I don't think that's relevant.) -- System Information: Debian Release: 4.0 APT prefers feisty-updates APT policy: (980, 'feisty-updates'), (980, 'feisty-security'), (980, 'feisty-proposed'), (980, 'feisty'), (500, 'gutsy'), (500, '... Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.22-10-generic Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages evince depends on: ii gconf22.18.0.1-0ubuntu1 GNOME configuration database syste ii gs-esp-x 8.15.4.dfsg.1-0ubuntu1 The Ghostscript PostScript interpr ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-0 1.18.0-0ubuntu1The ATK accessibility toolkit ii libbonobo2-0 2.18.0-0ubuntu1Bonobo CORBA interfaces library ii libbonoboui2-02.18.0-0ubuntu1The Bonobo UI library ii libc6 2.5-0ubuntu14 GNU C Library: Shared libraries ii libcairo2 1.4.2-0ubuntu1 The Cairo 2D vector graphics libra ii libdbus-1-3 1.0.2-1ubuntu4 simple interprocess messaging syst ii libdbus-glib-1-2 0.73-1 simple interprocess messaging syst ii libdjvulibre153.5.17-3ubuntu2Runtime support for the DjVu image ii libfontconfig12.4.2-1ubuntu1 generic font configuration library ii libfreetype6 2.2.1-5ubuntu1.1 FreeType 2 font engine, shared lib ii libgconf2-4 2.18.0.1-0ubuntu1 GNOME configuration database syste ii libglade2-0 1:2.6.0-3 library to load .glade files at ru ii libglib2.0-0 2.12.11-0ubuntu1 The GLib library of C routines ii libgnome-keyring0 0.8.1-0ubuntu1 GNOME keyring services library ii libgnome2-0 2.18.0-0ubuntu1The GNOME 2 library - runtime file ii libgnomecanvas2-0 2.14.0-3ubuntu2A powerful object-oriented display ii libgnomeui-0 2.17.92-0ubuntu1 The GNOME 2 libraries (User Interf ii libgnomevfs2-01:2.18.1-0ubuntu1 GNOME virtual file-system (runtime ii libgtk2.0-0 2.10.11-0ubuntu3 The GTK+ graphical user interface ii libice6 2:1.0.3-1build1X11 Inter-Client Exchange library ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libkpathsea4 3.0-27ubuntu1 path search library for teTeX (run ii liblaunchpad-inte 0.1.13 library for launchpad integration ii libnautilus-exten 1:2.18.1-0ubuntu1 libraries for nautilus components ii liborbit2 1:2.14.7-0ubuntu1 libraries for ORBit2 - a CORBA ORB ii libpango1.0-0 1.16.2-0ubuntu1Layout and rendering of internatio ii libpng12-01.2.15~beta5-1ubuntu1 PNG library - runtime ii libpoppler1 0.5.4-0ubuntu8.1 PDF rendering library ii libpoppler1-glib 0.5.4-0ubuntu8.1 PDF rendering library (GLib-based ii libpopt0 1.10-3build1 lib for parsing cmdline parameters ii libsm62:1.0.2-1build1X11 Session Management library ii libstdc++64.1.2-0ubuntu4 The GNU Standard C++ Library v3 ii libtiff4 3.8.2-6Tag Image File Format (TIFF) libra ii libx11-6 2:1.1.1-1ubuntu3 X11 client-side library ii libxcursor1 1:1.1.8-1 X cursor management library ii libxext6 2:1.0.3-1build1X11 miscellaneous extension librar ii libxfixes31:4.0.3-1 X11 miscellaneous 'fixes' extensio ii libxi62:1.1.0-1build1X11 Input extension library ii libxinerama1 2:1.0.1-4build1X11 Xinerama extension library ii libxml2 2.6.27.dfsg-1ubuntu3 GNOME XML library ii libxrandr22:1.2.0-3ubuntu1 X11 RandR extension library ii libxrender1 1:0.9.1-3 X Rendering Extension client libra ii zlib1g1:1.2.3-13ubuntu4 compression library - runtime evince recommends no packages. -- evince chokes on absolute paths that include a # https://bugs.launchpad.net/bugs/135680 You received this
Re: [Bug 135680] Re: evince chokes on absolute paths that include a #
On Mon, Sep 03, 2007 at 03:09:41PM -, Sebastien Bacher wrote: is that specific to evince? or do you have similar issues with other GNOME softwares? AFAICT, only evince has this problem. bluefish, eog, file-roller, gedit and ghex2 are all fine on symlinks on /net/llama, and don't make copies of things in /tmp. I only have them installed because Ubuntu-desktop depends on them; I'm kind of a crusty command-line curmudgeon, so I use fluxbox on most of my desktops, not metacity+nautilus+... :) -- #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 -- evince chokes on absolute paths that include a # https://bugs.launchpad.net/bugs/135680 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 135680] evince chokes on absolute paths that include a #
Public bug reported: Binary package hint: evince evince './ACTInc_Quote#1722076.2.pdf' works evince '/net/llama/home/peter/ACTInc_Quote#1722076.2.pdf' pops up a dialog that says Unable to open document The local file URI 'file:/tmp/evince-8626/document-0-ACTInc_Quote#1722076.2.pdf' may not include a '#' It has copied the file to file to it's /tmp directory with a changed filename. [EMAIL PROTECTED]:~$ cmp '/net/llama/home/peter/ACTInc_Quote#1722076.2.pdf' /tmp/evince-8626/document-0-ACTInc_Quote [EMAIL PROTECTED]:~$ echo $? 0 The copying seems kind of unnecessary. If I give a program a path in /net, I expect it to access it the same as a path in /home. In this case, my PDF is tiny, so it didn't matter whether it was cached or not. But maybe there should be a URI other than file:/ that means to cache to /tmp. If I wanted files pre-cached, I'd go find a FUSE filesystem that did that, or something. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- evince chokes on absolute paths that include a # https://bugs.launchpad.net/bugs/135680 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
