By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1048

Summary:	Digikam: Unexpected Q_LLONG messages
Product:	TDE	Reporter:	Darrell <darrella>
Component:	non-core programs	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	major	CC:	bugwatch, darrella, trin
Priority:	P1
Version:	R14.0.0 [Trinity]
Hardware:	Other
OS:	Other
Compiler Version:		TDE Version String:
Application Version:		Application Name:	Digikam
Attachments:	Patch to build tqca with recent TQ fixes. Partyial patch to build python-tqt with recent TQ fixes Arch Linux FTBFS Logs 6/20/12 (rankin)

Description Darrell 2012-06-17 16:25:00 CDT

Latest GIT. When starting digikam from the terminal, the following messages appear:

TQObject::connect: No such signal Digikam::ImageAttributesWatch::signalImageTagsChanged(Q_LLONG)
TQObject::connect:  (sender name:   'unnamed')
TQObject::connect:  (receiver name: 'unnamed')
TQObject::connect: No such signal Digikam::ImageAttributesWatch::signalImageRatingChanged(Q_LLONG)
TQObject::connect:  (sender name:   'unnamed')
TQObject::connect:  (receiver name: 'unnamed')
TQObject::connect: No such signal Digikam::ImageAttributesWatch::signalImageDateChanged(Q_LLONG)
TQObject::connect:  (sender name:   'unnamed')
TQObject::connect:  (receiver name: 'unnamed')
TQObject::connect: No such signal Digikam::ImageAttributesWatch::signalImageCaptionChanged(Q_LLONG)
TQObject::connect:  (sender name:   'unnamed')
TQObject::connect:  (receiver name: 'unnamed')

The strings repeat a second time.

Looking at the digikam sources shows instances of TQ_LLONG but not Q_LONG.

TQ_LLONG is defined in tqt.h.

Comment 1 Timothy Pearson 2012-06-17 17:17:18 CDT

This looks to be due to missing renaming of the following defines in tqt3:

TQ_INT8
TQ_INT16
TQ_INT32
TQ_INT64
TQ_UINT8
TQ_UINT16
TQ_UINT32
TQ_UINT64
TQ_LONG
TQ_LLONG
TQ_ULONG
TQ_ULLONG

I'll see what I can do to correct this.

Comment 2 Timothy Pearson 2012-06-17 17:31:02 CDT

This should be resolved in GIT hashes 6dec101 and 7a453a2.

The ABI may have broken with those commits, and building is not guaranteed either.  I will perform a rebuild test over the next few days and fix any problems as they appear.

Comment 3 Darrell 2012-06-18 10:54:48 CDT

I rebuilt tqt3, tqtinterface, digikam. Starting digikam from the command line is now clean.

Thank you!

I'll leave this bug report open for a few days. As you implied, I will build a full package set and watch for other possible effects.

Comment 4 Darrell 2012-06-18 11:55:06 CDT

Looks like the latest patches affect tdebase, which now fails to build:

/dev/shm/tdebase/kioslave/sftp/sftpfileattr.h:48: error: 'Q_ULLONG' does not name a type
/dev/shm/tdebase/kioslave/sftp/sftpfileattr.h:97: error: expected ')' before 'size_'
/dev/shm/tdebase/kioslave/sftp/sftpfileattr.h:107: error: 'Q_ULLONG' has not been declared
/dev/shm/tdebase/kioslave/sftp/sftpfileattr.h:116: error: 'Q_ULLONG' does not name a type
/dev/shm/tdebase/kioslave/sftp/sftpfileattr.h:108: error: 'mSize' was not declared in this scope
/dev/shm/tdebase/kioslave/sftp/sftpfileattr.h:113: error: 'mSize' was not declared in this scope
/dev/shm/tdebase/kioslave/sftp/kio_sftp.cpp:350: error: 'class sftpFileAttr' has no member named 'fileSize'
/dev/shm/tdebase/kioslave/sftp/kio_sftp.cpp:883: error: 'class sftpFileAttr' has no member named 'fileSize'
/dev/shm/tdebase/kioslave/sftp/kio_sftp.cpp:921: error: 'class sftpFileAttr' has no member named 'fileSize'
/dev/shm/tdebase/kioslave/sftp/kio_sftp.cpp:1058: error: 'class sftpFileAttr' has no member named 'fileSize'

Comment 5 Timothy Pearson 2012-06-18 14:23:16 CDT

tdebase issue should be resolved in GIT hash 31b5c99.

I expect there to be failures sprinkled throughout the source tree.

Comment 6 Darrell 2012-06-18 14:30:56 CDT

I think I see from the tdebase patch what failures to watch. I think.... :-)

Okay, try again from scratch.

Comment 7 Darrell 2012-06-18 15:30:52 CDT

Created attachment 680 [details]
Patch to build tqca with recent TQ fixes.

tqca failed to build. Attaching a patch for your review.

Comment 8 Timothy Pearson 2012-06-18 15:41:13 CDT

(In reply to comment #7)
> Created attachment 680 [details]
> Patch to build tqca with recent TQ fixes.
> 
> tqca failed to build. Attaching a patch for your review.

That is the correct solution; go ahead and push.

Comment 9 Darrell 2012-06-18 19:50:07 CDT

Created attachment 681 [details]
Partyial patch to build python-tqt with recent TQ fixes

tqca patch pushed in GIT hash 2356bc27.

python-tqt needs patching too. I tried the attached patch to no avail.

Comment 10 David C. Rankin 2012-06-20 10:09:30 CDT

Tim,

  After my complete build on gcc 4.7.1, here is the FTBFS list:

tde-avahi-tqt-14.0.0_dev-1-i686-build.log
tde-gtk-qt-engine-14.0.0_dev-1-i686-build.log
tde-python-tqt-14.0.0_dev-1-i686-build.log
tde-tdegraphics-14.0.0_dev-1-i686-build.log
tde-tdesvn-14.0.0_dev-1-i686-build.log

I will include the logs as an attachment.

Comment 11 David C. Rankin 2012-06-20 10:13:24 CDT

Created attachment 684 [details]
Arch Linux FTBFS Logs 6/20/12 (rankin)

kipi-plugins also failed, that log is included with the rest in the tarball.

Comment 12 Darrell 2012-06-20 10:36:47 CDT

I ran a full build run against Slackware 13.1 32-bit. I pushed patches for some remaining nominal build failures, but all has been built. We're probably in the clear for this bug report, but should wait for others to report as well.

Note: Bug report 843 affects recent build failures too. Those changes require rebuilding (T)Qt3 (starting from scratch).

Comment 13 Darrell 2012-07-07 20:00:26 CDT

No incidents reports in two weeks. Closing as resolved.