Not sure if this is related...
I've instlaled both Kubuntu 11.04 and Ubuntu 10.10 on my desktop with a
MSI GeForce GTS 450 and both installations have the same results,
except:
In Kubuntu 11.04, I get the famous Activated but not in use message, while in
Ubuntu 10.10 I don't get this message.
Not sure if this is related...
I've instlaled both Kubuntu 11.04 and Ubuntu 10.10 on my desktop with a MSI
GeForce GTS 450 and both installations have the same results, except:
In Kubuntu 11.04, I get the famous Activated but not in use message, while in
Ubuntu 10.10 I don't get this message.
OK, got the latest jaunty version and that has fixed the problem. Thank
you :)
--
Wesnoth becomes unresponsive when game starts
https://bugs.launchpad.net/bugs/358590
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: wesnoth
When I open wesnoth, the menus work fine, I choose a campaign, go
through the stories leading up to it, and it all works fine so far. Then
the game begins and wesnoth becomes unresponsive. One cpu goes to 100%.
Closing the window does nothing,
** Attachment added: output of lshw
http://launchpadlibrarian.net/25129721/lshw.txt
--
Wesnoth becomes unresponsive when game starts
https://bugs.launchpad.net/bugs/358590
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
UnreportableReason: This is not a genuine Ubuntu package
Not sure why that is the case, I have just installed it (using aptitude
install ...). As far as I know it should be a genuine Ubuntu package.
--
Wesnoth becomes unresponsive when game starts
https://bugs.launchpad.net/bugs/358590
You
Fixed with some help from irc.
I had not installed wesnoth-music and this caused the problem. This is a
bug that has been fixed in version 1.6.1 of wesnoth.
An alternative work around (if you don't want to install the music
package) is to turn off the music in game. (On the first screen, click
This is confirmed by talking to upstream on irc, they have a patch in
their svn repository. The patch looks pretty small, so can this be
included in the jaunty release?
** Changed in: wesnoth (Ubuntu)
Status: New = Confirmed
--
Wesnoth becomes unresponsive when game starts
Just to note for others who find this bug - there is another kernel
available particularly for the aspire one. You can get it from
http://www.aspireonekernel.com/
http://www.kuki.me/downloads/
It's officially for the kuki distribution (which is based on ubuntu
jaunty) but works fine with stock
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/24486633/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/24486638/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24486639/Dependencies.txt
**
Public bug reported:
I use an aspire one (A110) - 8 GB ssd.
The machine seemed to go into hibernate fine, but when I pushed the
power button it started a normal boot.
The system seemed to notice this and asked if I wanted to do a bug
report, so hopefully all relevant information is attached.
Right, I'm starting to follow the instructions at
https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume
The behaviour does seem consistent (tried 3 times - same every time)
So I tried booting with no_console_suspend and (on VT1) doing
setfont /usr/share/consolefonts/Uni1-VGA8.psf.gz
OK, carried on and echoed various things to /sys/power/xyz as per the
wiki page in the above comment. Booted with no_console_suspend. To copy
from there
# lsmod lsmod.output.txt
# echo devices /sys/power/pm_test
# echo platform /sys/power/disk
# echo disk /sys/power/state
# dmesg
** Attachment added: dmesg-devices-platform.txt
http://launchpadlibrarian.net/24488183/dmesg-devices-platform.txt
--
[Acer AOA110] hibernate/resume failure
https://bugs.launchpad.net/bugs/351066
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: dmesg-core-reboot.txt
http://launchpadlibrarian.net/24488205/dmesg-core-reboot.txt
--
[Acer AOA110] hibernate/resume failure
https://bugs.launchpad.net/bugs/351066
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: dmesg-core-platform.txt
http://launchpadlibrarian.net/24488201/dmesg-core-platform.txt
--
[Acer AOA110] hibernate/resume failure
https://bugs.launchpad.net/bugs/351066
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Package available in ppa.
** Changed in: mypasswordsafe (Ubuntu)
Assignee: (unassigned) = mish (mishd)
Status: New = In Progress
--
MyPasswordSafe package needs updating
https://bugs.launchpad.net/bugs/221893
You received this bug notification because you are a member of Ubuntu
Bugs
** Changed in: mypasswordsafe (Ubuntu)
Status: Confirmed = In Progress
--
MyPasswordSafe crashes on file save
https://bugs.launchpad.net/bugs/199012
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Here is the .diff.gz aswell
** Changed in: mypasswordsafe (Ubuntu)
Status: In Progress = Confirmed
** Attachment added: the diff.gz
http://launchpadlibrarian.net/16368887/mypasswordsafe_0.0.20061216-1ubuntu1%7Eppa1.diff.gz
--
MyPasswordSafe package needs updating
Hello, think I've done the right thing subscribing the ubuntu-universe-
sponsors ... There is a link to the package in my ppa above. This
version will be ahead of debian, but the upstream release was in 2006 so
it is about time, should be fine for intrepid I think. Be nice to get
it into hardy
I've got around to learning to package, so I've packaged up the newer
version and put it in my PPA. You can get it by adding the following
lines to your /etc/apt/sources.list
deb http://ppa.launchpad.net/mishd/ubuntu hardy main
deb-src http://ppa.launchpad.net/mishd/ubuntu hardy main
Please use
I've got around to learning to package, so I've packaged up the newer
version and put it in my PPA. You can get it by adding the following
lines to your /etc/apt/sources.list
deb http://ppa.launchpad.net/mishd/ubuntu hardy main
deb-src http://ppa.launchpad.net/mishd/ubuntu hardy main
Please use
One workaround I've found is to use an external USB hub. This won't
work for everyone I imagine, but I was inspired to try by one of the
above comments. It may work for you if, like me:
* most devices work OK with USB2
* you have one device that doesn't (MP3 players seem to be the common one)
*** This bug is a duplicate of bug 226279 ***
https://bugs.launchpad.net/bugs/226279
** This bug has been marked a duplicate of bug 226279
Kernel 2.6.24-17 - broken resume from suspend to RAM
--
linux-image-2.6.24-17-generic don't work after resume suspend/hibernate
*** This bug is a duplicate of bug 226279 ***
https://bugs.launchpad.net/bugs/226279
** This bug has been marked a duplicate of bug 226279
Kernel 2.6.24-17 - broken resume from suspend to RAM
--
Update to kernel 2.6.24-17 kills networking on resume from suspend
*** This bug is a duplicate of bug 226279 ***
https://bugs.launchpad.net/bugs/226279
** This bug has been marked a duplicate of bug 226279
Kernel 2.6.24-17 - broken resume from suspend to RAM
--
[Hardy] [Regression] 2.6.24-17-generic breaks suspend
https://bugs.launchpad.net/bugs/235186
*** This bug is a duplicate of bug 226279 ***
https://bugs.launchpad.net/bugs/226279
** This bug has been marked a duplicate of bug 226279
Kernel 2.6.24-17 - broken resume from suspend to RAM
--
[regression] Broken suspend wakeup in kernel 2.6.24-17
https://bugs.launchpad.net/bugs/235462
might be a duplicate of bug 226279
Maybe read through that and mark this as a duplicate if you agree.
--
networking fails on resume from suspend
https://bugs.launchpad.net/bugs/235347
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This may well be a duplicate of bug 226279
Please read through that, and if it is the same, then mark this bug as a
duplicate of it.
--
[Hardy] Laptop can't resume from suspend
https://bugs.launchpad.net/bugs/235315
You received this bug notification because you are a member of Ubuntu
Bugs,
For those reporting the failure of returning from suspend to RAM with
2.6.24-17, the main bug for this appears to be bug 226279. Please go
there.
Other comments for this bug should be as the title - suspend to disk
(more commonly referred to as hibernate).
--
[hardy][regression] System doesn't
Having looked at bug 221893 I thought I'd try that version. So I
downloaded
http://www.semanticgap.com/myps/release/MyPasswordSafe-20061216-amd64.bin.tgz
and tried using that - no problem :)
I have tried building from the source package (had to install qt3-dev-
tools) and got some errors.
On my hardy install, I am asked for my password in graphical mode. (I
have an unencrypted boot partition, and the other partitions are in an
encrypted logical volume, installed using the alternative install disk).
So if someone else can confirm this is the case for other encrypted set
ups (at
This is also upstream in debian
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427074
Not sure what the procedure is here ... Contact the debian admin and
ask them to update? Contact MOTU?
--
MyPasswordSafe package needs updating
https://bugs.launchpad.net/bugs/221893
You received this bug
Also needed to install x11proto-scrnsaver-dev and libxss-dev to get the
full compile to work. Once compiled it works fine - I can save files
without crashing. So it would appear we just need to use the newer
source code.
This bug is in the debian bug tracker aswell - http://bugs.debian.org
Last night when switching off I thought I'd try killing one job at a
time. The first job I tried, which did allow the shutdown to continue,
was
/usr/bin/seahorse-agent --execute /usr/bin/keytouchd-launch x-session-
manager
A quick search finds quite a few bugs that involve seahorse crashing.
I did find this in my /var/log/messages
Apr 25 13:23:35 whisper kernel: [ 243.484594] keytouchd[9293]: segfault
at 8 rip 7f5535c28dc2 rsp 7fff3e42ccc8 error 4
--
[hardy] keytouch blocks logout
https://bugs.launchpad.net/bugs/186713
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 186713 ***
https://bugs.launchpad.net/bugs/186713
Based on the last few comments, I've marked this as a duplicate of bug
186713 Add another comment if you think that is wrong.
** This bug has been marked a duplicate of bug 186713
[hardy] keytouch blocks
It looks to me like a problem with gdm. Here's why
* It affects logout as well as shutdown for me.
* Ctrl-Alt-Backspace gets me out of it
* Going to a tty and doing $ sudo /etc/init.d/gdm restart gets me out of it.
* I have found entries in /var/log/messages about gdm (see below).
From
sudo lshw
** Attachment added: lshw.txt
http://launchpadlibrarian.net/13898730/lshw.txt
--
gnome shutdown/logout hangs
https://bugs.launchpad.net/bugs/210859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: dmesg.txt
http://launchpadlibrarian.net/13898751/dmesg.txt
--
gnome shutdown/logout hangs
https://bugs.launchpad.net/bugs/210859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This part of /var/log/messages includes the segfault lines.
** Attachment added: Part of /var/log/messages
http://launchpadlibrarian.net/13898779/messages
--
gnome shutdown/logout hangs
https://bugs.launchpad.net/bugs/210859
You received this bug notification because you are a member of
Based on my recent comments, gdm seems like a good place to start.
** Changed in: gdm (Ubuntu)
Sourcepackagename: None = gdm
--
gnome shutdown/logout hangs
https://bugs.launchpad.net/bugs/210859
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Actually, maybe it is a duplicate of bug 186713 - do others on this bug
have keytouch installed? If you're not sure try
$ aptitude search keytouch
and if there is an i in front of keytouch, then you have it installed.
--
gnome shutdown/logout hangs
https://bugs.launchpad.net/bugs/210859
You
I have this problem as well. It developed fairly recently - I have been
running hardy (amd64) for at least a month, and for most of that time
shutdown worked fine. It started as a problem maybe a week ago.
When selecting shutdown from the logout menu, all panels disappear, but
the mouse cursor
Found some relevant comments about why the speed of the connection may be lower
than expected.
http://lwn.net/Articles/278191/
To quote it here:
At the moment the semi-free madwifi is more reliable than ath5k with 2.6.25-rc
kernels[*], due
(I suspect) to problems with the mac80211 layer being
I have this problem as well (Fujitsu Siemens Esprimo E5916, USB
keyboard). From the gnome keyboard preferences, I have chosen Swap ESC
and Caps Lock
The keys work as far as typing output goes (checked in vim) but the caps
lock key turns the caps lock light on and off, and the Escape key does
I get the same problem on hardy (amd64). I previously used
MyPasswordSafe with gutsy (i386) and had no problems.
$ aptitude show mypasswordsafe
...
Version: 0.0.20050615-2
...
Reading works fine.
As an extra note, the file output when saving is 192 bytes long. And
when trying to reopen it
I think your problem is related to using /dev/random in your crypttab
swap /dev/sda4 /dev/random swap
/dev/random collects entropy from different parts of the system
(including mouse/touchpad usage). I'm not sure, but I suspect entropy
is not saved at shutdown, so entropy must be collected
I suspect this is a duplicate of bug #118539 (the same card is mentioned
in at least one of the comments).
--
dlink DWL-G650+
https://bugs.launchpad.net/bugs/132083
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
had the same problem when I tried tribe 5.
This is stopping me using gutsy for testing purposes. And if this is
not fixed before release there'll be a lot of very unhappy people who
installed feisty and their wireless 'just worked' (tm) do an upgrade and
suddenly they can't access the net ...
Did some more searching today and I now think my problem is a duplicate
of bug #92299
--
Changing ESSID requires reboot or, or manual iwconfig for changes to take effect
https://bugs.launchpad.net/bugs/80499
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
Did a little experiment on boot today. I booted into safe mode. When I
landed at the root command prompt I typed ifconfig and discovered that
the network was working fine at that point. ifconfig reported my IP
address and I was able to ping the internet.
I then did telinit 5 to complete the
Since yesterday's updates, the behaviour has changed a little - I still
have no network connection on boot (and the essid is not set). But now,
when I run
$ sudo /etc/init.d/networking restart
it does set the essid and start the network properly. So only one
command to run each time I start my
Related to this (I think) is that the network restart does not set the
essid for me any more. I've just upgraded to feisty with settings that
used to work. The relevant part of /etc/network/interfaces is
auto wlan0
iface wlan0 inet dhcp
wireless-essid default
wlan0 is my primary interface.
Don't know if it's related but the latest cryptsetup update in edgy
appears to have broken setting up my (non luks) partition. I have
usplash turned off, but have been unable to get a passphrase prompt. I
have tried manually putting in the fixes to
/lib/cryptsetup/cryptdisks.functions but have
A little further information. On my other (luks) system it works fine.
Anyone got ideas as to what might be the non-luks specific bug?
--
Upstart doesn't activate luks volumes (also non luks) in cryptsetup
https://launchpad.net/bugs/62751
--
ubuntu-bugs mailing list
Is there a manual way to make it use the legacy driver (which Christian
Bjälevik reports works OK)? By the legacy driver I assume you are
referring to
/lib/modules/2.6.17-10-386/kernel/drivers/net
/wireless/rt2x00-legacy/rt2500/rt2500.ko
I've tried a few things but been unable to get ra0 up as
The fix worked for me :)
As a possible improvement to the code, to include the old option (ie
ON_VT == yes )
stdin=`readlink /proc/self/fd/0`
if [ ${stdin#/dev/null} != $stdin ]; then
if [ $ON_VT != yes ]; then
exec env ON_VT=yes /usr/bin/openvt -f -c `fgconsole` $0 $@
else
Oh and I had to do a little searching for the file (as no one seems to
mention it in the text above). The fix should be applied to
/lib/cryptsetup/cryptdisks.functions
(I'm not familiar with patch, so after a little blundering around
failing to get it to work I went for the direct edit).
--
59 matches
Mail list logo
