Em 14-08-2015 12:20, Ken Moffat escreveu:
Hopefully fixed at r16345.
Som e differences explained in line, below.
> 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.
OK.
>>> 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.
>> For me, it was a question of convenience.
>>
>> 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.
Thanks. That will be very good.
>>> 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.
Included a note in the respective pages.
>>> 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.
Here, I spent most of the time, today. Installed and tested fluxbox, and
had xfwm4 already installed. What I wrote works, but is a little
different from what you described. Please, improve anything that you
wish. Some sentences are difficult to write. This is also the case for
next point, lxqt-runner.
>>> 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.
>
> [...]
Done.
>>
>>> 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).
Yes, that is bad.
BTW, FF crashed again today, now, FF-40.0.2. :-(
>> {{{
>> 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"
>> 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.
The same, here.
> If nothing is broken on subsequent uses then there is no reason to
> recommend against it.
OK. Thanks.
>
> 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.
You can configure it for not opening last files. I think it is the first
option of the first entry in Tools -> Definitions.
I like it reopening them.
I have two sessions: blfs (scripts, buold, instal, etc.) and blfs-book
(actual editing). Without leaving the window, I can switch from one to
the other and back, without losing any of the particular session open tabs.
For scripts, I have a template.sh and the scripts for what I'm working
on. Often we need to close all windows to test session, X, etc, you
know. When back to work, what I was doing is there again.
For the book edition, it reopens general.ent, packages.ent, gnome.ent
and changelog.xml.
After it is open, I just need to type "juffed <new files to edit>" and
the other files to edit are added to the session.
This is a great time saving and less clutter in the screen.
>
> iĸen
>
Why the "i"? :-)
Thank you very much!!!
--
[]s,
Fernando
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
