You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Friday, April 7th 2006, 8:55am

[KOPETE] 0.12 beta2 won't start

Hi,

I'm running KDE 3.3.2 on a Debian Sarge machine and downloaded kopete 0.12 beta2 yesterday. Configuring the source runs without any problems, it just tells me at the end that it can't find the xmms libs which would be required for kopete to talk to xmms. That doesn't bother me since I don't want to use this feature.
Anyway, when running make there are a lot of warnings concerning a videodevice. The message is always the same: "'Visibilty' attribute does not apply to types." I tried make install to see what happens and the same warnings occured. Now if I click on the Kopete entry in the KDE Menu it tries to start kopete but fails without any error messages, so basically it cannot run kopete and I don't know why.
I don't have a webcam installed so I have no clue what videodevice it possibly means.

Does anyone here know how to solve this problem? Otherwise I would have to go back and use kopete 0.9 or gaim.

Red M&M

bram85

Professional

Posts: 948

Location: Eindhoven

Occupation: Software Engineer

  • Send private message

2

Friday, April 7th 2006, 10:06am

RE: [KOPETE] 0.12 beta2 won't start

And when you run Kopete from the console? Does it say anything useful?
Bram Schoenmakers
KDE Netherlands (www.kde.nl)

3

Friday, April 7th 2006, 11:32am

Yeah there was something but I don't remember exactly what is was.
I'm at work right now and cannot check it until tonight. I'll let you know as soon as I get home.

4

Friday, April 7th 2006, 4:11pm

So here is what is says when I try to run kopete from konsole:

Source code

1
2
kopete: relocation error: kopete: undefined symbol: _ZN17KopeteContactList11contactListEv
kopete: ERROR: Communication problem with kopete, it probably crashed.



while running make these are the warnings I get:

Source code

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
In file included from videodevice.cpp:26:
videoinput.h:77: warning: `visibility' attribute does not apply to types
videodevice.cpp: In member function `int
   Kopete::AV::VideoDevice::selectInput(int)':
videodevice.cpp:752: warning: comparison between signed and unsigned integer
   expressions
videodevice.cpp: In member function `int
   Kopete::AV::VideoDevice::setInputParameters()':
videodevice.cpp:798: warning: comparison between signed and unsigned integer
   expressions
videodevice.cpp: In member function `float
   Kopete::AV::VideoDevice::setBrightness(float)':
videodevice.cpp:1314: warning: converting to `short unsigned int' from `float'
videodevice.cpp: In member function `float
   Kopete::AV::VideoDevice::setContrast(float)':
videodevice.cpp:1349: warning: converting to `short unsigned int' from `float'
videodevice.cpp: In member function `float
   Kopete::AV::VideoDevice::setSaturation(float)':
videodevice.cpp:1384: warning: converting to `short unsigned int' from `float'
videodevice.cpp: In member function `float
   Kopete::AV::VideoDevice::setWhiteness(float)':
videodevice.cpp:1419: warning: converting to `short unsigned int' from `float'
videodevice.cpp: In member function `float
   Kopete::AV::VideoDevice::setHue(float)':
videodevice.cpp:1454: warning: converting to `short unsigned int' from `float'
videodevice.cpp: In member function `long long unsigned int
   Kopete::AV::VideoDevice::signalStandardCode(Kopete::AV::signal_standard)':
videodevice.cpp:1773: error: `V4L2_STD_SECAM_DK' undeclared (first use this
   function)
videodevice.cpp:1773: error: (Each undeclared identifier is reported only once
   for each function it appears in.)


Hope that helps

bram85

Professional

Posts: 948

Location: Eindhoven

Occupation: Software Engineer

  • Send private message

5

Friday, April 7th 2006, 6:44pm

Quoted

Source code

1
2
kopete: relocation error: kopete: undefined symbol: _ZN17KopeteContactList11contactListEv
kopete: ERROR: Communication problem with kopete, it probably crashed.


It looks like that Kopete is still using old libraries.

Quoted

Source code

1
2
3
4
videodevice.cpp:1773: error: `V4L2_STD_SECAM_DK' undeclared (first use this
   function)
videodevice.cpp:1773: error: (Each undeclared identifier is reported only once
   for each function it appears in.)


I think you should report this at http://bugs.kde.org , with some system specifications and which configure options you passed along.

If you exclude the directory from the Makefile which causes this error, does Kopete install and run well then?
Bram Schoenmakers
KDE Netherlands (www.kde.nl)

6

Saturday, April 8th 2006, 5:21pm

Quoted


I think you should report this at http://bugs.kde.org , with some system specifications and which configure options you passed along.

I can't report a bug, since my KDE is to old to use in the bugtracker system and I don't want to upgrade my KDE just for Kopete.

Quoted


If you exclude the directory from the Makefile which causes this error, does Kopete install and run well then?


How would I do that? I'm not very familiar with makefiles and such.

Thanks for the help!

Red M&M

bram85

Professional

Posts: 948

Location: Eindhoven

Occupation: Software Engineer

  • Send private message

7

Saturday, April 8th 2006, 6:07pm

Quoted

I can't report a bug, since my KDE is to old to use in the bugtracker system and I don't want to upgrade my KDE just for Kopete.


Which version of KDE if I may ask? Please read the following note:

Quoted

From http://kopete.kde.org
People using the following versions of KDE should be able to compile and install Kopete 0.12 Beta 2:
KDE 3.3, KDE 3.4, KDE 3.5


Quoted

How would I do that? I'm not very familiar with makefiles and such.


Locate the directory where the build fails, go one directory up and edit it's Makefile. Find the line starting with

Source code

1
SUBDIRS=
and remove the failing directory from this list. Save and quit and start make again.

Note: this solution may not always work, maybe the directory you're excluding is required by other components of Kopete.
Bram Schoenmakers
KDE Netherlands (www.kde.nl)

8

Sunday, April 9th 2006, 12:53am

I'm running KDE 3.3.2, so I think Kopete should run according to the release notes.
The bugtracker only allows reporting bugs in KDE 3.4 and 3.5.x.

I tried removing the directory from the makefile as you suggested but it produced the same error. Going up another level would result into removing the directory "libkopete" which I guess is a very imortant one.

I think I just habe to wait until the final release is published and see if it will run then.

I appreciate your help!

Greetings,
Red M&M

bram85

Professional

Posts: 948

Location: Eindhoven

Occupation: Software Engineer

  • Send private message

9

Sunday, April 9th 2006, 10:49am

Again, you should report it at http://bugs.kde.org , the developers will be aware of the problems. You can select "Any version older than KDE 3.4.0, which will apply for your KDE 3.3 installation.-
Bram Schoenmakers
KDE Netherlands (www.kde.nl)

10

Sunday, April 9th 2006, 11:21am

I tried the option "any version older than 3.4" but then the wizard says I should upgrade my KDE since the problem might most likely be resolved with a newer version of KDE. So I cannot even get to entering my issue to the bugtracker system.

I'll just wait till the final release is published.

Again, thanks a lot for your help and patience with that problem!!

Greetings, Red M&M

mattr

Trainee

Posts: 105

Location: US

Occupation: Software Engineer

  • Send private message

11

Monday, April 10th 2006, 5:48pm

The error you received on the console about the undefined symbol means that something didn't get installed correctly and the only way to
fix it is to make sure that you installed the new kopete over your old kopete. Please try recompiling and reinstalling again, and be sure run configure like so:

Source code

1
./configure --prefix=`kde-config --prefix`


It is preferable (since it's not a final release yet) to also add

Source code

1
--enable-debug=full
to the above configure line so that you can report good backtraces in case it crashes.

As far as the bug tracking system goes, please just ignore the warning about upgrading your KDE.
--Matt