Re: Bug#231392: konqueror: Can't talk to klauncher
On Monday 09 February 2004 16:54, Dominique Devriese wrote: > Peter Nuttall writes: > > On Monday 09 February 2004 12:46, Helge Kreutzmann wrote: > >> Hello Peter, > >> > >> On Fri, Feb 06, 2004 at 04:25:10PM +, Peter Nuttall wrote: > >> > Thanks for reporting the bug. can you tell be if the same problem > >> > happens within kde itself? > >> > >> Mmh, that'll be difficult. Since it only happens sometimes, this > >> would mean I would have to use KDE for a longer time which I really > >> would like to avoid[1]. If you have anything which requires testing > >> once, I could install KDE, try it out, and remove it again. > > > > > > > > The reason I asked was becuase kde has this thing called DCOP which > > lets kde programs talk to each other (like IPC in a tty). I was > > thinking that it wasn't running in wmaker. (klauncher is part of > > this). You could check if it is running with the kdcop program, if > > you have konqi installed, then it should already be there. The > > problems you are descibing sound like a problem with the dcop system > > to me. > > The dcopserver is supposed to be started by kde apps if it is not > already running. > > The klauncher warning is probably unrelated to the bug, as it is > issued by kded when it can't run the cache update program with > klauncher. After this warning, it falls back to the system call for > starting the program, and this is probably not a problem. > > cheers > domi Domi, are you saying the bug isn't a problem, or the error message? thanks -- Peter Nuttall [EMAIL PROTECTED]
Bug#231392: konqueror: Can't talk to klauncher
On Monday 09 February 2004 12:46, Helge Kreutzmann wrote: > Hello Peter, > > On Fri, Feb 06, 2004 at 04:25:10PM +0000, Peter Nuttall wrote: > > Thanks for reporting the bug. can you tell be if the same problem happens > > within kde itself? > > Mmh, that'll be difficult. Since it only happens sometimes, this would > mean I would have to use KDE for a longer time which I really would > like to avoid[1]. If you have anything which requires testing once, I > could install KDE, try it out, and remove it again. > The reason I asked was becuase kde has this thing called DCOP which lets kde programs talk to each other (like IPC in a tty). I was thinking that it wasn't running in wmaker. (klauncher is part of this). You could check if it is running with the kdcop program, if you have konqi installed, then it should already be there. The problems you are descibing sound like a problem with the dcop system to me. - Peter Nuttall
Bug#231392: konqueror: Can't talk to klauncher
On Friday 06 February 2004 08:39, Helge Kreutzmann wrote: > Package: konqueror > Version: 4:3.1.3-1 > Severity: normal > > I run wmaker and use the session support by wmaker to restore the > windows when X is started with startx. > > Konqueror-windows are opened fine, but sometimes I get for every > window the error message (a button): > Could not start process Can't talk to klauncher > > If you want I can provide a screenshot of this. > > > I tried manually starting klauncher with > klauncher & > but this does not help (nor do I see a process klauncher running > afterwards). > > The same error appears when pressing the "Home" button, and local file > directory browsing is impossible; the file open dialog is also > unusuable. > > This also happend with konqueror under woody, but was not reported. > > I am not sure how to properly debug this to report the error more > precicesly. Please tell me what to look for/at when this happenes next > time, to provide you with the necessary details. > > My *impression* (!!) is, that it is related to system load. If only > one konqueror window is to be openend, the error is a lot less likly > to occur; also usually the system has some load when X is started > directly after boot (e.g. checksecurity), so it takes a while for the > konqueror windows to appear (much later than e.g. the xterms). But I > might be wrong on that guess. > > It would be great if at least a possibility existed, to (re)start > klauncher manually instead of having unusuable konqueror windows. > > Even better would be, if all windows could be opend at once (with the > proper location on the screen and maybe even the proper directories). > But I know KDE has decided against this route. > > -- System Information: > Debian Release: testing/unstable > Architecture: alpha > Kernel: Linux sixtyfor 2.4.21-pre1 #1 Don Okt 2 18:27:25 CEST 2003 alpha > Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] > > Versions of packages konqueror depends on: > ii kate4:3.1.3-1KDE Advanced Text Editor > ii kcontrol4:3.1.3-1KDE Control Center > ii kdelibs44:3.1.4-3KDE core libraries > ii kfind 4:3.1.3-1KDE File Find Utility > ii libart-2.0-22.3.8-1 The Gnome 2 canvas widget - > runtim ii libc6.1 2.3.2.ds1-10 GNU C Library: Shared > libraries an ii libfam0c102 2.6.10-6 client library to > control the FAM ii libgcc1 1:3.3.2-4GCC support > library > ii libjpeg62 6b-9 The Independent JPEG Group's > JPEG ii libkonq44:3.1.3-1Core libraries for KDE's > file mana ii libpcre34.3-3Philip Hazel's Perl > 5 Compatible R ii libpng12-0 1.2.5.0-4PNG library - > runtime ii libqt3c102-mt 3:3.2.1-6Qt GUI Library > (Threaded runtime v ii libstdc++5 1:3.3.2-4The GNU > Standard C++ Library v3 ii libxrender1 0.8.3-5 X > Rendering Extension client libra ii xlibs 4.2.1-12.1 > X Window System client libraries ii zlib1g > 1:1.2.1-3compression library - runtime > > -- debconf information: > * konqueror/crypto: hi Thanks for reporting the bug. can you tell be if the same problem happens within kde itself? Pete -- Peter Nuttall [EMAIL PROTECTED]
Re: check the wiki
On Thursday 05 February 2004 19:42, Yves Glodt wrote: > On Thursday 05 February 2004 20:26, Peter Nuttall wrote: > > On Thursday 05 February 2004 19:08, Yves Glodt wrote: > > > Hi, > > > subject says all, > > > > > > TIA! > > > > as above: > > http://wiki.debian.net/?DebianKDE > > Thank you for the information, however it triggered another question... > > When could KDE 3.1.5 make it into testing? I (and I guess many other > users too), wanna just know if I wait, or go experimental. I prefer > staying unstable as it is less likely to break stuff... > > regards, > Yves It is a good question. As you might know, debian is warming up to relase its next version: sarge. as the testing branch is what will become sarge, then it is in a state of flux at present. on one hand, the debian higher-ups would prefer it if the kde matainers did not upgrade kde futher in sarge. this would lessen pressure on the bbluids and mean that they could finsh sarge and get it out the door on the other hand, the debian kde people would want sarge to release with the latest version of kde, if not 3.2 at least 3.1.5. this would fix lots of bugs. Also as long as people keep breaking the kde packages in sarge by upgrading libs and the toolchain, then the debian kde people will be upgrading and fixing the packages anyway, and does it matter that they are now the latest version? in conclusion, we have no idea when 3.1.5 is going to move to testing, but it will probably be a week or two. the packages in experamental are iffy at present, they suffer from a lot of packaging bugs. then again, people have got them to work. it is your machine and I can not tell you what to do with it, so make up your own mind. best of luck pete -- Peter Nuttall [EMAIL PROTECTED]
Re: sarge beta2 out
On Thursday 15 Jan 2004 9:54 pm, Mark Bucciarelli wrote: > http://www.debian.org/devel/debian-installer/ Thats just the installer. It will be a little while until all the packages are sorted out and ready. You may want to read this email and its replies: http://lists.debian.org/debian-devel/2004/debian-devel-200401/msg00264.html > Anyone know if 3.2 compiles on Sarge out of the box? Chris has suggested that the final version of sarge will ship with KDE 3.2. also it will enter unstable soon and so it will be easier to backport with debs rather than source code. All the best -- Peter Nuttall [EMAIL PROTECTED]
Re: Anyone else getting frequent Konqueror segfaults?
On Wednesday 10 Dec 2003 4:17 am, Doug Holland wrote: > On Tue 09 Dec 2003 2:40 pm, Anders Ellenshøj Andersen wrote: > > On Tuesday 09 December 2003 21:16, James Wells wrote: > > > I'm running 2.4.22-1-k7 and I get the same problem when dragging from > > > one Konqueror window to another. > > > > I think we should open a bug for this. Could someone do it and post a > > link to it so we can comment on it? > > > > Anders > > > > -- > > This email was generated using KMail from KDE 3.1.4 on Debian GNU/Linux > > There is one already: Bug#222662 at bugs.debian.org. > > Meldroc I just looked though the bug report and I think it is a problem with the kernel package rather than with konqueror because I can not produce it on my machine which is running a self-compiled kernel (2.4.22). I find it quite hard to segfault konqueror, normally it just hangs if it can not cope with something. -- Peter Nuttall [EMAIL PROTECTED]
Re: KDE keyboard layout
On Saturday 06 Dec 2003 8:23 pm, herve wrote: > Hi i have kde 3.1.4 and a logitech keyboard cordless desktop the one with > the optical mouse (4 btn) + wheel on the left of the keyboard. > I chose in configuration panel the option "logitech Cordless desktop pro" > aplly the nex settings, logout and relog but nothing appen... > > Could someone help me to use the multimedia keys of this keyboard?? > > > All help would be very appreciated...this keyboard turns me crazy :-( > > Thx in advance > > Hervé hi I have a multimedia keyboard I use the multimedia buttons by having the kde keyboard tool running in the background. To set this up open the control center and go to the regional and Accessibilty menu then to Keyboard layout. Enter the country that you come from and the model of your keyboard. (you may have to guess the model or use a differant model) apply this then see if you can set any of the multimedia buttons in any of the standard shortcut dialogs. This is a simple and fast explanion of how to do it. If you have any problems post them. good luck -- Peter Nuttall [EMAIL PROTECTED]
Re: KDE 3.1.4 arts alsa problem
On Thursday 04 Dec 2003 11:35 pm, herve wrote: > Hi all > i have a probleme after alsa 0.5 install with arts > > I have a woody with kde 3.1.4 and some backports. > After alsa installation, i choose alsa in the sound control panel...then i > got an error : > > Sound server informational message: > Error while initializing the sound driver: > device: default can't be opened for playback (Unknown error) > The sound server will continue, using the null output device. > > it's very curious... > > When i was using oss all was ok with kde sounds, noatun was workingand > xmms freeze > > After alsa installation and arts disabled, there is no longer kde sounds > and sound from noatun but xmms works > > do i have to say goodbye to alsa and xmms? that would fix your problem. try juk as a media player in kde. > i've installed alsa cause i though thath i could bring me more > configuration possibility than oss about mixers it does > > When i want to install xmmsarts in order tu use arts output plugin for > xmms, it tells me that i have to install libarts-alsa and libarts... > When i try to install libarts-alsa apt "want" to remove nearly all my kde > packages > as you might know the debian servers are offline at present so no fixes can be made. Otherwise the problem would have been fixed overnight. > Someone has an idea of what is all this tricky thing ?? > > thx in advance hope this helps -- Peter Nuttall [EMAIL PROTECTED]
Re: the kde meta-package or BTS #211985
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 24 Oct 2003 3:21 am, Chris Cheney wrote: > On Thu, Oct 23, 2003 at 09:58:34PM +0100, Peter Nuttall wrote: > > my point was questioning the value of a meta-package that would be the > > logical thing to install if you were wanting kde but that seemed to be > > both big and broken. > > It will be primarily of use for stable Debian releases when the dist has > actually stablized and is installable. ;) > > > > That said meta-kde will be restructured very soon in that unofficial > > > KDE apps will no longer be mentioned by meta-kde directly, there will > > > be a second meta-kde-extras source that provides metapackages for them. > > > This will allow backports to use meta-kde without unsolvable > > > dependencies. > > > > this is want I was asking for. but went you talk of 'unofficial' > > packages are you refering to the kde things like the games and the > > multimedia packages or koffice and quanta or things like juk and arson? > > The official kde packages are: > arts > kde-i18n > kdeaddons > kdeadmin > kdeartwork > kdebase > kdebindings > kdeedu > kdegames > kdegraphics > kdelibs > kdemultimedia > kdenetwork > kdepim > kdesdk > kdetoys > kdeutils > quanta > > Note: Juk will be part of kdemultimedia in KDE 3.2 so will be part > official at that point. > thanks > Chris - -- Peter Nuttall [EMAIL PROTECTED] Don't CC me unless I ask "... being a Debian unstable user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed." -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/mWuzcA58uJCvV4URAjx+AKCnTwUzs2rKlqQYsFM4H7YnSGiNegCfVDt7 OoBNchp7x7YXOJMjMxc7nVU= =0Qnp -END PGP SIGNATURE-
Re: the kde meta-package or BTS #211985
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 23 Oct 2003 7:33 pm, Chris Cheney wrote: > On Thu, Oct 23, 2003 at 04:10:11PM +0100, Peter Nuttall wrote: > > and #212933 > > Date: Thu, 23 Oct 2003 16:10:58 +0100 > > User-Agent: KMail/1.5.4 > > MIME-Version: 1.0 > > Content-Type: Text/Plain; > > charset="us-ascii" > > Content-Transfer-Encoding: quoted-printable > > Content-Description: clearsigned data > > Content-Disposition: inline > > Message-Id: <[EMAIL PROTECTED]> > > Status: RO > > X-Status: Q > > X-KMail-EncryptionState: > > X-KMail-SignatureState: > > > > =2DBEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > Hi=20 > > > > I was looking at the BTS for kde while reading some other debian-qt-kde > > mai= l=20 > > and I saw that the meta kde package seems to be always broken. I think > > this= =20 > > is because it depends on a big chunk of the kde packages (fontconfig,=20 > > kde-core, kde-amusements, kdeaddons, kdeadmin, kdeartwork, > > kdegraphics,=20 kdemultimedia, kdenetwork, kdepim, kdeutils, koffice and > > quanta)and if any= =20 > > one of them is broken or is not compatible with any other then it falls > > ove= r.=20 > > Since the normal advice on debian-kde is not to use this and the wiki=20 > > ( http://wiki.debian.net/DebianKDE ) also says not to use this, could it > > be= =20 > > changed to just show the normal install instructions though debconf or=20 > > attempt to just install a base kde system ( ie not kde-amusements, > > kdeaddon= s,=20 > > kdemultimedia, kdenetwork, kdepim, kdeutils, koffice and quanta) > > Why not use kde-core which already only depends on the minimal packages: > arts, kdelibs, kdebase... my point was questioning the value of a meta-package that would be the logical thing to install if you were wanting kde but that seemed to be both big and broken. However, in the past the part that keeps > getting broken is kdebase which happens to be one of the most important > packages. kdemultimedia is currently broken but that is due to the > gcc-3.3 transition (#203303), once glibc is fixed properly this is > unlikely to happen again. As I understand it glibc will be fixed > sometime next week. > thanks for that data > That said meta-kde will be restructured very soon in that unofficial KDE > apps will no longer be mentioned by meta-kde directly, there will be a > second meta-kde-extras source that provides metapackages for them. This > will allow backports to use meta-kde without unsolvable dependencies. > this is want I was asking for. but went you talk of 'unofficial' packages are you refering to the kde things like the games and the multimedia packages or koffice and quanta or things like juk and arson? > Chris thanks ps sorry about the email. I think the subject was too long. - -- Peter Nuttall [EMAIL PROTECTED] Don't CC me unless I ask "... being a Debian unstable user is sort of like living in a house inhabited by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed." -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/mED9cA58uJCvV4URApK2AKDMpzVa2T5pciEi5l3FSATwFQOedQCfRbm7 lbdm41A3PAHs/j/gcPUEHU4= =oz6+ -END PGP SIGNATURE-
the kde meta-package or BTS #211985
and #212933 Date: Thu, 23 Oct 2003 16:10:58 +0100 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <[EMAIL PROTECTED]> Status: RO X-Status: Q X-KMail-EncryptionState: X-KMail-SignatureState: =2DBEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi=20 I was looking at the BTS for kde while reading some other debian-qt-kde mai= l=20 and I saw that the meta kde package seems to be always broken. I think this= =20 is because it depends on a big chunk of the kde packages (fontconfig,=20 kde-core, kde-amusements, kdeaddons, kdeadmin, kdeartwork, kdegraphics,=20 kdemultimedia, kdenetwork, kdepim, kdeutils, koffice and quanta)and if any= =20 one of them is broken or is not compatible with any other then it falls ove= r.=20 Since the normal advice on debian-kde is not to use this and the wiki=20 ( http://wiki.debian.net/DebianKDE ) also says not to use this, could it be= =20 changed to just show the normal install instructions though debconf or=20 attempt to just install a base kde system ( ie not kde-amusements, kdeaddon= s,=20 kdemultimedia, kdenetwork, kdepim, kdeutils, koffice and quanta) I'm sorry if this sounds like I am dumping on Chris Cheney or whoever takes= on=20 his packages but it seems from Adrian Bunk's words that people have=20 complained about the bug sitution in kde and removing the cause of bug=20 reports like this one is one way forward. =20 thanks =2D --=20 Peter Nuttall [EMAIL PROTECTED] Don't CC me unless I ask "... being a debian unstable user is sort of like living in a house inhabit= ed by a large family of carpenters and architects. Every morning when you wake up, the house is a little different. Maybe there is a new turret, or some walls have moved. Or perhaps someone has temporarily removed the floor under your bed." =2DBEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/l++GcA58uJCvV4URAvCrAKCgATWk1bTBJTbCBq046B+Ybs1zFwCgm1hW cuBOT+zNx9MFl/EVW3t/Rl0=3D =3DYdtE =2DEND PGP SIGNATURE-
Re: Orphaning Packages
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 22 Oct 2003 7:10 pm, Chris Cheney wrote: > I have orphaned the following packages for anyone interested in adopting > them: > > arts > hdparm > jasper > jfsutils > kdeadmin > kdebase > kdegraphics > kdelibs > kdenetwork > kdepim > kdeutils > libboulder-perl > libcflow-perl > libconfigreader-perl > libhtml-table-perl > libnet-patricia-perl > libusb > meta-kde > usbutils > > Thanks, > Chris Cheney I'm not a debian developer but I could do one or two of the higher-level kde things, such as kdenetwork or kdeadmin. I will do what I can before becoming a developer, reading thougfh the new mantainers stuff on www.debian.org in suggests doing some packing before becoming a developer. thanks - -- Peter Nuttall [EMAIL PROTECTED] Dont CC me unless I ask Someone esle can help you better than I can. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/l3j1cA58uJCvV4URAk+cAJ9eEtukKxHUAnVuOIqlFvViR87+pACgvWAb 7MXmU8td/63Ar3ZHOeLLQy0= =CkAk -END PGP SIGNATURE-
