@Andres - thanks, it would be nice to be able too test the wake-on-ARP,
so putting this in a PPA looks like a great idea.
This being said, I just realized that my server does not have the "Wake-
On: a" support that is required, so I won't be able to test this unless
I change the card :-(
--
You
Thanks for the quick answer ! Indeed it is an issue between powernap and
pm-utils. I had looked in /etc/pm but did not think to look in /usr/lib
/pm-utils.
I really think this disable_wol should be deactivated by default (how
much power does that save ?) - many people will want to use auto
suspend
OK, I think I have found the reason for this bug. It is not due to stage
2 in power nap, but rather stage 1 - during powersave mode the ethernet
configuration for the card is changed, which deactivates wake-on-lan.
Since power nap first enters in stage1 then stage2, when the computer is
turned off
Added the apport information.
WOL=WakeOnLAN
thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989175
Title:
Powernap prevents waking from WOL
To manage notifications about this bug go to:
htt
apport information
** Attachment added: "modified.conffile..etc.powernap.config.txt"
https://bugs.launchpad.net/bugs/989175/+attachment/3107396/+files/modified.conffile..etc.powernap.config.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: "modified.conffile..etc.powernap.action.txt"
https://bugs.launchpad.net/bugs/989175/+attachment/3107395/+files/modified.conffile..etc.powernap.action.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/989175/+attachment/3107394/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989175
Ti
apport information
** Tags added: apport-collected precise
** Description changed:
I have a server running Ubuntu 12.04. The current issue is the
following:
* if I activate 2nd-stage powernap to poweroff (or 'shutdown -h' by
using /etc/powernap/action), the computer will not wake when
** Attachment added: "/etc/powernap/config (with 2nd stage commented out)"
https://bugs.launchpad.net/bugs/989175/+attachment/3106397/+files/config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9891
Public bug reported:
I have a server running Ubuntu 12.04. The current issue is the
following:
* if I activate 2nd-stage powernap to poweroff (or 'shutdown -h' by
using /etc/powernap/action), the computer will not wake when sent a
magic packet.
* if however, I manually shutdown the computer (usi
Version 1.9.6.0-2 is now used in Oneiric, so this bug can be closed.
** Changed in: objcryst-fox (Ubuntu Oneiric)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
The package now in Debian has been fixed a few days ago, see:
https://buildd.debian.org/status/package.php?p=objcryst-fox
http://packages.qa.debian.org/o/objcryst-fox.html
I'm not sure how this propagates to the ubuntu package ?
--
You received this bug notification because you are a member of U
The bug has now been fixed in the upstream package (version
1.9.6.0-R1295), and Objcryst-Fox now compiles correctly with gcc 4.6, as
tested with an up-to-date oneiric.
The testing was made using the shared libraries (frreglu, newmat and
wxGTK) provided with ubuntu.
Up-to-date package:
https://sou
** Changed in: objcryst-fox (Ubuntu Oneiric)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770878
Title:
objcryst-fox version 1.9.0.2-1 failed to build on amd64 wit
** Changed in: objcryst-fox (Ubuntu Oneiric)
Assignee: (unassigned) => vincefn (vincent-favre-nicolin)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/770878
Title:
objcryst-fox version 1.9.
Thanks for the quick upload !
This looks OK, I installed the new package using:
wget
http://archive.ubuntu.com/ubuntu/pool/universe/i/ipython/ipython_0.10.1-1ubuntu0.1_all.deb
dpkg -i ipython_0.10.1-1ubuntu0.1_all.deb
And with this new version, both ipython -pylab and ipython -wthread seem to
I really believe this qualifies for an SRU:
* the thread-handling of ipython represents a large part of its added value
compared to a standard python console
* it affects matplotlib, although a workaround using a different backend is
possible, it removes some functionality (described in this bug
> png is supported which is lossless and compresses very well unless
your plotting photos.
Unfortunately I am plotting images recorded from 2D detectors, so
compression is not that good with png (yes I can post-convert to jpg but
I'd rather avoid that sort of kludge).
> I have 0.10.2 in my ppa:
A quick followup: about the 'threads' issue, this seems to be a bug
related to ipython (see https://bugs.launchpad.net/bugs/777420 and
https://github.com/ipython/ipython/issues/185).
This is fixed by upgrading to ipython 0.10.2, which is available from ubuntu
oneiric (no additional dependency com
Answering my own query: apparently installing ipython 0.10.2 (from
oneiric) fixes the issue:
http://launchpadlibrarian.net/70857487/ipython_0.10.2-1_all.deb
Is there any chance this could be pushed as an update for natty (when
installing, no dependency conflict appeared) ?
--
You received this
I also have this problem with ipython & natty.
Even if TkAgg works fine, not being able to use GTK(Agg) means that
figures cannot be saved directly as jpg's - which is a problem when you
want to save a lot (1's) of 2D plots without using too much disk
space.
Also, I can't seem to be able tu u
Same issue under natty (11.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762025
Title:
acroread package from canonical reports errors on amd64 systems
--
ubuntu-bugs mailing list
ubuntu-bugs@l
>That kinda sucks. Are you sure that you are using the Wx backend for
>Mayavi. Do you have the python-traitsbackendwx package installed? If
>something is not working with Wx, Mayavi now defaults to Qt.
I had installed python-traitsbackendwx, python-traitsgui, and not
python-traitsbackendqt. I al
> What's your IPython version?
Python 2.7.1+ (r271:86832, Apr 11 2011, 18:13:53)
IPython 0.10.1 -- An enhanced Interactive Python.
>When you try with simply python, do you use'mlab.show()' to start the
event loop?
Ah, right - the mlab window popped open without using show(), so I did
not try
Hi,
I have a freshly updated natty system. I can confirm the bug. I can
also confirm that updating to python-enthoughtbase 3.0.6 fixes the issue
when importing mlab, but then the event loop seems stuck (can't interact
with the mlab window, using ipython -wthread or simply python).
For those who
@gied:
The behavior looks a bit different so it's not the same bug - which is why
you'll have to file another bug report, otherwise you won't get attention.
It would be interesting to test if you can solve your issues by using
kernel 2.6.31, as I did before (you can find it in
ftp://ftp.ubuntu.co
Thanks a lot for the quick fix !
I tested the -proposed packages (manually installed nvidia-current-dev,
nvidia-current and nvidia-current-modaliases with
version=195.36.15-0ubuntu3), and they work fine !
I tested this with my two nvidia cards, 9600GT+GTX295, without any
problem, CUDA also works
Alan wrote:
"This may be related to
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/519123";
Apparently not - that other bug happens when booting the live CD, which
I believe does not use the nvidia driver but rather nouveau. Moreover
removing the second card does not help, contrary to thi
Alberto Milone wrote:
"If you didn't use the Nvidia installer (and installed the driver from Jockey)
and you're experiencing a problem with 2 cards then you're facing a different
issue and I'd be glad if you could open a separate bug report about it."
OK, I just did that. New bug report speci
** Attachment added: "nvidia195.36.15-bug-report.log.gz"
http://launchpadlibrarian.net/47216462/nvidia195.36.15-bug-report.log.gz
--
nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system
https://bugs.launchpad.net/bugs/573557
You received this bug notification because you are a
Public bug reported:
This is a followup on a bug discussion started in bug
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers/+bug/548362
This bugs is related to a crash when loading X, for PC with at least two
nVidia graphics cards and using the nvidia-current drivers (195.36.15)
Alberto Milone wrote
> Please try to reproduce the problem and attach your /var/log/Xorg.0.log and
> /var/log/Xorg.0.log.old
Sorry, this is impossible - somehow the crash occurs *before* Xorg writes
anything in the log. I have attached the nvidia bug report.
What I did was:
1) Start from wo
seanlano wrote:
>I had a similar problem, but I only have one graphics card.
>
>On 32bit Lucid everything worked fine, but on 64bit Lucid all of the
>nvidia drivers cause the system to not load a graphical environment,
>but I can still use a tty to uninstall the driver and go back to nouveau.
petogal wrote:
> the same for me
> 32bit system video is GeForce Go7300
This bug happens with two nVidia cards - do you also have two ?
--
nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system
https://bugs.launchpad.net/bugs/548362
You received this bug notification because you ar
Has anyone encountered this bug with an 32bit (rather than amd64)
installation ?
--
nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system
https://bugs.launchpad.net/bugs/548362
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
> Changed back to confirmed since this affects Ubuntu's 'nvidia-current'
package.
Thanks - indeed this bug is not about the installer but really about a
hard crash which affects the nvidia-current package.
--
nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system
https://bugs.lau
This morning I tried the beta drivers 195.36.24 (available from the
x-swat ppa), with the same result as before : hard crash with
2.6.32-21+195.36.24, and booting fine using 2.6.31-21+195.36.24...
I also updated my bug report on the nvnews forum
(http://www.nvnews.net/vbulletin/showthread.php?p=22
Other similar bug report:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/567202
--
nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system
https://bugs.launchpad.net/bugs/548362
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have the same symptoms, which seems to be related to the nVidia
driver, the 2.6.32 kernel, and haveing TWO nVidia cards.
A workaround is using a 2.6.31 kernel.
See the other bug report (maybe should be merged):
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers/+bug/548362
--
** Tags added: lucid
--
nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system
https://bugs.launchpad.net/bugs/548362
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
I took the liberty of renaming the bug as it seems not to be an
installation issue, but rather a crash at restart around the time X
launches, specifically when using dual cards with a 2.6.32+ kernel.
I can confirm (after a few hours) the 2.6.31-21 kernel works fine,
including CUDA 3.0 computing.
** Summary changed:
- Cannot install nvidia 195.36.15 - crashes system
+ nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system
--
nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system
https://bugs.launchpad.net/bugs/548362
You received this bug notification because
Further news... I managed to boot find by installing older kernel
2.6.31-21-generic (from ftp://ftp.ubuntu.com/ubuntu/pool/main/l/linux/),
still with the nvidia-current (195.36.15) package.
So far, it seems to work all right - I had a graphic message telling
me that nvidia-current had failed t
Hi,
I have a similar issue: I am testing Lucid on a PC (amd64) )with two nVidia
cards (one 9600GT with two screens attached, and ont GTX295 for CUDA
computing). Kubuntu (beta2) installs fine, and works all right with the nouveau
driver.
Since I need CUDA, I installed nvidia-current (195.36
Is there any chance that this will be backported to jaunty ? This is
fairly annoying - work a day or 2 in KDE, then you need tolog off and
start again...
--
Epic plasma memory leak (0.1 mb / sec)
https://bugs.launchpad.net/bugs/343944
You received this bug notification because you are a member of
Correction- I meant that both "gstreamer0.10-plugins-good" and
"gstreamer0.10-ffmpeg" are required for video display to work.
--
[kubuntu] OpenOffice Impress: Movies do not play
https://bugs.launchpad.net/bugs/375891
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I can confirm this bug (same symptoms) and the proposed solution -
adding gstreamer0.10-ffmpeg does allow to play movies in OpenOffice 3.01
(on my up-to-date jaunty 9.04 amd64)
It may be good to add "gstreamer0.10-ffmpeg" as a dependency to
"openoffice.org-java-common" ?
--
[kubuntu] OpenOffice
I misread your first message - yes it is defintely beyond the scope of
that bug fix, because you want SATA, not SAS.
Have you looked at: http://wiki.debian.org/pata_marvell ?
Another person (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/335615) used that
paged and managed to see its sa
> Should this fix allow me to mount a SATA RAID array with this
controller?
The question is: does the mvsas module actually support hardware raid
?
You may want to ask the modules' author. Apparently most people under
linux use software raid which is quite good.
--
Marvel SAS 6440 not suppo
I can confirm that bug - I'm using:
Jaunty (up-to--date)
2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:31:32 UTC 2009 x86_64 GNU/Linux
nvidia-180
I also have two monitor on a single card (I have another nvidia card
just for number crunching).
The strangest thing is that this slow disappearing of
Kernel 2.6.28-12 (which is now in jaunty's proposed-updates) adds
support for mvsas:
uname -a
Linux gre019099 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:31:32 UTC 2009
x86_64 GNU/Linux
find /lib/modules/ -iname *mvsas*
/lib/modules/2.6.28-12-generic/kernel/drivers/scsi/mvsas.ko
Note tha
Kernel 2.6.28-12 (which is now in jaunty's proposed-updates) adds
support for mvsas:
uname -a
Linux gre019099 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:31:32 UTC 2009
x86_64 GNU/Linux
find /lib/modules/ -iname *mvsas*
/lib/modules/2.6.28-12-generic/kernel/drivers/scsi/mvsas.ko
See https:
I can confirm that 2.6.28-12 (which is now in jaunty's proposed-
updates) fixes this issue.
uname -a
Linux gre019099 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:31:32 UTC 2009
x86_64 GNU/Linux
find /lib/modules/ -iname *mvsas*
/lib/modules/2.6.28-12-generic/kernel/drivers/scsi/mvsas.ko
** Tags added: jaunty kernel marvell sas
--
Marvel SAS 6440 not supported, missing mvsas module in kernel
https://bugs.launchpad.net/bugs/352336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/24567885/uname-a.log
--
Marvel SAS 6440 not supported, missing mvsas module in kernel
https://bugs.launchpad.net/bugs/352336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
NB: The issue is the same for the -generic and -server kernels. The
-generic is more important to fix as it is used for the installer cd/dvd
images.
** Attachment added: "proc_version_signature.log"
http://launchpadlibrarian.net/24567882/proc_version_signature.log
--
Marvel SAS 6440 not suppo
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/24567857/lspci-vvnn.log
--
Marvel SAS 6440 not supported, missing mvsas module in kernel
https://bugs.launchpad.net/bugs/352336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/24567853/dmesg.log
--
Marvel SAS 6440 not supported, missing mvsas module in kernel
https://bugs.launchpad.net/bugs/352336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: linux-image-2.6.28-11-generic
The Serial Attached Scsi (SAS) diver for "Marvell Technology Group Ltd. Device
6440" is not included in the kernel. This prevents using SAS disks with Ubuntu
jaunty.
This driver is included in a number of motherboards (in
59 matches
Mail list logo
