Re: KDE 3.3.1 in Sarge
On Thursday 06 January 2005 15:38, Adeodato Simó wrote: I belive you can easily find a couple or more bugs related to non-working keyboards in kdm. IIRC, it's due to an upsteam change in the kdm/Xservers file. We will discuss providing a workaround for the 3.3.2 packages. Hmm. Yes, you are right. Checking the BTS, it looks like I was bitten by #266106. Fixed it like described there. I guess I just wasn't expecting a bug like this to make it to Sarge :-( Anyway, I'm still very happy with the improvements in 3.3.1. (Although I probably will change the new startup sound: it sounds too Windowsish for my taste) pgpjIjQYSTPho.pgp Description: PGP signature
Re: KDE 3.3.1 in Sarge
On Wednesday 05 January 2005 18:07, Andrew Schulman wrote:
kate always throws out reams of failed assertions to the console. I
got sick of it and now use
function kate
{
/usr/bin/kate $@ 2/dev/null
}
Yes, but that is not a real solution and it is very much worse than in the
previous version of kate in Sarge.
I yesterday deleted my ~/.xsession-errors, but now it is already at 180kB.
The main culprits are:
ASSERT: !m_doc-wrapCursor() in ../../../kate/part/katerenderer.cpp
(626)
konqueror: ERROR: Error in BrowserExtension::actionSlotMap(), unknown
action : searchProvider
IMHO, these really need to be fixed.
I also wonder if these messages really need to be printed:
gpgmeplug checkMessageSignature found email: [EMAIL PROTECTED]
gpgmeplug checkMessageSignature status flags: 3
Cheers,
FJP
pgp9gwwTVUU5X.pgp
Description: PGP signature
Re: KDE 3.3.1 in Sarge
On Wednesday 05 January 2005 16:59, Frans Pop wrote: On Wednesday 05 January 2005 14:36, Frans Pop wrote: Just upgraded to 3.3.1 in Sarge. No problems and... I ran into one other problem this morning when I booted the system. The keyboard was completely dead in kdm, including console switching. In the end I rebooted into single user mode, started kde with 'startx' and checked the keyboard settings in the control panel. It turned out that the Enable keyboard layouts checkbox had somehow been deselected and also my Xkb Options were gone. After resetting these, kdm works normally again. Cheers, FJP pgpMtiHEFQgQ3.pgp Description: PGP signature
Re: KDE 3.3.1 in Sarge
* Frans Pop [Thu, 06 Jan 2005 15:18:01 +0100]: I ran into one other problem this morning when I booted the system. The keyboard was completely dead in kdm, including console switching. In the end I rebooted into single user mode, started kde with 'startx' and checked the keyboard settings in the control panel. It turned out that the Enable keyboard layouts checkbox had somehow been deselected and also my Xkb Options were gone. After resetting these, kdm works normally again. Correct me if I'm wrong, but the settings of your user's keyborad layouts shouldn't affect what happens in kdm. I belive you can easily find a couple or more bugs related to non-working keyboards in kdm. IIRC, it's due to an upsteam change in the kdm/Xservers file. We will discuss providing a workaround for the 3.3.2 packages. -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 Listening to: Andrés Calamaro - Me Pierdo A conference is a gathering of important people who singly can do nothing but together can decide that nothing can be done. -- Fred Allen
KDE 3.3.1 in Sarge
Hi, Just upgraded to 3.3.1 in Sarge. No problems and... I love it! Thanks to everybody who worked on it! Cheers, FJP pgpRkWtNY2SYe.pgp Description: PGP signature
Re: KDE 3.3.1 in Sarge
On Wednesday 05 January 2005 14:36, Frans Pop wrote: Just upgraded to 3.3.1 in Sarge. No problems and... Hmmm. Maybe I spoke a little bit too soon. If I start kate from konsole, I get tons of messages like: ASSERT: !m_doc-wrapCursor() in ../../../kate/part/katerenderer.cpp (626) Can anyone confirm? Cheers, FJP pgpycUMNetahs.pgp Description: PGP signature
Re: KDE 3.3.1 in Sarge
If I start kate from konsole, I get tons of messages like:
ASSERT: !m_doc-wrapCursor() in ../../../kate/part/katerenderer.cpp
(626)
kate always throws out reams of failed assertions to the console. I got
sick of it and now use
function kate
{
/usr/bin/kate $@ 2/dev/null
}
--
To reply by email, replace deadspam.com by alumni.utexas.net
Processed: KDE 3.3.1 in sarge, closes many RC bugs
Processing commands for [EMAIL PROTECTED]: tags 285126 -sarge Bug#285126: CAN-2004-1171: plain text password exposure Tags were: sarge patch security Tags removed: sarge tags 271256 -sarge Bug#271256: EXPLANATION: Why testing lacks some kde packages in some architectures Tags were: sarge Tags removed: sarge tags 285126 -sarge Bug#285126: CAN-2004-1171: plain text password exposure Tags were: patch security Tags removed: sarge tags 252670 -sarge Bug#252670: klaptopdaemon: session-shutdown instantaneously when running on batteries Tags were: sarge fixed-upstream Tags removed: sarge tags 278173 +sid Bug#278173: kpdf: CAN-2004-0888: arbitrary code execution Tags were: patch sarge security Tags added: sid tags 253701 -sarge Bug#253701: krecord: Autobuilt package puts docs in /usr/share/doc/HTML Tags were: sarge Tags removed: sarge tags 247243 -sarge Bug#247243: /usr/bin/startkde: upgrades reset x-session-manager alternative to --auto Tags were: sarge Tags removed: sarge thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: KDE 3.3.1 for Sarge
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (Sorry for breaking the threads, but I'm not subscribed to d-release.) I'd be willing to help in testing apps for Sarge, provided that there is some clear coordination and the intention is let's go for KDE 3.3.1 unless ... and not maybe we'll allow KDE 3.3.1 if Although I haven't tried 3.3.1 yet (my system is running Sarge), I'd like to see it in Sarge as there are several minor annoying problems in 3.2.3 that I understand are solved in 3.3.1. I do think that proper support for and easy installation of encryption support for kmail (gpgme1.0, kleopatra) should be a condition for allowing 3.3.1. I understand from d-kde this is being worked on. Cheers, FJP -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBoS5/gm/Kwh6ICoQRAnvGAJ0X7VjKw2sawN9/TFbrAF+JZBsy3wCePRgM Kpzs267QWweL19z8yNhVK+I= =+/X9 -END PGP SIGNATURE-
Re: KDE 3.3.1 for Sarge
* Steve Langasek [Sun, 21 Nov 2004 02:47:35 -0800]: KDE 3.3 in sarge is contingent on the KDE maintainers being able to provide the same sort of assurances that were asked of the GNOME maintainers regarding the safety of allowing these packages to trickle in (i.e., the correctness of the package relationships), which calls for comprehensive partial upgrade testing. I have mixed feelinks when wrt 'partial upgrade testing' in KDE. we know from experience that KDE upstream really ensures that their monolithic x.y.z works together nicely, but that mixing even minor point releases can break things very badly. so, testing can you give the impression that the mixture works, but then it can show breakage unexpectedly. while is true that this could happen with Gnome too, it seems to me that for KDE the probability is much higher. I understand that kparts makes the package relationships more complex than those expressed in shlibs alone. This is one concrete reason I know of why testing of partial upgrades is called for -- though of course, there may be other reasons I don't know about, as well. my personal view/wish of the transition would be to let it happen, in a carefully chosen date, the more packages at once the better. if I'm not wrong, the full transition can happen, *without* *hints*, in three britney runs (kdelibs, then the core of kde, then 5 or so extra packages). IMVHO, such transition would have much less probability of breaking anything, in fact I think is as good as it can get, given kde's characteristics. * * * (the release managers may wish to skip this section, but please read the next one.) I attach the current state of kde packages. as calc already stated, they're mostly ready. kdemultimedia just needs the alpha buildd admin to have a look, and kdenetwork's dependencies will be satisfied soon. barring those two, the only important issue remaining is kdepim, which I think should get re-uploaded to fix the build system and fix a couple of dependency issues (e.g., #274611). * * * KDE 3.3.1 seems in quite good shape, being #266760 the only serious issue which can be resolved with a new arts upload. also, all the t-p-u uploads (of which at least 2 are remaining: kdegraphics for #278173 and #280373, probably kdenetwork for #282232) could be dropped, since all issues are addressed in sid. there is, however, one big issue left. my above talking about partial upgrades and leting all the transition happen at once, referred only to official KDE packages. but there is, as you know, nearly a hundred packages currently stalled by kdelibs (some with t-p-u uploads) that would become elegible for sarge once kdelibs 3.3.1 was allowed in. I have two concerns wrt these packages: 1. since there is no tranisition-all-at-once for them, one has really to check that the existing version in sarge will work correctly in a KDE 3.3 environment, as newer versions may or may not make sarge. if/when the KDE transition is approved, and before it happens, I volunteer (help welcome) to check the above, either by installing kdelibs 3.3 in a sarge system, or by installing the sarge verions of the packages in a sid system. most likely, will send mail to maintainers, too. 2. most importantly (but perhaps I'm being too paranoid here), and as all these packages were well known to be blocked from sarge, their versions in sid may not be really good release candidates (imagine, e.g., that an experimental version was uploaded to sid because it won't enter sarge anyway). hopefully, not candidate packages will have serious+ bugs on them, but I prefer to bet on the safe side. I'm seeking advice as how to deal with this (but perhaps the advice is the RMs don't see #2 as a real problem). the best I could come up with is a mass bug filing of 'serious' bugs tagged sid to all this packages, asking the maintainers to: (a) check if the package in sarge works in a KDE 3.3 environment (so that work for people helping with #1 can be reduced) (b) close the bug if is their opinion that the package in its current form is available for release. * * * and that was all for now, I think. sorry, as always, for the lengthy mail, and keep up the good work. cheers, -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 If you think nobody cares if you're alive, try missing a couple of car payments. -- Earl Wilson arts- In testing, should take care of #266760. kdelibs - Ready to enter kdebase - Waiting for kdelibs. kdegraphics - Waiting for kdelibs. kdeutils- Waiting for kdelibs. kdeadmin-
