On Fri, Aug 14, 2015 at 11:18:07AM -0300, Fernando de Oliveira wrote:
> Em 13-08-2015 16:41, Ken Moffat escreveu:
>
> Thank you very much for testing it.
>
> Do the reboot and shutdown buttons work now?
>
I don't think so - I haven't used it for a few days, and at the
moment I'm doing other things on the same machine.
> In what follows, I will write what I understand (or don't understand) is
> needed to modify in the book. Please, reply with comments, or just yes,
> if I understood correctly.
>
> > I said I would make some more comments on lxqt, but that got
> > sidelined by the stylesheets and firefox. Some of the things I
> > flagged up (particularly, the library directory where not mentioned
> > in the book) were bogus. The book instructions are ok.
>
> I will try to understand the "library directory" issue and try to solve it.
>
No, what you have done is correct - Some packages such as libqtxdg
have -DCMAKE_INSTALL_LIBDIR=lib and those are fine. Soem others
such as libsysstat do not have that, but they too are correct and do
not recognise that variable.
What you did is already correct.
> >
> > But finally, here are my remaining comments -
> >
> > 1. I built it in /usr - works for me.
> >
> > This was with qt5 in /opt : for lxqt, I cannot see any pressing reason
> > to build lxqt in /opt. So, I used $LXQT_PREFIX in my scripts.
> > My personal view is that Qt also belongs in /usr - in my normal
> > desktop builds I only put two things into /opt : llvm (to ensure it
> > will not be used by accident - I have to add it to $PATH when I want
> > to use it), and texlive.
>
> For me, it was a question of convenience: had to add a more or less
> "large" number of packages, without knowing what would work or not. Easy
> to remove afterwards (and I did remove and reinstall several times).
>
> I wouldn't mind if you modify the instructions to add$LXQT_PREFIX and
> optionally install either in /usr or /opt. Actually, I would appreciate
> that modification. Don't know if we have time to do it before freeze.
>
I'll try to fit it in.
> > 2. kf5 dependencies
> >
> > On the face of it, only the two named packages (kwindowsystem,
> > kguiaddons) are needed, plus the matching extra-cmake-modules. I
> > dropped these into /usr rather than having kf5 in my PATH during
> > this build. I would hate people to get the mistaken impression
> > that all of kf5 is needed here.
>
> I think you are suggesting that where the two referred packages are
> mentioned, I add a warning that only those are needed.
>
Yes (I've already failed to convince Bruce that the kf5 packages
should have individual pages, even though one or two are not
currently required.
> > 3. lxqt-common and another windowmanager -
> >
> > Note that icewm is NOT a valid replacement (you get icewm without
> > any of the lxqt additions). Fluxbox does work, although in this
> > context (with lxqt-config) openbox is better. The windowmanager
> > you are using needs to be in both /etc/xdg/lxqt/windowmanagers.conf
> > and there the Name is actually the _command_, e.g.
> >
> > fluxbox/Name=startfluxbox
> >
> > and then you can change the windowmanager= line in
> > /etc/xdg/lxqt/session.conf.
>
> OK. I need to add those comments, first generally, and then, with your
> example.
>
Thanks - if you look at windowmanagers,conf you will see that
several are already mentioned, it is only others which need to be
added by anybody who wants to use them. Many of the entries have a
comment, but those do not seem to be useful.
> >
> > 4. lxqt-runner : does this do anything, or show up in a menu ?
> > I had assumed it would let me type in the name of the program I
> > wanted to run, but could not find any way to do that.
>
> OK. Need to add a paragraph about this: At-F2 opens at the center top a
> small window where the program name can be typed. It is always running:
>
I'll try to remember that - for the next few days this box will be
running icewm while I do some builds in qemu and have another
attempt to sort out some photos.
[...]
>
> > Using an unsupported variable-width font in the terminal. This may produce
> > display errors.
> > Using an unsupported variable-width font in the terminal. This may produce
> > display errors.
>
> Those two lines don't appear for me.
>
I was using oxygen fonts (playing around with the configuration) - I
do remember that juffed seemed to be using a variable-width font in
its display, perhaps I misconfigured it [ or, it has something to do
with the 'cursor offset to right' problem I mentioned in kde5 which
was caused by an oxygen font ]
[...]
>
> I have, not Ken:
>
> QFileInfo::absolutePath: Constructed with empty filename
>
> > "[03:10:09]" " Entering tabRemoved (TabWidget.cpp:113)"
> > "[03:10:09]" " Entering onTabRemoved (DocViewer.cpp:434)"
> > "[03:10:09]" " Leaving onTabRemoved (DocViewer.cpp)"
> > "[03:10:09]" " Leaving tabRemoved (TabWidget.cpp)"
>
> Above, Ken, not Fernando.
>
> > QProcess: Destroyed while process ("/bin/bash") is still running.
> >
> > Segmentation fault
>
> Thanks for that!!!
>
> (BTW, minutes before starting to reply, FF crashed, after one day
> without problem. I'm looking forward to start creating the tickets,
> hoping that FF-40.0.2 fixes that.)
If it's any consolation, for me yesterday firefox was ok but the
whole box locked up twice (4.2.0-rc6 kernel, with qemu running).
>
> Spent the day up to now investigating that. I'm almost sure that the
> problem is with qtermwidget.
>
> This was suggested by gdb, running a -DCMAKE_BUILD_TYPE=Debug DESTDIR
> install, instead of Release:
>
> {{{
> GDB
> ...
> QProcess: Destroyed while process ("/bin/bash") is still running.
> [New Thread 0x7fffdb44d700 (LWP 20210)]
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x00007ffff5d6a06a in QObject::removeEventFilter(QObject*) ()
> from /opt/qt5/lib/libQt5Core.so.5
>
> Back Trace:
> (gdb) bt
> #0 0x00007ffff5d6a06a in QObject::removeEventFilter(QObject*) ()
> from /opt/qt5/lib/libQt5Core.so.5
> #1 0x00007fffda1c6766 in Konsole::TerminalDisplay::~TerminalDisplay() ()
> from /usr/lib/libqtermwidget5.so.0
> #2 0x00007fffda1c6989 in Konsole::TerminalDisplay::~TerminalDisplay() ()
> from /usr/lib/libqtermwidget5.so.0
> #3 0x00007ffff5d6177b in QObjectPrivate::deleteChildren() ()
> from /opt/qt5/lib/libQt5Core.so.5
> #4 0x00007ffff6a3e0ff in QWidget::~QWidget() ()
> from /opt/qt5/lib/libQt5Widgets.so.5
> #5 0x00007fffda1b0a99 in QTermWidget::~QTermWidget() ()
> from /usr/lib/libqtermwidget5.so.0
> #6 0x00007fffda3fc830 in TerminalPlugin::~TerminalPlugin() ()
> from /usr/lib/juffed/plugins/libterminal.so
> #7 0x00007fffda3fc909 in TerminalPlugin::~TerminalPlugin() ()
> from /usr/lib/juffed/plugins/libterminal.so
> #8 0x00007ffff5d2b0f5 in ?? () from /opt/qt5/lib/libQt5Core.so.5
> #9 0x00007ffff5d2c4ab in ?? () from /opt/qt5/lib/libQt5Core.so.5
> #10 0x00007ffff499812f in __cxa_finalize () from /lib/libc.so.6
> #11 0x00007ffff5b3ee43 in ?? () from /opt/qt5/lib/libQt5Core.so.5
> #12 0x00007fffffffdb10 in ?? ()
> #13 0x00007ffff7dea727 in _dl_fini () from /lib64/ld-linux-x86-64.so.2
> Backtrace stopped: frame did not save the PC
> (gdb)
> }}}
>
> After some searches, found many references for '"qtermwidget"
> segmentation fault' and a patch (for reasons that I can't remember any
> more I assumed was for that problem):
>
> [http://pkgs.fedoraproject.org/cgit/qtermwidget.git/plain/qtermwidget-0.6.0-qt-virt-manager.patch]
>
> Reinstalled qtermwidget and juffed, but still got the segfault.
>
> Reinstalled juffed with -DBUILD_TERMINAL=OFF, and the segfault is gone.
>
> Thinking of warning about that. Have used the terminal and it works, but
> never use it. Or do you think that it would be better a recommendation
> against it?
I don't think the segfault while closing is something that most
people who use juffed (from a menu) will notice. I just tried
qterminal itself from a different term and do not get a segfault.
If nothing is broken on subsequent uses then there is no reason to
recommend against it.
I recall that on using it the next time, the document from the
previous use was opened again - I'm not sure if that is what is
supposed to happen, but perhaps it is.
iĸen
--
This one goes up to eleven: but only on a clear day, with the wind in
the right direction.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
