I removed /usr/lib/sasl2/*digestmd5*, then did apt-get --reinstall
install libsasl2-modules.
Pidgin no longer crashes, and I am no longer able to reproduce the
issue.
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/393943
You received this bug notification because you are a
I've found a workaround.
As the -d output suggests, the problem is with the XMPP library, which
I am not using (I'm only using MSN and ICQ). I renamed
/usr/lib/purple-2/libxmpp.so to libxmpp.no and now Pidgin starts
successfully.
Before this, I tried removing the gstreamer-0.10-plugins-bad
I have now updated pidgin/libpurple to 2.5.8 using the instructions
here: http://pidgin.im/download/ubuntu/
The problem is still there. Again, moving/deleting the libxmpp.so file
solved the issue.
Help-About confirmed pidgin and libpurple has been updated to 2.5.8.
--
pidgin crashed with
Maybe I should point out I am running 32-bit 9.04. The problem appeared
less than a week ago, when suddenly Pidgin just wont start. Possibly
related to some updates?
--
pidgin crashed with SIGSEGV
https://bugs.launchpad.net/bugs/393943
You received this bug notification because you are a member
There was an automatic update for pidgin this morning, did not help.
I've tried starting older kernels; same problem in old 2.6.24.
I've tried deleting the /home/username/.pidgin folder, did not help.
This is very frustrating, this is the second time the automatic updates
breaks something in my
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/28553525/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28553526/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/28553527/Disassembly.txt
** Attachment
Sorry, did not work. The problem is still the same. There were some strange
messages about unmet dependencies though...
(
Below is the output. Afterwards, I also tried to remove everything pidgin in
its name using Synaptic, and then reinstall pidgin and everything it depends
on. Did not help.
Thank you, I followed your instructions and it now works properly!
--
NTFS partition is not automatically mounted on boot if it shares hard drive
with an ext3 partition
https://bugs.launchpad.net/bugs/303577
You received this bug notification because you are a member of Ubuntu
Bugs, which is
If this is a configuration problem, would it not still be a kind of bug,
as my system was set up using default settings? I have never changed any
mount settings or anything. Also, I have seen the same behaviour with
two entirely different systems with no same hardware.
The attachments below are
** Attachment added: sudo blkid
http://launchpadlibrarian.net/20422846/sudoblkid
--
NTFS partition is not automatically mounted on boot if it shares hard drive
with an ext3 partition
https://bugs.launchpad.net/bugs/303577
You received this bug notification because you are a member of Ubuntu
Forgot to mention: the name of the internal NTFS partition is
ScorpioNTFS, the name of the external NTFS partition is Passport.
Both of the hard drives are actually WD Scorpios, 120 gb (the internal
one) and 320 gb (the external one).
** Attachment added: sudo fdisk -l
** Attachment added: mount
http://launchpadlibrarian.net/20422853/mount
--
NTFS partition is not automatically mounted on boot if it shares hard drive
with an ext3 partition
https://bugs.launchpad.net/bugs/303577
You received this bug notification because you are a member of Ubuntu
Bugs,
The following attachments are AFTER I mounted the drive from Places
ScorpioNTFS... I do not know if they differ.
** Attachment added: fstab -- after
http://launchpadlibrarian.net/20422888/fstab
--
NTFS partition is not automatically mounted on boot if it shares hard drive
with an ext3
** Attachment added: sudo fdisk -l -- after
http://launchpadlibrarian.net/20422961/sudofdisk-l-after
--
NTFS partition is not automatically mounted on boot if it shares hard drive
with an ext3 partition
https://bugs.launchpad.net/bugs/303577
You received this bug notification because you
** Attachment added: sudo blkid -- after
http://launchpadlibrarian.net/20422979/sudoblkid-after
--
NTFS partition is not automatically mounted on boot if it shares hard drive
with an ext3 partition
https://bugs.launchpad.net/bugs/303577
You received this bug notification because you are a
** Attachment added: mount -- after
http://launchpadlibrarian.net/20422988/mount-after
--
NTFS partition is not automatically mounted on boot if it shares hard drive
with an ext3 partition
https://bugs.launchpad.net/bugs/303577
You received this bug notification because you are a member of
Public bug reported:
Yesterday, sound was working fine. I did nothing out of the ordinary
with my computer. When I shut down the computer, it hung at Stopping
ALSA It hung for a maybe 30 seconds or so, then the screen went
black with a flashing cursor, and I could type stuff that would just
I got the same thing, all sound channels were muted after freeze at
Shutting down ALSA
During one evening, I always got the hang at Shutting down ALSA...
when rebooting or shutting down the PC.
Perhaps not coincidentally, I was having network problems the same
evening, due to maintenance
I had this problem as well. During one evening, I always got the hang at
Shutting down ALSA... when rebooting or shutting down the PC.
Perhaps not coincidentally, I was having network problems the same
evening, due to maintenance from my ISP. (Basically, my local network
was fine, I just didn't
*** This bug is a duplicate of bug 288039 ***
https://bugs.launchpad.net/bugs/288039
Thank you.
My two issues seemed to be duplicates to those two, I marked this as a
duplicate of the sound problem.
** This bug has been marked a duplicate of bug 288039
pulseaudio upgrade breaks sound
--
All updates have been downloaded.
uname -a
Linux hp530 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686 GNU/Linux
echo $LANG
en_US.UTF-8
Nothing out of the ordinary here I guess...
** Attachment added: screen shot
http://launchpadlibrarian.net/20077282/thank%20you.png
--
Public bug reported:
When I boot the system, all NTFS partitions are not mounted. I have seen
this on completely different systems:
System #1 (desktop thingy with ASUS P5B-MX mobo)
- Internal IDE Hard drive, three partitions: 1x NTFS, 1x ext3, 1x swap (in that
order)
System #2 (hp laptop)
-
Public bug reported:
Click System, then About Ubuntu
On the page that is displayed, the second paragraph is:
Thank you for your interest in Ubuntu - the - released in .
Running Ubuntu 8.10, upgraded from 8.04. I do not know how it appeared
in 8.04.
** Affects: ubuntu
Importance:
Unfortunately I am running 8.04 and I don't know how to upgrade the
kernel to anything newer than 2.6.24-21...
Also, I will be unavailable for most of September so I am unable to test
Alpha 5 when it becomes available. When I am able to try it, I will.
Here's a recap with the most relevant info
Sorry, the workaround I stumbled upon was just a coincidence... For
some, probably random reason, the delay was reduced to ~5 seconds for a
number of boots. However, I have now found a REAL workaround... =)
With splash disabled, I looked carefully at the boot text and found that
the freezes were
I just found a kind of workaround:
If I disable the splash screen (either by removing the splash
parameter in grub before booting, or changing grub's configuration),
there is no freeze!
Still, the ntfs sata drive is not automounted, so I guess that is an
unrelated issue.
--
Waiting for root
I tried booting my system from the desktop-i386 iso of ubuntu 7.10 and 8.04.1
(I installed the system from the latter).
7.10 did not have this problem (also, it did not detect my built in sata hd at
all)
8.04 had the exact same problem (and the built in hd was detected, but NOT
automatically
sudo lspci -vvnn lspci-vvnn.log
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/16875682/lspci-vvnn.log
--
Waiting for root file system delay
https://bugs.launchpad.net/bugs/247717
You received this bug notification because you are a member of Ubuntu
Bugs, which is
cat /proc/version_signature version_signature.log
Ubuntu 2.6.24-19.36-generic
** Attachment added: version_signature.log
http://launchpadlibrarian.net/16875634/version_signature.log
--
Waiting for root file system delay
https://bugs.launchpad.net/bugs/247717
You received this bug
dmesg dmesg.log
** Attachment added: dmesg.log
http://launchpadlibrarian.net/16875587/dmesg.log
--
Waiting for root file system delay
https://bugs.launchpad.net/bugs/247717
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
uname -a uname-a.log
Linux hp530 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686
GNU/Linux
** Attachment added: uname-a.log
http://launchpadlibrarian.net/16875569/uname-a.log
--
Waiting for root file system delay
https://bugs.launchpad.net/bugs/247717
You received this bug
Changing the SATA Native Mode BIOS setting from Enabled to Disabled does not
affect anything.
When I installed the system, SATA Native Mode was Enabled.
BIOS is of the latest available version.
During the boot of the session of which I made the debug prints above,
the delay was about 55-59
*** This bug is a duplicate of bug 227003 ***
https://bugs.launchpad.net/bugs/227003
Hmm, I don't think they look similar at all... The only thing they have
in common is the waiting for root file system message...
My problem is completely concistent: it happens at every boot, and the
boot
Public bug reported:
My system is an HP 530, dualbooting Windows Vista and Ubuntu 8.04
(8.04.1?), all recently installed.
This was installed in the following order:
1. Vista, creating the NTFS partition with the Vista installer, leaving 10 GB
of space on the hd.
2. Ubuntu, creating an ext3 and
** Attachment added: ~/.xsession-errors
http://launchpadlibrarian.net/15247088/.xsession-errors
--
Compiz freeze on ATI X300SE
https://bugs.launchpad.net/bugs/225938
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: /var/log/Xorg.0.log
http://launchpadlibrarian.net/15247093/Xorg.0.log
--
Compiz freeze on ATI X300SE
https://bugs.launchpad.net/bugs/225938
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: lspci -vvnn
http://launchpadlibrarian.net/15247100/lspci
--
Compiz freeze on ATI X300SE
https://bugs.launchpad.net/bugs/225938
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
These files are from after a freeze and a hard reset.
The sequence was something like this:
1. Enabled Compiz
2. Used computer for about an hour
3. Left computer for several hours
4. Returned to computer
5. After a few minutes, it froze while changing focus between two maximized
windows (in the
*** This bug is a duplicate of bug 127280 ***
https://bugs.launchpad.net/bugs/127280
I have the funky colours. They were fine in Gutsy but after an upgrade
to Hardy, they freaked out... As the original description; boot splash
is fine, shutdown splash is inverted.
I'm having an ATI X300SE
Public bug reported:
Ok, as I understand by reading the last post in Bug #108527, I should
report this issue seperately as several different problems may cause
identical bugs. Hence, no one else should confirm this bug! Please
correct me if I am wrong.
My issue is the same as many others though,
** Summary changed:
- ATI X300SE freeze when compiz is enabled
+ Compiz freeze on ATI X300SE
** Description changed:
Ok, as I understand by reading the last post in Bug #108527, I should
- report this issue seperately as several different problems may cause
- identical bugs. Hence, no one
Public bug reported:
Binary package hint: compiz
Seriously, this is getting somewhat annoying, as this bug has been
around since the release of Gutsy. It appears to be Bug #108527 but
quite honestly, that report does no longer make any sense.
Problem is:
- The computer freeze randomly, usually
*** This bug is a duplicate of bug 63090 ***
https://bugs.launchpad.net/bugs/63090
I used to have this problem, had three partitions: NTFS and two FAT32
(in that order).
The problem disappeared after removing the FAT32 partitions and resizing
the NTFS partition to cover the whole drive.
The
Have the exact same problem. Not sure I can add something new, but
here's what I know...
- Random freezes, often within less than an hour.
- Any ongoing animation freeze in place, sometimes with graphical glitch
- Mouse cursor still moves, but can't click anything.
- Everything else (music etc)
44 matches
Mail list logo