Bug#408230: Bug #408230
severity 408230 important tags moreinfo thanks Looking at the backtrace, it appears to be related to OpenGL, meaning a 3D Windows app, not just any Windows app (assuming I'm reading it correctly). It would be helpful if you provided more info about what apps you were trying to run that crashed. Given that it doesn't crash for everyone, I'm downgrading it to important. No need for an unnecessary RC bug when Etch is trying to get out. :) pgp2HUQcKfTEE.pgp Description: PGP signature
Bug#321102: more ways to reproduce this bug
On Monday 15 January 2007 06:45, Bastian Venthur wrote: One last word about this bug: Bugs like this will always be reproducible until two-part actions like move mail from a to b (= copy mail from a to b, delete mail from a) are not handled somewhat atomic. In the current implementation KMail does not even try to do stuff like this atomic. If you fix this, then I think you will fix the bug. Summary: I've presented altogether five ways how certain situations in KMail can lead to data loss. I even was able to lose data by just justing CTRL-L like upstream suggests. All my examples might seem minimalistic and somewhat artificial, but please keep in mind that this is just in order to make the bug easy to reproduce! It's not hard to imagine how situations like this can happen to an average user on a more complicated setup. Thank you, Bastian, for writing that. I think that is the best explanation I've seen so far. I'm not sure if doing dIMAP atomically would make sense; that sounds like regular, online IMAP to me. The whole point of dIMAP is to make changes offline and then sync them all at once. (Although the reason I use dIMAP is merely to keep an offline copy of my IMAP mail for backup. I would love a hybrid IMAP mode that would keep a local copy of all messages, and make changes live on the server as you make them when you are online, but queue changes for later syncing when you're in offline mode [and KMail even has an offline mode option]). I think a good workaround would be for KMail to keep track of whether it has unsynced changes, and warn the user if he tries to close KMail or log out before syncing the changes. It would also be nice if the connection timeout/retry code was made more robust to cope better with times where the server or connection to it goes down. Just yesterday I had some timeouts while uploading a large message to the server after moving it from one folder to another (why can't it just tell the server to move the message, rather than uploading it again?), and the process didn't finish until I stopped and resynced a couple of times, because KMail didn't timeout and retry on its own. Perhaps the real solution is to get rid of a separate disconnected/offline IMAP mode and make a single, hybrid IMAP mode. When you're online, it should make changes on the server as you make them locally. When you're offline, it should queue changes for later syncing, and warn the user if he quits or logs out without syncing them. And whether you're online or offline, it should have an option to keep local copies of all messages. pgpe0HSbV7XKU.pgp Description: PGP signature
Bug#321102: Bug#350851 Bug#321102: KMail data loss still not fixed
close 350851 4:3.5.5-1 thanks Hi Bastian, On Mon, Jan 08, 2007 at 10:12:17PM +0100, Bastian Venthur wrote: reopen 350851 thanks Hi, I know this mail sucks (like this whole bug) but looking at the relevant KDE bugreport, I really doubt that this bug is fixed. http://bugs.kde.org/show_bug.cgi?id=104956 I'm not using KMail anymore so I can't give any first hand information, but I'm still following the relevant KDE bugreports and It simply looks like this bug is not fixed. Why was it closed anyway? Looks like upstreams bugreport is still open too. So, you do not use kmail anymore, go to the kde bugzilla and see people is still suffering this bug in kubuntu and decide to re-open this bug in the Debian BTS? The commit that should fix this bug was not committed before the kde3.5.5 release, so only distributions that have hand-picked the fix from svn had it included. It is 'closed' in kde bugzilla. 'Verified' is the 'step' after 'fixed' in bugzilla wordings. Verified that it is fixed). Don't mix it with 'confirmed' which is a confirmation that the bug exists. Ana Ana, If you check the latest reports on KDE #104956, you'll see that Christian Maluck reports mail loss with the 1.9.5 version in Kubuntu, which checking the changelog reveals to have the patch that is merged upstream in 3.5.5, which means it has the same patch that Debian has. Clearly, regardless of the upstream bug tracker's status field (which I and others would change but are unable to), this bug is not solved. I just experienced it myself a short time ago, and others are also experiencing it. Why don't you just reopen this bug, rather than asking me to open an entirely new bug and throwing away the logs associated with this one? This is a severely damaging bug resulting in mail loss both locally and on the server. Please reopen it until it is truly fixed. Adam Porter pgphJ7Gc6TJhA.pgp Description: PGP signature
Bug#350851: kmail: More mail loss :(
On Friday 29 December 2006 04:37, Ana Guerrero wrote: tags 350851 +fixed-upstream notfound 350851 4:3.5.5.dfsg.1-4 close 350851 4:3.5.5-1 thanks On Thu, Dec 28, 2006 at 07:06:16PM -0600, Adam Porter wrote: [...] I hate to be the bearer of bad news, but KMail still has this problem. (Or maybe this is actually a separate bug caused by a separate problem, but the end result is still mail loss in disconnected IMAP accounts.) Sorry Adam, we (KDE team) have been discussing this and we think this bug is fixed. Since this bug was fixed in october only you has reported this problem again. Also, after read your mail, it does not seem you have exactly the same problem neither. So, i'm closing the bug and you always can open a new one if you find out what it is exaclty the problem. P.S: btw, perhaps you could use /dev/input/mice instead? This is very disappointing. I just lost eight e-mails completely from my dIMAP account; they're just gone. Other people on the KDE bug tracker also reported the No Subject e-mails in the same KDE bug report. Not only was my local copy erased, but KMail erased the copy on the server as well. Were it not for my forwarding e-mails to GMail before they land in my inbox, I'd never see those e-mails again. There's absolutely no way to recover them. So I just don't understand how you can claim the bug is fixed, when I just experienced exactly what the bug reports: data loss with disconnected IMAP account. Clearly, KMail's dIMAP account support is still not completely trustworthy. And how will opening a new bug report do any good? People who have an interest in this problem are already subscribed to these bug reports. Opening a new one will just make it that much less likely for them to find out that the problem still exists. Please reconsider your decision and reopen this bug. At the very least, people need to be aware that the problem still exists. P.S. Thank you for your suggestion, but /dev/input/mice does not use the evdev driver. I think there is a way to configure udev to assign the same eventX device every time, but I haven't been successful in doing so yet. pgpJn3T9mxX9O.pgp Description: PGP signature
Bug#350851: kmail: More mail loss :(
tags 350851 -fixed-upstream reopen 350851 found 350851 4:3.5.5.dfsg.1-4 thanks (Actually I can't seem to reopen this bug in KDE. Argh. If someone doesn't notice and reopen it, I'll file a new one and link it to Debian.) It's with a heavy heart that I reopen this bug on KDE's and Debian's trackers. Here's what just happened to me (using KMail 4:3.5.5.dfsg.1-4 from Debian): Every time I reboot, the system changes my mouse evdev device back and forth from /dev/input/event[1|2] to /dev/input/event[1|2], so I end up with no mouse control, having to switch to another VT, edit xorg.conf and restart X. KMail is usually in my previous session, and I have auto-login set up in KDM, so when I booted, it logged me in, started KMail and downloaded new mail. When I returned and saw that there was no mouse control, I edited xorg.conf and restarted KDM. I probably should have used the keyboard to log out of my KDE session first, rather than restarting KDM and causing X and all child processes to be terminated. But still, should that have caused seven e-mails that were displaying perfectly fine in my inbox and two subfolders to suddenly turn to No Subject, completely-empty-view-the-source-and-there's-zilch goners? Then after logging back in, KMail proceeded to upload those empty mails to the IMAP server, erasing the e-mails there as well. Luckily I forward all my e-mail to GMail as well, so I can still see them there. The strange part is, after I restarted X and logged back in and started KMail, the e-mails in my inbox were fine, at first. I read one and replied to it even! But then when I clicked on the next unread message, the subject and sender of the message I just clicked on turned into No Subject and Unknown. And then when I clicked on the message that I had *just read and replied to*, it also turned into No Subject Unknown! Then when I checked two other folders, the new messages in them were also No Subject Unknown! I hate to be the bearer of bad news, but KMail still has this problem. (Or maybe this is actually a separate bug caused by a separate problem, but the end result is still mail loss in disconnected IMAP accounts.) pgpR4rBnochSH.pgp Description: PGP signature
Bug#404157: FTBFS: detect-autoconf.pl can't find autom4te, causes ./admin/cvs.sh: line 33: --version: command not found
On Friday 22 December 2006 02:33, Sune Vuorela wrote: How is your perl? Do you have autoconf2.13 installed? $ acp autoconf autoconf: Installed: 2.61-3 Candidate: 2.61-3 Version table: *** 2.61-3 0 800 http://ftp.us.debian.org unstable/main Packages 100 /var/lib/dpkg/status 2.61-1 0 900 http://ftp.us.debian.org testing/main Packages $ acp autoconf2.13 autoconf2.13: Installed: 2.13-58 Candidate: 2.13-58 Version table: *** 2.13-58 0 900 http://ftp.us.debian.org testing/main Packages 800 http://ftp.us.debian.org unstable/main Packages 100 /var/lib/dpkg/status $ acp perl perl: Installed: 5.8.8-7 Candidate: 5.8.8-7 Version table: *** 5.8.8-7 0 800 http://ftp.us.debian.org unstable/main Packages 100 /var/lib/dpkg/status 5.8.8-6.1 0 900 http://ftp.us.debian.org testing/main Packages As far as I know, Perl is fine on my system. I'm not aware of any other problems with it. I have another problem that I suppose could be related. I commented out that part of detect-autoconf.pl, and now in the build process I get this error: make[1]: Entering directory `/home/first/Temp/src/akregator/kdepim-3.5.5.dfsg.1' autoconf (GNU Autoconf) 2.61 *** automake (GNU automake) 1.9.6 found. *** Creating acinclude.m4 *** Creating configure.files *** Creating config.h template /usr/bin/autoconf2.50: line 582: exec: : not found automake: /usr/bin/autoconf2.50 failed with exit status: 127 make[1]: *** [dist] Error 1 make[1]: Leaving directory `/home/first/Temp/src/akregator/kdepim-3.5.5.dfsg.1' make: *** [debian/stamp-cvs-make] Error 2 E: Building failed I don't have a clue what could be causing this. Thanks for your help. pgp9RN6vVVOre.pgp Description: PGP signature
Bug#404157: FTBFS: detect-autoconf.pl can't find autom4te, causes ./admin/cvs.sh: line 33: --version: command not found
Package: kdepim Version: 4:3.5.5.dfsg.1-4 Severity: serious Justification: no longer builds from source -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ~/Temp/src/temp/kdepim-3.5.5.dfsg.1$ dpkg-buildpackage -b -rfakeroot make[1]: Entering directory `/home/first/Temp/src/temp/kdepim-3.5.5.dfsg.1' ../admin/cvs.sh: line 33: --version: command not found *** AUTOCONF NOT FOUND!. *** KDE requires autoconf 2.53 or newer make[1]: *** [dist] Error 1 make[1]: Leaving directory `/home/first/Temp/src/temp/kdepim-3.5.5.dfsg.1' make: *** [debian/stamp-cvs-make] Error 2 ~/Temp/src/temp/kdepim-3.5.5.dfsg.1$ cd admin ~/Temp/src/temp/kdepim-3.5.5.dfsg.1/admin$ perl detect-autoconf.pl # Unable to find autom4te!! ~/Temp/src/temp/kdepim-3.5.5.dfsg.1/admin$ which autom4te /usr/bin/autom4te $ apt-cache policy autoconf autoconf: Installed: 2.61-3 Candidate: 2.61-3 Version table: *** 2.61-3 0 800 http://ftp.us.debian.org unstable/main Packages 100 /var/lib/dpkg/status $ apt-cache policy automake1.9 automake1.9: Installed: 1.9.6+nogfdl-3 Candidate: 1.9.6+nogfdl-3 Version table: *** 1.9.6+nogfdl-3 0 900 http://ftp.us.debian.org testing/main Packages 800 http://ftp.us.debian.org unstable/main Packages 100 /var/lib/dpkg/status - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kdepim depends on: ii akregator 4:3.5.5.dfsg.1-2 RSS feed aggregator for KDE ii kaddressbook4:3.5.5.dfsg.1-2 KDE NG addressbook application ii kalarm 4:3.5.5.dfsg.1-2 KDE alarm message, command and ema ii kandy 4:3.5.5.dfsg.1-2 KDE mobile phone utility ii karm4:3.5.5.dfsg.1-2 KDE time tracker tool ii kdepim-kfile-plugins4:3.5.5.dfsg.1-2 KDE File dialog plugins for palm a ii kdepim-kio-plugins 4:3.5.5.dfsg.1-2 KDE pim I/O Slaves ii kdepim-kresources 4:3.5.5.dfsg.1-2 KDE pim resource plugins ii kdepim-wizards 4:3.5.5.dfsg.1-2 KDE server configuration wizards ii kitchensync 4:3.5.5.dfsg.1-2 Synchronization framework ii kleopatra 4:3.5.5.dfsg.1-2 KDE Certificate Manager ii kmail 4:3.5.5.dfsg.1-2 KDE Email client ii kmailcvt4:3.5.5.dfsg.1-2 KDE KMail mail folder converter ii knode 4:3.5.5.dfsg.1-2 KDE news reader ii knotes 4:3.5.5.dfsg.1-2 KDE sticky notes ii konsolekalendar 4:3.5.5.dfsg.1-2 KDE konsole personal organizer ii kontact 4:3.5.5.dfsg.1-2 KDE pim application ii korganizer 4:3.5.5.dfsg.1-2 KDE personal organizer ii korn4:3.5.5.dfsg.1-2 KDE mail checker ii kpilot 4:3.5.5.dfsg.1-2 KDE Palm Pilot hot-sync tool ii ksync 4:3.5.5.dfsg.1-2 KDE Sync ii ktnef 4:3.5.5.dfsg.1-2 KDE TNEF viewer ii libindex0 4:3.5.5.dfsg.1-2 KDE indexing library ii libkcal2b 4:3.5.5.dfsg.1-2 KDE calendaring library ii libkdepim1a 4:3.5.5.dfsg.1-2 KDE PIM library ii libkgantt0 4:3.5.5.dfsg.1-2 KDE gantt charting library ii libkleopatra1 4:3.5.5.dfsg.1-2 KDE GnuPG interface libraries ii libkpimexchange14:3.5.5.dfsg.1-2 KDE PIM Exchange library ii libkpimidentities1 4:3.5.5.dfsg.1-2 KDE PIM user identity information ii libksieve0 4:3.5.5.dfsg.1-2 KDE mail/news message filtering li ii libktnef1 4:3.5.5.dfsg.1-2 Library for handling KTNEF email a ii libmimelib1c2a 4:3.5.5.dfsg.1-2 KDE mime library ii networkstatus 4:3.5.5.dfsg.1-2 KDE network status monitor kdepim recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFi1oX5+GdyTDsrJsRAv1kAJ0T9qvdb8dAVHlM2E3zwQe+dMpMYwCdFxjg LjVkId5rk16Rr+3jREpnnPc= =luVO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#399016: kaddressbook: Data loss, involving strange file duplication and locking problems
Package: kaddressbook Version: 4:3.5.5.dfsg.1-1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have noticed this behavior for some time, since back in KDE 3.4.x at least, but this is the last straw, so I'm filing a bug. A week or so ago I entered a few new contacts into my KDE address book. When I went to look up the contacts' e-mail addresses just now, my search in KABC found nothing. I opened a shell and found this: $ cd .kde/share/apps/kabc/ $ ll total 504K drwx-- 2 first first 4.0K 2006-11-16 05:15 lock drwx-- 2 first first 4.0K 2005-12-19 18:58 logos drwx-- 2 first first 4.0K 2005-12-19 18:58 photos drwx-- 2 first first 4.0K 2005-12-19 18:58 sounds - -rwx-- 1 first first 41K 2006-11-16 05:15 std.vcf - -rwx-- 1 first first 41K 2006-11-16 05:15 std.vcf__0 - -rw-r--r-- 1 first first 41K 2006-11-16 05:15 std.vcf__1 - -rw-r--r-- 1 first first 41K 2006-11-16 05:15 std.vcf__2 - -rwx-- 1 first first0 2006-11-09 03:03 std.vcf2WPY5b.new - -rw-r--r-- 1 first first 41K 2006-11-16 05:15 std.vcf__3 - -rw-r--r-- 1 first first 41K 2006-11-16 05:15 std.vcf__4 - -rw-r--r-- 1 first first 41K 2006-11-16 05:15 std.vcf__5 - -rw-r--r-- 1 first first 42K 2006-11-16 05:15 std.vcf__6 - -rw-r--r-- 1 first first 42K 2006-11-16 05:15 std.vcf__7 - -rw-r--r-- 1 first first 42K 2006-11-16 05:15 std.vcf__8 - -rw-r--r-- 1 first first 41K 2006-11-16 05:15 std.vcf__9 - -rwx-- 1 first first0 2006-11-13 02:55 std.vcfVRcdrb.new $ ll lock total 8.0K - -rw-r--r-- 1 first first 11 2006-11-09 03:03 _home_first_.kde_share_apps_kabc_std.vcfMuo9TRh0 - -rw-r--r-- 1 first first 10 2006-11-13 02:55 _home_first_.kde_share_apps_kabc_std.vcfSj652hp5 $ rgrep lash . ../std.vcf__6:EMAIL:[EMAIL PROTECTED] ../std.vcf__7:EMAIL:[EMAIL PROTECTED] ../std.vcf__8:EMAIL:[EMAIL PROTECTED] As you can see, there are many duplicates of the std.vcf file, and two lock files. The dates on the lock files don't match the date on the current std.vcf file. There are two old std.vcf...new files that are empty. There are three std.vcf__# files that are larger than the rest, and inside those three files are the contacts that I entered that are now missing in std.vcf. Thankfully, I can copy one of those three files over the std.vcf file and regain those contacts. But what in the world is going on here? I'm rating this as grave because I consider it a data-loss bug. Most users won't have any idea how to dig for the vcf files, and even if they do, there's no guarantee that the missing data will be there. And even worse, if this went unnoticed for a while, you could end up with a branching scenario where some files had some contacts, and other files had other contacts, and somehow you'd have to merge them back together into a single file to get them all back. Worst of all, this makes the KDE address book system (which is used by Kontact/KMail/etc) completely unreliable and untrustworthy. I hope Etch isn't released with this bug. Please let me know how I can help debug this. - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-2-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages kaddressbook depends on: ii kdelibs4c2a4:3.5.5a.dfsg.1-3 core libraries and binaries for al ii libacl12.2.41-1 Access control list shared library ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libattr1 2.4.32-1 Extended attribute shared library ii libaudio2 1.8-2 The Network Audio System (NAS). (s ii libbluetooth2 3.7-1 Library to use the BlueZ Linux Blu ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries ii libfam02.7.0-11 Client library to control the FAM ii libfontconfig1 2.4.1-2 generic font configuration library ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libgcc11:4.1.1-19GCC support library ii libgnokii3 0.6.14-1 Gnokii library ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libidn11 0.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libkcal2b 4:3.5.5.dfsg.1-1 KDE calendaring library ii libkdepim1a4:3.5.5.dfsg.1-1 KDE PIM library ii libkleopatra1 4:3.5.5.dfsg.1-1 KDE GnuPG interface libraries ii libktnef1 4:3.5.5.dfsg.1-1 Library for handling KTNEF email a ii libpng12-0 1.2.8rel-7PNG library - runtime ii libqt3-mt 3:3.3.7-1 Qt GUI Library (Threaded runtime v
Bug#396158: Thanks
Joey, Thanks for the patch. Installing it seems to work fine, but I notice it still gives the using old version message. I don't know why, or if it's even a problem. (Reading database ... 300902 files and directories currently installed.) Preparing to replace duplicity 0.4.2-10+b1 (using duplicity_0.4.2-10.1_i386.deb) ... INFO: using old version '/usr/bin/python2.3' Unpacking replacement duplicity ... Setting up duplicity (0.4.2-10.1) ... INFO: using old version '/usr/bin/python2.3' pgpFQBMUwV6YR.pgp Description: PGP signature
Bug#316572: This is an apt-build bug; needs to either sign packages or --allow-unauthenticated
merge 369173 316572 retitle 369173 Doesn't work with authenticated apt; needs to sign debs or --allow-unauthenticated severity 369173 important thanks This is an apt-build bug. Installing apt-key does not fix the problem of apt-build creating unsigned packages. These unsigned packages will cause apt-get to complain when apt-build tries to install them. To fix this, apt-build should either: a) Sign packages that it builds (it would be nice if the postinst script used debconf to offer to automatically create a new signing key, or use an existing key to sign [which would require entering your passphrase when you use apt-build]) b) Pass through to apt the --allow-unauthenticated option. This is less desirable, since it would cause apt to not check other packages it installs, such as build-deps. However, to mitigate this, apt-build could only pass this through when installing packages it created, rather than build-deps. Without one of these solutions, apt-build will always fail to install packages it builds, requiring the user to then run $(apt-get install whatever) to actually install the packages apt-build makes. Temporarily, for my own use, I added --allow-unauthenticated to @apt_args, but that is not a good long-term solution. pgp63V9hSEmSk.pgp Description: PGP signature
Bug#389334: libgalago1.0-cil: Package setup fails
Package: libgalago1.0-cil Version: 0.5.0-1 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I tried to upgrade to Beagle 0.2.10, which pulled this in, but I got this error, and now I can't even shutdown beagle with $(beagle-shutdown): Setting up libgalago1.0-cil (0.5.0-1) ... * Installing 1 assembly from libgalago1.0-cil into Mono ** ERROR **: file threadpool.c: line 990 (mono_thread_pool_init): assertion failed: (async_call_klass) aborting... = Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. = Stacktrace: Native stacktrace: /usr/lib/libmono.so.0(mono_handle_native_sigsegv+0x113) [0xa7d4f5fa] /usr/lib/libmono.so.0 [0xa7d241e2] [0xe440] /lib/tls/i686/cmov/libc.so.6(abort+0x109) [0xa7ad0fb9] /usr/lib/libglib-2.0.so.0(g_logv+0x454) [0xa7c63114] /usr/lib/libglib-2.0.so.0(g_log+0x29) [0xa7c63149] /usr/lib/libglib-2.0.so.0(g_assert_warning+0x77) [0xa7c631c7] /usr/lib/libmono.so.0(mono_thread_pool_init+0x16a) [0xa7de58de] /usr/lib/libmono.so.0(mono_runtime_init+0x23) [0xa7decc65] /usr/lib/libmono.so.0(mini_init+0xb34) [0xa7d254f3] /usr/lib/libmono.so.0(mono_main+0x1388) [0xa7d41922] /usr/bin/mono [0x8048522] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xa7abbea8] /usr/bin/mono [0x8048471] Use of uninitialized value in scalar chomp at /usr/share/cli-common/runtimes.d/mono line 142. Use of uninitialized value in concatenation (.) or string at /usr/share/cli-common/runtimes.d/mono line 111. ** ERROR **: file threadpool.c: line 990 (mono_thread_pool_init): assertion failed: (async_call_klass) aborting... = Got a SIGABRT while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. = Stacktrace: Native stacktrace: /usr/lib/libmono.so.0(mono_handle_native_sigsegv+0x113) [0xa7e225fa] /usr/lib/libmono.so.0 [0xa7df71e2] [0xe440] /lib/tls/i686/cmov/libc.so.6(abort+0x109) [0xa7ba3fb9] /usr/lib/libglib-2.0.so.0(g_logv+0x454) [0xa7d36114] /usr/lib/libglib-2.0.so.0(g_log+0x29) [0xa7d36149] /usr/lib/libglib-2.0.so.0(g_assert_warning+0x77) [0xa7d361c7] /usr/lib/libmono.so.0(mono_thread_pool_init+0x16a) [0xa7eb88de] /usr/lib/libmono.so.0(mono_runtime_init+0x23) [0xa7ebfc65] /usr/lib/libmono.so.0(mini_init+0xb34) [0xa7df84f3] /usr/lib/libmono.so.0(mono_main+0x1388) [0xa7e14922] /usr/bin/mono [0x8048522] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xc8) [0xa7b8eea8] /usr/bin/mono [0x8048471] sh: line 1: 25484 Aborted /usr/bin/mono /usr/lib/mono/1.0/gacutil.exe /i `basename /usr/lib/cli/galago-sharp/galago-sharp.dll` /dev/null E: installing Assembly /usr/lib/cli/galago-sharp/galago-sharp.dll failed - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-k7 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages libgalago1.0-cil depends on: ii cli-common0.4.3 common files between all CLI (.NET ii libgalago20.5.1-2Galago presence library ii libglib2.0-cil2.8.3-1CLI binding for the GLib utility l ii libmono-corlib1.0-cil 1.1.13.8-1 Mono core library (1.0) libgalago1.0-cil recommends no packages. - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFF2o65+GdyTDsrJsRAgMyAJ9FkxTCZq7mG16BcxT9ADwckEvfNQCg1Bna 7FlePz11NLI2BngygoFewNE= =jLrs -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#389334: libgalago1.0-cil: Package setup fails
reassign 389334 libmono0 retitle 389334 ** ERROR **: file threadpool.c: line 990... thanks On Monday 25 September 2006 06:00, Steve Langasek wrote: Hi Adam, On Mon, Sep 25, 2006 at 12:33:46AM -0500, Adam Porter wrote: I tried to upgrade to Beagle 0.2.10, which pulled this in, but I got this error, and now I can't even shutdown beagle with $(beagle-shutdown): So given that the stacktrace shows only libmono and libglib, what reason is there to think that this is a galago bug rather than a mono bug? (Apologies if this is an ignorant question, I know next to nothing about mono and its stacktrace conventions.) Hm, duh. Sorry about that. It should have been obvious to me since Beagle crashed too. Sorry for wasting your time. :) pgpf9OrLYBMuc.pgp Description: PGP signature
Bug#321102: data-loss still possible with kmail 3.5.2
On Tuesday 16 May 2006 11:03, Christopher Martin wrote: Perhaps a better solution would be disable dimap support in the 3.5.3 upload, and make sure that the fixed package makes Etch (which is looming). Daniel, what do you feel about this? Given that upstream appears to be unable to replicate and fix the problem, I think this might be the safest, and least bothersome (to all other KMail users) way of dealing with this issue. Personally, I'd be disappointed if this was done. I know the bug is present, but I rely on KMail's dimap support for my mail. I switched from Thunderbird because of Thunderbird's lousy, buggy dimap support. KMail's is superb, other than this bug (which hasn't hit me yet). By the way, you referred to the fixed package. As far as I'm aware, this bug isn't about to be fixed. A comment was made on the KDE Bugzilla that really fixing it would require a restructuring of the IMAP backend/kioslave. Did I miss something? I sure hope so, cause I'd love for this bug to be truly fixed. pgpJ62AnXdKg9.pgp Description: PGP signature
Bug#208344: Argh, locking...
severity 208344 important thanks Well, I looked at the e-mail logcheck just sent me, and I found this: gconfd (me-19567): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-me/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable) I killall-9'ed gconfd-2 and removed that lock file, and now Newton's working. So I'm downgrading it back to important. The problem is, those crazy CORBA errors gave _no indication_ of the actual problem. The only way I discovered it was by logcheck notifying me of those entries in the logs, I was going to try rebooting today if I couldn't figure it out otherwise, and that would most likely have fixed it (the PID in the lockfile was the same as the running gconfd-2 process), and then the real problem might still not be known. Remember that I looked for those lock files that were listed in the earlier reports, but I'm guessing that the location of the gconf lockfile has changed since then. pgpSEvt7Pvrd5.pgp Description: PGP signature
Bug#350851: Crash is back :(
Well, it took longer, but I got the same crash I got with 3.5.1. Oh well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#350851: Possibly fixed in 3.5.2?
FYI, since upgrading to KDE 3.5.2 (Debian), my KMail IMAP problems and crashes have gone away. If you have had this problem, please test with 3.5.2. This may have been fixed as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321102: Possibly fixed in 3.5.2?
FYI, since upgrading to KDE 3.5.2 (Debian), my KMail IMAP problems and crashes have gone away. If you have had this problem, please test with 3.5.2. This may have been fixed as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#332473: Possibly fixed in 3.5.2?
FYI, since upgrading to KDE 3.5.2 (Debian), my KMail IMAP problems and crashes have gone away. If you have had this problem, please test with 3.5.2. This may have been fixed as well. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315392: Suggest closing or degrading
May I suggest that this bug be closed, or at least degraded, since a) it's most likely been fixed in later versions, and b) seems to happen when used after a different version of KMail on the same config files? Doesn't seem like an RC bug to me. (But what do I know, I'm just a user. :) pgpZEmf0tO2jh.pgp Description: PGP signature
Bug#349316: In 3.5.1, patch posted
found 349316 4:3.5.1-1 tags 349316 patch It's reported in the KDE tracker to be in 3.5.1, and a rather large test patch has been posted: http://bugs.kde.org/87163#c27 pgpEgNehTa2Go.pgp Description: PGP signature
Bug#332473: Found in other versions too?
On Monday 13 February 2006 11:33, Debian Bug Tracking System wrote: found 350851 4:3.4.2-2 http://bugs.kde.org/show_bug.cgi?id=104956 At the bottom it says that it's also in KMail-1.9.1/KDE-3.5.0. Should it be marked found there as well? FYI, I haven't had any problems like this with KMail-1.8.3 from KDE 3.4.3, even while using it with KDE 3.5.0/1. pgpy4EEfS6ccY.pgp Description: PGP signature
Bug#350851: kmail: v1.9.1: Data loss w/disconnected IMAP (reported upstream)
Package: kmail Version: 4:3.5.0-5 Severity: critical Justification: causes serious data loss -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 KMail 1.9.1 seems to have a serious data loss bug with disconnected IMAP accounts. It's been reported upstream at http://bugs.kde.org/show_bug.cgi?id=104956. I couldn't find this mentioned in the Debian BTS already, so I thought I should file it so Debian can track it as well, and prevent it from entering testing. Please forgive me if this isn't the proper thing to do. I tried to add debian-qt-kde@lists.debian.org to the Cc list, but it's not registered with the KDE Bugzilla, so I can't. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD4D9e5+GdyTDsrJsRAv4kAJ9XcTjkXZZ4WNY08/kglMJg3f/MdgCcCfel uC9iBXfnBVBBmQgGwWnakhQ= =xpB0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#294520: QTParted 0.4.5-1 still does it!
I just noticed that QTParted 0.4.5-1 (listed as v0.4.5-cvs in the program) still does it. I've attached a screenshot of QTParted, and the output of fdisk and partman on the same disk. I also attached a screenshot of QTParted 0.4.4 from Knoppix 3.7; you can see a lot of extraneous stuff, but the real partitions are also displayed the same as in 0.4.5: completely wrong. Notice that partitions are mixed up, and QTParted doesn't even show there being two ext partitions. It's been 318 days since I submitted this bug, and nothing has been done. This is a CRITICAL DATA LOSS BUG. It makes QTParted completely useless and untrustworthy. Something has got to be done! qtparted-bug.png Description: PNG image $ sudo fdisk -l /dev/hdb Disk /dev/hdb: 120.0 GB, 120034123776 bytes 16 heads, 63 sectors/track, 232581 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/hdb1 * 1 20799104823817 HPFS/NTFS /dev/hdb2 20800 232576 106735608f W95 Ext'd (LBA) /dev/hdb5 47845 68643104823817 HPFS/NTFS /dev/hdb6 68643 9984915727603+ 7 HPFS/NTFS /dev/hdb7 99849 120647104823817 HPFS/NTFS /dev/hdb8 162260 22467131455238+ 7 HPFS/NTFS /dev/hdb9 224672 232576 3984088+ 7 HPFS/NTFS /dev/hdb10 20800 4784413630617 83 Linux /dev/hdb11 120648 16225920972416+ 83 Linux Partition table entries are not in disk order(parted) print Disk geometry for /dev/hdb: 0kB - 120GB Disk label type: msdos Number Start End SizeType File system Flags 1 32kB11GB11GBprimary ntfs boot 2 11GB120GB 109GB extended lba 10 11GB25GB14GBlogical fat32 5 25GB35GB11GBlogical ntfs 6 35GB52GB16GBlogical ntfs 7 52GB62GB11GBlogical ntfs 11 62GB84GB21GBlogical ext3 8 84GB116GB 32GBlogical ntfs 9 116GB 120GB 4080MB logical ntfs qtparted-knoppix.png Description: PNG image pgpJ0Hd7f8jkY.pgp Description: PGP signature
Bug#328170: Does --nowrapper help?
I'm having similar problems with apt-build from unstable. If I do not use
--nowrapper, I get segfaults in make like this:
checking dependency style of i486-linux-gnu-g++... ./configure: line 4135:
19100 Segmentation fault ${MAKE-make} -s -f confmf /dev/null 21
In this case, line 4135 looks like this, probably typical of a configure file:
for depmode in $am_compiler_list; do
As a result, when make tries to actually compile it, it segfaults too:
make all-recursive
make[1]: *** [all] Segmentation fault
But if I run apt-build with --nowrapper, it works fine.
There seem to be similar bugs in here, but I'm getting different errors.
Should I file a new bug, or is this it?
pgpyXNuEhOOXm.pgp
Description: PGP signature
Bug#294520: QTParted Mixes Up Partiton Numbers
Package: qtparted Version: 0.4.4 Severity: critical I'm running libparted 1.6.11-8, BTW. When I run `fdisk -l`, I get this: - Disk /dev/hda: 120.0 GB, 120034123776 bytes 16 heads, 63 sectors/track, 232581 cylinders Units = cylinders of 1008 * 512 = 516096 bytes ~ Device Boot Start End Blocks Id System /dev/hda1 * 1 20799104823817 HPFS/NTFS /dev/hda2 20800 232576 106735608f W95 Ext'd (LBA) /dev/hda5 47845 68643104823817 HPFS/NTFS /dev/hda6 68643 9984915727603+ 7 HPFS/NTFS /dev/hda7 99849 120647104823817 HPFS/NTFS /dev/hda8 162260 22467131455238+ 7 HPFS/NTFS /dev/hda9 224672 232576 3984088+ 7 HPFS/NTFS /dev/hda10 20800 4784413630617 83 Linux /dev/hda11 120648 16225920972416+ 83 Linux Partition table entries are not in disk order - When I run qtparted, it shows /dev/hda9 as being a 20 GB ext3 partition, which is actually /dev/hda11. It also gets the other partition numbers wrong. I discovered this when I tried to mount /dev/hda5, an NTFS partition, but since the number was mixed up, it mounted /dev/hda10 instead. This is a serious bug. I started qtparted to clear out another partition to use for something else. If I hadn't noticed that the numbers were wrong, I could have wiped out the wrong partition! Forgive me, but I'm not about to try it and see which partition qtparted *actually* wipes out. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
