Slavek,
I know there isn't a 3.5.13-sru branch for tqca-tls. I'll look at creating
a patch. Currently there is an error where it is looking for libtqt-mt.so.3
instead of libqt-mt.so.3
When there is NO 3.5.13-sru branch for a module (like tqca-tls), does this
mean you are still using the 3.5.13 tarball for the module and not the current
GIT tree?
For those that know cmake, what would I have to change to fix this? Can it
be done as a conditional to look for either Qt3 or TQt3 libs like we were
doing in the Jan.-Feb. timeframe when TDE could still build on QT3?? The error is:
==> Starting configure...
Configuring qca-tls ...
Verifying TQt 3.x Multithreaded (MT) build environment ... fail
There was an error compiling 'conf'. Be sure you have a proper
TQt 3.x Multithreaded (MT) build environment set up.
One possible reason is that you don't have
libtqt-mt.so.3 installed in /opt/qt3/lib/
or /opt/qt3/lib64/.
==> ERROR: A failure occurred in build().
Aborting...
--
David C. Rankin, J.D.,P.E.
All,
When checking the screenshots before posting, I'm normally in firefox.
However, I was testing konqueror. When I go to e.g.:
http://www.3111skyline.com/dl/bugs/Archlinux/gtk-gimp28.jpg
I cannot view the image in konqueror, but instead I'm faced with this
dialog:
http://www.3111skyline.com/dl/dt/trinity/ss/konqueror-jpg.jpg
What is preventing konqueror from viewing the jpg? I can rt-click and
choose to view in e.g. kview, but in the web browser, I should be able
to just open the image in the browser. Anybody else see this? How to fix?
All,
In R14, when you right-click an image and choose External Tools, any
association you make (i.e. gimp) does not get added to the list and is
not preserved between gwenview sessions. In the change from gimp 2.6 to
2.8, the executable changed names so I need to update the 'External
Tools' reference. If I go though the process of rt-click, External Tools
-> Other... and choose the new gimp from the menu, "[x] Remember
application association for this type of file", then the image is
launched in gimp, but when I rt-click the next image, there is nothing
in the External Tools for the new gimp. It goes through the normal
"Updating System..." dialog as normal, so I would expect to see the new
association in qwenview. (maybe not)
This problem seems limited to gwenview as I have updated other file
types in the file manager and I believe that worked.
I can use External Tools -> Configure External Tools and create/edit
the associations. So that part works. It's just strange that there seems
to be a disconnect with this setting in qwenview. Anybody else try this?
All,
I want to build a set of 3.5.13 packages for arch. I have made a copy of my
GIT tree and I want to revert it back. I tried to follow Slavek's advice of using
(switch to v3.5.13-sru branch)
git checkout v3.5.13-sru && git pull && git submodule update
However, that fails:
16:23 providence:~/pvd/tde13/tde> git checkout v3.5.13-sru
error: pathspec 'v3.5.13-sru' did not match any file(s) known to git.
I have seen the v3.5.13-sru label before during updates, but I can't figure
out how to go back. What say the experts?
--
David C. Rankin, J.D.,P.E.
All,
With the latest build of TDE, the input actions in 'Regional &
Accessibility -> Input Actions' don't work.
prtscr (print screen) no longer launches ksnapshot. (Preset Actions ->
PrintScreen)
ctrl+alt+t no longer launches konsole. (Examples -> Run Konsole)
The key presses are correctly seen by the system. You can verify by
reassigning the keystroke and tde sees prtscr when print screen is pressed.
TDE sees the multi-keystroke combination ctrl+alt+t when it is pressed. Even
though the keystrokes are seen in TDE, no input actions are executed.
The keystroke recognition was also verified in xev.
So the regression is that TDE is no longer passing keystrokes to the Input
Actions for execution.
filed as: http://bugs.pearsoncomputing.net/bugzilla/show_bug.cgi?id=1124
--
David C. Rankin, J.D.,P.E.
All,
I think we are at the point where we need to implement a code freeze
against new changes to TDE until we have resolved all BLOCKER and CRITICAL
bugs. Shooting at a moving target makes getting R14 to an acceptable baseline
much more difficult than it need be. If there are a few more new changes
required to build in functionality that is wanted in R14, that's fine, but
once they are added, let's implement a 14 or 30 day freeze against new changes
and get R14 in shape. What do you think? Please weigh in on the discussion.
Additionally, if you have the knowledge to lend any help in resolving
existing bugs -- your help is needed. I know a lot of you reading this are a
lot smarter than I am on c++, but for whatever reason haven't yet grabbed a
keyboard and jumped in to the bug tracker to help. Darrell has shouldered much
of the recent fixing and updating, but we cannot rely on his efforts alone --
there is too much to do. Regardless of your level of expertise, you can help
by taking a bug and working through the code to find out where things are not
working. Even if you can't fix it, identifying where the problem is moves the
ball forward and is greatly needed. Lord knows that is what I do most of the time.
Seriously, if we are going to get R14 to the point of release, we need
every able body to help. We are all busy, it is just a matter of making time.
We have some really smart people on the list, let's all take a bug and work it
to move R14 closer to done.
--
David C. Rankin, J.D.,P.E.
All,
This patch updates k3b/plugins/decode/ffmpeg to be compatible with ffmpeg
0.11-1 and eliminates all deprecated warnings during compile of
k3bffmpegwrapper.cpp. It needs review and testing. Since these deprecations have
existed for quite some time, there may be no need for preprocessor checks as the
replaced functions have been deprecated for a long time. The patch addresses all
of the following:
k3bffmpegwrapper.cpp: In member function 'bool K3bFFMpegFile::open()':
k3bffmpegwrapper.cpp:82:84: error: 'av_open_input_file' was not declared in this
scope
k3bffmpegwrapper.cpp:89:3: warning: 'int av_find_stream_info(AVFormatContext*)'
is deprecated (declared at /usr/include/libavformat/avformat.h:1357)
[-Wdeprecated-declarations]
k3bffmpegwrapper.cpp:89:41: warning: 'int av_find_stream_info(AVFormatContext*)'
is deprecated (declared at /usr/include/libavformat/avformat.h:1357)
[-Wdeprecated-declarations]
k3bffmpegwrapper.cpp:117:7: warning: 'int avcodec_open(AVCodecContext*,
AVCodec*)' is deprecated (declared at /usr/include/libavcodec/avcodec.h:3380)
[-Wdeprecated-declarations]
k3bffmpegwrapper.cpp:117:44: warning: 'int avcodec_open(AVCodecContext*,
AVCodec*)' is deprecated (declared at /usr/include/libavcodec/avcodec.h:3380)
[-Wdeprecated-declarations]
k3bffmpegwrapper.cpp:131:63: error: 'dump_format' was not declared in this scope
k3bffmpegwrapper.cpp: In member function 'void K3bFFMpegFile::close()':
k3bffmpegwrapper.cpp:153:5: warning: 'void
av_close_input_file(AVFormatContext*)' is deprecated (declared at
/usr/include/libavformat/avformat.h:1533) [-Wdeprecated-declarations]
k3bffmpegwrapper.cpp:153:43: warning: 'void
av_close_input_file(AVFormatContext*)' is deprecated (declared at
/usr/include/libavformat/avformat.h:1533) [-Wdeprecated-declarations]
k3bffmpegwrapper.cpp: In member function 'int K3bFFMpegFile::fillOutputBuffer()':
k3bffmpegwrapper.cpp:318:11: warning: 'int
avcodec_decode_audio3(AVCodecContext*, int16_t*, int*, AVPacket*)' is deprecated
(declared at /usr/include/libavcodec/avcodec.h:3658) [-Wdeprecated-declarations]
k3bffmpegwrapper.cpp:320:14: warning: 'int
avcodec_decode_audio3(AVCodecContext*, int16_t*, int*, AVPacket*)' is deprecated
(declared at /usr/include/libavcodec/avcodec.h:3658) [-Wdeprecated-declarations]
It has been included with bug: 1119
--
David C. Rankin, J.D.,P.E.
Oh, I just had to share:
<quote>
Writing software is actually quite easy. Writing good software is relatively
harder, but still easy. Writing software to a programmer is like painting to a
painter. Shipping software is an incredibly complicated task. It’s like getting
a stadium full of babies to all have clean diapers at the same time with only
one or two people to do the work. As soon as you fix one thing, you discover
more crap. The process stinks and you’ll never reach the end. Those who do it
either by printing a CD, uploading a binary, or pushing out changes to a tier of
web servers know what I’m talking about.
</quote>
http://robert.accettura.com/blog/2011/08/17/on-firefox-versioning/
--
David C. Rankin, J.D.,P.E.