Re: [gentoo-user] KDE plasmashell and wallpapers.

2019-12-27 Thread Dale
Peter Humphrey wrote:
> On Tuesday, 24 December 2019 20:42:07 GMT Dale wrote:
>
>> I think I'm just going to have to whittle down the number for a while. 
>> Maybe later on a fix will come along.  Maybe. 
> What happens if you switch off file indexing in the control panel, or just 
> its 
> subsidiary option Also Index file content? Workspace > Search > Enable File 
> Search.
>


I looked around in the System Settings window and can't find that
setting.  Am I looking in the right place?  I sort of think this is a
separate thing tho.  It may be using the same tool but won't be
controlled by system settings.  Anything is possible tho.  I'll
certainly test the option if I can find it. ;-)

Here's what I did test tho.  I added a couple more smaller directories. 
It would make short use of the CPU but it seemed to finish.  Then I
picked one that is plenty large enough to allow me to see just how long
it takes.  The directory I used has a little under 800 sub-directories
and about 13,700 files.  When I added it, it pegged one core at 100% for
over a minute.  It seemed to finish its task and went back to normal. 
During that, the desktop locked up just like it did on login when the
huge directory was selected.  The next test, see if it does it at each
login or if it only does it once and then on the next login, it uses the
previously generated index/db/whatever or if it repeats building that
index/db/whatever on each login.  If it is the former, I can add them a
little at a time and work with that. If it is the later one, well,
that's a issue.

Thing is, if the tool that is used to do this is turned off, it may
break the slideshow option as well since it seems pretty much bent on
building a index/db of these images.  While the devs may be using a
buggy tool, as Wols pointed out, it seems that having a large number of
wallpapers just isn't feasible at the moment.  Either the devs need to
change the tool or change the way it works without that tool at all, the
way KDE3 did it for example. 

Maybe a fix will be upcoming, eventually. 

Dale

:-)  :-) 

P. S.  Some may recall me using a HDMI splitter to run my TV in my
bedroom and living room at the same time with the same video. I
mentioned once that my bedroom TV would blink from a brief signal loss. 
It would only be a second or so but it was annoying.  I replaced the
HDMI cable, no problems since. I have not seen a single blink. Odd thing
is, the first cable was pricey.  Second cable was half the cost.  Go
figure.  ROFL 



Re: [gentoo-user] "Application Menu" missing on Desktop after KDE/Plasma update from 5.16.5 to 5.17.4

2019-12-27 Thread Dale
Dan Johansson wrote:
> After updating KDE/Plasma from 5.16.5 to 5.17.4 "Left Button"
> (Application Launcher) does not work anymore. Nothing happens when I
> "Left Click" on the Desktop. The other actions ("Right Button",
> "Middle Button" and "Vertical Scroll") works as they should.
>
> This happens on two machines of mine (the two with KDE/Plasma).
>
> This is really annoying as this is the main way I launch new programs.
>
> Any suggestion?
>
> Regards,


I'd suspect something is missing.  Since mine works here, I'll post some
info and if no one else comes up with a better idea, maybe you can
compare yours and mine and notice something missing or different. 


root@fireball / # equery f kde-frameworks/plasma | grep menu
/usr/lib64/qt5/qml/QtQuick/Controls.2/Plasma/Menu.qml
/usr/lib64/qt5/qml/QtQuick/Controls.2/Plasma/MenuItem.qml
/usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/EditMenuTouch.qml
/usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/MenuBarStyle.qml
/usr/lib64/qt5/qml/QtQuick/Controls/Styles/Plasma/MenuStyle.qml
/usr/lib64/qt5/qml/org/kde/plasma/calendar/MonthMenu.qml
/usr/lib64/qt5/qml/org/kde/plasma/components.3/Menu.qml
/usr/lib64/qt5/qml/org/kde/plasma/components.3/MenuItem.qml
/usr/lib64/qt5/qml/org/kde/plasma/components/ContextMenu.qml
/usr/lib64/qt5/qml/org/kde/plasma/components/ModelContextMenu.qml
root@fireball / #


root@fireball / # equery f kde-plasma/plasma-desktop | grep menu
/usr/share/help/en/plasma-desktop/application-menu.png
/usr/share/kservices5/ServiceMenus
/usr/share/kservices5/ServiceMenus/installfont.desktop
/usr/share/kservices5/plasma-layout-template-org.kde.plasma.desktop.appmenubar.desktop
/usr/share/metainfo/org.kde.plasma.desktop.appmenubar.appdata.xml
/usr/share/plasma/layout-templates/org.kde.plasma.desktop.appmenubar
/usr/share/plasma/layout-templates/org.kde.plasma.desktop.appmenubar/contents
/usr/share/plasma/layout-templates/org.kde.plasma.desktop.appmenubar/contents/layout.js
/usr/share/plasma/layout-templates/org.kde.plasma.desktop.appmenubar/metadata.desktop
/usr/share/plasma/layout-templates/org.kde.plasma.desktop.appmenubar/metadata.json
/usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/ActionMenu.qml
/usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/MenuRepresentation.qml
/usr/share/plasma/plasmoids/org.kde.plasma.kickoff/contents/ui/ActionMenu.qml
/usr/share/plasma/plasmoids/org.kde.plasma.kimpanel/contents/ui/ActionMenu.qml
/usr/share/plasma/plasmoids/org.kde.plasma.kimpanel/contents/ui/ContextMenu.qml
/usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/ContextMenu.qml
/usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/panelconfiguration/MoreSettingsMenu.qml
root@fireball / #

root@fireball / # equery f kde-plasma/plasma-workspace | grep menu
/etc/xdg/autostart/gmenudbusmenuproxy.desktop
/usr/bin/gmenudbusmenuproxy
/usr/lib64/qt5/plugins/kf5/kded/appmenu.so
/usr/lib64/qt5/plugins/plasma/applets/plasma_applet_appmenu.so
/usr/lib64/qt5/plugins/plasma/containmentactions/plasma_containmentactions_contextmenu.so
/usr/lib64/qt5/qml/org/kde/plasma/private/appmenu
/usr/lib64/qt5/qml/org/kde/plasma/private/appmenu/libappmenuplugin.so
/usr/lib64/qt5/qml/org/kde/plasma/private/appmenu/qmldir
/usr/share/dbus-1/interfaces/com.canonical.AppMenu.Registrar.xml
/usr/share/dbus-1/interfaces/org.kde.kappmenu.xml
/usr/share/desktop-directories/kf5-settingsmenu.directory
/usr/share/kservices5/plasma-applet-org.kde.plasma.appmenu.desktop
/usr/share/metainfo/org.kde.plasma.appmenu.appdata.xml
/usr/share/plasma/plasmoids/org.kde.plasma.appmenu
/usr/share/plasma/plasmoids/org.kde.plasma.appmenu/contents
/usr/share/plasma/plasmoids/org.kde.plasma.appmenu/contents/config
/usr/share/plasma/plasmoids/org.kde.plasma.appmenu/contents/config/config.qml
/usr/share/plasma/plasmoids/org.kde.plasma.appmenu/contents/config/main.xml
/usr/share/plasma/plasmoids/org.kde.plasma.appmenu/contents/ui
/usr/share/plasma/plasmoids/org.kde.plasma.appmenu/contents/ui/configGeneral.qml
/usr/share/plasma/plasmoids/org.kde.plasma.appmenu/contents/ui/main.qml
/usr/share/plasma/plasmoids/org.kde.plasma.appmenu/metadata.desktop
/usr/share/plasma/plasmoids/org.kde.plasma.appmenu/metadata.json
/usr/share/plasma/plasmoids/org.kde.plasma.clipboard/contents/ui/Menu.qml
/usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/MonthMenu.qml
/usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/EditContextMenu.qml
/usr/share/sddm/themes/breeze/BreezeMenuStyle.qml
root@fireball / #

I don't see any USE flags that would matter but just in case.

root@fireball / # emerge -p kde-frameworks/plasma
kde-plasma/plasma-desktop kde-plasma/plasma-workspace

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ~] kde-frameworks/plasma-5.65.0:5/5.65::gentoo  USE="X
-debug -doc (-gles2) -test -wayland" 0 KiB
[ebuild   R    ] kde-plasma/plasma-workspace-5.17.4-r1:5::gentoo 
USE="calendar 

[gentoo-user] "Application Menu" missing on Desktop after KDE/Plasma update from 5.16.5 to 5.17.4

2019-12-27 Thread Dan Johansson
After updating KDE/Plasma from 5.16.5 to 5.17.4 "Left Button" 
(Application Launcher) does not work anymore. Nothing happens when I 
"Left Click" on the Desktop. The other actions ("Right Button", "Middle 
Button" and "Vertical Scroll") works as they should.


This happens on two machines of mine (the two with KDE/Plasma).

This is really annoying as this is the main way I launch new programs.

Any suggestion?

Regards,
--
Dan Johansson,
***
This message is printed on 100% recycled electrons!
***



Re: [gentoo-user] NFS problem

2019-12-27 Thread Peter Humphrey
On Tuesday, 24 December 2019 06:11:12 GMT J. Roeleveld wrote:
> What happens when you remove the IPv6 adresses from the NFS config? As you
> are using IPv4, those should not be needed.

After losing my little server I decided to recommission another box I had 
handy. It's a four-core, 64-bit Celeron box, so it's a lot more powerful than 
the Atom. Then I tested using that as NFS host and this box as NFS client.

I tried removing all references to IPv6 under /etc on both machines, but still 
got "No such file or directory." So I recompiled both kernels without IPv6, 
shut down the DSL router and checked that no IPv6 addresses were present on 
the two-machine LAN. I still got the same error.

Ergo, IPv6 is a red herring, and I'm left with some misconfiguration of NFS 
between the two machines. Everything is now as I wrote the first time, except 
for IPv6 addresses which are all commented out pro tem.

-- 
Regards,
Peter.






Re: [gentoo-user] Re: startx does not work for AMD/ATI Radion HD 4770

2019-12-27 Thread gevisz
пт, 27 дек. 2019 г. в 09:48, Ian Zimmerman :
>
> On 2019-12-26 18:12, gevisz wrote:
>
> > It seems that it finally was satisfied with those two blobs added.
> > At least I can now start twm.
>
> Good that you have a working system.  But it should _not_ be necessary
> to build the blobs into the kernel.  I have similar hardware (Gigabyte
> mobo with a Phenom and a Radeon) and I get by just fine with the blobs
> in /lib/firmware/radeon/* .
>
> I know they are being loaded because I patched my kernel to tell me in
> demsg, even in the case of success.
>
> qfile says these files belong to the linux-firmware package.  Do you
> have it installed?  And are they in the right location, /lib/firmware?
> I can see potential for mischief with the recent lib / lib64 migration.

All those blobs are from /lib/firmware/radeon. The problem was that
they were not mentioned in the documentation as needed for my
Radeon HD 4770 video card.