Re: libqt2 - 18 Works
John Gay [EMAIL PROTECTED] wrote: On Tuesday 01 January 2002 00:26, Robert Tilley wrote: I recently had problems with lost icons and downgraded to libqt 2.3.1-17 from 2.3.1-18 which seemed to solve the problem. In a recent system update, libqt was again upgraded to -18 and icon problem recurred. Later that night 12-31-01, around 1900 hours I did another system update (apt-get update, -f install, dist-upgrade). libqt was still 2.3.1-18 but the icon problem had vanished. I did log out, restart my X-server, and log in. Regardless, the problem is gone from my system. Thanks to all the hard-working KDE developers and Debian packagers! Is this confirmation that the icon problem is fixed, or just one lucky person? Cheers, John Gay I did the fix with the new libqt 2.3.2-18, and some Icons returned...most of the visable onew missing in fact. BUT I now have lost my card-deck selections for playing card games! No Free-Cell :( NOT a big deal, but a nuisance anyway. Where there is a will, there is a way g. This problem doesn't seem to have hit the Alpha version of KDE yet, sooo I just use the X-forwarding feature of SSH to play the games on my Alpha and relay the screen to my broken machine (s). Ain't Linux neat?? Cheers, -Don Spoon-
Lost icons in some KDE apps
Hi, I'm very sorry if this question might allready have been asked, but i've just joined the mailing list. In kdevelop I lost all icons in toolbars etc. This is since I did a unstable dist-upgrade 2 days ago. Also, the taskbar icon for alarmd could not load at logon. Korganizer also seem to be having trouble. It's not very crucial (someone on the KDE user list called KDE unusable with this problem, I don't agree). BTW I think you guys are doing a GREAT job with the KDE packages!!! Freek
Re: Lost icons in some KDE apps
I have uploaded fixed KDevelop packages. They should be in unstable tomorrow. On Wed, Jan 02, 2002 at 09:24:42AM +0100, Freek wrote: Hi, I'm very sorry if this question might allready have been asked, but i've just joined the mailing list. In kdevelop I lost all icons in toolbars etc. This is since I did a unstable dist-upgrade 2 days ago. Also, the taskbar icon for alarmd could not load at logon. Korganizer also seem to be having trouble. It's not very crucial (someone on the KDE user list called KDE unusable with this problem, I don't agree). BTW I think you guys are doing a GREAT job with the KDE packages!!! Freek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Norman Jordan [EMAIL PROTECTED] GnuPG public key available at http://rtfm.phpwebhosting.com/gnupg_key.txt Fingerprint: 1024D/095918D0 807B A7C5 0D7D 81C0 C21F 1D36 775A C806 0959 18D0
Re: Bug#127252: -unstable compiled against the wrong libpng
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] (Thomas Bushnell, BSG) writes: That's the problem; there is just no real solution besides a big recompile. My question still remains. If we require a big recompile, when/ how are we going to bother to advise the maintainers of these packages? It has been stated that we are talking about 300+ packages :-( Or are we going to do as we are currently and wait until users report vague problems (these don't get straight forward bug reports - aka debian-kde confusion over the real problem). Personally I would like to see an automated bug report stating what the issues are and how the maintainer can fix it. That's what I got during the last update to python and it made my life as a maintainer straight forward. Rather than having to guess some non-backwards compatable change in an dependant package. Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8MuKtoCzanz0IthIRAuDHAJ9VZ1Fbn+X45XPjttkqLNNxJuMJeQCfdpzN N1ylOMPx3JAyrNZPimA/BVg= =M723 -END PGP SIGNATURE-
Re: Bug#127252: -unstable compiled against the wrong libpng
On Wed, 2 Jan 2002 21:36:24 +1100 Mark Purcell [EMAIL PROTECTED] wrote: My question still remains. If we require a big recompile, when/ how are we going to bother to advise the maintainers of these packages? It has been stated that we are talking about 300+ packages :-( Mass NMU, setting Build-Depends to libpng-dev version that is for libpng3 sounds like a way to go. Note that the recent python translation took more than a month to complete, I believe (well, I didn't). It might be easier to set libpng3 to conflict with libpng2, so that until libpng2 is removed from the system libpng3 does not enter, which would make the problem more obvious. Then again, do we really want to do this now? regards, junichi
memory leak in xfs (AA?) with kde?
Hello, after upgrading most kde packages on my notebook (to sid) I am no longer able to start kde (via kdm). The xfs process is rapidly consuming a lot of memory ( 100MB!) and leads to Out of Memory errors from the kernel. The system gets extremely unresponsive until the start of kde is aborted. I am not sure if one of the kde packages, xfs or some fonts are causing this! I use anti-aliasing on this machine! Any help appreciated! Olaf
Re: Bug#127252: -unstable compiled against the wrong libpng
On Mit, 02 Jan 2002, Mark Purcell wrote: That's the problem; there is just no real solution besides a big recompile. My question still remains. If we require a big recompile, when/ how are we going to bother to advise the maintainers of these packages? It has been stated that we are talking about 300+ packages :-( Maybe we could use: debian-devel-announce: Announcements for developers -- Noèl Köthe
Re: memory leak in xfs (AA?) with kde?
Am Mittwoch, 2. Januar 2002 12:52 schrieb Olaf Stetzer: Hello, after upgrading most kde packages on my notebook (to sid) I am no longer able to start kde (via kdm). The xfs process is rapidly consuming a lot of memory ( 100MB!) and leads to Out of Memory errors from the kernel. The system gets extremely unresponsive until the start of kde is aborted. I am not sure if one of the kde packages, xfs or some fonts are causing this! I use anti-aliasing on this machine! Some additional infos: I could start window maker with no problems, now using kmail without kde! So the problem must be related to either kde or AA! I upgraded most X packages to sid too! Kernel is 2.4.13 (some known issues with this kernel version and VM?) Olaf
Re: Bug#127252: -unstable compiled against the wrong libpng
On Wed, Jan 02, 2002 at 01:06:21PM +0100, Noel Koethe wrote: On Mit, 02 Jan 2002, Mark Purcell wrote: That's the problem; there is just no real solution besides a big recompile. My question still remains. If we require a big recompile, when/ how are we going to bother to advise the maintainers of these packages? It has been stated that we are talking about 300+ packages :-( Maybe we could use: debian-devel-announce: Announcements for developers I guess we could do something like that. Problem is we still have lots of users who will be wondering where their graphics have gone and will be filing bug reports against all sorts of packages, as well as creating all sorts of bogus links to the wrong shared libraies to work around the problem. (Have a look in debian-kde) Then of course not every developer actually reads/ acts on devel-announce, yes I know hard to believe isn't it. I still think the only solution is to do the same as per python and automatically file bug reports/ conflicts with all pacakges which depend on libpng2. But I would be happy to be told otherwise. Mark
Re: Lost icons in some KDE apps
Appearrently this is due to a recent change to libpng. See:Re: Bug#127252: -unstable compiled against the wrong libpng It seems that the libpng has been changed in a major way, and is therefore affecting anything that is compiled against it. The 'fix' is to re-compile ALL apps against the new libpng. The 'problem' is this is more than 300 packages in Debian that are known and many others are unknown. It 'seems' that most of base KDE? has been re-compiled, hence the recent reports of KDE now working, and kdevelop has been fixed and put into incoming, so this will take a bit of time to hit all the mirrors. But it is hard to tell how many other packages are affected by this change. It would be a good idea to sign-up to debian-devel mailing list to keep tabs on this development. After-all, this is why it's called unstable. Of course this is just my best guess from the recent storm of mails on this subject and I could be very wrong but for myself, I'm going to wait until this sorts itself out before doing any more major upgrades. I hope this answers your question. Cheers, John Gay
KMail crash on attaching a file (Debian testing packages)
Hi I have a Debian Woody system with the KDE packages from testing, all is running really well apart from a couple of issues with KMail, the worst of which is if I try to attach a file it crashes with a Signal 11, when I OK the file I have selected by browsing to it. I've pasted the backtrace below. The crash happens every time i try to attach a file. Its a standard up to date install from the testing packages on an Athlon 1gig machine, Abit KT7A mainboard. Rachel (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40fd78f9 in wait4 () from /lib/libc.so.6 #0 0x40fd78f9 in wait4 () from /lib/libc.so.6 #1 0x410501f0 in __check_rhosts_file () from /lib/libc.so.6 #2 0x407e70b8 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.3 #3 0x40f60848 in sigaction () from /lib/libc.so.6 #4 0x080cfecd in KDialog::marginHint () #5 0x080ad0d9 in KDialog::marginHint () #6 0x40492a6f in KIO::Job::result () from /usr/lib/libkio.so.3 #7 0x40479d7c in KIO::Job::emitResult () from /usr/lib/libkio.so.3 #8 0x4047ab96 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.3 #9 0x4047ccc1 in KIO::TransferJob::slotFinished () from /usr/lib/libkio.so.3 #10 0x40a6ea0d in QObject::activate_signal () from /usr/lib/libqt.so.2 #11 0x4046ccd5 in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.3 #12 0x4046911c in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.3 #13 0x40468e68 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.3 #14 0x40467aa0 in KIO::Slave::gotInput () from /usr/lib/libkio.so.3 #15 0x40a6ecce in QObject::activate_signal () from /usr/lib/libqt.so.2 #16 0x40ac6658 in QSocketNotifier::activated () from /usr/lib/libqt.so.2 #17 0x40aa5242 in QSocketNotifier::event () from /usr/lib/libqt.so.2 #18 0x40a1aa87 in QApplication::notify () from /usr/lib/libqt.so.2 #19 0x40755da4 in KApplication::notify () from /usr/lib/libkdecore.so.3 #20 0x409e53ba in qt_set_socket_handler () from /usr/lib/libqt.so.2 #21 0x409e5abe in QApplication::processNextEvent () from /usr/lib/libqt.so.2 #22 0x40a1cf4f in QApplication::enter_loop () from /usr/lib/libqt.so.2 #23 0x409ec9c3 in QApplication::exec () from /usr/lib/libqt.so.2 #24 0x08133ae3 in KDialog::marginHint () #25 0x40f5065f in __libc_start_main () from /lib/libc.so.6
Re: Lost icons in some KDE apps
It seems that the libpng has been changed in a major way, and is therefore affecting anything that is compiled against it. Is this really true? Both versions of libpng can co-exist on a system, and an application that was linked against one of them will automatically pick the right version. The problem with the kde apps was that they were linked against the old version whereas libqt was changed to be linked against the newer one. So loading a kde app loaded both versions of libpng, which cannot work. -- Wolfgang Ratzka GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
Re: KMail crash on attaching a file (Debian testing packages)
On Wednesday 02 January 2002 07:01 am, Rachel Andrew wrote: hy Resent-From: debian-kde@lists.debian.org X-Mailing-List: debian-kde@lists.debian.org archive/latest/6129 X-Loop: debian-kde@lists.debian.org Precedence: list Resent-Sender: [EMAIL PROTECTED] Hi I have a Debian Woody system with the KDE packages from testing, all is running really well apart from a couple of issues with KMail, the worst of which is if I try to attach a file it crashes with a Signal 11, when I OK the file I have selected by browsing to it. I've pasted the backtrace below. The crash happens every time i try to attach a file. Its a standard up to date install from the testing packages on an Athlon 1gig machine, Abit KT7A mainboard. Rachel (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found).. .(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40fd78f9 in wait4 () from /lib/libc.so.6 #0 0x40fd78f9 in wait4 () from /lib/libc.so.6 #1 0x410501f0 in __check_rhosts_file () from /lib/libc.so.6 #2 0x407e70b8 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.3 #3 0x40f60848 in sigaction () from /lib/libc.so.6 #4 0x080cfecd in KDialog::marginHint () #5 0x080ad0d9 in KDialog::marginHint () #6 0x40492a6f in KIO::Job::result () from /usr/lib/libkio.so.3 #7 0x40479d7c in KIO::Job::emitResult () from /usr/lib/libkio.so.3 #8 0x4047ab96 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.3 #9 0x4047ccc1 in KIO::TransferJob::slotFinished () from /usr/lib/libkio.so.3 #10 0x40a6ea0d in QObject::activate_signal () from /usr/lib/libqt.so.2 #11 0x4046ccd5 in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.3 #12 0x4046911c in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.3 #13 0x40468e68 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.3 #14 0x40467aa0 in KIO::Slave::gotInput () from /usr/lib/libkio.so.3 #15 0x40a6ecce in QObject::activate_signal () from /usr/lib/libqt.so.2 #16 0x40ac6658 in QSocketNotifier::activated () from /usr/lib/libqt.so.2 #17 0x40aa5242 in QSocketNotifier::event () from /usr/lib/libqt.so.2 #18 0x40a1aa87 in QApplication::notify () from /usr/lib/libqt.so.2 #19 0x40755da4 in KApplication::notify () from /usr/lib/libkdecore.so.3 #20 0x409e53ba in qt_set_socket_handler () from /usr/lib/libqt.so.2 #21 0x409e 5abe in QApplication::processNextEvent () from /usr/lib/libqt.so.2 #22 0x40a1cf4f in QApplication::enter_loop () from /usr/lib/libqt.so.2 #23 0x409ec9c3 in QApplication::exec () from /usr/lib/libqt.so.2 #24 0x08133ae3 in KDialog::marginHint () #25 0x40f5065f in __libc_start_main () from /lib/libc.so.6 Rachel: That is correct. If you are running a pure Woody box, then parts of KDE are broken and we are kind of in limbo waiting for some new packages to trickle down from Sid to fix these problems. An option is to install the Sid version of KDE, or wait until the repaired newer packages make it into Woody. tatah -- Jaye Inabnit\ARS ke6sls\/A GNU-Debian linux user\/ http://www.qsl.net/ke6sls If it's stupid, but works, it ain't stupid. I SHOUT JUST FOR FUN. Free software, in a free world, for a free spirit. Please Support freedom!
Re: Lost icons in some KDE apps
Le Mercredi 2 Janvier 2002 18:39, Wolfgang Ratzka a écrit : Is this really true? Both versions of libpng can co-exist on a system, and an application that was linked against one of them will automatically pick the right version. The problem with the kde apps was that they were linked against the old version whereas libqt was changed to be linked against the newer one. So loading a kde app loaded both versions of libpng, which cannot work. It's true that I've got both libraries and that my icons dispeared anyway. dpkg -l libpng* Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé |/ Err?=(aucune)/H=à garder/besoin Réinstallation/X=les deux (Etat,Err: majuscule=mauvais) ||/ Nom Version Description +++-=-=-== ii libpng-dev1.2.1-1 PNG library - development un libpng0 néant (aucune description n'est disponible) un libpng0-altdevnéant (aucune description n'est disponible) un libpng0g néant (aucune description n'est disponible) un libpng0g-dev néant (aucune description n'est disponible) un libpng1-dev néant (aucune description n'est disponible) ii libpng2 1.0.12-3 PNG library - runtime pn libpng2-dev néant (aucune description n'est disponible) ii libpng3 1.2.1-1 PNG library - runtime -- [EMAIL PROTECTED]
Re: Lost icons in some KDE apps
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 02 January 2002 08:39 am, Wolfgang Ratzka wrote: It seems that the libpng has been changed in a major way, and is therefore affecting anything that is compiled against it. Is this really true? Both versions of libpng can co-exist on a system, and an application that was linked against one of them will automatically pick the right version. The problem with the kde apps was that they were linked against the old version whereas libqt was changed to be linked against the newer one. So loading a kde app loaded both versions of libpng, which cannot work. Here is what I get when I start kmail from a Xterm. Woody with latest KDE from Sid. libpng error: Incompatible libpng version in application and library libpng warning: Application was compiled with png.h from libpng-1.0.12 libpng warning: Application is running with png.c from libpng-1.2.1 - -- Greg Madden -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjwzl48ACgkQaefA3q8KcpBZCQCeLIG1VIwnl9qDv+elNSHqHzf9 C5oAnjmJ3Uu2THIMu+Bb4Fk9ISthJzog =YNb9 -END PGP SIGNATURE-
Re: Lost icons in some KDE apps
Le Jeudi 3 Janvier 2002 00:28, Greg Madden a écrit : Here is what I get when I start kmail from a Xterm. Woody with latest KDE from Sid. libpng error: Incompatible libpng version in application and library libpng warning: Application was compiled with png.h from libpng-1.0.12 libpng warning: Application is running with png.c from libpng-1.2.1 You have to install libpng3 (1.2.1-1). I use KMail and everything is working fine with this library on my system. I've got all the icons. Well, I'm talking to fast. I've just discovered that the menu entry for KMail configuration has disapeared, and all the menu are bizarre :-). But at least, I can send and receive email. I'm longing for the stable version of Debian 3.0 :-) -- [EMAIL PROTECTED]
Re: libpng problems--aka no icons
Le Lundi 31 Décembre 2001 19:58, Oliver Johns a écrit : Just did a full upgrade to latest unstable packages. Then used Bjoern Krombholz's fix: dpkg --force-depends -r libpng2 ln -s /usr/lib/libpng.so.3.1.2.1 /usr/lib/libpng.so.2 It seems that you can't make any upgrade after that. upgrade is blocked by the sofware needing libpng2. So I didn't remove libpng2 but I simply renamed the symlink libpng.so.2 in libpng.so.2.old and I made the symlink you mentionned (ln -s /usr/lib/libpng.so.3.1.2.1 /usr/lib/libpng.so.2). It works. -- [EMAIL PROTECTED]
Kword crash on save
Hi, I've looked through tons of bug reports and searched ad nauseam on Google, but can't find a solution: my Kword crashes (segfaults) on save. I have never even customized its configuration or anything, so it is right out of the box. And it crashes always, even with an empty document. I know it worked around 12/20/01, so it is a relatively recent problem. I have done upgrades since, but not sure what exactly got upgraded; I don't think it was koffice. I'm using Woody and all my packages are up-to-date (with the minor SNAFU that koffice wants python-base and something else wants python-1.5 (or vice-versa), and they conflict, but I've kept everything necessary for koffice and removed all other conflicting stuff). The problem occurs on two different machines (same packages, more or less), and caused my wife to utter the words from now on I will use only MS Word... she lost a full page of text (a late first save). My kword is KWord 1.1 (pre-beta2) (Using KDE 2.2.2). No debugging symbols, of course. Sorry for the long description. Am I the only one with this problem? If so, could somebody using Woody send me a list of their packages and versions (e.g., dpkg -l)? I could compare and perhaps find a way out... Are there any other recommendations for how I should proceed? Any help will be much appreciated. If answering directly, please remove DELETE THIS and leave only krikis before @. I apologize for obfuscation but mailing lists have always exposed me to spammers otherwise... Martins Krikis
Re: Kword crash on save
On Wed, 2002-01-02 at 22:32, Martins Krikis wrote: I'm using Woody and all my packages are up-to-date (with the minor SNAFU that koffice wants python-base and something else wants python-1.5 (or vice-versa), and they conflict, but I've kept everything necessary for koffice and removed all other conflicting stuff). The problem occurs on two different machines (same packages, more or less), and caused my wife to utter the words from now on I will use only MS Word... she lost a full page of text (a late first save). use reportbug to report the bug to the maintainer, this will give him a snapshot of your box(ie what packages you have installed) and take what you report and get a real bug report going on the issue -- [EMAIL PROTECTED] GPG key can be found at http://www.monochromatic.net/yugami.gpg pgpG0VuLCeWZ2.pgp Description: PGP signature
