Re: [gentoo-user] Re: tab-grouping in Firefox
On October 22, 2018 7:26:53 AM Philip Webb wrote: 181015 Philip Webb wrote: The big question is whether I can still group tabs, whether directly with FF or via some add-on (whatever they're now called). I've now been using FF for a few days & can report my experience. There doesn't seem to be an add-on which reproduces the old version. However, I've done what I thought mb the best imitation : the answer is windows ! -- no, not that Windows, but FF windows. It's simple to drag-drop tabs from one FF window to another : you just have to make sure you drop it into the Tab Bar. My daily use of this is when reading news stories. If I'm reading the Guardian, there are 5 story lists I check : World, UK, Biz, Opinion + the home page. The problem is that not all Biz stories are listed there, but mb eg under World, so to group them for easy reading I need to grab all of them, then move them into my desired groups, ie World, UK, Biz (incl Brexit), Science+Environment, Entertainment (sport history pictures etc). This was easy fun using the old Tab Groups ; now it's not fun, but fairly easy to do by creating separate windows & dragging the appropriate tabs into the appropriate windows ; dragging the 1st onto the desktop creates each window. Does anyone know why FF dropped this feature ? It looks as if it sb easy to develop as a front-end to window management. Otherwise, the new FF is noticeably faster than the old FF. Also, can anyone tell me how to remove an add-on ? The "hamburger" menu (three horizontal lines) need the top-right) has a menu item to get to addons - simply disable or uninstall from there. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
[gentoo-user] Re: tab-grouping in Firefox
181015 Philip Webb wrote: > The big question is whether I can still group tabs, > whether directly with FF or via some add-on (whatever they're now called). I've now been using FF for a few days & can report my experience. There doesn't seem to be an add-on which reproduces the old version. However, I've done what I thought mb the best imitation : the answer is windows ! -- no, not that Windows, but FF windows. It's simple to drag-drop tabs from one FF window to another : you just have to make sure you drop it into the Tab Bar. My daily use of this is when reading news stories. If I'm reading the Guardian, there are 5 story lists I check : World, UK, Biz, Opinion + the home page. The problem is that not all Biz stories are listed there, but mb eg under World, so to group them for easy reading I need to grab all of them, then move them into my desired groups, ie World, UK, Biz (incl Brexit), Science+Environment, Entertainment (sport history pictures etc). This was easy fun using the old Tab Groups ; now it's not fun, but fairly easy to do by creating separate windows & dragging the appropriate tabs into the appropriate windows ; dragging the 1st onto the desktop creates each window. Does anyone know why FF dropped this feature ? It looks as if it sb easy to develop as a front-end to window management. Otherwise, the new FF is noticeably faster than the old FF. Also, can anyone tell me how to remove an add-on ? -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] problem updating KDE breeze : solved
181022 Philip Webb wrote:
> /usr/lib64/libKF5Declarative.so.5: undefined reference to
> `QQmlPropertyMap::init(QMetaObject const*)@Qt_5'
> /usr/lib64/libKF5Declarative.so.5: undefined reference to
> `QQmlPropertyMap::allocatePrivate()@Qt_5'
> collect2: error: ld returned 1 exit status
> make[2]: *** [kstyle/config/CMakeFiles/breeze-settings5.dir/build.make:121:
> kstyle/config/breeze-settings5] Error 1
The file causing the problem belongs to kde-frameworks/kdeclarative :
root:586 ~> equery belongs /usr/lib64/libKF5Declarative.so.5
kde-frameworks/kdeclarative-5.50.0 (/usr/lib64/libKF5Declarative.so.5.50.0)
kde-frameworks/kdeclarative-5.50.0 (/usr/lib64/libKF5Declarative.so.5 ->
libKF5Declarative.so.5.50.0)
I updated it the previous weekend :
root:587 ~> eix kdeclar
[I] kde-frameworks/kdeclarative
Available versions: (5) 5.50.0(5/5.50) ~5.51.0(5/5.51) {debug doc}
Installed versions: 5.50.0(5/5.50)([2018-10-13 11:50:09])(-debug -doc)
So I just tried the obvious & re-merged Kdeclarative.
After I did that, Breeze + the other 5 pkgs merged successfully.
Somewhere in the toils of the ebuilds, there's a missing requirement,
but if anyone else runs into this, it's now on record here.
I would have worked this out for myself,
if I had known there cb > 1 'Error' in emerge output.
Thanks to you both for educating me : I'll add a note to my help files.
(Big smile)
--
,,
SUPPORT ___//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] problem updating KDE breeze
On Mon, Oct 22, 2018 at 7:15 AM Philip Webb wrote: > > 181021 Franz Fellner wrote: > > the actual error really is missing. > > Can you use pastebin or something similar to upload the whole build.log? > > The number of cores may help to estimate the unmber of compilation units > > that still get built. Unfortunately not with cmake. It usually continues > > building targets that do not depend on the failed target. > > You may have to scroll up hundreds of lines. > > So, again: Please give us the complete build.log ! > > I hadn't run into this kind of error before > & assumed there cb only 1 error for each Emerge. > Here is where 'Error 1' occurs : > > [ 37%] Building CXX object > kdecoration/CMakeFiles/breezedecoration.dir/breezesettings.cpp.o > cd > /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kdecoration > && /usr/bin/x86_64-pc-linux-gnu-g++ -DKCOREADDONS_LIB -DKGUIADDONS_LIB > -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -\ > DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB > -DTRANSLATION_DOMAIN=\"breeze_kwin_deco\" -D_GNU_SOURCE -D_LARGEFILE64_SOURCE > -Dbreezedecoration_EXPORTS -I/var/tmp/portage/portage/kde-plasm\ > a/breeze-5.13.5/work/breeze-5.13.5_build/kdecoration > -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kdecoration > -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.1\ > 3.5_build/kdecoration/breezedecoration_autogen/include -isystem > /usr/include/qt5 -isystem /usr/include/qt5/QtCore -isystem > /usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtGui -isystem > /usr/i\ > nclude/qt5/QtDBus -isystem /usr/include/KDecoration2 -isystem > /usr/include/KF5 -isystem /usr/include/KF5/KConfigCore -isystem > /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KConfigWidgets -isyste\ > m /usr/include/KF5/KCodecs -isystem /usr/include/KF5/KWidgetsAddons -isystem > /usr/include/qt5/QtWidgets -isystem /usr/include/KF5/KConfigGui -isystem > /usr/include/qt5/QtXml -isystem /usr/include/KF5/KAut\ > h -isystem /usr/include/KF5/KGuiAddons -isystem /usr/include/KF5/KI18n > -isystem /usr/include/KF5/KWindowSystem -isystem /usr/include/qt5/QtX11Extras > -DQT_NO_DEBUG -DNDEBUG -march=native -O2 -pipe -std=\ > c++0x -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align > -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef > -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type\ > -Wvla -Wdate-time -fPIC -fvisibility=hidden -fvisibility-inlines-hidden > -fPIC -std=gnu++11 -o CMakeFiles/breezedecoration.dir/breezesettings.cpp.o -c > /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/\ > work/breeze-5.13.5_build/kdecoration/breezesettings.cpp > /usr/lib64/libKF5Declarative.so.5: undefined reference to > `QQmlPropertyMap::init(QMetaObject const*)@Qt_5' > /usr/lib64/libKF5Declarative.so.5: undefined reference to > `QQmlPropertyMap::allocatePrivate()@Qt_5' > collect2: error: ld returned 1 exit status > make[2]: *** [kstyle/config/CMakeFiles/breeze-settings5.dir/build.make:121: > kstyle/config/breeze-settings5] Error 1 > make[2]: Leaving directory > '/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build' > make[1]: *** [CMakeFiles/Makefile2:550: > kstyle/config/CMakeFiles/breeze-settings5.dir/all] Error 2 > make[1]: *** Waiting for unfinished jobs > Generating MOC source 4NBMFDNHZT/moc_breezetransitionwidget.cpp > /usr/lib64/qt5/bin/moc > -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kstyle > > -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kstyle/breeze_autog\ > en/include > -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kstyle > -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kstyle/animations > -I/var/tmp/portage/portag\ > e/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kstyle/debug -I/usr/include/qt5 > -I/usr/include/qt5/QtCore -I/usr/lib64/qt5/mkspecs/linux-g++ > -I/usr/include/qt5/QtGui -I/usr/include/qt5/QtWidgets -I/usr/inc\ > lude/qt5/QtDBus -I/usr/include/qt5/QtQuick -I/usr/include/qt5/QtQml > -I/usr/include/qt5/QtNetwork -I/usr/include/KF5/KConfigCore > -I/usr/include/KF5 -I/usr/include/KF5/KConfigWidgets -I/usr/include/KF5/KCo\ > decs -I/usr/include/KF5/KWidgetsAddons -I/usr/include/KF5/KConfigGui > -I/usr/include/qt5/QtXml -I/usr/include/KF5/KAuth > -I/usr/include/KF5/KCoreAddons -I/usr/include/KF5/KGuiAddons > -I/usr/include/KF5/KWin\ > dowSystem -I/usr/include/KF5/KStyle -I/usr/include/qt5/QtX11Extras > -I/usr/include -I/usr/include -DKCOREADDONS_LIB -DKGUIADDONS_LIB > -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG\ > -DQT_QML_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB > -D_GNU_SOURCE -D_LARGEFILE64_SOURCE --include > /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/ksty\ > le/breeze_autogen/moc_predefs.h -o >
Re: [gentoo-user] problem updating KDE breeze
181021 Franz Fellner wrote: > the actual error really is missing. > Can you use pastebin or something similar to upload the whole build.log? > The number of cores may help to estimate the unmber of compilation units > that still get built. Unfortunately not with cmake. It usually continues > building targets that do not depend on the failed target. > You may have to scroll up hundreds of lines. > So, again: Please give us the complete build.log ! I hadn't run into this kind of error before & assumed there cb only 1 error for each Emerge. Here is where 'Error 1' occurs : [ 37%] Building CXX object kdecoration/CMakeFiles/breezedecoration.dir/breezesettings.cpp.o cd /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kdecoration && /usr/bin/x86_64-pc-linux-gnu-g++ -DKCOREADDONS_LIB -DKGUIADDONS_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -\ DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB -DTRANSLATION_DOMAIN=\"breeze_kwin_deco\" -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -Dbreezedecoration_EXPORTS -I/var/tmp/portage/portage/kde-plasm\ a/breeze-5.13.5/work/breeze-5.13.5_build/kdecoration -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kdecoration -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.1\ 3.5_build/kdecoration/breezedecoration_autogen/include -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtCore -isystem /usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtGui -isystem /usr/i\ nclude/qt5/QtDBus -isystem /usr/include/KDecoration2 -isystem /usr/include/KF5 -isystem /usr/include/KF5/KConfigCore -isystem /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KConfigWidgets -isyste\ m /usr/include/KF5/KCodecs -isystem /usr/include/KF5/KWidgetsAddons -isystem /usr/include/qt5/QtWidgets -isystem /usr/include/KF5/KConfigGui -isystem /usr/include/qt5/QtXml -isystem /usr/include/KF5/KAut\ h -isystem /usr/include/KF5/KGuiAddons -isystem /usr/include/KF5/KI18n -isystem /usr/include/KF5/KWindowSystem -isystem /usr/include/qt5/QtX11Extras -DQT_NO_DEBUG -DNDEBUG -march=native -O2 -pipe -std=\ c++0x -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type\ -Wvla -Wdate-time -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -std=gnu++11 -o CMakeFiles/breezedecoration.dir/breezesettings.cpp.o -c /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/\ work/breeze-5.13.5_build/kdecoration/breezesettings.cpp /usr/lib64/libKF5Declarative.so.5: undefined reference to `QQmlPropertyMap::init(QMetaObject const*)@Qt_5' /usr/lib64/libKF5Declarative.so.5: undefined reference to `QQmlPropertyMap::allocatePrivate()@Qt_5' collect2: error: ld returned 1 exit status make[2]: *** [kstyle/config/CMakeFiles/breeze-settings5.dir/build.make:121: kstyle/config/breeze-settings5] Error 1 make[2]: Leaving directory '/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build' make[1]: *** [CMakeFiles/Makefile2:550: kstyle/config/CMakeFiles/breeze-settings5.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs Generating MOC source 4NBMFDNHZT/moc_breezetransitionwidget.cpp /usr/lib64/qt5/bin/moc -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kstyle -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kstyle/breeze_autog\ en/include -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kstyle -I/var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kstyle/animations -I/var/tmp/portage/portag\ e/kde-plasma/breeze-5.13.5/work/breeze-5.13.5/kstyle/debug -I/usr/include/qt5 -I/usr/include/qt5/QtCore -I/usr/lib64/qt5/mkspecs/linux-g++ -I/usr/include/qt5/QtGui -I/usr/include/qt5/QtWidgets -I/usr/inc\ lude/qt5/QtDBus -I/usr/include/qt5/QtQuick -I/usr/include/qt5/QtQml -I/usr/include/qt5/QtNetwork -I/usr/include/KF5/KConfigCore -I/usr/include/KF5 -I/usr/include/KF5/KConfigWidgets -I/usr/include/KF5/KCo\ decs -I/usr/include/KF5/KWidgetsAddons -I/usr/include/KF5/KConfigGui -I/usr/include/qt5/QtXml -I/usr/include/KF5/KAuth -I/usr/include/KF5/KCoreAddons -I/usr/include/KF5/KGuiAddons -I/usr/include/KF5/KWin\ dowSystem -I/usr/include/KF5/KStyle -I/usr/include/qt5/QtX11Extras -I/usr/include -I/usr/include -DKCOREADDONS_LIB -DKGUIADDONS_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG\ -DQT_QML_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE --include /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/ksty\ le/breeze_autogen/moc_predefs.h -o /var/tmp/portage/portage/kde-plasma/breeze-5.13.5/work/breeze-5.13.5_build/kstyle/breeze_autogen/4NBMFDNHZT/moc_breezetransitionwidget.cpp /var/tmp/portage/portage/kde-\
Re: [gentoo-user] problem updating KDE breeze
Franz Fellner wrote: > Hi Philipp, > the actual error really is missing. > Can you use pastebin or something similar to upload the whole build.log? > > The number of cores may help to estimate the unmber of compilation > units that still get built. > Unfortunately not with cmake. It usually continues building targets > that do not depend on the failed target. > You may have to scroll up hundreds of lines. > > So, again: Please give us the complete buld.log! > > Thx > Franz > > Exactly. Whenever a build fails, the compile phase generally, the first error calls itself error 1. Since I use Konsole here, I usually use the Find function and search for "error 1" to help find it. Then I scroll backward until I see what really failed. As you and I point out, it can be a good ways back. Usually in my case, it is less than 10 or 15 lines since I have somewhat smaller settings. Of course, depending on settings, it can be hundreds of lines as you say. OP. The original error is further up. Otherwise, one would see error 1 in there somewhere. It's sometimes hard to find but it's hiding in there somewhere. I'm not big on paste bin but if you can't find it, posting a link to it is better than nothing. As it is, it's going to be hard to help since we can't see what failed, exactly. Dale :-) :-)
Re: [gentoo-user] problem updating KDE breeze
Hi Philipp, the actual error really is missing. Can you use pastebin or something similar to upload the whole build.log? The number of cores may help to estimate the unmber of compilation units that still get built. Unfortunately not with cmake. It usually continues building targets that do not depend on the failed target. You may have to scroll up hundreds of lines. So, again: Please give us the complete buld.log! Thx Franz Am So., 21. Okt. 2018 um 10:30 Uhr schrieb Philip Webb : > 181021 Dale wrote: > > You need to go back further on your copy n paste. > > The first error I see error 2. Somewhere further back is error 1. > > I don't think so : isn't that the type of error taken from a list ? > I don't see another error higher up. > > > That is the first trigger and may point to a problem. > > I usually go back 20 or 30 lines before error 1 > > just to be sure I went back far enough. > > I have a 4 core CPU here. > > Whatever does that have to do with the problem ? > > > My only other suggestion is to make sure you have not run out of space, > > either hard drive mount point or memory if using tmpfs. > > That can cause a strange error > > because it fails wherever it runs out of space. > > Sometimes it fails at different spots too. > > There's no reason to expect that here. > > Thanks for trying, but I believe the problem is somewhere else. > > -- > ,, > SUPPORT ___//___, Philip Webb > ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto > TRANSIT`-O--O---' purslowatchassdotutorontodotca > > >
Re: [gentoo-user] problem updating KDE breeze
181021 Dale wrote: > You need to go back further on your copy n paste. > The first error I see error 2. Somewhere further back is error 1. I don't think so : isn't that the type of error taken from a list ? I don't see another error higher up. > That is the first trigger and may point to a problem. > I usually go back 20 or 30 lines before error 1 > just to be sure I went back far enough. > I have a 4 core CPU here. Whatever does that have to do with the problem ? > My only other suggestion is to make sure you have not run out of space, > either hard drive mount point or memory if using tmpfs. > That can cause a strange error > because it fails wherever it runs out of space. > Sometimes it fails at different spots too. There's no reason to expect that here. Thanks for trying, but I believe the problem is somewhere else. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
