[Bug 1598300] Re: CUPS web interface stops responding after a while
Thank you Robie for pointing to the fix in comment 21 and for the comment that the final fix should be exactly as that one. Any estimate about when will we see the final fix in updates? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: CUPS web interface stops responding after a while To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 538774] [NEW] scipy.io.loadmat() excessively slow (regression)
Public bug reported: Binary package hint: python-scipy Recent ubuntus (at least from 9.04 till lucid) provide scipy v0.7.0 (python-scipy) which has an important regression problem for the function scipy.io.loadmat(). The loadmat() imports data from Matlab format (.mat) files into NumPy arrays, a task which is very popular among scipy users. Note that there is no alternative to using this function if you need to work with Matlab files. Scipy v0.7.0 introduced a severe regression problem in that function which became excessively slow, like requiring tens of minutes instead of ten seconds to load files. The result is that the loadmat() function is unusable in SciPy v0.7.0. This bug has been tracked and solved by SciPy developers nearly one year ago with very simple patch. Details here, with a test case and thorough discussion: http://thread.gmane.org/gmane.comp.python.scientific.devel/9934/focus=9974 The very simple patch is here: http://article.gmane.org/gmane.comp.python.scientific.devel/9944 it modifies few lines of gzipstreams.py which lies here: /usr/share/pyshared/scipy/io/matlab/gzipstreams.py Note that within the discussion's thread there more than one patch was proposed, but the only correct one is the last proposed, which the above link refers to. I am attaching the same patch here for your convenience. Please apply it or upgrade python-scipy package to a more recent SciPy version. Thanks. ** Affects: python-scipy (Ubuntu) Importance: Undecided Status: New -- scipy.io.loadmat() excessively slow (regression) https://bugs.launchpad.net/bugs/538774 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 538774] Re: scipy.io.loadmat() excessively slow (regression)
** Patch added: Original patch from SciPy-dev mailing list http://launchpadlibrarian.net/40931375/scipy-gzipstreams.patch -- scipy.io.loadmat() excessively slow (regression) https://bugs.launchpad.net/bugs/538774 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 120375] Re: cannot boot raid1 with only one disk
Hosed wrote: Hi, I have Ubuntu 9.04. I have Two (2) 36gb Seagate Cheetah with Raid 1 - Mirroring Setup. When I boot to Ubuntu 9.04 with One (1) of the hard disks unplugged, it fails to boot, it drops me to a shell with initramfs. What's the deal with that? Does it mean that Raid1 is NOT WORKING with Ubuntu 9.04? Any help is greatly appreciated. Thanks. Hi, I had a similar issue on Friday: a disk failed on a raid 1 ubuntu 9.10 system. After shutdown I removed the failed disk and added a new one. While booting I got an initramfs shell, as in your case. In my case the instructions on screen said that the system requested me whether to boot with a degraded array (y/N) or not and that and I did not answer quickly enough to the question, so, after timeout, it brought me the initramfs shell. To be honest I never saw that question on screen and the reason was that the splashscreen covered it. So I just rebooted and pressed 'y' some times when the splashscreen appeared and then the degraded boot started as expected. After that I had to manually partition the new disk (I have 2 different raid1 systems, one for /boot, one for / ) and add each partition to the raid system: sfdisk -d /dev/sda | sfdisk /dev/sdb # partition sdb as sda mdadm /dev/md0 -a /dev/sdb1# add sdb1 to the raid1 system md0 (/boot) mdadm /dev/md1 -a /dev/sdb2# add sdb2 to the raid1 system md1 (/) WARNING: this worked for my setting so don't take them as general instructions! If you have a mirroring setup than you could need just to add sdb1. After this the new disk sdb started syncing as expected. HTH, Emanuele -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 You received this bug notification because you are a member of Ubuntu Server Team, which is a subscriber of a duplicate bug. -- 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 120375] Re: cannot boot raid1 with only one disk
Hosed wrote: Hi, I have Ubuntu 9.04. I have Two (2) 36gb Seagate Cheetah with Raid 1 - Mirroring Setup. When I boot to Ubuntu 9.04 with One (1) of the hard disks unplugged, it fails to boot, it drops me to a shell with initramfs. What's the deal with that? Does it mean that Raid1 is NOT WORKING with Ubuntu 9.04? Any help is greatly appreciated. Thanks. Hi, I had a similar issue on Friday: a disk failed on a raid 1 ubuntu 9.10 system. After shutdown I removed the failed disk and added a new one. While booting I got an initramfs shell, as in your case. In my case the instructions on screen said that the system requested me whether to boot with a degraded array (y/N) or not and that and I did not answer quickly enough to the question, so, after timeout, it brought me the initramfs shell. To be honest I never saw that question on screen and the reason was that the splashscreen covered it. So I just rebooted and pressed 'y' some times when the splashscreen appeared and then the degraded boot started as expected. After that I had to manually partition the new disk (I have 2 different raid1 systems, one for /boot, one for / ) and add each partition to the raid system: sfdisk -d /dev/sda | sfdisk /dev/sdb # partition sdb as sda mdadm /dev/md0 -a /dev/sdb1# add sdb1 to the raid1 system md0 (/boot) mdadm /dev/md1 -a /dev/sdb2# add sdb2 to the raid1 system md1 (/) WARNING: this worked for my setting so don't take them as general instructions! If you have a mirroring setup than you could need just to add sdb1. After this the new disk sdb started syncing as expected. HTH, Emanuele -- cannot boot raid1 with only one disk https://bugs.launchpad.net/bugs/120375 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 155681] Re: emacs22 and python-mode do not play together
Same problem for me on hardy: ipython inside emacs does not work (as default python shell). Even using latest ipython (0.9.1). I had to revert to emacs21 to let it work. Any hint on how to use emacs22 together with ipython in hardy? -- emacs22 and python-mode do not play together https://bugs.launchpad.net/bugs/155681 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 206864] Re: Unable to set max_cstate on hardy kernel
Victor's solution works well and it is straightforward. I'm using it on a Dell D430 and the whining noise disappears. Unfortunately the CPU heating increases too much and causes too active (noisy) fans. For standard use (editing txt) CPU temperature is around 65 Celsius degrees when max_cstate is C2, and only 59 (i.e., no fans) when max_cstate is C8. So, at least on D430, you have to trade-off fans noise and cpu noise. -- Unable to set max_cstate on hardy kernel https://bugs.launchpad.net/bugs/206864 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 208181] Re: Optional Information Needed to Connect to Samba Share
Quite the same problem for me: a fresh install of Hardy Heron (amd64) updated until today (21 Apr 2008). Everything works well with some other Gutsy box. In any case smbclient works well. It seems a gnome issue... Places - Connect to Server... - Windows share I fill these entries: - Server : 192.168.235.8 - User name : *** - Domain name : *** Then I got an error: 'Can't display location smb://192.168.235.8/ No application is registered as handling this file' If I repeat I got: 'Can't display location smb://192.168.235.8/ Location is already mounted' But there is no evidence in Nautilus or on Desktop about that connection. If I provide the 'Folder' information too, so: Palces - Connect to Server... - Windows share - Server : 192.168.235.8 - Folder : public - Unser name : *** - Domain name : *** After the password prompt I got the usual message 'Can't display location smb://192.168.235.8/ No application is registered as handling this file'... but a 192.168.235.8 icon appears on Desktop (it's the smb connection)! If I double click it I get the authorization request (login, password and domain) and then a _second_ icon appears on the screen, identical to the previous one. Now nautilus shows successfully the content of the windows share. If I unmount the 'first' smb connection (left click on the first icon on Desktop) it disappears but the connection to the windows share still holds. Unmounting the second smb connection removes the actual connection. Even more strange: If I use gnomevfs from command line everithing works ok, even without specifying the target folder: gnomevfs-ls smb://192.168.235.8 (asks for login, domain and password) then it shows the required information. -- Optional Information Needed to Connect to Samba Share https://bugs.launchpad.net/bugs/208181 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 119630] Re: spurious keyboard input on intel macbook to blobwars and mplayer
Same on my macbook C2D x86_64. But here follows an explanation. Try unloading applesmc module. Mplayer is getting input from the macbook accelerometer that act as joystick. When you touch the keyboard or just the laptop case there is a little motion detected by the accelerometer. Then a joystick event is generated and processed by mplayer causing the mess. Try it when applesmc is loaded and mplayer running: tap the laptop case in different places to see different joystick movements :) In any case I believe this is a bug: applesmc is way too useful to unload it just for mplayer. Mplayer should be more smooth to joystick events. I guess other packages are affected by this issue. -- spurious keyboard input on intel macbook to blobwars and mplayer https://bugs.launchpad.net/bugs/119630 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 151016] Re: New in 2.6.22-13: System doesn't always wake from suspend
I can confirm the same bug on my macbook with 2.6.22-14 (CPU: Intel Core 2 Duo T7400 2.16GHz). Just a (most probably unrelated) note: I started having this issue after playing a bit with powertop (USB autosuspend etc.). Never experienced in 2.6.22-13. -- New in 2.6.22-13: System doesn't always wake from suspend https://bugs.launchpad.net/bugs/151016 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
