Re: [Bug 351408] Re: tbf kills torrents
On Fri, Jun 29, 2012 at 2:16 PM, Stéphane Graber stgra...@stgraber.orgwrote: This seems odd, are you still able to reproduce that with a supported version of Ubuntu (ideally 12.04)? I thought it was odd. I abandoned Linux as a router shortly after that (although I love Tomato), so no I haven't done any further testing. db -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/351408 Title: tbf kills torrents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute/+bug/351408/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011790] [NEW] freerdp segfaults if $HOME is unset
Public bug reported:
Ubuntu 12.04 i386
FreeRDP 1.0.1
LTSP calls xfreerdp from xinit, but the process dies unless we first do
export HOME=${HOME:-/root}
in /usr/share/ltsp/xinitrc on the thin client. Other users have reported
that this can be replicated by doing
unset HOME
xfreerdp host
on any non-thin host.
ref:
http://sourceforge.net/mailarchive/forum.php?thread_name=4FD2EE88.8000506%40gmail.comforum_name
=ltsp-discuss
** Affects: freerdp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011790
Title:
freerdp segfaults if $HOME is unset
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1011790/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 405120] Re: resume from suspend doesn't work (powers off instead) for various Acer Timeline laptops
Did you do 'update-grub' after? db On 9/25/10, Prokopenko Alexandr 405...@bugs.launchpad.net wrote: Thanks, Tom, i tried to move i8042.reset=1 to GRUB_CMDLINE_LINUX, but it not helped. Still doesn't work =( -- resume from suspend doesn't work (powers off instead) for various Acer Timeline laptops https://bugs.launchpad.net/bugs/405120 You received this bug notification because you are a direct subscriber of the bug. -- Sent from my mobile device -- resume from suspend doesn't work (powers off instead) for various Acer Timeline laptops https://bugs.launchpad.net/bugs/405120 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 385974] Re: rdesktop has black cursor instead of white cursor
Confirmed here connecting from Ubuntu 9.04 and 10.04 alpha3 to Windows Server 2008 R2 with Desktop Experience installed and Aero theme active. Mouse pointer appears all black. Choosing another pointer theme yields all black or all white pointer, sometimes with noise. -- rdesktop has black cursor instead of white cursor https://bugs.launchpad.net/bugs/385974 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 405120] Re: resume from suspend doesn't work (powers off instead) for Acer Timeline 3810t/3410t
da...@stimpy:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid -o value -s UUID' to print the universally unique identifier # for a device; this may be used with UUID= as a more robust way to name # devices that works even if disks are added and removed. See fstab(5). # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/sda1 / ext4 noatime,errors=remount-ro 0 1 /dev/sda2 /winntfs-3g nosuid,nodev,allow_other,default_permissions,blksize=4096 0 2 tmp /tmptmpfs defaults0 0 mule:/mnt/1000 /home/david/media nfs user,noauto,tcp,rsize=1048576,wsize=1048576,exec0 2 I installed the beta last week. I'm fully up to date today (2.6.31-14-generic) and still experiencing this problem with BIOS 1.14. db -- resume from suspend doesn't work (powers off instead) for Acer Timeline 3810t/3410t https://bugs.launchpad.net/bugs/405120 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 101946] Re: [jaunty] ltsp client and server sound problem
https://help.ubuntu.com/community/UbuntuLTSP/LTSPQuickInstall https://help.ubuntu.com/community/UbuntuLTSP db -- [jaunty] ltsp client and server sound problem https://bugs.launchpad.net/bugs/101946 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 343354] Re: ondemand governor should be used by default
Confirmed here using 9.04 up to date. Linux zacharias 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux Installing powernowd fixed the problem. Wasn't powernowd formerly part of the default Ubuntu install? db -- ondemand governor should be used by default https://bugs.launchpad.net/bugs/343354 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 351408] [NEW] tbf kills torrents
Public bug reported: I've been using a QOS script for years to keep voip and general internet usage usable with torrents running on the same connection. Until recently this script has worked very well. Now torrents are seeding very slowly, but return to maximum speed immediately when the QOS script is unloaded. Reproducing this problem is very simple: 1. Seed some active torrents without limiting your upload rate. 2. Code: tc qdisc add dev eth1 root handle 1: tbf rate 675kbit latency 50ms burst 1540 where eth1 is the connected to the internet with a routable IP address on a connection that is limited to greater than 675 kbps by the ISP. 3. Watch your torrent upload speed drop to 10 KiB/s or less within seconds. 4. Code: sudo tc qdisc del dev eth1 root 2 /dev/null /dev/null 5. Watch your upload speed return to normal within seconds. Other info # lsb_release -rd Description:Ubuntu 8.10 Release:8.10 # apt-cache policy iproute iproute: Installed: 20080417-1 Candidate: 20080417-1 Version table: *** 20080417-1 0 500 http://ubuntu.mirror.rafal.ca intrepid/main Packages 100 /var/lib/dpkg/status # uname -a Linux zacharias 2.6.27-11-server #1 SMP Thu Jan 29 20:13:12 UTC 2009 x86_64 GNU/Linux db ** Affects: iproute (Ubuntu) Importance: Undecided Status: New -- tbf kills torrents https://bugs.launchpad.net/bugs/351408 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 319214] [NEW] network stalls using r8169 and mtu 2550
Public bug reported: My desktop's onboard realtek gigabit network adapter supports an mtu up to 7200 bytes. It is connected to a Netgear Prosafe gigabit switch that supports mtu up to 9k. An ubuntu firewall/file server on the network has its mtu set to 9k. When I set the mtu on the desktop to any value higher than 2550 the internet appears to function as normal, even at full speed transfers (3000/640 kbps). However file transfers between the desktop and the server stop and start intermittently. I have seen this intermittent behaviour consistently using scp, nfs/cp, nfs/nautilus, and iperf. Setting the mtu on the desktop to 2550 or less results in uninterrupted transfers of expected speed (250 mbps+). dmesg shows no unusual entries when the problem is occurring. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: nvidia Package: linux-image-2.6.27-9-generic 2.6.27-9.19 ProcCmdLine: root=UUID=05f4b11c-84cb-44a7-a340-10a0999fa383 ro quiet splash ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.27-9.19-generic SourcePackage: linux ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- network stalls using r8169 and mtu 2550 https://bugs.launchpad.net/bugs/319214 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 319214] Re: network stalls using r8169 and mtu 2550
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/21471743/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/21471744/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/21471745/Dependencies.txt ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/21471746/HalComputerInfo.txt ** Attachment added: LsUsb.txt http://launchpadlibrarian.net/21471747/LsUsb.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/21471748/Lspci.txt ** Attachment added: ProcCpuInfo.txt http://launchpadlibrarian.net/21471749/ProcCpuInfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/21471750/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/21471751/ProcModules.txt -- network stalls using r8169 and mtu 2550 https://bugs.launchpad.net/bugs/319214 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 319214] Re: network stalls using r8169 and mtu 2550
I'm not able to try the Jaunty prerelease yet, but perhaps upgrading the kernel from that release would be useful? That much I could do. On Tue, Jan 20, 2009 at 12:42 PM, Leann Ogasawara leann.ogasaw...@canonical.com wrote: Hi David, Just in case you'd be willing to test, you may want to try the latest pre-release of Jaunty (currently Alpha3) - http://cdimage.ubuntu.com/releases/jaunty/ . It contains a 2.6.28 based kernel. It would be nice to know if this issue still exists in the upcoming release. Thanks. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- network stalls using r8169 and mtu 2550 https://bugs.launchpad.net/bugs/319214 You received this bug notification because you are a direct subscriber of the bug. -- network stalls using r8169 and mtu 2550 https://bugs.launchpad.net/bugs/319214 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 304298] Re: / partition is read-only after upgrading 8.04 - 8.10
I'm now experiencing the exact same problem on totally different hardware, under totally different circumstances. For a description I'm linking to my post on Ubuntu Forums to avoid repetition: http://ubuntuforums.org/showpost.php?p=6435369postcount=8 db -- / partition is read-only after upgrading 8.04 - 8.10 https://bugs.launchpad.net/bugs/304298 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 304298] Re: / partition is read-only after upgrading 8.04 - 8.10
acpi=off made the laptop bootable and / is mounted rw. [code]$ dmesg | grep -i pnp [ 19.960985] pnp: PnP ACPI: disabled [ 19.960989] PnPBIOS: Scanning system for PnP BIOS support... [ 19.960995] PnPBIOS: Found PnP BIOS installation structure at 0xc00f6a30 [ 19.960999] PnPBIOS: PnP BIOS version 1.0, entry 0xf:0xbcfc, dseg 0x400 [ 19.963828] PNPBIOS fault.. attempting recovery. [ 19.963874] PnPBIOS: Warning! Your PnP BIOS caused a fatal error. Attempting to continue [ 19.963924] PnPBIOS: You may need to reboot with the pnpbios=off option to operate stably [ 19.963974] PnPBIOS: Check with your vendor for an updated BIOS [ 19.964019] PnPBIOS: get_dev_node: unexpected status 0x37 [ 19.964063] PnPBIOS: 0 nodes reported by PnP BIOS; 0 recorded by driver [ 28.734726] isapnp: Scanning for PnP cards... [ 29.088808] isapnp: No Plug Play device found [ 29.117879] PNP: No PS/2 controller found. Probing ports directly. [/code] I thought these messages looked odd, but maybe they're normal with the acpi=off option. db -- / partition is read-only after upgrading 8.04 - 8.10 https://bugs.launchpad.net/bugs/304298 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 87805] Re: users and groups empty since upgrade
I have this problem, although not directly due to an upgrade. I had to reinstall 8.10 from scratch (upgrade from 8.04 was a bomb). I left my /home partition intact. I then attempted to restore my users' accounts and passwords by pasting lines from backed-up /etc/passwd, group, shadow, and gshadow files. I didn't replace the new file entirely from backup, just lines pertinent to my 1000+ uid users. Overall the operation appears to be a success; my users can log in and their files and settings are intact. But there are some odd side- effects, like my primary login (uid 1000) was removed from the admin group in the process. I'm pretty sure I didn't do that manually, but I had to boot up in recovery mode to re-add it. I'm pretty sure my messing around with those four files caused all my users to disappear from that window. So maybe I'm the bug in this scenario. [ducks.] db -- users and groups empty since upgrade https://bugs.launchpad.net/bugs/87805 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 304298] [NEW] / partition is read-only after upgrading 8.04 - 8.10
Public bug reported: 1) Release: Freshly upgraded from 8.04 to 8.10 via GUI Update Manager 2) Package version: Unknown package 3) Expected: system to boot normally immediately after upgrade, as it always did before the upgrade 4) What happened: Quoting from my posts on ubuntuforums.org on this topic: /boot is on its own ext2 partition / is on a 3-disk raid5, md0, xfs /home is on a 3-disk raid5, md1, xfs (same 3 disks, different member partitions) swap partitions on each of the same 3 disks I have a fourth disk with a couple partitions acting as hot spares for md0 and md1 When I try to boot the system normally from the hdd, I get a maintenance shell and some errors, all indicating that / is read-only. It tells me to manually check my fs for errors, but 'xfs_repair -d /dev/md0' fails. 'xfs_repair -L /dev/md0' should kill the fs jounral, but that also fails. 'mount -o remount,rw /' gives some error (I don't have access to this machine at the moment), and / is still mounted ro. If I do a 'mount' it shows that / is mounted rw, probably because mtab is not writable. 'cat /proc/mdstat' shows that my raids are healthy. So unable to get past my maintenance shell, I saved dmesg to a writable partition and booted from a live cd. I used 'mdadm -A /dev/md0' to assemble my array and then ran 'xfs_repair -d /dev/md0'. It made some repairs, I rebooted from the hdd, but / is still ro. I go back to the live cd, assemble the array, and rerun 'xfs_repair -d /dev/md0' but no errors this time. I try 'xfs_repair -L /dev/md0' to kill the journal, reboot from the hdd, and still / is ro. lspci -vvnn is here: http://launchpadlibrarian.net/14057715/lspci partial dmesg and other related info is here: http://ubuntuforums.org/showpost.php?p=6280024postcount=2 db ** Affects: ubuntu Importance: Undecided Status: New -- / partition is read-only after upgrading 8.04 - 8.10 https://bugs.launchpad.net/bugs/304298 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 285595] Re: Intrepid kernel UDMA/33 (slow disk transfer rate)
I didn't see this in 8.04, but upgrading to 8.10 a couple days ago initiated this bug on my system. db ** Attachment added: version.log http://launchpadlibrarian.net/19265812/version.log -- Intrepid kernel UDMA/33 (slow disk transfer rate) https://bugs.launchpad.net/bugs/285595 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 285595] Re: Intrepid kernel UDMA/33 (slow disk transfer rate)
** Attachment added: uname-a.log http://launchpadlibrarian.net/19265817/uname-a.log -- Intrepid kernel UDMA/33 (slow disk transfer rate) https://bugs.launchpad.net/bugs/285595 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 285595] Re: Intrepid kernel UDMA/33 (slow disk transfer rate)
** Attachment added: dmesg.log http://launchpadlibrarian.net/19265826/dmesg.log -- Intrepid kernel UDMA/33 (slow disk transfer rate) https://bugs.launchpad.net/bugs/285595 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 285595] Re: Intrepid kernel UDMA/33 (slow disk transfer rate)
** Attachment added: lspci-vvnn.log http://launchpadlibrarian.net/19265831/lspci-vvnn.log -- Intrepid kernel UDMA/33 (slow disk transfer rate) https://bugs.launchpad.net/bugs/285595 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 285595] Re: Intrepid kernel UDMA/33 (slow disk transfer rate)
I'd like to retract my earlier posts, as I had DMA disabled in my BIOS for some reason. Reversing that resolved this problem for me. db -- Intrepid kernel UDMA/33 (slow disk transfer rate) https://bugs.launchpad.net/bugs/285595 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 276640] Re: The firefox window takes up all of the screen, impossible to reduce size and cannot access the close, reduce and clear screen options. The page also flickers when the mouse passes ove
TKEP's fix is only temporary for me. 8.10 amd64. Additionally, FF's top border is white as though inactive until switching focus to another window and back. db -- The firefox window takes up all of the screen, impossible to reduce size and cannot access the close, reduce and clear screen options. The page also flickers when the mouse passes over certain areas of the screen. Firefox home page appears as a tiny page in the middle of the screen. https://bugs.launchpad.net/bugs/276640 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 222831] Re: e1000 driver loaded for PCI 8086:10b9 instead of e1000e
I did a fresh install of 8.04.1 x86_64 this week and the included e1000e driver (0.2.0) is still broken on this NIC (before and after updating linux-image through apt). I downloaded and compiled Intel.com's latest e1000e (0.4.1.7-NAPI) and that works. -- e1000 driver loaded for PCI 8086:10b9 instead of e1000e https://bugs.launchpad.net/bugs/222831 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 222831] Re: e1000 driver loaded for PCI 8086:10b9 instead of e1000e
This made it onto slashdot this morning. http://linux.slashdot.org/article.pl?sid=08/09/23/133258 db -- e1000 driver loaded for PCI 8086:10b9 instead of e1000e https://bugs.launchpad.net/bugs/222831 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 219473] Re: no policykit access on ltsp thin client
** Description changed: Not sure if this should be pinned to policykit or the ltsp project. The unlock button does not work in control panels such as users settings on thin clients. Is it possible to implement this? Is this a bug or a feature? Some of my staff are administrators and should be able to add users but they do not have access to the server room. In the days - before policykit, Ubuntu administrator's were able to add users without + before policykit, Ubuntu administrators were able to add users without having to know CLI. db -- no policykit access on ltsp thin client https://bugs.launchpad.net/bugs/219473 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 219473] Re: no policykit access on ltsp thin client
There were users logged in on 2 thin clients at that time and nobody on the server. For some reason the first command listed 2 sessions per logged-in user. Both commands were run by uid 1000, so session 4 or 5. I should also mention that the network in question uses the LDM_DIRECTX=True option in lts.conf, making for an unencrypted ssh connection between client and server. I'm not sure if this is relevant or not. ( http://doc.ubuntu.com/edubuntu/edubuntu/handbook/C/customizing-thin-client.html ) db ** Attachment added: unnamed http://launchpadlibrarian.net/15240192/unnamed -- no policykit access on ltsp thin client https://bugs.launchpad.net/bugs/219473 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 219473] Re: no policykit access on ltsp thin client
# ck-list-sessions Session4: uid = '1000' realname = 'David ,,,' seat = 'Seat4' session-type = '' active = TRUE x11-display = 'localhost:12.0' x11-display-device = '' display-device = '/dev/pts/1' remote-host-name = '192.168.0.248' is-local = FALSE on-since = '2008-06-12T02:18:45Z' Session5: uid = '1000' realname = 'David *,,,' seat = 'Seat5' session-type = 'ck-launch-sessi' active = FALSE x11-display = '192.168.0.248:6' x11-display-device = '' display-device = '' remote-host-name = '' is-local = FALSE on-since = '2008-06-12T02:18:45Z' Session6: uid = '1025' realname = 'Tristen ,,,' seat = 'Seat6' session-type = '' active = TRUE x11-display = 'localhost:10.0' x11-display-device = '' display-device = '/dev/pts/0' remote-host-name = '192.168.0.247' is-local = FALSE on-since = '2008-06-12T02:20:57Z' Session7: uid = '1025' realname = 'Tristen ,,,' seat = 'Seat7' session-type = 'ck-launch-sessi' active = FALSE x11-display = '192.168.0.247:6' x11-display-device = '' display-device = '' remote-host-name = '' is-local = FALSE on-since = '2008-06-12T02:20:57Z' # polkit-auth --show-obtainable [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:294:kit_hash_lookup(): key != NULL Not built with -rdynamic so unable to print a backtrace [WARN 10741] kit-hash.c:206:kit_hash_insert():
[Bug 222831] Re: e1000 driver loaded for PCI 8086:10b9 instead of e1000e
I updated my kernel to 2.6.24-17-generic today and got the same result as WhoCares? with e1000e version 0.2.0, i.e., it didn't work. db -- e1000 driver loaded for PCI 8086:10b9 instead of e1000e https://bugs.launchpad.net/bugs/222831 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 226014] [NEW] blacklisted e1000 module still loading
Public bug reported: My Intel motherboard has onboard intel GBE. I am also using an intel pro 1000 PT card. Both should be using the e1000e driver, but the latter loads the e1000 module by default (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/222831), so lsmod shows both the e1000 and e1000e modules loaded on a fresh boot. I added a line blacklist e1000 to the file /etc/modprobe.d/blacklist, but after a reboot e1000 is loaded again for the pro 1000 pt. This can be corrected by doing rmmod e1000e rmmod e1000 modprobe e1000e /etc/init.d/networking restart. I'm not sure if it's necessary to restart the networking but it works. db 1. # lsb_release -rd Description:Ubuntu 8.04 Release:8.04 2. # uname -r 2.6.24-16-generic db ** Affects: ubuntu Importance: Undecided Status: New -- blacklisted e1000 module still loading https://bugs.launchpad.net/bugs/226014 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 226014] Re: blacklisted e1000 module still loading
** Attachment added: lspci-vvnn http://launchpadlibrarian.net/14148622/lspci-vvnn -- blacklisted e1000 module still loading https://bugs.launchpad.net/bugs/226014 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 222831] Re: e1000 driver loaded for PCI 8086:10b9 instead of e1000e
I'm afraid my original description was incomplete. In fact I downloaded the latest e1000e driver from sf.net before blacklisting e1000, so I didn't try the shipping version of e1000e and so I don't know whether would work with the hardware in question or not. db On Thu, May 1, 2008 at 2:36 PM, WhoCares? [EMAIL PROTECTED] wrote: Hi Leann, that can be my fault and there's a chance that the driver shipping with Ubuntu is actually working. I might have to reinstall tonight anyway so I may be able to test this later. In that case I'll report back with more info. -Stefan -- e1000 driver loaded for PCI 8086:10b9 instead of e1000e https://bugs.launchpad.net/bugs/222831 You received this bug notification because you are a direct subscriber of the bug. -- e1000 driver loaded for PCI 8086:10b9 instead of e1000e https://bugs.launchpad.net/bugs/222831 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 222831] Re: e1000e identified as e1000 in Hardy
Same problem here. Causes sine-wave-shaped network history graph in gnome system monitor at any speed and poor thin client performance when affected interface is used on client-facing interface of ltsp server. Blacklisting the e1000 driver corrected both problems. $uname -r 2.6.24-16-generic http://ubuntuforums.org/showthread.php?t=750910 http://marc.info/?l=ltsp-discussm=120900833431608w=2 db ** Attachment added: lspci http://launchpadlibrarian.net/14057715/lspci -- e1000e identified as e1000 in Hardy https://bugs.launchpad.net/bugs/222831 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 219473] [NEW] no policykit access on ltsp thin client
Public bug reported: Not sure if this should be pinned to policykit or the ltsp project. The unlock button does not work in control panels such as users settings on thin clients. Is it possible to implement this? Is this a bug or a feature? Some of my staff are administrators and should be able to add users but they do not have access to the server room. In the days before policykit, Ubuntu administrator's were able to add users without having to know CLI. db ** Affects: policykit (Ubuntu) Importance: Undecided Status: New -- no policykit access on ltsp thin client https://bugs.launchpad.net/bugs/219473 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 204133] Re: wubi install unusable - Buffer I/O error on device loop0
I no longer have access to the problem machine (until August). I'll try wubi on a couple other windows machines I have permanent access to. db -- wubi install unusable - Buffer I/O error on device loop0 https://bugs.launchpad.net/bugs/204133 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 101946] Re: [edubuntu feisty] ltsp client and server sound problem
This is still an issue in Hardy Beta, fully updated as of 4 April 2008. db -- [edubuntu feisty] ltsp client and server sound problem https://bugs.launchpad.net/bugs/101946 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 207509] [NEW] / is read-only after wubi install
Public bug reported: Attempted 4 times wubi install using Ubuntu 8.04 beta x86_64 extracted iso. Attempted 1 time wubi install using x86 extracted iso on same computer. wubi.exe appears to run fine, reboots and installer appears to run fine until second reboot. Second reboot shows ubuntu splash screen with progress bar to completion, but then gdm doesn't start. Screen reverts to logging console. Some investigation shows that / is mounted read-only (/dev/loop0) and lots of I/O errors. Sometimes I got a tty login prompt and sometimes not, but was never able to login. Booting in recovery mode sometimes produced a shell and sometimes not, but in every case / was mounted read-only. I'm not sure what info to provide, so rather than spend hours hand- typing the dmesg output or flooding this report with all kinds of shotgun info that may or may not be useful, I'm seeking feedback on the type of information that would be useful to developers. db ** Affects: ubuntu Importance: Undecided Status: New -- / is read-only after wubi install https://bugs.launchpad.net/bugs/207509 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 130075] Re: Random pauses when transferring data at gigabit speeds with forcedeth driver
The fact that Rodrigo fixed this by using the noapic boot option led me to do some more reading into APIC, and I am convinced that there is a reasonable chance that this problem is due to poor APIC support on my motherboard, which, if true, could also validate Miravlix' theory. Unfortunately I haven't been able to test the noapic option as my board is away on RMA. I will be testing this when it returns. I've read that other users, having disabled apic on their boards, were able to reenable it after a bios update. I have also learned that in time, many great things come from the able kernel team. Here's to hoping. db -- Random pauses when transferring data at gigabit speeds with forcedeth driver https://bugs.launchpad.net/bugs/130075 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 130075] Re: Random pauses when transferring data at gigabit speeds with forcedeth driver
I have to agree that this doesn't look like a hardware problem. If it were, then how would one explain different kernels behaving differently? Parenthetically, I have posted some throughput benchmarks for a handful of nics on the m0n0wall forum for any interested. And no, I have never seen the nforce GBE lose its interrupt or cease up for any reason in my m0n0walls, even under full bench load, but then again, m0n0wall doesn't use SMP either. http://forum.m0n0.ch/index.php/topic,875.0.html db On 10/13/07, BullCreek [EMAIL PROTECTED] wrote: More testing with these boards and latest Gutsy (2.6.22-14-generic x86) yields the following observations above and beyond those previously reported: 1. It still locks up under Gutsy latest (I can't tell any change between 2.6.22-12 and 2.6.22-14). Someone should probably report this as a problem to the kernel mailing list or whoever maintains the forcedeth driver. 2. It isn't hardware though. I booted a XenSource 4.0.1 install in the system (partly to test a different distro and partly to see if they had support for these nforce boards because SuperMicro makes a dual socket Barcelona board based on the big brother workstation version of this NF570 chipset that looks fairly tasty except it has the same dual nforce LAN setup). The Xen kernel gives the same spurious too many iterations but unlike Ubuntu, refused to lock up even after hours of serious abuse. XenSource's kernel is a stripped down version of 2.6.18 based on CentOS 4.4 I believe. 3. FWIW, the cheap PCIe Marvell 88E8053 based NICs from Rosewill mentioned earlier do seem to work reliably in Gutsy (although the requisite sky2 module is a nightmare on other platforms including Xen). I've transfered TB of data both ways with it via NFS in Gutsy with no problem other than high CPU usage (see next item). 4. Both the Marvell and the Nforce hardware can't hold a candle to Intel as far as CPU offloading goes. For troubleshooting this problem, I used an old 1.8Ghz P4 (single core) system running Feisty with an intel 82547EI gigabit adapter on the MB - it never goes above 50% CPU usage serving or pulling at 1Gbps - whereas the Marvell and Nforce solutions routinely use most of what a 2.1GHz dual core Athlon 64 X2 system has to offer, just to run iperf! I know I could make this CPU usage go down by enabling jumbo frames across the board, but that introduces a whole other list of compatibility problems I don't want to face. Long story short - you get what you pay for I guess. It's a shame, because the 6 channel SATA2 controller on these Nforce 570 boards seems to perform quite nicely and reliably using mdadm and RAID5 or RAID6. If the dual nforce LAN worked, the board would be quite a steal for $80 and another $80 or so for a fast Athlon X2 proc - but unfortunately, it doesn't. -- Random pauses when transferring data at gigabit speeds with forcedeth driver https://bugs.launchpad.net/bugs/130075 You received this bug notification because you are a direct subscriber of the bug. -- Random pauses when transferring data at gigabit speeds with forcedeth driver https://bugs.launchpad.net/bugs/130075 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 130075] Re: Random pauses when transferring data at gigabit speeds with forcedeth driver
Do I understand correctly that this will be an issue with my motherboard as long as I am using more than one core of a multicore cpu? How in the world did my motherboard make it onto AMD's list of recommended motherboards for a dual-core AMD cpu? And how can Nvidia market this as their stable Business Platform? I'm feeling cheated. If Steen's post is correct, then my motherboard clearly doesn't do what it claims to do. And if this is truly a hardware issue then we should see the problem occurring in other smp-using OSes too, right? Has anybody seen problems or reports of problems with this in Windows, for example? This is disappointing. I thought I did my research. db On 9/27/07, BullCreek [EMAIL PROTECTED] wrote: I try to boot with the nosmp option to test this and 2.6.20-16-generic just hangs shortly into the boot (no output on any of the virtual screens). Any ideas on how to work around? I don't really see nosmp as a viable solution, but am willing to at least validate it as an option for some. If this is indeed a problem with nforce motherboards, I think it probably needs to get more attention and documentation - as I certainly was never aware of it and sort of just considered that the boards were so plentiful they can't be bad. FWIW, I do notice that Asus uses Broadcom LAN rather than Nvidia's on their AMD server boards that otherwise use the rest of nforce. I wonder if this is why? Miravlix, do you have any links to threads where this has been discussed in public forum before or is it just your personal findings? -- Random pauses when transferring data at gigabit speeds with forcedeth driver https://bugs.launchpad.net/bugs/130075 You received this bug notification because you are a direct subscriber of the bug. -- Random pauses when transferring data at gigabit speeds with forcedeth driver https://bugs.launchpad.net/bugs/130075 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 130075] Re: Random pauses when transferring data at gigabit speeds with forcedeth driver
I just returned one of these RMA. Now I'm wondering if my problems with it were actually due to this bug. I suspect not entirely though, as this card sometimes didn't work right off a fresh boot. http://www.intel.com/network/connectivity/products/pro1000pt_desktop_adapter.htm On 9/29/07, BullCreek [EMAIL PROTECTED] wrote: And how can Nvidia market this as their stable Business Platform? I'm feeling cheated. If Steen's post is correct, then my motherboard clearly doesn't do what it claims to do. I'm ordering a couple of these to see if just disabling the nforce NICs on these boards will result in a stable system under heavy NFS loads. I'll let everyone know how it works out. http://www.newegg.com/Product/Product.asp?item=N82E16833166015 If it doesn't work - I'm considering returning the boards and procs for Intel - although that will be a lot of trouble for all parties involved. -- Random pauses when transferring data at gigabit speeds with forcedeth driver https://bugs.launchpad.net/bugs/130075 You received this bug notification because you are a direct subscriber of the bug. -- Random pauses when transferring data at gigabit speeds with forcedeth driver https://bugs.launchpad.net/bugs/130075 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 130075] Re: Random pauses when transferring data at gigabit speeds with forcedeth driver
iperf -c machine1 -d doesn't lock mine up, but adding -p 2 (any number of multiple threads) will do it every time, although not necessarily right away. And yes, this makes the forcedeth driver virtually useless on a gigabit network. My findings were the same, only a reboot will bring the interface back online. db On 9/25/07, BullCreek [EMAIL PROTECTED] wrote: I've played around with it a bit more, and even with the options max_interrupt_work=20 set in /etc/modprobe.d/forcedeth, it still happens. Only additional thing to report, is I happened upon an easy way to reproduce the hangup every time: 1. Login to machine1 which has a gigabit ethernet card in it and is attached to a gigabit switch. Run iperf -s 2. Login to a machine that has the gigabit forcedeth adapter in it - also hooked up to a gigabit switch. Run iperf -c machine1 -d. The command in step two generates a lot of traffic in that it tells it to test speeds going both ways at once. On both my forcedeth systems, it will lock up the interface almost immediately, requiring a full reboot (i.e. /etc/init.d/networking restart has no effect). Note the problem only occurs under heavy load - if you just run iperf -c machine1 without the -d option, it usually won't lock up. Should we report this bug to the kernel mailing list? I see that back in August, someone reported similar behavior in 2.6.22.1 but said adding the forcedeth.max_interrupt_work=20 option to their bootline fixed it (FWIW, I tried that and just go invalid option with feisty). Here is the thread: http://lkml.org/lkml/2007/8/5/92 Does anyone know how to tell if the options in modprobe.d are in effect - dmesg doesn't show anything and lsmod doesn't have any flags? I have tried putting the appropriate line in /boot/grub/menu.lst, in /etc/modprobe.d/options, and in /etc/modprobe.d/forcedeth and as best as I can tell none have had any effect. P.S. I'm now wishing I had spent a little more and bought Intel boards with Intel NICs. -- Random pauses when transferring data at gigabit speeds with forcedeth driver https://bugs.launchpad.net/bugs/130075 You received this bug notification because you are a direct subscriber of the bug. -- Random pauses when transferring data at gigabit speeds with forcedeth driver https://bugs.launchpad.net/bugs/130075 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 122972] Re: logout stalls until esd is killed
I implemented the workaround outlined here: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/101946/comments/2 which worked, but only on a fresh install. If I were to reverse the workaround I could tell you whether or not it was still an issue, but if the answer is no, then reinstalling at this point is unpalatable. db -- logout stalls until esd is killed https://bugs.launchpad.net/bugs/122972 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 130075] Re: Random pauses when transferring data at gigabit speeds with forcedeth driver
I'm getting this message in Edubuntu Feisty AMD64 while doing tests with iperf on a gigabit link. Both iperf client and server are using the forcedeth driver on identical nic/motherboards. While the failing driver is running in the OS mentioned above, I've had no trouble on the second machine running Ubuntu server 7.04 AMD64. I've found some potentially related threads in other forums: http://lists.debian.org/debian-amd64/2006/08/msg00274.html http://www.nvnews.net/vbulletin/showthread.php?t=57791page=11 Here the command that causes it for me: iperf -c 192.168.0.195 -i 2 -f mbps -t 30 -d -P 16 -P 8 doesn't seem to cause a problem. Here's the partial output of dmesg when the link goes down: [ 1235.537521] eth1: too many iterations (6) in nv_nic_irq. [ 1247.641652] NETDEV WATCHDOG: eth1: transmit timed out [ 1247.641657] eth1: Got tx_timeout. irq: 0036 [ 1247.641660] eth1: Ring at 7b5ec000: next 2597442 nic 2597186 [ 1247.641662] eth1: Dumping tx registers [ 1247.641667] 0: 0036 00ff 0003 017203ca I tried bringing down the link, reloading the forcedeth module and bringing the link back up, but then dmesg | tail gives: [ 1301.525982] eth1: forcedeth.c: subsystem: 01043:816a bound to :00:14.0 [ 1301.553024] eth1: no link during initialization. [ 1301.553263] ADDRCONF(NETDEV_UP): eth1: link is not ready although the interface is connected and lit up. As per somebody's recommendation from an above-linked thread, I tried adding the following option to the forcedeth driver at boot, but I haven't succeeded in doing so: options forcedeth max_interrupt_work=20 I've also attached the output of sudo lspci -vvn. ** Attachment added: lspci -vvn lspci.output http://launchpadlibrarian.net/8750802/lspci.output -- Random pauses when transferring data at gigabit speeds with forcedeth driver https://bugs.launchpad.net/bugs/130075 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 131166] Re: apt-get update deletes local Packages.gz file
I can't recreate this in Edubuntu 7.04 amd64. I followed your steps and after running apt-get update five times the Packages.gz file is still there. db -- apt-get update deletes local Packages.gz file https://bugs.launchpad.net/bugs/131166 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 101946] Re: [edubuntu feisty] ltsp client and server sound problem
I'm using Feisty release and Andrew's fix restored sound to my thin client but not to my server. A fresh install (formatting / but not /home), followed by Andrew's fix preserved sound on my thin client and server. Thanks, Andrew. I hope this will be fixed in Gutsy, if not in Feisty. I can't imagine every user having to reinstall their system after learning about this. db -- [edubuntu feisty] ltsp client and server sound problem https://bugs.launchpad.net/bugs/101946 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 122972] Re: logout stalls until esd is killed
I have investigated this somewhat further and found that if I do in gnome-terminal while logged into X on the server $ esd *** PULSEAUDIO: Unable to connect: Connection refused It appears that esound is not able to run, although enable sofware sound mixing (ESD) is selected in System Preferences Sound. If I'm not mistaken, pulseaudio is the appropriate sound device on a thin client. I'm sure in my steps to reproduce bug I should have included 2a. Change Volume Control Applet device to Pulseaudio. Although I have changed the device back to the server's hardware setting (HDA NVidia (Alsa mixer)) when logged into the server, there appears to be another esound setting somewhere that needs to be changed back manually if not automatically when logged into the server. I checked /etc/esound/esd.conf but saw no such setting. Likewise in gconf-editor. db ** Changed in: esound (Ubuntu) Sourcepackagename: None = esound -- logout stalls until esd is killed https://bugs.launchpad.net/bugs/122972 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 122972] Re: logout stalls until esd is killed
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/8247327/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/8247328/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/8247329/ProcStatus.txt -- logout stalls until esd is killed https://bugs.launchpad.net/bugs/122972 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 122972] logout stalls until esd is killed
Public bug reported: Fresh install of Edubuntu server x86_64 Feisty. Steps to reproduce bug 100% of the time: 1. Create user 2. Boot thin client and login with username 3. Log out of thin client 3. Login to server with username 4. Click the logout button 5. Click any of the logout options The computer is not totally frozen; I can still move the mouse and if there is music playing it continues playing. I can still use tty and ssh. If I login to tty1 with a different user and do ps -u guest echo output.normal while in an X session with guest, then after trying to logout, do ps -u guest echo output.frozen then diff output.normal output.frozen I see 3c3 7879 ?00:00:00 x-session-manag --- 7879 ?00:00:01 x-session-manag 19a20 8631 ?00:00:00 esd which looks like esd has started with the attempt to logout. If I do sudo kill -9 8631 then I get back to my gdm login screen, as if the esd was causing the hang. db ProblemType: Bug Architecture: amd64 Date: Thu Jun 28 23:40:41 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/gnome-panel Package: gnome-panel 1:2.18.1-0ubuntu3.1 PackageArchitecture: amd64 ProcCmdline: gnome-panel --sm-client-id default1 ProcCwd: /home/guest ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SourcePackage: gnome-panel Uname: Linux micah 2.6.20-16-generic #2 SMP Thu Jun 7 19:00:28 UTC 2007 x86_64 GNU/Linux ** Affects: Ubuntu Importance: Undecided Status: New -- logout stalls until esd is killed https://bugs.launchpad.net/bugs/122972 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
