KDE3.1 beta2 package conflicts (log included)
Hi. I'm running an up to date sid system, and I have been using (with great pleasure) Karolina's KDE3.1-beta1 packages for some time now. I decided to upgrade to the KDE3.1-beta2 packages that I believe she created - I apt-got them ;) from http://shakti.ath.cx/debian/kde3.1-beta2. I have some conflicts with the new packages that I cannot resolve by any apt method I've tried. It looks as though libarts1, libarts1-dev, and kdelibs4-bin are using files that are part of the KDE3.1-beta1 packages. Any suggestions are appreciated. log follows: [EMAIL PROTECTED]:~$ sudo apt-get -f install Reading Package Lists... Done Building Dependency Tree... Done Correcting dependencies... Done The following extra packages will be installed: libartsflow-data libartsflow1 libkutils1 libmcop1 libsoundserver-bin libsoundserver-data libsoundserver1 The following NEW packages will be installed: libartsflow-data libartsflow1 libkutils1 libmcop1 libsoundserver-bin libsoundserver-data libsoundserver1 0 packages upgraded, 7 newly installed, 0 to remove and 109 not upgraded. 14 packages not fully installed or removed. Need to get 0B/1089kB of archives. After unpacking 4727kB will be used. Do you want to continue? [Y/n] y Reading changelogs... (Reading database ... 90738 files and directories currently installed.) Unpacking libkutils1 (from .../libkutils1_4%3a3.0.8.cvs20020930-1.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libkutils1_4%3a3.0.8.cvs20020930-1.2_i386.deb (--unpack): trying to overwrite `/usr/lib/libkutils.so.1.1.0', which is also in package kdelibs4-bin dpkg-deb: subprocess paste killed by signal (Broken pipe) Unpacking libmcop1 (from .../libmcop1_1.1.0.cvs20020926-1.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libmcop1_1.1.0.cvs20020926-1.2_i386.deb (--unpack): trying to overwrite `/usr/lib/libgmcop.so.1.0.0', which is also in package libarts1-dev dpkg-deb: subprocess paste killed by signal (Broken pipe) Unpacking libartsflow-data (from .../libartsflow-data_1.1.0.cvs20020926-1.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libartsflow-data_1.1.0.cvs20020926-1.2_i386.deb (--unpack): trying to overwrite `/usr/lib/mcop/Arts/DataHandlePlay.mcopclass', which is also in package libarts1 Unpacking libartsflow1 (from .../libartsflow1_1.1.0.cvs20020926-1.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libartsflow1_1.1.0.cvs20020926-1.2_i386.deb (--unpack): trying to overwrite `/usr/lib/libartsflow.so.1.0.0', which is also in package libarts1 dpkg-deb: subprocess paste killed by signal (Broken pipe) Unpacking libsoundserver-data (from .../libsoundserver-data_1.1.0.cvs20020926-1.2_all.deb) ... dpkg: error processing /var/cache/apt/archives/libsoundserver-data_1.1.0.cvs20020926-1.2_all.deb (--unpack): trying to overwrite `/usr/lib/mcop/Arts/FileInputStream.mcopclass', which is also in package libarts1 Unpacking libsoundserver-bin (from .../libsoundserver-bin_1.1.0.cvs20020926-1.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libsoundserver-bin_1.1.0.cvs20020926-1.2_i386.deb (--unpack): trying to overwrite `/usr/bin/artscat', which is also in package libarts1-bin dpkg-deb: subprocess paste killed by signal (Broken pipe) Unpacking libsoundserver1 (from .../libsoundserver1_1.1.0.cvs20020926-1.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libsoundserver1_1.1.0.cvs20020926-1.2_i386.deb (--unpack): trying to overwrite `/usr/lib/libartsgslplayobject.so.0.0.0', which is also in package libarts1 dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libkutils1_4%3a3.0.8.cvs20020930-1.2_i386.deb /var/cache/apt/archives/libmcop1_1.1.0.cvs20020926-1.2_i386.deb /var/cache/apt/archives/libartsflow-data_1.1.0.cvs20020926-1.2_i386.deb /var/cache/apt/archives/libartsflow1_1.1.0.cvs20020926-1.2_i386.deb /var/cache/apt/archives/libsoundserver-data_1.1.0.cvs20020926-1.2_all.deb /var/cache/apt/archives/libsoundserver-bin_1.1.0.cvs20020926-1.2_i386.deb /var/cache/apt/archives/libsoundserver1_1.1.0.cvs20020926-1.2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [EMAIL PROTECTED]:~$ Nathan Waddell
ugle background when starting kdm
I would say look at the Xserver logs. I would bet you have something in there that X is searching for and not finding. If you have both a 'Configured Mouse' and 'Generic Mouse' section, disable the one that is NOT set as root pointer. This caused a few seconds of hangup on my box. Look for any warnings, like unused font paths and such, and correct the errors. If some fonts are not used by X anyway, comment them out of XF86Config-4. Nathan
/usr/share/templates/.source/emptydir
Can anyone who can successfully create empty directories on their desktop please email me with the contents of this file? I am trying to create new directories on my desktop with the right-click menu, but it is not creating the directories for me. Nathan
Re: Cannot create emptydir
If the icon is then that of a 'broken' document, add the following to the file called emptydir: [Destop Entry] Icon=folder I just need to figure out what its 'type' is. Nathan On Saturday 14 September 2002 11:31 pm, Warren Dodge wrote: > This one time, at band camp, Malcolm Hunter said: > > > fails and the following dialog appears: > > > "The templates file /usr/share/templates/.source/emptydir" doesn't > > > exist!" > > > > Does emptydir exist there? Have you tried creating it? > > Too simple! Works great!
Re: kde 3.* in sid will it ever happen?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Friday 13 September 2002 09:08 am, James Lindenschmidt wrote: > Though I wouldn't know from experience, by most accounts I've heard KDE > 3.x has several advantages over KDE 2.x, speed and stability being two. Of > course, the improved eye candy doesn't hurt either (so much for speed! > LOL). I am running KDE 3.1 on debian sid, and it is nice and stable, and the speed is good, but I honestly don't believe that the desktop environment is faster as a whole - individual applications, like Konqueror's HTML rendering speed, yes, - but the overall 'snappiness' and memory usage is (AFAICT) about the same as 2.2. > You raise some good points. I am quite productive in KDE 2.2.2, but many > of the applications I am using have moved to KDE 3.x, and as such I don't > get bug fixes and/or new features since KDE 3 isn't yet in sid. Yup. This is one of the reasons I moved up also. > I am definitely a non-geek end-user type, with a strong ethical commitment > to Free software, which is why I turned to Debian in the first place. I > would love to run LibraNet, but they seem to want to not have users, since > they don't allow downloads of their latest versions. This seems contrary > to the spirit of the GPL to me (though it is apparently within the 'letter > of the law') :-( The spirit of the GPL is not to give away software for free. That's free as in "free beer". The spirit of the GPL is that the source is always included, and you can do what you like with your own software. That's free as in "freedom". > I agree that I don't relish going back to RedHat, but it looks to me that > RH8 may have what I need as an end-user type. But I would certainly miss > apt-get. IMHO, RedHat is not more "bleeding-edge" than Debian. They're just crazy enough to release software that still has major bugs - that the upstream (the folks who work on individual projects like Gnome, KDE, E, gcc, etc.) are issuing warnings about. I'd rather have a stable OS that works as it should than one that looks really cool if and when it runs. That's why most ex-windoze linux users converted to using Linux, right? For the stability. IMNSHO, the RedHat Package Manager is far less powerful and flexible than Debian's dpkg. Forcing users to go searching for RPM's that may or may not have that dependency you need to compile/run an important program is idiocy. The situation is worsened because of all the RPM's that are built by upstream authors who may or may not adhere to the FSH and the LSB. Heck, Suse is different enough from RedHat to cause wierd problems with some distributor-inspecific RPMs. My point is that Debian has FAR more pro's than con's. It will install and run on more architectures than many distributions, and if you stick with the potato or woody distribution, you are almost guaranteed that your software will run flawlessly. Sure, the version may be 2.2 instead of 3.1, but that will be ameliorated when gcc-3.2 enters unstable/sid. Don't get discouraged - and if you need more 'bleeding edge' unstable/sid, take a look at http://www.golum.org/aptgetlinks.shtml. That is my local LUG homepage, where we have published some of the more popular 'unofficial' apt-getables. Just add the lines indicated to your /etc/apt/sources.list and dist-upgrade. When the unofficial packages enter sid, just remove the line. It doesn't get much easier than that. Nathan -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9ghkm4e9YdOpQYMsRAuauAJsFjkZFcV5J0HBZpePXNW7c5y2DKgCfT5/4 NjhEBxPLSek+/HfVPFPGIJU= =t1JF -END PGP SIGNATURE-
Re: Wanted: text editor where word wrap does not insert newline
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Have you submitted this patch to the Kate team? Nathan On Wednesday 04 September 2002 06:14 pm, Jarno Elonen wrote: > Hi, > > I just made a KDE 3.0.3 patch that fixes virtual wrapping in kedit. > The patch, and also a binary .deb for the impatient, are available at: > > http://koti.welho.com/jelonen/code/unofficial-debs/kedit-wordwrap/ > > Choose "Virtual (visible but not saved)" as Word Wrap from options. It > replaces the "Let editor width decide" option. > > - Jarno - -- 12413AEB2ED4FA5E6F7D78E78BEDE820945092OF923A40EElOE5IOCC98D444AA08E324 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9ePjK4e9YdOpQYMsRAhWKAJ9nnuM/pQcNvU6nvA9zeuVC9Q1nBwCfcbrZ h6UpU/W7TXSrVF//64/F6DE= =Bh92 -END PGP SIGNATURE-
Konqueror 3.07 crashing upon sending mail to OWA
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. I'm using Debian unstable on KDE3.1-beta1, and Konqueror 3.07. At work, I routinely use OWA (Outlook Web Access) to email via our corporate exchange server. All functions work fine except sending mail. Every time I send an email, Konqueror crashes, and produces a KDE crash handler. Not that my email DOES get sent every time. Here is the debugging information from the crash handler: (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)...[New Thread 1024 (LWP 3375)] (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)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x40e35609 in wait4 () from /lib/libc.so.6 #0 0x40e35609 in wait4 () from /lib/libc.so.6 #1 0x40eaadd0 in __check_rhosts_file () from /lib/libc.so.6 #2 0x40ce0eeb in waitpid () from /lib/libpthread.so.0 #3 0x405986ac in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #4 0x40cdea44 in pthread_sighandler () from /lib/libpthread.so.0 #5 0x40dbe518 in sigaction () from /lib/libc.so.6 #6 0x413d014a in KHTMLPart::qt_invoke () from /usr/lib/libkhtml.so.4 #7 0x4086db26 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #8 0x4086da7e in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #9 0x413e84f8 in DOM::DocumentImpl::finishedParsing () from /usr/lib/libkhtml.so.4 #10 0x413e8569 in DOM::DocumentImpl::qt_emit () from /usr/lib/libkhtml.so.4 #11 0x4140c3e0 in DOM::HTMLDocumentImpl::qt_emit () from /usr/lib/libkhtml.so.4 #12 0x4086db0e in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #13 0x4086da7e in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #14 0x413f87a8 in Tokenizer::finishedParsing () from /usr/lib/libkhtml.so.4 #15 0x4140466a in HTMLTokenizer::end () from /usr/lib/libkhtml.so.4 #16 0x414048cb in HTMLTokenizer::finish () from /usr/lib/libkhtml.so.4 #17 0x413e4dcd in DOM::DocumentImpl::finishParsing () from /usr/lib/libkhtml.so.4 #18 0x413bdcc1 in KHTMLPart::end () from /usr/lib/libkhtml.so.4 #19 0x413bd229 in KHTMLPart::slotFinished () from /usr/lib/libkhtml.so.4 #20 0x413d013c in KHTMLPart::qt_invoke () from /usr/lib/libkhtml.so.4 #21 0x4086db83 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #22 0x40143493 in KIO::Job::result () from /usr/lib/libkio.so.4 #23 0x401348f8 in KIO::Job::emitResult () from /usr/lib/libkio.so.4 #24 0x40135955 in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.4 #25 0x40136e20 in KIO::TransferJob::slotFinished () from /usr/lib/libkio.so.4 #26 0x4014470c in KIO::TransferJob::qt_invoke () from /usr/lib/libkio.so.4 #27 0x4086db26 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #28 0x4086da7e in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #29 0x4012a79c in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.4 #30 0x40129334 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4 #31 0x40128e88 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4 #32 0x40126d58 in KIO::Slave::gotInput () from /usr/lib/libkio.so.4 #33 0x40128549 in KIO::Slave::qt_invoke () from /usr/lib/libkio.so.4 #34 0x4086db26 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #35 0x4086dc34 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #36 0x40aa940b in QS
Re: kde programs and environment
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It seems as though there is a void to be filled here. Someone with a good understanding of KDE and this problem should create a fix, perhaps reading in all of the aforementioned files or something. What would also be very cool to have would be a gui program that checks defined environment settings and reports them, as well as allowing you to click on them and change/set their values within KDE. Wish I understood KDE well enough, but alas not yet. Nathan On Friday 06 September 2002 12:54 am, Nikita V. Youshchenko wrote: > > How do I forward environment variables to kde program? > > I am using ktexmaker2 and it does not see my TEXINPUTS > > environment variable when I click a TeX file. When I start > > ktexmaker2 from a shell it is fine but then I have to use the > > open button to get to the file. Direct clicking is more convenient. >> > Seems that currently there is NO WAY to set up user's own environment > corectly (unless pam_env can read some per-user configuration which I am > not aware of). -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9eMyb4e9YdOpQYMsRAnozAJ4nzL7qL/Z5u7cris2lZ7dan5m0kACeJKrL 5Pp0yW9pupShE+8V8O3x7L4= =JqhI -END PGP SIGNATURE-
Re: Kbear crashes in KDE3.1beta on Debian unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I got the deb I am referring to from the source in your email: >I have done that. >I did nothing more than just rebuild it on kde 3.1. The package I made is on >http://cgi.algonet.se/htbin/cgiwrap/pgd/debian/kde3.1-apps/kbear_2.0beta2.kde31-1_i386.deb > >-- Karolina either a) Kbear was never upgraded from my KDE 3.0 version because of the name of the package (kbear_2.0beta2.kde31-1_i386.deb, which dpkg believed was a downgrade) and I never noticed because I use apt-get dist-upgrade or aptitude, or b) the Kbear that I had was never upgraded from the KDE 2.2 version. Either one is likely, as I don't remember when it was upgraded before this. If that kbear package is the same package you provided with the 3.1 packages, and you didn't rebuild it because of my original email, then one of these two things must have occured. The package probably needs to be renamed in such a way that dpkg does not interpret it as a downgrade. Nathan On Friday 06 September 2002 02:05 am, Karolina Lindqvist wrote: > I didn't have the debian files for 2.0-beta2-1. > > I have a kind of feeling that the problem with kbear might be a possible > problem for every package built separately for kde 3.0, when kde 3.1 is > coming. Maybe the officiall kde 3.1 packager is solving that problem > somehow? > > I am not sure exactly how to build the beta so that all packages that > depend on older versions of kde will be automatically rejected, at the same > time as packages built with kde 3.1- beta should be compatible with the > future kde 3.1 official packages. If anyone have an idea, I would be > grateful, since I will rebuild for kde 3.1-beta2 when it is official. > > -- Karolina - -- 12413AEB2ED4FA5E6F7D78E78BEDE820945092OF923A40EElOE5IOCC98D444AA08E324 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD4DBQE9eMuD4e9YdOpQYMsRAqEXAJwIUH9SEAwBh5TPaHumi9SYTg01CQCXWwko GsN/EJl/PizMyGtfhuS5vg== =vBkh -END PGP SIGNATURE-
Re: Kbear crashes in KDE3.1beta on Debian unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Karolina, I downloaded this deb and kbear loads fine now. So this issue is fixed ;) Just so you know, dpkg believes that I was DOWNGRADING kbear: [EMAIL PROTECTED]:~/src/debs$ sudo dpkg -i kbear_2.0beta2.kde31-1_i386.deb dpkg - warning: downgrading kbear from 2.0-beta2-1 to 2.0beta2.kde31-1. (Reading database ... 75273 files and directories currently installed.) Preparing to replace kbear 2.0-beta2-1 (using kbear_2.0beta2.kde31-1_i386.deb) ... Unpacking replacement kbear ... Setting up kbear (2.0beta2.kde31-1) ... [EMAIL PROTECTED]:~/src/debs$ Thanks for the fix! If there is a better way to report bugfixes in these packages in the future, let me know. Ravenhall On Friday 06 September 2002 12:15 am, Karolina Lindqvist wrote: > torsdagen den 5 september 2002 12.08 skrev Ben Burton: > > So one suggestion would be to get the debian kbear sources (apt-get > > source kbear) and rebuild the package yourself on your 3.1 system and see > > if this helps; otherwise you could perhaps ask Karolina for help since I > > understand she's providing the core 3.1 stuff. > > I have done that. > I did nothing more than just rebuild it on kde 3.1. The package I made is > on > http://cgi.algonet.se/htbin/cgiwrap/pgd/debian/kde3.1-apps/kbear_2.0beta2.k >de31-1_i386.deb > > -- Karolina - -- 12413AEB2ED4FA5E6F7D78E78BEDE820945092OF923A40EElOE5IOCC98D444AA08E324 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9eEWl4e9YdOpQYMsRAia5AJ9tRWs5CDdgs+AeEjoc/s1IZPheawCgmGgy q29liKy9osFx2Y7pPrcbU5Y= =k4/n -END PGP SIGNATURE-
Re: Kbear crashes in KDE3.1beta on Debian unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 That's odd, because Kmail doesn't give me any problems at all. Rav On Thursday 05 September 2002 05:17 am, Børre Gaup wrote: > I also had problems with libkjava after I installed 3.1beta. I got an error > from kmail, claiming it needed libkjava. > What I did was to first purge (apt-get remove --purge) all packages with > any connection to kde, e.g. libqt3, arts1, etc and then reinstall KDE. That > solved my problem. Don't ask me why, but it worked:-) > > Hope it is of any help. > > regards, > -- > Børre Gaup - -- 12413AEB2ED4FA5E6F7D78E78BEDE820945092OF923A40EElOE5IOCC98D444AA08E324 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9d+Hv4e9YdOpQYMsRAv/nAJoDjPawszwEHybQ4KqnEL0S796K2QCcCxo8 GzdML8fkYr1hlcYfNnoCSdo= =Q5Lo -END PGP SIGNATURE-
Re: Kbear crashes in KDE3.1beta on Debian unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The version of Kbear I am running: [EMAIL PROTECTED]:~$ kbear -v Qt: 3.0.5 KDE: 3.0.7 (KDE 3.1 beta1) KBear: 2.0beta2 [EMAIL PROTECTED]:~$ Hope this helps. Ravenhall On Wednesday 04 September 2002 09:10 pm, Ben Burton wrote: > > Kbear crashes upon opening in KDE3.1beta1 on Debian unstable. The > > packages for KDE3.1beta1 I got from > > http://folk.uio.no/johannwi/kde3.1-beta1/, so perhaps this is a bug with > > those packages. I am emailing the maintainer of KBear, the debian-kde > > mailing list, and the creator of the KDE packages. > > Hi. You could try the kbear packages at > http://people.debian.org/~bab/kde3/ (the full apt-line is in the KDE3 > debian faq). They're built against 3.0.3, not sure whether this will cause > problems, but it's worth a try. > > These kbear packages are running fine on my 3.0.3 system. > > Ben. > > -- > > Ben Burton > [EMAIL PROTECTED] | [EMAIL PROTECTED] > Public Key: finger [EMAIL PROTECTED] > > My songs are like friends. I have a special relationship with my > songs and some of them I always want to have around me. I want to hold > on to them. Others are not always so close to me. They're still friends, > but I don't need to have them around all the time. But they're still my > friends. They're still close to me; they're still my creatures but they > need to go on holiday sometimes. > - Tori Amos - -- 12413AEB2ED4FA5E6F7D78E78BEDE820945092OF923A40EElOE5IOCC98D444AA08E324 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9dsDL4e9YdOpQYMsRApjVAJ930Isw6hhoiqc7Q/FOmvnG7td6BQCfUncp MAmzhtBIrWo8uDl8JQ5j7JM= =DFzh -END PGP SIGNATURE-
Re: Kbear crashes in KDE3.1beta on Debian unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This is whence I get my KOffice debs, and where I'm pulling Kbear from. I guess this is a bug with the 3.1beta1 debs then? Or a system misconfiguration? Rav On Wednesday 04 September 2002 09:10 pm, Ben Burton wrote: > > Kbear crashes upon opening in KDE3.1beta1 on Debian unstable. The > > packages for KDE3.1beta1 I got from > > http://folk.uio.no/johannwi/kde3.1-beta1/, so perhaps this is a bug with > > those packages. I am emailing the maintainer of KBear, the debian-kde > > mailing list, and the creator of the KDE packages. > > Hi. You could try the kbear packages at > http://people.debian.org/~bab/kde3/ (the full apt-line is in the KDE3 > debian faq). They're built against 3.0.3, not sure whether this will cause > problems, but it's worth a try. > > These kbear packages are running fine on my 3.0.3 system. > > Ben. > > -- > > Ben Burton > [EMAIL PROTECTED] | [EMAIL PROTECTED] > Public Key: finger [EMAIL PROTECTED] > > My songs are like friends. I have a special relationship with my > songs and some of them I always want to have around me. I want to hold > on to them. Others are not always so close to me. They're still friends, > but I don't need to have them around all the time. But they're still my > friends. They're still close to me; they're still my creatures but they > need to go on holiday sometimes. > - Tori Amos - -- 12413AEB2ED4FA5E6F7D78E78BEDE820945092OF923A40EElOE5IOCC98D444AA08E324 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9dsBz4e9YdOpQYMsRAh5FAJ4yfTKhbRapUmIAf5P1EGSceh8VNQCgm8E9 3nxIKWPvHDfbE7zlzVpj1jM= =sXmE -END PGP SIGNATURE-
Kbear crashes in KDE3.1beta on Debian unstable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kbear crashes upon opening in KDE3.1beta1 on Debian unstable. The packages for KDE3.1beta1 I got from http://folk.uio.no/johannwi/kde3.1-beta1/, so perhaps this is a bug with those packages. I am emailing the maintainer of KBear, the debian-kde mailing list, and the creator of the KDE packages. Hopefully one of you will be able to comment as to the correct place to file an official bug report. I don't wish to clog anyone's Bugzilla with someone else's bugs. Without further ado: Trying to start Kbear from the command line: [EMAIL PROTECTED]:~$ kbear WARNING: KActionCollection::beginXMLPlug() already called! WARNING: KActionCollection::beginXMLPlug() already called! WARNING: KActionCollection::beginXMLPlug() already called! WARNING: KActionCollection::beginXMLPlug() already called! kdecore (KLibLoader): WARNING: library=libkbearfilesyspart: file=/usr/lib/kde3/libkbearfilesyspart.la: libkjava.so.1: cannot open shared object file: No such file or directory kbear: FATAL: No KBearFileSysPart found ! KCrash: Application 'kbear' crashing... ERROR: KUniqueApplication: DCOP communication error! [EMAIL PROTECTED]:~$ This creates a crash handler instance in KDE: The application KBear (kbear) crashed and caused the signal 6 (SIGABRT). Backtrack: (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)...[New Thread 1024 (LWP 16761)] (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)... 0x40ed8609 in wait4 () from /lib/libc.so.6 #0 0x40ed8609 in wait4 () from /lib/libc.so.6 #1 0x40f4ddd0 in __check_rhosts_file () from /lib/libc.so.6 #2 0x40dbeeeb in waitpid () from /lib/libpthread.so.0 #3 0x406186ac in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4 #4 0x40dbca44 in pthread_sighandler () from /lib/libpthread.so.0 #5 0x40e61518 in sigaction () from /lib/libc.so.6 #6 0x40dbce29 in raise () from /lib/libpthread.so.0 #7 0x40e628d1 in abort () from /lib/libc.so.6 #8 0x405bf560 in kDebugBackend () from /usr/lib/libkdecore.so.4 #9 0x405bf9d3 in kdbgstream::flush () from /usr/lib/libkdecore.so.4 #10 0x4007b813 in endl () from /usr/lib/libkbear.so.2 #11 0x40068183 in KBearMdiChildView::resolveConnection () from /usr/lib/libkbear.so.2 #12 0x40067cf4 in KBearMdiChildView::KBearMdiChildView () from /usr/lib/libkbear.so.2 #13 0x4006a2f6 in KBear::initViewLocal () from /usr/lib/libkbear.so.2 #14 0x40069954 in KBear::KBear () from /usr/lib/libkbear.so.2 #15 0x40069d2e in KBear::self () from /usr/lib/libkbear.so.2 #16 0x0804bafb in QDataStream::~QDataStream () #17 0x4062f4ed in KUniqueApplication::processDelayed () from /usr/lib/libkdecore.so.4 #18 0x4062f83b in KUniqueApplication::qt_invoke () from /usr/lib/libkdecore.so.4 #19 0x0804c12b in QDataStream::~QDataStream () #20 0x4091fb26 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #21 0x40b5a823 in QSignal::signal () from /usr/lib/libqt-mt.so.3 #22 0x409342f5 in QSignal::activate () from /usr/lib/libqt-mt.so.3 #23 0x40939aa3 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3 #24 0x408d8773 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #25 0x408d8614 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #26 0x405af8c4 in KApplication::notify () from /usr/lib/libkdecore.so.4 #27 0x4088985e in qt_activate_timers () from /usr/lib/libqt-mt.so.3 #28 0x4088754c in QApplication::processNextEvent () from /usr/lib/libqt-mt.so.3 #29 0x408d9bbf in QApplication::enter_loop () from /usr/lib/libqt-mt.so.3 #30 0x4088717b in QApplication::exec () from /usr/lib/libqt-mt.so.3 #31 0x0804b83e in QDataStream::~QDataStream () #32 0x40e510bf in __libc_start_main () from /lib/libc.so.6 Again, I hope this all helps,
Re: libkjava library
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I am having the same problem. It is affecting the program Kbear. When opening Kbear from the command line, I get: [EMAIL PROTECTED]:~$ kbear WARNING: KActionCollection::beginXMLPlug() already called! WARNING: KActionCollection::beginXMLPlug() already called! WARNING: KActionCollection::beginXMLPlug() already called! WARNING: KActionCollection::beginXMLPlug() already called! kdecore (KLibLoader): WARNING: library=libkbearfilesyspart: file=/usr/lib/kde3/libkbearfilesyspart.la: libkjava.so.1: cannot open shared object file: No such file or directory kbear: FATAL: No KBearFileSysPart found ! KCrash: Application 'kbear' crashing... ERROR: KUniqueApplication: DCOP communication error! [EMAIL PROTECTED]:~$ Hope this helps in identifying the library in question. I'm running KDE3.1 beta on Debian Sid. Ravenhall On Wednesday 04 September 2002 07:30 am, Zdzislaw A. Kaleta wrote: > In kdelibs3 package is a file libkjava.so.1. > There is no such file in kdelibs4 packages, or at least I can't find it. > This file is used by other programs. Wher I can find it? > > zdzislaw a. kaleta - -- 12413AEB2ED4FA5E6F7D78E78BEDE820945092OF923A40EElOE5IOCC98D444AA08E324 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9dosW4e9YdOpQYMsRAuXtAJ4whyGMNGnSp+6B050gSzV88as7+wCaAnyT Dpf8lx0zjBznRafGmYmz/iI= =vC4E -END PGP SIGNATURE-
Karolina's KDE 3.1-beta debs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all. These debs are SWEET. I just upgraded to them and I am having a BLAST! The new look is even more unbelievable when it's on your own box. Ok, small bug report / howto / warning: My machine is tracking sid/unstable. I first upgraded to KDE 3.03. That only involved a lot of apt-get dist-upgrade - --fix-broken. That's really all that is required for 3.1beta, except for two things: 1) If you are using cups with kde 2.2, you will need to apt-get install kdelibs4-cups (This is probably a bug in the KDE 3.03 debs, but it'd be nice if Karoline's packages looked for it if you have kdelibs3-cups installed. 2) In order to finish installing KOffice, you will have to apt-get remove kspread, which will remove kspread and the 'virtual' koffice package. Then, just do another apt-get dist-upgrade to finish the install, and then apt-get install kspread to get it back. The dpkg error message indicated it was a shared library that was conflicting. Sorry, I don't recall which. Very good job, I am truly happy with the debs and excited about my desktop again! Ravenhall - -- 12413AEB2ED4FA5E6F7D78E78BEDE820945092OF923A40EElOE5IOCC98D444AA08E324 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9cBBW4e9YdOpQYMsRAheoAKCKIppFalOFbwlCJusAGstgWxkpZACgn2Ge Z0qtaOEGNt1kS0slmMvpdT8= =i/vC -END PGP SIGNATURE-
