Re: libqt just broke again
On Tue, Jan 08, 2002 at 12:04:41AM -0500, Justin R. Miller wrote: Thus spake Saadiq Rodgers-King ([EMAIL PROTECTED]): Me too. :-( Where'd you find the *-18 debs? I tried `apt-get install uic=2.3.1-18 libqt2=2.3.1-18` but no luck. Thanks. Yes, can anyone provide these someplace? Why not just use -19? -- Daniel Stone[EMAIL PROTECTED] wolfie 0 .. 1.. 10.. 11.. 100.. wolfie counting is easy dude pgpnLnykKvPlw.pgp Description: PGP signature
m68k
The reason for rolling it slowly is apparently to preserve the autobuilders; you have to bear in mind here that m68k takes 40 hours to build kdebase alone. Daniel: Is there an emulator we could use on an intel machine for building m68k stuff?? I know I can run windoz under my intel linux box now. . . That would surely speed things up enormously. tatah and 73 -- 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: m68k
On Mon, Jan 07, 2002 at 11:56:02PM -0800, Jaye Inabnit ke6sls wrote: The reason for rolling it slowly is apparently to preserve the autobuilders; you have to bear in mind here that m68k takes 40 hours to build kdebase alone. Daniel: Is there an emulator we could use on an intel machine for building m68k stuff?? I know I can run windoz under my intel linux box now. . . That would surely speed things up enormously. There's no decent, working m68k emulator yet, unfortunately. BTW, thankyou all for your generous offers of hardware, but I look to be OK for the meantime. Should I ever need anything, I'll give a yell on the list. Much appreciated. :) d -- Daniel Stone[EMAIL PROTECTED] Omnic no Omnic bod's kids are watching elmo... elmo's song pgpl5cbLP0EKk.pgp Description: PGP signature
Re: libqt just broke again
Am Dienstag, 8. Januar 2002 07:31 schrieb Daniel Stone: On Tue, Jan 08, 2002 at 12:04:41AM -0500, Justin R. Miller wrote: Thus spake Saadiq Rodgers-King ([EMAIL PROTECTED]): Me too. :-( Where'd you find the *-18 debs? I tried `apt-get install uic=2.3.1-18 libqt2=2.3.1-18` but no luck. Thanks. Yes, can anyone provide these someplace? Why not just use -19? Don't worry, it just happend if you revert qt back to libpng2 and forget to supply new kde debs complied against it at the same time. Max
Re: m68k
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 08 January 2002 02:02 am, Daniel Stone wrote: On Mon, Jan 07, 2002 at 11:56:02PM -0800, Jaye Inabnit ke6sls wrote: The reason for rolling it slowly is apparently to preserve the autobuilders; you have to bear in mind here that m68k takes 40 hours to build kdebase alone. Daniel: Is there an emulator we could use on an intel machine for building m68k stuff?? I know I can run windoz under my intel linux box now. . . That would surely speed things up enormously. There's no decent, working m68k emulator yet, unfortunately. No need for an emulator... How about a gcc cross-compiler? Probably hosted on PPC, targeting m68k? - -- ++ | Ron Johnson, Jr.Home: [EMAIL PROTECTED] | | Jefferson, LA USA http://ronandheather.dhs.org:81| || ! Fair is where you take your cows to be judged. ! !Unknown ! ++ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8OtXNjTz5dS9Us5wRAu1VAJ9/6G2ZHEkR3JeP8PLicXW3LllYpQCdGwaj WQ42rGfQIcAL2JxEcBQh9Xc= =Q7ru -END PGP SIGNATURE-
Fresh install of kde from woody
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, With all this talk about people falling back, and pkgs being slow to move from sid to woody, what would happen if I made a complete woody install to a blank disk? Would kde work? Or, is it broken because of the libqt2/libpng2 problem and take 14 days to fix, and then, only be in sid? Also, would it be a complete kde 2.2.1? (Dare I ask for 2.2.2?) Would it be better to build the woody kde from source? TIA, Ron - -- ++ | Ron Johnson, Jr.Home: [EMAIL PROTECTED] | | Jefferson, LA USA http://ronandheather.dhs.org:81| || ! Fair is where you take your cows to be judged. ! !Unknown ! ++ -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8OtgZjTz5dS9Us5wRAuHyAJ43J1QG6ihW4Q0AGt+oh+0STZyHEACfZDCw SwfnAWX0xaG3teRIvFQ8+qs= =SSKf -END PGP SIGNATURE-
[kde] anti-aliasing is *NOT* supported!
Hi guys, Just to let you know that I will *not* support anti-aliasing. You can use it, but don't expect me to urgently follow up on bug reports involving AA, as it causes problems such as #123264. If you report an AA bug, I'll probably downgrade its severity and tag wontfix, because it's too buggy. That said, *please* make mention of whether you're using AA or not in your bug reports, because it makes my life easier. -d (no, this is nothing new, as it was Ivan's policy too; I completely agree with it and am just re-stating it) -- Daniel Stone[EMAIL PROTECTED] rcw liiwi: printk(CPU0 on fire\n); pgpv41YBE1h51.pgp Description: PGP signature
Re: [kde] anti-aliasing is *NOT* supported!
On Die, 08 Jan 2002, Daniel Stone wrote: Just to let you know that I will *not* support anti-aliasing. You can use it, but don't expect me to urgently follow up on bug reports involving AA, as it causes problems such as #123264. If you report an AA bug, I'll probably downgrade its severity and tag wontfix, because it's too buggy. Why not report it upstream? -- Noèl Köthe
Re: [kde] anti-aliasing is *NOT* supported!
On Tue, Jan 08, 2002 at 12:57:07PM +0100, Noel Koethe wrote: On Die, 08 Jan 2002, Daniel Stone wrote: Just to let you know that I will *not* support anti-aliasing. You can use it, but don't expect me to urgently follow up on bug reports involving AA, as it causes problems such as #123264. If you report an AA bug, I'll probably downgrade its severity and tag wontfix, because it's too buggy. Why not report it upstream? I may upstream it, but it's at the bottom of my TODO. -- Daniel Stone[EMAIL PROTECTED] TenBaseT the thing you forget TenBaseT is that all yanks are armed to the teeth danish you forget my Mutant Healing Factor. TenBaseT I forgot he was a freak TenBaseT with his bones made of unobtanium pgpq5gRgCWLTx.pgp Description: PGP signature
Re: [kde] anti-aliasing is *NOT* supported!
On Tuesday 08 January 2002 06:50 am, Daniel Stone wrote: Hi guys, Just to let you know that I will *not* support anti-aliasing. You can use it, but don't expect me to urgently follow up on bug reports involving AA, as it causes problems such as #123264. If you report an AA bug, I'll probably downgrade its severity and tag wontfix, because it's too buggy. That said, *please* make mention of whether you're using AA or not in your bug reports, because it makes my life easier. In that case, please stop KDE from turning it on by default when you ask for more effects in the startup wizard. (it does currently) Daniel
Re: [ccheney@cheney.cx: libqt2 libpng2 resolution]
Chris Cheney [EMAIL PROTECTED] cum veritate scripsit: How do you plan to prevent programs that link with libqt2 to also link with libpng3 ? Manual check ? yes manual check How about libqt2-dev conflicting with libpng3-dev, or something like that. regards, junichi -- [EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
Re: libqt just broke again
On Tue, Jan 08, 2002 at 08:19:22AM -0500, Justin R. Miller wrote: The only icons problems I had before yesterday were korganizer and knotes (all I noticed anyway). After yesterday I don't even get a splash screen or a logo in kdm. I have a completely unusable KDE. LD_PRELOAD=/usr/lib/libpng.so.2.1.0.12 startx until kde packages are upgraded. And always remember sid/woody != stable :) Björn
Re: libqt just broke again
Thus spake Bjoern Krombholz ([EMAIL PROTECTED]): LD_PRELOAD=/usr/lib/libpng.so.2.1.0.12 startx until kde packages are upgraded. You're a livesaver! And always remember sid/woody != stable :) Yeah, I was gonna live with it and use... ick... GNOME ;-) -- Justin R. Miller [EMAIL PROTECTED] View my website at http://codesorcery.net Please encrypt email using key 0xC9C40C31 pgpDVdJvdhdtD.pgp Description: PGP signature
Re: [ccheney@cheney.cx: libqt2 libpng2 resolution]
On Tue, Jan 08, 2002 at 11:11:49PM +0900, Junichi Uekawa wrote: Chris Cheney [EMAIL PROTECTED] cum veritate scripsit: How do you plan to prevent programs that link with libqt2 to also link with libpng3 ? Manual check ? yes manual check How about libqt2-dev conflicting with libpng3-dev, or something like that. That's a bit obnoxious. Some folks might like to be developing code that uses libqt2 and *other code* tha uses libpng3, on the same debian box. -S -- by Rocket to the Moon, by Airplane to the Rocket, by Taxi to the Airport, by Frontdoor to the Taxi, by throwing back the blanket and laying down the legs ... - They Might Be Giants
Re: libqt just broke again
I'm confused. Here are a couple of responses I received back on this problem: *Don't worry, it just happend if you revert qt back to libpng2 and forget to *supply new kde debs complied against it at the same time. * * Max * Maximilian Reiss [EMAIL PROTECTED] How do I do this ? A quick how-to to the users would help. *Yep, that is a known side effect of going back to libpng2. * *Chris * Chris Cheney [EMAIL PROTECTED] What is the proper thing to do until these issues get fixed? What I did before was create my own set of debs by building qt-x11 (that is where the -18.deb files came from). I am currently building my own set of debs again for the -19 version. I understand we have a mixture of kde packages that depend on both png2 and png3. Are we eventually going to have only png2 dependency for kde2 and png3 for kde3? Is that the plan? In the meantime, shouldn't we have only libpng2 dependency in the Sid tree for kde2 ? On Monday 07 January 2002 08:37 pm, James D. Freels wrote: This evening, I upgraded my Debian/Sid system via apt-get, and several packages were installed. Among them were several kde/qt packages as listed below to -19.deb version and the icons were not visible on the desktop (broken as before). -rw-r--r--1 root root 894 Jan 7 20:26 qt-designer.list -rw-r--r--1 root root 293 Jan 7 20:26 uic.list -rw-r--r--1 root root 308 Jan 7 20:26 libqt2.list -rw-r--r--1 root root 261 Jan 7 20:26 libqutil1.list -rw-r--r--1 root root 261 Jan 7 20:26 libqt2-mt.list -rw-r--r--1 root root 261 Jan 7 20:26 libqt2-gl.list -rw-r--r--1 root root 239 Jan 7 20:26 libqt-mt-dev.list -rw-r--r--1 root root 239 Jan 7 20:26 libqt-gl-dev.list -rw-r--r--1 root root 8868 Jan 7 20:26 libqt-dev.list I then downgraded these same nine packages from -18.deb files I had saved from the previous version, and everything is now working as it should (icons appear again). ii libqt-dev 2.3.1-18 Qt GUI development headers, static libraries ii libqt-gl-dev 2.3.1-18 Qt GUI development libraries for GL version ii libqt-mt-dev 2.3.1-18 Qt GUI development headers, static libraries ii libqt2 2.3.1-18 Qt GUI Library (runtime version). ii libqt2-gl 2.3.1-18 Qt GUI Library (GL version). ii libqt2-mt 2.3.1-18 Qt GUI Library (runtime threaded version). ii libqutil1 2.3.1-18 Qt Util Library ii qt-designer2.3.1-18 Qt GUI Designer ii uic2.3.1-18 Qt ui compiler
Re: libqt just broke again
On Tue, Jan 08, 2002 at 10:49:53AM -0500, James D. Freels wrote: -snip- What is the proper thing to do until these issues get fixed? What I did before was create my own set of debs by building qt-x11 (that is where the -18.deb files came from). I am currently building my own set of debs again for the -19 version. I understand we have a mixture of kde packages that depend on both png2 and png3. Are we eventually going to have only png2 dependency for kde2 and png3 for kde3? Is that the plan? In the meantime, shouldn't we have only libpng2 dependency in the Sid tree for kde2 ? Yes, libpng2 will be used for qt-x11 (libqt2) and libpng3 will be used for qt-x11-free (libqt3). qt-x11 (libqt2) was installed into sid yesterday, kdelibs will be installed today, and kdebase will be installed tomorrow. After that I will be building all remaining packages. Each of those first three packages are known to take ~ 40+ hours on m68k to compile. The packages should be ready to be installed into woody within 12 days, if all other RC bugs are resolved. Chris
Re: Fresh install of kde from woody
Ron Johnson [EMAIL PROTECTED] wrote: Hi, With all this talk about people falling back, and pkgs being slow to move from sid to woody, what would happen if I made a complete woody install to a blank disk? Would kde work? Or, is it broken because of the libqt2/libpng2 problem and take 14 days to fix, and then, only be in sid? Also, would it be a complete kde 2.2.1? (Dare I ask for 2.2.2?) Would it be better to build the woody kde from source? TIA, Ron Despite my earlier elation (Lord, Love-A-Duck...), the upgrade to the newer libqt2-19 turned into a real disaster for me. I was using KDE 2.2.2 from SID, and although I regained some icons I was missing before, I lost a LOT more. In the process of attempting a recovery, other programs started dropping off-line (Control Center would not start, etc).I dunno if this was a result of the new libqt2, or my bumbling around. I decided that enuf was enuf and reverted back to the KDE in Woody. I really didn't want to wait 7 to 14 days right now to get back a working KDE install on this machine. It is amazing just how many KDE packages get removed when you remove libqt2 from your system grin. It did almost a complete purge of my SID KDE install!! It left a few packages, but nothing that interfered with the kdebase install from Woody. I did have to do a bit of magic with --force-overwrite or pulling a few selected packages from SID to get kde-crypto, koffice, and kde-extras installed. Anyway, the version of KDE in Woody as of early morning, 8 Jan 02 was a mixture of KDE 2.1.2, 2.2.1, and 2.2.2 packages. It needed a few packages from SID (kivio, etc) in order to get all the pieces working. I did a rather full install (kde-extras, koffice, kde-crypto, etc.) Most importantly. it DOESN'T have the libqt2 / libpng3 icon problem currently seen in SID!! I can now upgrade gracefully from Woody (hopefully) as the newer packages appear, while still having a functioning KDE install. I really doubt I will try SID again. Everytime I do, I get into a bind like this that exceeds my intelligence and experience! It usually results in a purge / re-install back to a lesser but more stable version. I am getting to old for this Submitted FYI. Cheers, -Don Spoon-
Re: Fresh install of kde from woody
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 08 January 2002 07:17 am, Donald R. Spoon wrote: snip I can now upgrade gracefully from Woody (hopefully) as the newer packages appear, while still having a functioning KDE install. I really doubt I will try SID again. Everytime I do, I get into a bind like this that exceeds my intelligence and experience! It usually results in a purge / re-install back to a lesser but more stable version. I am getting to old for this Submitted FYI. Cheers, -Don Spoon- Hi Don, thanks for the info. While this particular case is most extraordinary I think breakage in unstable is to be expected. Their will always be some pain involved :) It's just hard to get the timing right on when to do an upgrade when to wait. I shoulda waited a few more days on this one. (then not upgraded!) - -- Greg Madden -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjw7NTEACgkQaefA3q8KcpBYWwCcCTpksecO59xlC+HrUJa6RyUX qN8An0+8aRCei7RJEJpLcjSCFfW/8SDq =G67x -END PGP SIGNATURE-
Re: [kde] anti-aliasing is *NOT* supported!
* Daniel Stone schrieb am 08.01.02 um 12:50 Uhr: Hi guys, Just to let you know that I will *not* support anti-aliasing. You can use it, but don't expect me to urgently follow up on bug reports involving AA, as it causes problems such as #123264. If you report an AA bug, I'll probably downgrade its severity and tag wontfix, because it's too buggy. That said, *please* make mention of whether you're using AA or not in your bug reports, because it makes my life easier. Does this mean I've to rebuild the packages if I want to use AA? Is there a compile option that turns AA-Support on or off? I think AA will be nice in KDE3 since then AA-Fonts should be supported to live near non-AA fonts (QT3)... I hope you understand what I mean ;) -Marc -- +--+ | -- http://www.links2linux.de -- Jetzt mit neuen Features! | | wie z.B. [EasyLink]| +---Registered-Linux-User-#136487http://counter.li.org + pgpKMx8R0clCN.pgp Description: PGP signature
Re: anti-aliasing is *NOT* supported!
* Daniel Stone [EMAIL PROTECTED] [020108 06:08]: I may upstream it, but it's at the bottom of my TODO. Why dont you tag it upstream, wontfix and merge everyone in. Then you dont need to make blnket -devel announcements because your open bug is the policy on your support of AA. -- Scott Dier [EMAIL PROTECTED] http://www.ringworld.org/ the desire for space travel is a metaphor for escape
Re: Lord, Love-A-Duck! My Icons are back!
I've built all a number of packages from source using libpng2-dev and I'm pretty sure I have everything back. My cable modem connection is up to the challenge but if anyone has a bigger pipe I can upload the files for anyone interested. On Mon, Jan 07, 2002 at 09:42:17PM -0600, Chris Cheney scribbled: On Mon, Jan 07, 2002 at 10:23:23PM -0500, John S. J. Anderson wrote: So, is there any way to speed one's way back to a functional KDE? Doesn't seem like 'apt-get -b source kde' is likely to work; can anyone provide a list of packages that need to be rebuilt? This is probably more complicated than it needs to be, but I don't know how to use all the tools really well: apt-cache showpkg libpng3 | grep libpng3 - | cut -f 1 -d , | xargs apt-cache show | grep Source: | sort | uniq That lists all sources that depend on libpng3 not all of which will need to rebuilt. Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [kde] anti-aliasing is *NOT* supported!
On Tue, Jan 08, 2002 at 02:58:30PM +0100, Allan Sandfeld Jensen wrote: On Tuesday 08 January 2002 14:43, Daniel Burrows wrote: On Tuesday 08 January 2002 06:50 am, Daniel Stone wrote: Hi guys, Just to let you know that I will *not* support anti-aliasing. You can use it, but don't expect me to urgently follow up on bug reports involving AA, as it causes problems such as #123264. If you report an AA bug, I'll probably downgrade its severity and tag wontfix, because it's too buggy. That said, *please* make mention of whether you're using AA or not in your bug reports, because it makes my life easier. In that case, please stop KDE from turning it on by default when you ask for more effects in the startup wizard. (it does currently) You are refering to kpersonalizer The patch is trivial: Thanks for the patch, Alan, you saved me from trying to hack at 6:30am. I've applied to kdebase, and it'll be in the next upload. Thanks! :) d -- Daniel Stone[EMAIL PROTECTED] ChuChu chuu! ^_^; * illuzion studies ^_^; and determines it looks like a squashed insect pgpcVjwSZn4qI.pgp Description: PGP signature
Re: [kde] anti-aliasing is *NOT* supported!
On Tue, Jan 08, 2002 at 07:45:48PM +0100, Marc Schiffbauer wrote: * Daniel Stone schrieb am 08.01.02 um 12:50 Uhr: Hi guys, Just to let you know that I will *not* support anti-aliasing. You can use it, but don't expect me to urgently follow up on bug reports involving AA, as it causes problems such as #123264. If you report an AA bug, I'll probably downgrade its severity and tag wontfix, because it's too buggy. That said, *please* make mention of whether you're using AA or not in your bug reports, because it makes my life easier. Does this mean I've to rebuild the packages if I want to use AA? Is there a compile option that turns AA-Support on or off? It's just a checkbox in the KDE config. I think AA will be nice in KDE3 since then AA-Fonts should be supported to live near non-AA fonts (QT3)... I hope you understand what I mean ;) Support will be much better in qt3, but suckssuckssucks in qt2.2. -- Daniel Stone[EMAIL PROTECTED] * Overfiend_ can't recall reading about Francois MITTERAND or Georges CLEMENCEAU, let alone Napoleon BONAPARTE. Overfiend_ Or Louis THE FOURTEENTH ElectricElf Overfiend_: None of them were Japanese. pgpLkzaJ1TOQ2.pgp Description: PGP signature
Re: [kde] anti-aliasing is *NOT* supported!
On Tue, Jan 08, 2002 at 09:32:06PM +0200, Jarno Elonen wrote: Just to let you know that I will *not* support anti-aliasing. You can use it, but don't expect me to urgently follow up on bug reports involving AA, as it causes problems such as #123264. If you report an AA bug, I'll probably downgrade its severity and tag wontfix, because it's too buggy. Ok, you're the boss now (;-) but whatever you do, please don't at least disable AA *support*, leave it out of binary packages etc! The support will remain in the packages, but it's not an option I'm supporting. I don't think AA on KDE is particularily buggy and should, instead, be considered quite an important feature if we want to eventually build a desktop UI that can seriously compete with the commercial one(s). Look feel and usability are one of the areas we are most likely to fail in and therefore requires extra attention, IMHO. It will be quite important as an interface option in KDE3, but I think these three words sum up its state in KDE2.2: buggy as shit. I don't intend to support something that is indeed buggy as shit. Live with the odd jagged pixel. -- Daniel Stone[EMAIL PROTECTED] Craig Sanders isn't a real man; he's a social degenerate. -- Branden Robinson to debian-devel pgpCKWbGyIRfr.pgp Description: PGP signature
Re: [ccheney@cheney.cx: libqt2 libpng2 resolution]
On Wed, Jan 09, 2002 at 01:27:04AM +0900, Junichi Uekawa wrote: Steve M. Robbins [EMAIL PROTECTED] cum veritate scripsit: How about libqt2-dev conflicting with libpng3-dev, or something like that. That's a bit obnoxious. Some folks might like to be developing code that uses libqt2 and *other code* tha uses libpng3, on the same debian box. It's only the -dev package, which is only required for the compile time, and I believe it is quite small, only with the symlinks and the static link files... Or better, libqt2-dev depend on libpng2-dev. They generally Build-Depend on libpng2-dev, I believe. -- Daniel Stone[EMAIL PROTECTED] JALH hello? flood-join bots on the loose. InnerFIRE ack it's the irc equivelant of slashdot users pgpKKCwOwzfNo.pgp Description: PGP signature
Real Player, Konqueror, and JavaScript
Is there a way to make certain plugins appear to JavaScript to be installed? I have Real Player installed, but JavaScript will not detect it and some sites will not let you use their files unless they can detect Real Player. It is rather annoying, but there is little I can do about it. -- Alternate e-addys: [EMAIL PROTECTED], [EMAIL PROTECTED] public_key.asc Description: application/pgp-keys
Re: [kde] anti-aliasing is *NOT* supported!
On Tue, Jan 08, 2002 at 10:50:27PM +1100, Daniel Stone wrote: That said, *please* make mention of whether you're using AA or not in your bug reports, because it makes my life easier. You might be able to make this happen more often by installing a hook for bug (does reportbug support something similar?) which collects this information automatically, if that is possible. -- - mdz
Re: Real Player, Konqueror, and JavaScript
On Tue, Jan 08, 2002 at 01:54:17PM -0600, Rene Horn wrote: Is there a way to make certain plugins appear to JavaScript to be installed? I have Real Player installed, but JavaScript will not detect it and some sites will not let you use their files unless they can detect Real Player. It is rather annoying, but there is little I can do about it. You don't have the plugin installed, only the player. There's actually a specific plugin you can get somewhere to install. -- Daniel Stone[EMAIL PROTECTED] StevenK Because you need to shove in coal every farking 30 minutes with Slackware. pgpTybcbbnAqW.pgp Description: PGP signature
Re: [kde] anti-aliasing is *NOT* supported!
* Jarno Elonen schrieb am 08.01.02 um 20:32 Uhr: Just to let you know that I will *not* support anti-aliasing. You can use it, but don't expect me to urgently follow up on bug reports involving AA, as it causes problems such as #123264. If you report an AA bug, I'll probably downgrade its severity and tag wontfix, because it's too buggy. Ok, you're the boss now (;-) but whatever you do, please don't at least disable AA *support*, leave it out of binary packages etc! It works very well at least on two computers I have tried so far and makes the desktop a *lot* more usable - provided the following is in XftConfig: # Many true type fonts are optimized for point size 9-12 # and look clearer without AA in those sizes: match any family == * edit antialias = true; match all size 8 all size 13 edit antialias = false; I have the Problem here, that those 8 all size 13 fonts are very ugly then (if AA is enabled). They are not AA and ugly. With AA disabled they look nice then... (See http://iki.fi/elonen/devel/konq_aa.png for a screenshot. The page title is antialiased as are the window title and small menu texts.) And bug #123264 for example (huge fonts in konsole after AA enabled) was very easily fixed by just choosing the font manually from [popup]/font/Custom You could use the --noxft Option for that instead... I don't think AA on KDE is particularily buggy and should, instead, be considered quite an important feature if we want to eventually build a desktop UI that can seriously compete with the commercial one(s). Look feel and usability are one of the areas we are most likely to fail in and therefore requires extra attention, IMHO. ACK but looking forward to QT3, too. -Marc -- +-O . . . o . . . O . . . o . . . O . . . ___ . . . O . . . o .-+ | Ein neuer Service von Links2Linux.de: / o\ RPMs for SuSE | | -- PackMan! -- naeheres unter| __| and others| | http://packman.links2linux.de/ . . . O \__\ . . . O . . . O . |
Re: Bug#127252: kmerlin: Nope, it broke it
Ok I see what has happened now. The libpng2/3 fiasco continues. It appears that after having to recompile kmerlin to work with libqt2/libpng3 that they (maintainers of those pacakages) have decided that I again have to recompile, but this time with libqt2/libpng2. :-( I'll upload something in the next couple of days. If you are really desperate an `apt-get build-dep apt-get source -b kmerlin` will build your own kmerlin package for you which is usable. Mark
Re: Real Player, Konqueror, and JavaScript
On Tuesday 08 January 2002 02:02 pm, Daniel Stone wrote: You don't have the plugin installed, only the player. There's actually a specific plugin you can get somewhere to install. You mean the rpnp.so? I already installed that, but that did not remedy the problem. -- Alternate e-addys: [EMAIL PROTECTED], [EMAIL PROTECTED] public_key.asc Description: application/pgp-keys
testing KDE3 (was: anti-aliasing is *NOT* supported!)
I don't think AA on KDE is particularily buggy and should, instead, be considered quite an important feature if we want to eventually build a desktop UI that can seriously compete with the commercial one(s). Look feel and usability are one of the areas we are most likely to fail in and therefore requires extra attention, IMHO. It will be quite important as an interface option in KDE3, but I think Great! Now that we are on it, btw, do you know: + How smoothly does the CVS version of KDE 3 beta coexist on the same computer with current 2.2 debian packages? I would very much like to test it already but haven't dared to install yet in the fear of making the currently fine working 2.2 unusable.. + Have they announced any estimated schedule for KDE3 release on KDE mailing lists? Ie. about when can we expect official Debian packages to appear in 'unstable?' these three words sum up its state in KDE2.2: buggy as shit. I don't intend to support something that is indeed buggy as shit. Live with the odd jagged pixel. :) If you say so.. - Jarno
Re: testing KDE3 (was: anti-aliasing is *NOT* supported!)
On Tue, Jan 08, 2002 at 10:44:13PM +0200, Jarno Elonen wrote: It will be quite important as an interface option in KDE3, but I think Great! Now that we are on it, btw, do you know: + How smoothly does the CVS version of KDE 3 beta coexist on the same computer with current 2.2 debian packages? I would very much like to test it already but haven't dared to install yet in the fear of making the currently fine working 2.2 unusable.. I'm not sure that it does, at all. Chris? + Have they announced any estimated schedule for KDE3 release on KDE mailing lists? Ie. about when can we expect official Debian packages to appear in 'unstable?' When it's ready. Bear in mind, however, that KDE has the fastest release team/whatever known to man. these three words sum up its state in KDE2.2: buggy as shit. I don't intend to support something that is indeed buggy as shit. Live with the odd jagged pixel. :) If you say so.. Well, by all means fix it in Qt 2.2 and KDE2.2 upstream if you want. :) -- Daniel Stone[EMAIL PROTECTED] BenC wow...Brother is like a good company BenC I called about a problem with this printer, that I didn't even buy, and they are sending me a new drum/toner cart. free pgplJa7h2dTEY.pgp Description: PGP signature
Re: [kde] anti-aliasing is *NOT* supported!
XftConfig: # Many true type fonts are optimized for point size 9-12 # and look clearer without AA in those sizes: match any family == * edit antialias = true; match all size 8 all size 13 edit antialias = false; I have the Problem here, that those 8 all size 13 fonts are very ugly then (if AA is enabled). They are not AA and ugly. With AA disabled they look nice then... A bit confused now.. If they look nice with AA disabled in those sizes, the snippet above should do just the right trick..? It enables AA for fonts smaller or equal to 8 points and bigger or equal to 13. Sizes 9, 10, 11, 12 and 13 (ie. the most common sizes) are always non-antialiased in every application. - Jarno -- What good is an obscenity trial except to popularize literature? -- Nero Wolfe, The League of Frightened Men
Re: testing KDE3 (was: anti-aliasing is *NOT* supported!)
On Wed, Jan 09, 2002 at 07:50:48AM +1100, Daniel Stone wrote: On Tue, Jan 08, 2002 at 10:44:13PM +0200, Jarno Elonen wrote: It will be quite important as an interface option in KDE3, but I think Great! Now that we are on it, btw, do you know: + How smoothly does the CVS version of KDE 3 beta coexist on the same computer with current 2.2 debian packages? I would very much like to test it already but haven't dared to install yet in the fear of making the currently fine working 2.2 unusable.. I'm not sure that it does, at all. Chris? I am still working with you on KDE 2.2 (remember) ;) + Have they announced any estimated schedule for KDE3 release on KDE mailing lists? Ie. about when can we expect official Debian packages to appear in 'unstable?' When it's ready. Bear in mind, however, that KDE has the fastest release team/whatever known to man. Yea, I will have to start looking at the packaging of KDE3 ASAP. these three words sum up its state in KDE2.2: buggy as shit. I don't intend to support something that is indeed buggy as shit. Live with the odd jagged pixel. :) If you say so.. Well, by all means fix it in Qt 2.2 and KDE2.2 upstream if you want. :) Sound like a plan to me. ;) Chris Cheney
Re: testing KDE3 (was: anti-aliasing is *NOT* supported!)
On Tuesday 08 January 2002 21:50, Daniel Stone wrote: On Tue, Jan 08, 2002 at 10:44:13PM +0200, Jarno Elonen wrote: + How smoothly does the CVS version of KDE 3 beta coexist on the same computer with current 2.2 debian packages? I would very much like to test it already but haven't dared to install yet in the fear of making the currently fine working 2.2 unusable.. I'm not sure that it does, at all. Chris? There was an article on DebianPlanet recently: http://www.debianplanet.org//article.php?sid=533mode=order=0thold=0 -- Regards Jeppe
Re: testing KDE3 (was: anti-aliasing is *NOT* supported!)
On Tuesday 08 January 2002 23:06, Chris Cheney wrote: :) If you say so.. Well, by all means fix it in Qt 2.2 and KDE2.2 upstream if you want. :) Sound like a plan to me. ;) Don't push me.. I just might! :P (if I knew what there is to fix, that is..) - Jarno
Re: testing KDE3 (was: anti-aliasing is *NOT* supported!)
On Tue, Jan 08, 2002 at 10:11:28PM +0100, Jeppe Buk wrote: On Tuesday 08 January 2002 21:50, Daniel Stone wrote: On Tue, Jan 08, 2002 at 10:44:13PM +0200, Jarno Elonen wrote: + How smoothly does the CVS version of KDE 3 beta coexist on the same computer with current 2.2 debian packages? I would very much like to test it already but haven't dared to install yet in the fear of making the currently fine working 2.2 unusable.. I'm not sure that it does, at all. Chris? There was an article on DebianPlanet recently: http://www.debianplanet.org//article.php?sid=533mode=order=0thold=0 Yeah, I posted that. That doesn't detail the packages themselves, BTW. Ivan may or may not have 3.0beta1 packages, I can't remember. -d -- Daniel Stone[EMAIL PROTECTED] * Tv takes a voodoo doll that looks like liiwi and stamps NM on its forehead. liiwi Tv: I'll confess nothing pgpsCinH04J8u.pgp Description: PGP signature
Re: [kde] anti-aliasing is *NOT* supported!
* Jarno Elonen schrieb am 08.01.02 um 22:00 Uhr: XftConfig: # Many true type fonts are optimized for point size 9-12 # and look clearer without AA in those sizes: match any family == * edit antialias = true; match all size 8 all size 13 edit antialias = false; I have the Problem here, that those 8 all size 13 fonts are very ugly then (if AA is enabled). They are not AA and ugly. With AA disabled they look nice then... A bit confused now.. If they look nice with AA disabled in those sizes, the snippet above should do just the right trick..? It enables AA for fonts smaller or equal to 8 points and bigger or equal to 13. Sizes 9, 10, 11, 12 and 13 (ie. the most common sizes) are always non-antialiased in every application. Yes, I know. That was the strange thing that those fonts were ugly although AA was disabled for them. These 9-12 Size fonts looked different with or without AA. When I enabled AA for them by disabling the specific configline they were AA enabled and you know what that looks like... -Marc -- +--+ | -- http://www.links2linux.de -- Jetzt mit neuen Features! | | wie z.B. [EasyLink]| +---Registered-Linux-User-#136487http://counter.li.org +
repairing busted upgrade
i'm trying to repair the consequences of a mid-upgrade crash and find that kpackage lists files as installed that, actually, are not. where does kpackage read its installed files list from? additionally, attempts to uninstall corrupted packages return the following: Sorry, but the following packages have unmet dependencies: konsole: Depends: kdebase-libs (= 4:2.2.2-6) but 4:2.2.2-12 is to be installed given that i'm essentially trying to abort that previously crashed upgrade, how do i relieve kpackage of its desire to complete the upgrade, and get to keep the 4:2.2.2.-6 versions of eg. kdebase-libs, and etc., that are installed?
Re: [ccheney@cheney.cx: libqt2 libpng2 resolution]
On 7 Jan 2002, Philippe Troin wrote: Chris Cheney [EMAIL PROTECTED] writes: On Mon, Jan 07, 2002 at 05:06:27AM -0800, Philippe Troin wrote: -snip- Sounds good to fix all the current problems... however how are we going to handle the libpng2 - libpng3 conversion ? Your solution just seems to postpone the problem. libqt 3.x already uses libpng3 so that looks like a good conversion spot. Sounds good to me. How do you plan to prevent programs that link with libqt2 to also link with libpng3 ? Manual check ? Another possiblility is the following (only the new dependencies are listed): Package: libqt2-dev Conflicts: libpng3 Build-Conflicts: libpng3 [note that libpng3 is the library package _not_ the -dev package] This way neither a program that links with libqt2 nor a library libqt2 is linked with can be linked with libpng3. Phil. cu Adrian
Re: [ccheney@cheney.cx: libqt2 libpng2 resolution]
Daniel Stone [EMAIL PROTECTED] cum veritate scripsit: It's only the -dev package, which is only required for the compile time, and I believe it is quite small, only with the symlinks and the static link files... Or better, libqt2-dev depend on libpng2-dev. They generally Build-Depend on libpng2-dev, I believe. If libqt-dev depends on libpng2-dev, and libpng2-dev conflicts with libpng3-dev, whic is the case, any package build-depending on libqt-dev AND libpng3-dev will not build, which is probably the thing we want. Isn't it? regards. junichi -- [EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
Re: libqt just broke again
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 08 January 2002 09:29 am, Bjoern Krombholz wrote: On Tue, Jan 08, 2002 at 08:19:22AM -0500, Justin R. Miller wrote: The only icons problems I had before yesterday were korganizer and knotes (all I noticed anyway). After yesterday I don't even get a splash screen or a logo in kdm. I have a completely unusable KDE. LD_PRELOAD=/usr/lib/libpng.so.2.1.0.12 startx Somebody want to tell the dumb guy where to put this line? :) - -- Rykard [EMAIL PROTECTED] http://www.worldforge.org/ GPG Fingerprint= B466 4098 BDC4 F2FF 12C8 80EA B8D4 4C28 93DC 1EEA GPG KeyID=93DC1EEA If you take this message seriously, please report to your nearest mental health clinic to have your sarcasm detection parameters checked. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjw7psgACgkQuNRMKJPcHuoaVACgpHy6oSKowDhisWwqWgSueix4 TosAn14NgCKNlS8i5IDMr817Fa/MceAr =4bLa -END PGP SIGNATURE-
Re: libqt just broke again
-BEGIN PGP SIGNED MESSAGE- On Tuesday 08 January 2002 06:11 pm, Krystian G Bates wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 08 January 2002 09:29 am, Bjoern Krombholz wrote: On Tue, Jan 08, 2002 at 08:19:22AM -0500, Justin R. Miller wrote: The only icons problems I had before yesterday were korganizer and knotes (all I noticed anyway). After yesterday I don't even get a splash screen or a logo in kdm. I have a completely unusable KDE. LD_PRELOAD=/usr/lib/libpng.so.2.1.0.12 startx Somebody want to tell the dumb guy where to put this line? :) uh, how about at a command prompt? - -- Rykard [EMAIL PROTECTED] http://www.worldforge.org/ GPG Fingerprint= B466 4098 BDC4 F2FF 12C8 80EA B8D4 4C28 93DC 1EEA GPG KeyID=93DC1EEA If you take this message seriously, please report to your nearest mental health clinic to have your sarcasm detection parameters checked. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjw7psgACgkQuNRMKJPcHuoaVACgpHy6oSKowDhisWwqWgSueix4 TosAn14NgCKNlS8i5IDMr817Fa/MceAr =4bLa -END PGP SIGNATURE- - -- __ OutCast Computer Consultants of Central Oregon http://outcast-consultants.redmond.or.us [EMAIL PROTECTED] (541) 504-1388 Toll Free (866) 562-7160 Via IRC at; 205.227.115.251:6667:#OutCasts Via ICQ: UIN 138930 Failure is not an option...it's bundled with Microsoft -anonymous- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! Software is like sex. They're both better when they're free!! - Linus Torvalds As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product.
Re: libqt just broke again
LD_PRELOAD=/usr/lib/libpng.so.2.1.0.12 startx Somebody want to tell the dumb guy where to put this line? :) uh, how about at a command prompt? And for those who's kdm/gdm/xdm boot directly into X?
Re: libqt just broke again
Thus spake John Gay ([EMAIL PROTECTED]): And for those who's kdm/gdm/xdm boot directly into X? I'm making do with startx for the time being ;-) -- Justin R. Miller [EMAIL PROTECTED] View my website at http://codesorcery.net Please encrypt email using key 0xC9C40C31 pgpzbV8mi4XsS.pgp Description: PGP signature
Re: libqt2 libpng2 resolution
On Tue, 8 Jan 2002 15:00:39 +1100, Daniel Stone wrote: On Tue, Jan 08, 2002 at 03:15:00AM +, Nick wrote: Can Chris or anyone else who Understands please give a corresponding comment about testing ?I believe the standard wisdom is that testing KDE has been less useful than unstable KDE (though I don't understand why), and I'm just wondering whether that will now change. I suggest using the packages from unstable. Migration to testing isn't automatic, and KDE packages are being held back due to problems with libstdc++3 and such on hppa and arm. Thus the packages are older, such as kdenetwork, which is still lacking IMAP support in woody ... Many thanks for the advice, and for the explanation for why unstable might have more promising KDE content than testing. I note your comment in a later thread (Fresh install of kde from woody) that I suggest you do the following: * Install woody from scratch. This works fine. * Wait 5 days. * Install KDE from testing - you'll now have *working* KDE 2.2.2. and I take it you mean in this case that although the resulting KDE 2.2.2 will be working, it may be lacking some features that haven't made it through from unstable (yet). I guess the sensible thing to do might be (a) install KDE from testing, and then (b) update that KDE to the unstable version if desired things are missing - picking a good unstable moment if at all possible :) I'll have a go. Cheers, Nick Boyce Bristol, UK -- Special Relativity: The person in the other queue thinks yours is moving faster.
