Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
KDE4 Overlay (Part 3)
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, ... 22, 23, 24  Next  
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
Maguscrowley
n00b
n00b


Joined: 23 Dec 2007
Posts: 12
Location: MD

PostPosted: Sat Dec 29, 2007 5:09 pm    Post subject: Reply with quote

I was adding a news-ticker plasmoid and everything just crashed :( Now the plasma crashes every time I try to start a kde-svn session. Could it be the plasmiod's fault? If so how do I configure what plasmoids or widgits are on my desktop without actually entering the session. I looked under the desktop folder but nothings there. Where does kde4 keep the user configureation for the desktop plasmoids, icons, and widgets?
Here's the relevant portion of the trace. For some reason all the rest says no debuggin symbol found even though I used the debug use flag.

Code:
0xffffe410 in __kernel_vsyscall ()
[Current thread is 0 (LWP 17638)]

Thread 2 (Thread 0xb3c11b90 (LWP 17639)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb72a1825 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb72fa604 in QWaitCondition::wait () from /usr/lib/qt4/libQtCore.so.4
#3  0xb3d04c1a in ?? ()
   from /usr/kde/svn/lib/kde4/plasma_containment_desktop.so
#4  0x08193de0 in ?? ()
#5  0x08193ddc in ?? ()
#6  0xffffffff in ?? ()
#7  0x00000000 in ?? ()

Thread 1 (Thread 0xb56e36f0 (LWP 17638)):
#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb650dac6 in nanosleep () from /lib/libc.so.6
#2  0xb650d8eb in sleep () from /lib/libc.so.6
#3  0xb7a2e833 in ?? () from /usr/kde/svn/lib/libkdeui.so.5
#4  0x00000001 in ?? ()
#5  0x00000000 in ?? ()
#0  0xffffe410 in __kernel_vsyscall ()

This can't possibly be ready for release in 12 days.

timmy334 wrote:

PORTDIR_OVERLAY="/usr/local/layman/xeffects /usr/local/layman/custom-kernels /usr/local/layman/gentoo-de /usr/local/layman/xen /usr/local/layman/rox /usr/local/layman/gnash-cvs /usr/local/layman/kolab /usr/local/layman/postgresql-testing /usr/local/layman/pd-overlay /usr/local/layman/openoffice-geki /usr/local/layman/wrobel /usr/local/layman/enlightenment /usr/local/layman/drizzt-overlay /usr/local/layman/mpd /usr/local/layman/live-ebuilds /usr/local/layman/zugaina /usr/local/layman/wschlich-testing /usr/local/layman/voip /usr/local/layman/d /usr/local/layman/finnish /usr/local/layman/secondlife /usr/local/layman/chtekk-syscp /usr/local/layman/xwing /usr/local/layman/jokey /usr/local/layman/java-overlay /usr/local/layman/dirtyepic /usr/local/layman/kde /usr/local/layman/vdr-testing /usr/local/layman/vmware /usr/local/layman/halcy0n /usr/local/layman/je_fro /usr/local/layman/cell /usr/local/layman/trauma /usr/local/layman/verlihub /usr/local/layman/wolf31o2 /usr/local/layman/powerpc /usr/local/layman/java-gcj-overlay /usr/local/layman/gentoo-taiwan /usr/local/layman/musicbrainz /usr/local/layman/toolchain /usr/local/layman/einit /usr/local/layman/lapis /usr/local/layman/gentoo-china /usr/local/layman/iwlwifi /usr/local/layman/gnome-experimental /usr/local/layman/sipx /usr/local/layman/gentopia /usr/local/layman/xfce /usr/local/layman/pda /usr/local/layman/masterdriverz /usr/local/layman/berkano /usr/local/layman/marineam-xen /usr/local/layman/hollow /usr/local/layman/armagetron /usr/local/layman/flameeyes-overlay /usr/local/layman/n4g-experimental /usr/local/layman/n4g /usr/local/layman/initng /usr/local/layman/dertobi123 /usr/local/layman/emacs /usr/local/layman/vdr-1.5 /usr/local/layman/voyageur /usr/local/layman/php-experimental /usr/local/layman/dev-zero /usr/local/layman/deathwing00 /usr/local/layman/vps /usr/local/layman/mozilla /usr/local/layman/efika /usr/local/layman/trapni /usr/local/layman/webapps-experimental /usr/local/layman/dma147 /usr/local/layman/science /usr/local/layman/rbu /usr/local/layman/eclipse /usr/local/layman/pro-audio /usr/local/layman/seemant /usr/local/layman/vdr-experimental /usr/local/layman/pythonhead /usr/local/layman/genstef /usr/local/layman/wschlich /usr/local/layman/ffmpeg-svn /usr/local/layman/plan9 /usr/local/layman/freevo /usr/local/layman/mysql-experimental /usr/local/layman/php-testing /usr/local/layman/ecatmur /usr/local/layman/chtekk-apps /usr/local/layman/postgresql-experimental /usr/local/layman/bangert /usr/local/layman/suka /usr/local/layman/luke-jr /usr/local/layman/nx /usr/local/layman/sunrise /usr/local/layman/xemacs /usr/local/layman/philantrop /usr/local/layman/pioto-overlay /usr/local/layman/sabayon /usr/local/layman/aross /usr/local/layman/lu_zero /usr/local/layman/mysql-testing /usr/local/layman/liquidx /usr/local/layman/lila-theme /usr/local/layman/gnustep /usr/local/layman/swegener /usr/local/layman/hanno-xgl /usr/local/portage /usr/local/layman/xeffects /usr/local/layman/custom-kernels"


Holy hell that's a lot of overlays.
_________________
"Does wisdom perhaps appear on earth as a raven is inspired by the smell of carrion." -Friedrich Nietzsche, Twilight of the Idols (1889)
Back to top
View user's profile Send private message
timmy334
n00b
n00b


Joined: 24 Sep 2003
Posts: 69
Location: Montgomery, AL

PostPosted: Sat Dec 29, 2007 5:46 pm    Post subject: Reply with quote

Yes, it's a lot of overlays. I did the big layman -a ALL command. I don't know how to use half of them properly, but I like to be adventurous with my linux :lol:
_________________
It is by caffeine alone I set my mind in motion,
It is by the beans of Java my thoughts acquire speed,
My hands acquire shaking, the shaking becomes a warning,
It is by caffeine alone I set my mind in motion
Back to top
View user's profile Send private message
Apetrini
Veteran
Veteran


Joined: 09 Feb 2005
Posts: 1158

PostPosted: Sat Dec 29, 2007 5:54 pm    Post subject: Reply with quote

Hi,
I have some problems to emerge some packets. For example:
kdepimlibs,amarok.
The problem is the fetching...

Code:

>>> Emerging (1 of 1) kde-base/kdepimlibs-9999.4 to /
 * checking ebuild checksums ;-) ...                                             [ ok ]
 * checking auxfile checksums ;-) ...                                            [ ok ]
 * checking miscfile checksums ;-) ...                                           [ ok ]

 * WARNING! This is an experimental ebuild of the kdepimlibs KDE4 SVN tree.
 * Use at your own risk. Do _NOT_ file bugs at bugs.gentoo.org because
 * of this ebuild!

>>> Unpacking source...
 * subversion update start -->
 *      repository: svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs
svn: La connessione di rete � stata improvvisamente chiusa
 *
 * ERROR: kde-base/kdepimlibs-9999.4 failed.
 * Call stack:
 *               ebuild.sh, line   46:  Called src_unpack
 *             environment, line 2531:  Called kde4svn_src_unpack
 *             environment, line 1948:  Called subversion_src_unpack
 *             environment, line 2739:  Called subversion_fetch
 *             environment, line 2727:  Called die
 * The specific snippet of code:
 *           ${ESVN_UPDATE_CMD} ${options} || diefunc "$FUNCNAME" "$LINENO" "$?" "${ESVN}: can't update from ${repo_uri}.";
 *  The die message:
 *   subversion.eclass: can't update from svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs.
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/kde-base/kdepimlibs-9999.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/kde-base/kdepimlibs-9999.4/temp/environment'.
 *

 * Messages for package kde-base/kdepimlibs-9999.4:

 * WARNING! This is an experimental ebuild of the kdepimlibs KDE4 SVN tree.
 * Use at your own risk. Do _NOT_ file bugs at bugs.gentoo.org because
 * of this ebuild!
 *
 * ERROR: kde-base/kdepimlibs-9999.4 failed.
 * Call stack:
 *               ebuild.sh, line   46:  Called src_unpack
 *             environment, line 2531:  Called kde4svn_src_unpack
 *             environment, line 1948:  Called subversion_src_unpack
 *             environment, line 2739:  Called subversion_fetch
 *             environment, line 2727:  Called die
 * The specific snippet of code:
 *           ${ESVN_UPDATE_CMD} ${options} || diefunc "$FUNCNAME" "$LINENO" "$?" "${ESVN}: can't update from ${repo_uri}.";
 *  The die message:
 *   subversion.eclass: can't update from svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs.
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/kde-base/kdepimlibs-9999.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/kde-base/kdepimlibs-9999.4/temp/environment'.
 *


svn: La connessione di rete � stata improvvisamente chiusa ------> svn: the connection closed unexpectedly.

If I try to download it from svn manually, in a fresh directory with
Code:
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs

I get the same error(but not immediately)!!
Code:

localhost pim # svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs
A    kdepimlibs/kxmlrpcclient
A    kdepimlibs/kxmlrpcclient/client.cpp
A    kdepimlibs/kxmlrpcclient/Messages.sh
A    kdepimlibs/kxmlrpcclient/tests
...
...
A    kdepimlibs/syndication/rss2/textinput.h
A    kdepimlibs/syndication/rss2/cloud.h
A    kdepimlibs/syndication/rss2/category.cpp
A    kdepimlibs/syndication/rss2/document.cpp
A    kdepimlibs/syndication/rss2/tools_p.cpp
A    kdepimlibs/syndication/rss2/image.cpp
A    kdepimlibs/syndication/rss2/category.h
A    kdepimlibs/syndication/rss2/document.h
svn: La connessione di rete � stata improvvisamente chiusa

The connection closed always after the same file.

It's a very strange problem. Also because many other packets(as kdebase, kdelibs, kdemultimedia, kdegrapgics etc..) fetchs without problems.

Someone can help me?

Thanks!!
_________________
Linux ape 2.6.31-vanilla. Paludis since 0.28.0.
Back to top
View user's profile Send private message
Maguscrowley
n00b
n00b


Joined: 23 Dec 2007
Posts: 12
Location: MD

PostPosted: Sat Dec 29, 2007 5:59 pm    Post subject: Reply with quote

I went to #plasma and asked them, in the most humble manner possible, where they keep the configuration files for plasma pertaining to a users desktop widgets. They told me it's in $KDEHOME/share/config/plasma but I couldn't find it, and I didn't want to bug them too much, so I'm going to just emerge -C everything from the svn and try emerging from the meta and log the entire emerge so I can see where everything is going for each ebuild.
_________________
"Does wisdom perhaps appear on earth as a raven is inspired by the smell of carrion." -Friedrich Nietzsche, Twilight of the Idols (1889)
Back to top
View user's profile Send private message
Ingmarv
Retired Dev
Retired Dev


Joined: 27 Feb 2007
Posts: 188
Location: Belgium

PostPosted: Sat Dec 29, 2007 8:33 pm    Post subject: Reply with quote

Maguscrowley wrote:
I went to #plasma and asked them, in the most humble manner possible, where they keep the configuration files for plasma pertaining to a users desktop widgets. They told me it's in $KDEHOME/share/config/plasma but I couldn't find it, and I didn't want to bug them too much, so I'm going to just emerge -C everything from the svn and try emerging from the meta and log the entire emerge so I can see where everything is going for each ebuild.


That's correct.
However, gentoo doesn't set or use $KDEHOME. For the live ebuilds, it's "$HOME/.kdesvn", for RC2 it's under "$HOME/.kde3.9".
Note that the ebuilds don't touch those files at all, they get created when you run KDE. You can just delete that file and restart plasma if you want the defaults back.

You're welcome in #genkdesvn too. :D
Back to top
View user's profile Send private message
titoucha
Advocate
Advocate


Joined: 21 Jul 2005
Posts: 2374
Location: Genève

PostPosted: Sun Dec 30, 2007 4:46 am    Post subject: Reply with quote

Maguscrowley wrote:

This can't possibly be ready for release in 12 days.


That's right, it's too many buggs
_________________
Assurez-vous que le titre de votre message soit conforme aux conventions de ce forum (paragraphe 3/3 : Comment poster sur le forum ??)
Back to top
View user's profile Send private message
lekter
n00b
n00b


Joined: 19 Sep 2003
Posts: 12

PostPosted: Sun Dec 30, 2007 3:44 pm    Post subject: Reply with quote

titoucha wrote:
Maguscrowley wrote:

This can't possibly be ready for release in 12 days.


That's right, it's too many buggs


I have been using kde4 apps to do real work (dolphin, okular, konqueror, ...) along with a 3.5.8 desktop and everything seems quite stable (only minor bugs).

The problem comes when you try to use plasma, which seems rather unfinished compared with the rest of kde4 apps. Being Plasma one of the key technologies in KDE4, I wouldn't mind if they get another 20 or 30 days to finish it and release the whole KDE4 somewhere around february.
_________________
Fernando Monera Daroqui
fmonera at opensistemas dot com
http://www.opensistemas.com
Back to top
View user's profile Send private message
Finswimmer
Moderator
Moderator


Joined: 02 Sep 2004
Posts: 5467
Location: Langen (Hessen), Germany

PostPosted: Sun Dec 30, 2007 3:59 pm    Post subject: Reply with quote

Okular does not allow me to put more than one file in it.
So there is no possibility to make a slideshow for e.g. 50 pictures.

Am I the only one?

Tobi
_________________
Bitte auf Rechtschreibung, korrekte Formatierung und Höflichkeit achten!
Danke
Back to top
View user's profile Send private message
smorg
n00b
n00b


Joined: 03 Apr 2006
Posts: 40
Location: Germany

PostPosted: Sun Dec 30, 2007 4:20 pm    Post subject: Reply with quote

Maguscrowley wrote:

This can't possibly be ready for release in 12 days.


In order to be released on time it has to be ready in 5 days (January 4th). The last week is needed for packaging and preparing the release. See http://techbase.kde.org/index.php?title=Schedules/KDE4/4.0_Release_Schedule
Back to top
View user's profile Send private message
lekter
n00b
n00b


Joined: 19 Sep 2003
Posts: 12

PostPosted: Sun Dec 30, 2007 8:19 pm    Post subject: Reply with quote

Finswimmer wrote:
Okular does not allow me to put more than one file in it.
So there is no possibility to make a slideshow for e.g. 50 pictures.

Am I the only one?

Tobi


Hmmm, was Okular able to do that in the past?
_________________
Fernando Monera Daroqui
fmonera at opensistemas dot com
http://www.opensistemas.com
Back to top
View user's profile Send private message
Finswimmer
Moderator
Moderator


Joined: 02 Sep 2004
Posts: 5467
Location: Langen (Hessen), Germany

PostPosted: Sun Dec 30, 2007 9:05 pm    Post subject: Reply with quote

lekter wrote:
Finswimmer wrote:
Okular does not allow me to put more than one file in it.
So there is no possibility to make a slideshow for e.g. 50 pictures.

Am I the only one?

Tobi


Hmmm, was Okular able to do that in the past?


Never used it before.
But it should be the replacement for kuickshow...and kuickshow was able to browse through a directory...

Tobi
_________________
Bitte auf Rechtschreibung, korrekte Formatierung und Höflichkeit achten!
Danke
Back to top
View user's profile Send private message
Nemonux
n00b
n00b


Joined: 27 Nov 2004
Posts: 19
Location: Aachen, Germany

PostPosted: Sun Dec 30, 2007 9:26 pm    Post subject: Reply with quote

Finswimmer wrote:
lekter wrote:
Finswimmer wrote:
Okular does not allow me to put more than one file in it.
So there is no possibility to make a slideshow for e.g. 50 pictures.

Am I the only one?

Tobi


Hmmm, was Okular able to do that in the past?


Never used it before.
But it should be the replacement for kuickshow...and kuickshow was able to browse through a directory...

Tobi



Well I think Okular is a documentreader and shall replace kpdf, kdvi, kghostview etc.
Gwenview is supposed to be the new imagebrowser :-)
_________________
A rainy day in May...
Back to top
View user's profile Send private message
Berniyh
l33t
l33t


Joined: 07 Jun 2006
Posts: 677

PostPosted: Sun Dec 30, 2007 10:05 pm    Post subject: Reply with quote

Finswimmer wrote:
lekter wrote:
Finswimmer wrote:
Okular does not allow me to put more than one file in it.
So there is no possibility to make a slideshow for e.g. 50 pictures.

Am I the only one?

Tobi


Hmmm, was Okular able to do that in the past?


Never used it before.
But it should be the replacement for kuickshow...and kuickshow was able to browse through a directory...

Tobi

There will be kuickshow for KDE4, it is already in the repos and I already thought about making an ebuild for it, but didn't do so yet, because there doesn't seem anything going on in that repo. ;)

http://websvn.kde.org/trunk/extragear/graphics/kuickshow/
Back to top
View user's profile Send private message
Maguscrowley
n00b
n00b


Joined: 23 Dec 2007
Posts: 12
Location: MD

PostPosted: Mon Dec 31, 2007 6:42 am    Post subject: Reply with quote

I went into systemsettings and went into the screen configuration and most of the panal dissipeared leaving the settings window and a few of the widgets that were previously attached to it. When I logged out and back in the background was only half there with no panel. Is this already filed as a bug?
_________________
"Does wisdom perhaps appear on earth as a raven is inspired by the smell of carrion." -Friedrich Nietzsche, Twilight of the Idols (1889)
Back to top
View user's profile Send private message
Qlawy
Apprentice
Apprentice


Joined: 11 Jul 2006
Posts: 200

PostPosted: Mon Dec 31, 2007 3:47 pm    Post subject: Reply with quote

I cant compile systemsettings-3.97.0 and krunner-3.97.0 it seems to be a problem with kscreensaver but they were compiled and installed without errors :/
I cant find a reason of this issue :(

SystemSettings
Code:
Scanning dependencies of target kcm_screensaver
[ 70%] Building CXX object kcontrol/screensaver/CMakeFiles/kcm_screensaver.dir/kcm_screensaver_automoc.o
[ 70%] Building CXX object kcontrol/screensaver/CMakeFiles/kcm_screensaver.dir/scrnsave.o
[ 71%] Building CXX object kcontrol/screensaver/CMakeFiles/kcm_screensaver.dir/testwin.o
[ 71%] Building CXX object kcontrol/screensaver/CMakeFiles/kcm_screensaver.dir/saverlist.o
[ 71%] Building CXX object kcontrol/screensaver/CMakeFiles/kcm_screensaver.dir/saverconfig.o
[ 72%] Building CXX object kcontrol/screensaver/CMakeFiles/kcm_screensaver.dir/advanceddialog.o
[ 72%] Building CXX object kcontrol/screensaver/CMakeFiles/kcm_screensaver.dir/kswidget.o
[ 72%] Building CXX object kcontrol/screensaver/CMakeFiles/kcm_screensaver.dir/kscreensaver_interface.o
Linking CXX shared module ../../lib/kcm_screensaver.so
CMakeFiles/kcm_screensaver.dir/kswidget.o: In function `KSWidget::KSWidget(QWidget*, QFlags<Qt::WindowType>)':
kswidget.cpp:(.text+0x2e2): undefined reference to `glXChooseVisual'
CMakeFiles/kcm_screensaver.dir/kswidget.o: In function `KSWidget::KSWidget(QWidget*, QFlags<Qt::WindowType>)':
kswidget.cpp:(.text+0x582): undefined reference to `glXChooseVisual'
collect2: ld returned 1 exit status
make[2]: *** [lib/kcm_screensaver.so] Error 1
make[1]: *** [kcontrol/screensaver/CMakeFiles/kcm_screensaver.dir/all] Error 2
make: *** [all] Error 2
*
* ERROR: kde-base/systemsettings-3.97.0 failed.
* Call stack:
*              ebuild.sh, line  46:  Called src_compile
*            environment, line 2708:  Called kde4-meta_src_compile
*            environment, line 1987:  Called kde4-meta_src_make


krunner
Code:
[ 88%] Building CXX object krunner/lock/CMakeFiles/krunner_lock.dir/lockdlg.o
[ 90%] Building CXX object krunner/lock/CMakeFiles/krunner_lock.dir/autologout.o
[ 92%] Building CXX object krunner/lock/CMakeFiles/krunner_lock.dir/main.o
[ 94%] Building CXX object krunner/lock/CMakeFiles/krunner_lock.dir/ksmserver_interface.o
[ 96%] Building CXX object krunner/lock/CMakeFiles/krunner_lock.dir/kscreensaver_interface.o
[ 98%] Building CXX object krunner/lock/CMakeFiles/krunner_lock.dir/kxkb_interface.o
[100%] Building CXX object krunner/lock/CMakeFiles/krunner_lock.dir/kscreensaversettings.o
Linking CXX executable krunner_lock
CMakeFiles/krunner_lock.dir/lockprocess.o: In function `LockProcess::createSaverWindow()':
lockprocess.cc:(.text+0x3b13): undefined reference to `glXChooseVisual'
collect2: ld returned 1 exit status
make[2]: *** [krunner/lock/krunner_lock] Error 1
make[1]: *** [krunner/lock/CMakeFiles/krunner_lock.dir/all] Error 2
make: *** [all] Error 2
*
* ERROR: kde-base/krunner-3.97.0 failed.
* Call stack:
*              ebuild.sh, line  46:  Called src_compile
*            environment, line 2716:  Called kde4-meta_src_compile
*            environment, line 1998:  Called kde4-meta_src_make
*            environment, line 2105:  Called kde4-base_src_make
*            environment, line 1919:  Called cmake-utils_src_make
*            environment, line  699:  Called die
* The specific snippet of code:
*          emake "$@" || diefunc "$FUNCNAME" "$LINENO" "$?" "Make failed!";
*  The die message:
*  Make failed!
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/kde-base/krunner-3.97.0/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/kde-base/krunner-3.97.0/temp/environment'.
* This ebuild used the following eclasses from overlays:
*  /usr/portage/local/layman/kde/eclass/kde4-meta.eclass
*  /usr/portage/local/layman/kde/eclass/kde4-functions.eclass
*  /usr/portage/local/layman/kde/eclass/kde4-base.eclass


EDIT:
I decided to wait for oficial release :?


Last edited by Qlawy on Mon Dec 31, 2007 5:03 pm; edited 1 time in total
Back to top
View user's profile Send private message
wrc1944
Advocate
Advocate


Joined: 15 Aug 2002
Posts: 3271
Location: Gainesville, Florida

PostPosted: Mon Dec 31, 2007 3:52 pm    Post subject: Reply with quote

After being away on Xmas vacation for 10 days, I just completed an update on my kde-svn box. The difference is really impressive- everything I use compiled with no problems (used the tips found here). Among other things, I can finally get my preferred 1280x1024 @75Hz monitor setting, and File manager- Super User Mode now works. Haven't really got into trying each app/feature yet, but this is really coming along great! My compliments and thanks to the maintainers and others who help with this overlay. :D

Here's a list of what I normally use for a monolithic kde installation, and the revisions I got last night from svn.
Quote:
kdelibs 754856
kdebase 754729
kdepimlibs 754982
kdeadmin 754987
kdepim 754990
kdegraphics 754995
kdeartwork 754996
kdemultimedia 754996
kdenetwork 754997
kdeutils 755000

BTW, on my other kde4 box using 3.97 split ebuilds, I previously found I couldn't omit ANY package from any of the groups, or else I couldn't compile. In other words, you had to take all the split ebuilds, or compiling was apparently blocked. Is this just me, or has anyone else experienced this, and at this point in kde4 development is this to be expected?

EDIT: Hmmm... 1280x1024 @75Hz monitor setting didn't survive reboot- reverts to 1024x768 @60Hz, even though "apply to kde at startup" box is checked.

Emerged konq-plugins and extragear-plasma OK (with debug and opengl USE Flags).
I read where dolphin is supposed to have a "open as root" button, but I can't seem to find it. :?:
_________________
Main box- AsRock x370 Gaming K4
Ryzen 1700, 3.0GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
Gentoo ~amd64 plasma, glibc-2.30-r2, gcc-9.2.0 kernel-5.4.1-gentoo USE=experimental


Last edited by wrc1944 on Mon Dec 31, 2007 8:36 pm; edited 1 time in total
Back to top
View user's profile Send private message
kavol
n00b
n00b


Joined: 31 Aug 2005
Posts: 57
Location: .cz

PostPosted: Mon Dec 31, 2007 6:44 pm    Post subject: Reply with quote

Maguscrowley wrote:
For some reason all the rest says no debuggin symbol found even though I used the debug use flag.


did you set FEATURES splitdebug or nostrip? - see How to get meaningful backtraces in Gentoo
Back to top
View user's profile Send private message
kavol
n00b
n00b


Joined: 31 Aug 2005
Posts: 57
Location: .cz

PostPosted: Mon Dec 31, 2007 6:59 pm    Post subject: Reply with quote

lekter wrote:
titoucha wrote:
Maguscrowley wrote:

This can't possibly be ready for release in 12 days.


That's right, it's too many buggs


....

The problem comes when you try to use plasma, which seems rather unfinished compared with the rest of kde4 apps.


oh well, we are told this every here and there that it is just plasma and the rest is fine, but ... have they already fixed bug #153582, bug #153693, bug #153929 and a lot of others which are not plasma related? (note that I have not recompiled from svn recently so I cannot try, maybe it is fixed ... but I do not believe that "it's just plasma")

lekter wrote:
Being Plasma one of the key technologies in KDE4, I wouldn't mind if they get another 20 or 30 days to finish it and release the whole KDE4 somewhere around february.


I guess a few months would be better ... but they won't do that, the train is already running and nobody is going to stop it :-/
Back to top
View user's profile Send private message
Maguscrowley
n00b
n00b


Joined: 23 Dec 2007
Posts: 12
Location: MD

PostPosted: Tue Jan 01, 2008 8:08 am    Post subject: Reply with quote

kavol wrote:
Maguscrowley wrote:
For some reason all the rest says no debuggin symbol found even though I used the debug use flag.


did you set FEATURES splitdebug or nostrip? - see How to get meaningful backtraces in Gentoo


Thanks, that guide helps a lot.
_________________
"Does wisdom perhaps appear on earth as a raven is inspired by the smell of carrion." -Friedrich Nietzsche, Twilight of the Idols (1889)
Back to top
View user's profile Send private message
Jakub
Guru
Guru


Joined: 04 Oct 2003
Posts: 377
Location: Warsaw, Poland

PostPosted: Tue Jan 01, 2008 3:38 pm    Post subject: Reply with quote

I have some trouble updating kdepimlibs from svn...:
Code:
>>> Emerging (1 of 14) kde-base/kdepimlibs-9999.4 to /
>>> Creating Manifest for /usr/portage/local/layman/kde/kde-base/kdepimlibs
  digest.assumed                 1
   digest-kdepimlibs-3.97.0::kdepimlibs-3.97.0.tar.bz2
 * checking ebuild checksums ;-) ...                                                                                                    [ ok ]
 * checking auxfile checksums ;-) ...                                                                                                   [ ok ]
 * checking miscfile checksums ;-) ...                                                                                                  [ ok ]

 * WARNING! This is an experimental ebuild of the kdepimlibs KDE4 SVN tree.
 * Use at your own risk. Do _NOT_ file bugs at bugs.gentoo.org because
 * of this ebuild!

>>> Unpacking source...
 * subversion update start -->
 *      repository: svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs
svn: Connection closed unexpectedly
 *
 * ERROR: kde-base/kdepimlibs-9999.4 failed.
 * Call stack:
 *               ebuild.sh, line   46:  Called src_unpack
 *             environment, line 2584:  Called kde4svn_src_unpack
 *             environment, line 1992:  Called subversion_src_unpack
 *             environment, line 2792:  Called subversion_fetch
 *             environment, line 2780:  Called die
 * The specific snippet of code:
 *           ${ESVN_UPDATE_CMD} ${options} || diefunc "$FUNCNAME" "$LINENO" "$?" "${ESVN}: can't update from ${repo_uri}.";
 *  The die message:
 *   subversion.eclass: can't update from svn://anonsvn.kde.org/home/kde/trunk/KDE/kdepimlibs.
 *
 * If you need support, post the topmost build error, and the call stack if relevant.
 * A complete build log is located at '/var/tmp/portage/kde-base/kdepimlibs-9999.4/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/kde-base/kdepimlibs-9999.4/temp/environment'.
Back to top
View user's profile Send private message
Berniyh
l33t
l33t


Joined: 07 Jun 2006
Posts: 677

PostPosted: Tue Jan 01, 2008 5:41 pm    Post subject: Reply with quote

I think that is just KDE's anonsvn, that once again can't cope with the load of users using it.
If that is the case just try later.
I had that from time to time, but it was always temporary.

But it could also possible, that you ran into the same problem I had and which I worked around by doing:
Code:
cd $DISTFILES/svn-src/KDE/kdepimlibs
rm -fr kdepimlibs
svn co svn://websvn.kde.org/home/kde/trunk/KDE/kdepimlibs
find kdepimlibs -path "*.svn*" -name "entries" -exec sed -i -e 's%svn://websvn.kde.org%svn://anonsvn.kde.org%' "{}" ";"

anonsvn seems to have some problems from time to time.
If you do not change websvn -> anonsvn you will run into problems with the ebuilds.
Of course replace $DISTFILES. ;)
Back to top
View user's profile Send private message
orgoz
n00b
n00b


Joined: 15 Nov 2006
Posts: 48

PostPosted: Tue Jan 01, 2008 6:43 pm    Post subject: Reply with quote

I didn't found the digikam-0.10.0-svn ebuild. Could anyone send me a link please ?
Thanks.
Back to top
View user's profile Send private message
Jakub
Guru
Guru


Joined: 04 Oct 2003
Posts: 377
Location: Warsaw, Poland

PostPosted: Tue Jan 01, 2008 6:47 pm    Post subject: Reply with quote

Thanks a lot, your instructions worked :)
Back to top
View user's profile Send private message
brumgabrasch
n00b
n00b


Joined: 01 Jan 2008
Posts: 7

PostPosted: Tue Jan 01, 2008 10:59 pm    Post subject: Reply with quote

I tried to rename the i18l ebuild wich was posted earlier in this thread, unfortunately I get this error:
Quote:

>>> Unpacking source...
/usr/portage/local/layman/kde/kde-base/kde-l10n/kde-l10n-9999.4.ebuild: line 48: kde4svn_src_unpack: command not found
/usr/portage/local/layman/kde/kde-base/kde-l10n/kde-l10n-9999.4.ebuild: line 53: kde4svn_src_unpack: command not found
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/kde-base/kde-l10n-9999.4 ...
/usr/portage/local/layman/kde/kde-base/kde-l10n/kde-l10n-9999.4.ebuild: line 59: ./scripts/autogen.sh: No such file or directory
/usr/portage/local/layman/kde/kde-base/kde-l10n/kde-l10n-9999.4.ebuild: line 60: cd: de: No such file or directory
CMake Error: The source directory "/var/tmp/portage/kde-base/kde-l10n-9999.4/work" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
make: *** No targets specified and no makefile found. Stop.


it would be great if somebody could quick post a working kde-l10n-9999.4 ebuild!
Back to top
View user's profile Send private message
Berniyh
l33t
l33t


Joined: 07 Jun 2006
Posts: 677

PostPosted: Tue Jan 01, 2008 11:06 pm    Post subject: Reply with quote

orgoz wrote:
I didn't found the digikam-0.10.0-svn ebuild. Could anyone send me a link please ?
Thanks.


brumgabrasch wrote:
I tried to rename the i18l ebuild wich was posted earlier in this thread, unfortunately I get this error:
Quote:

>>> Unpacking source...
/usr/portage/local/layman/kde/kde-base/kde-l10n/kde-l10n-9999.4.ebuild: line 48: kde4svn_src_unpack: command not found
/usr/portage/local/layman/kde/kde-base/kde-l10n/kde-l10n-9999.4.ebuild: line 53: kde4svn_src_unpack: command not found
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/kde-base/kde-l10n-9999.4 ...
/usr/portage/local/layman/kde/kde-base/kde-l10n/kde-l10n-9999.4.ebuild: line 59: ./scripts/autogen.sh: No such file or directory
/usr/portage/local/layman/kde/kde-base/kde-l10n/kde-l10n-9999.4.ebuild: line 60: cd: de: No such file or directory
CMake Error: The source directory "/var/tmp/portage/kde-base/kde-l10n-9999.4/work" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
make: *** No targets specified and no makefile found. Stop.


it would be great if somebody could quick post a working kde-l10n-9999.4 ebuild!

Install git and do:
Code:
git clone git://bandi.homelinux.com/kde4-additional

Although I didn't try kde-l10n lately, normally it fails, because there is so much movement in that one.
I fixed de locale once, but I guess it broke again. ;)
If I remember correctly 2 out of 10 langs I tried two weeks ago worked, all the other ones failed.
Back to top
View user's profile Send private message
Display posts from previous:   
This topic is locked: you cannot edit posts or make replies.    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3, ... 22, 23, 24  Next
Page 2 of 24

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum