I do not get any bug report window (I don't know what Johannes means),
for me the setup simply freezes. ps shows that the gpg-agent starts
pinentry, but then nothing happens. No windows is shown, and the
application wait for a password that never comes.
--
You received this bug notification
I have attached a pinentry-kwallet.debug trace. Apparently pinentry is
started, but nothing happens (until I get a timeout from the host
program). I also saw the invocation in pstree:
gpg-agent───mksh───pinentry
but nothing happens on screen.
Running your commands manually failed, apparently
This happens to me, too, server installation is currently broken in some
settings. This appears to be a bug or a race in the installer logic, as
running the apt-get command by hand in a chroot succeeded. So apparently
there is not really an error during the underlying package installation,
just
Have you tried cleaning your package cache before running these
commands? (sudo aptitude clean). There is definitively something funny
happening here, I think some package is lying about its version number.
Of course it could be that I had accidentally replaced the offending
package earlier
Correction: I did not test this properly, eqonomize still crashes. It
just does not crash immedately when not opening an existing file. But
adding an entry for example still crashes it reliably, with the same
error message as the original poster:
eqonomize: symbol lookup error: eqonomize:
Interesting. Indeed it seems to be possible to fix the issue by doing a
sudo aptitude reinstall libqt4-xml libqtcore4 libqtgui4
sudo aptitude purge eqonomize eqonomize-doc
sudo aptitude install eqonomize
but the funny thing is that aptitude claims that the version numbers are
the same before and
A workaround for this is to run
apt-get --build source eqonomize
(assuming you have all necessary development packages installed)
and to then run
sudo dpkg -i equonomize*.deb
eqonomize works afterards.
I think the problem is that the current official binary packages are
build against a wrong
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/42034995/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/42034996/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/42034997/Disassembly.txt
** Attachment
Public bug reported:
Binary package hint: getmail4
getmail4 uses the deprecated sets module, which triggers a warning in
jaunty. Executing getmail produces the warning
/usr/share/getmail4/getmailcore/baseclasses.py:26: DeprecationWarning: the sets
module is deprecated
import sets
which is
*** This bug is a duplicate of bug 284215 ***
https://bugs.launchpad.net/bugs/284215
Here is the backtrace - I hope its now with full dbg-information...
** Attachment added: backtrace
http://launchpadlibrarian.net/18608439/gdb-evolution.txt.gz
--
evolution crashed with SIGSEGV in
*** This bug is a duplicate of bug 284215 ***
https://bugs.launchpad.net/bugs/284215
Previous backrace hat no debug info on libcamel - this one is better...
** Attachment added: backtrace
http://launchpadlibrarian.net/18608518/gdb-evolution.txt.gz
--
evolution crashed with SIGSEGV in
I attached an apparently corrupted akregator archive. The file is the
content of .kde/share/apps/akregator, as written by akregator itself. At
startup akregator crashes reproducible until I delete the content of the
Archive directory.
** Attachment added: corrupted akregator archive
It crashed on me today, so the bug seems still in there. It manfiests itself
roughly like this:
1. start akkregator
2. use it for a few hours, read messages. No problem.
3. quit akregator
4. restart akregator. crash.
I think the crash does not occur for each restart, but once akregator crashes
I no longer have the laptop, so unfortunately I cannot test this on
hardy/intrepid.
--
iwlist ath0 scan corrupts the kernel
https://bugs.launchpad.net/bugs/35837
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
The crash went away with the latest thunderbird update, so the bug can
probably be closed now. If you really want to I can of course try to
reproduce it again with the old version.
--
[GUTSY] thunderbird crashed
https://bugs.launchpad.net/bugs/129055
You received this bug notification because
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/8595588/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/8595589/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/8595590/Disassembly.txt
** Attachment
Private bug reported:
Binary package hint: thunderbird
Thunderbird crashes immediately at start with a SIGBUS. This only
happens since the recent thunderbird update (ca. 2007-07- 27).
ProblemType: Crash
Architecture: amd64
Date: Sun Jul 29 15:10:32 2007
DistroRelease: Ubuntu 7.10
17 matches
Mail list logo
