Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 104376 - kdevelop-3.2.2 error on first startup, invalid/unreadable project path
Summary: kdevelop-3.2.2 error on first startup, invalid/unreadable project path
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: AMD64 Linux
: High minor (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-31 06:03 UTC by Chris Torske
Modified: 2005-09-20 02:18 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Torske 2005-08-31 06:03:55 UTC
When Kdevelop was updated from 3.1.2 to 3.2.2, kdevelop gives a startup error
complaining it can not access the old project path  (that was deleted long time
ago); even though there was no projects open to begin with.

Reproducible: Always
Steps to Reproduce:
1.  Emerge kdevelop 3.1.2
2.  Make a project in kdevelop
3.  Exit out and remove the project directories and files.
4.  Emerge kdevelop 3.2.2
5.  Start kdevelop back up.

Actual Results:  
Error message on startup; complaining it can't access the last project's directory.

Expected Results:  
Start up with no errors, with no projects open.

Portage 2.0.51.22-r2 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r1,
2.6.11-gentoo-r11 x86_64)
=================================================================
System uname: 2.6.11-gentoo-r11 x86_64 AMD Athlon(tm) 64 Processor 3200+
Gentoo Base System version 1.6.13
dev-lang/python:     2.3.5
sys-apps/sandbox:    1.2.11
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6
sys-devel/binutils:  2.15.92.0.2-r10
sys-devel/libtool:   1.5.18-r1
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=k8"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/lib64/mozilla/defaults/pref /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=k8"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig distlocks sandbox sfperms strict"
GENTOO_MIRRORS="http://gentoo.osuosl.org/"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.us.gentoo.org/gentoo-portage"
USE="amd64 X a52 alsa avi bash-completion berkdb bitmap-fonts bzip2 cdr crypt
cups curl doc dvd eds encode esd fam flac foomaticdb fortran gd gdbm gif gnome
gpm gstreamer gtk gtk2 hal imagemagick imlib ipv6 java jpeg junit kde kerberos
libwww lzw lzw-tiff mad motif mozilla mp3 mpeg ncurses nls nvidia ogg oggvorbis
opengl oss pam pdflib perl plotutils png python qt quicktime readline ruby sdl
spell ssl tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts usb
userlocales vorbis xml2 xpm xv zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTDIR_OVERLAY
Comment 1 Marcus D. Hanwell (RETIRED) gentoo-dev 2005-09-02 06:39:30 UTC
Does it still give that error on subsequent start up of kdevelop after the first
time?
Comment 2 Chris Torske 2005-09-02 12:12:19 UTC
Yes, it keeps coming up with the same error message, until you make a project in
the new version.  After the new project, there isn't any startup error messages
afterwards.
Comment 3 Thomas Fischer 2005-09-14 06:11:50 UTC
Can you still reproduce this bug? Please check out 
~/.kde/share/config/kdeveloprc and report any line referring to your old 
project. 
Additionally, try to disable Configure KDevelop -> General -> Load last 
project on startup. 
Otherwise, it looks like a KDevelop bug for me. Maybe you want to report it to 
the KDE bug system? 
Comment 4 Chris Torske 2005-09-14 06:24:52 UTC
I'll see about recompiling kdevelop again, see if it still gives me the error or
not.  Most likly be a few days till I can do that, as I am not having any free
time right now.
Comment 5 Gregorio Guidi (RETIRED) gentoo-dev 2005-09-20 02:18:14 UTC
There are already similar bugs reported at bugs.kde.org: 
http://bugs.kde.org/show_bug.cgi?id=89267 
http://bugs.kde.org/show_bug.cgi?id=109514 
 
I suggest to comment there or to open a new one.