[gentoo-user] fdm fails during ./configure: libssl not found
--- fdm-1.9 consistently fails to build, with configure citing a lack of libssl as the reason. I have openssl installed, and /usr/lib64/libssl.so (symlink to /usr/lib64/libssl.so.1.1) exists. I've looked for similar problems online, with no luck. It originally seemed to be related to a broken version of openssl being unmasked along with the use of ~amd64 in ACCEPT_KEYWORDS, but resolving that made no difference. It seems to me that fdm's config scripts simply can't find libssl, but they appear to be looking in all of the correct places. I had it installed and working in the past, but it was removed due to a stupid (on my part) accident with emerge --depclean and now fails to reinstall. Output of emerge -pqv 'net-mail/fdm-1.9::gentoo': http://dpaste.com/2B1YBPZ //emerge -pqv Output of emerge --info 'net-mail/fdm-1.9::gentoo': http://dpaste.com/0D1PK0E //emerge --info Contents of build.log: http://dpaste.com/1CFZF87 //build.log Contents of portage environment file: http://dpaste.com/2XJD461 //environment
Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]
Mick wrote: > On Monday, 24 June 2019 23:41:03 BST Neil Bothwick wrote: >> On Mon, 24 Jun 2019 21:19:09 +0100, Mick wrote: >>> Can someone please explain how the removal of the 'wireless' USE flag >>> from powerdevil ends up with no buttons for Suspend-to-RAM, >>> Hibernation, Reboot or Shutdown under the Leave tab of the KMenu? What >>> does wireless have to do with those functions which should work >>> regardless? >> Those options are still present here. > Thanks Neil, these are the packages which were depcleaned following USE="- > wireless" for powerdevil, USE="-espeak" for speech-dispatcher and USE="device- > mapper-only -thin" for lvm: > > 1561390348: Started emerge on: Jun 24, 2019 16:32:28 > 1561390348: *** emerge --ask --verbose --depclean > 1561390348: >>> depclean > 1561390428: === Unmerging... (virtual/w3m-0) > 1561390432: >>> unmerge success: virtual/w3m-0 > 1561390432: === Unmerging... (virtual/linux-sources-3) > 1561390436: >>> unmerge success: virtual/linux-sources-3 > 1561390436: === Unmerging... (kde-frameworks/networkmanager-qt-5.57.0) > 1561390440: >>> unmerge success: kde-frameworks/networkmanager-qt-5.57.0 > 1561390440: === Unmerging... (sys-block/thin-provisioning-tools-0.7.0) > 1561390445: >>> unmerge success: sys-block/thin-provisioning-tools-0.7.0 > 1561390445: === Unmerging... (app-accessibility/espeak-1.48.04-r1) > 1561390449: >>> unmerge success: app-accessibility/espeak-1.48.04-r1 > 1561390449: === Unmerging... (www-client/w3m-0.5.3_p20180125) > 1561390453: >>> unmerge success: www-client/w3m-0.5.3_p20180125 > 1561390453: === Unmerging... (media-sound/sox-14.4.2-r1) > 1561390458: >>> unmerge success: media-sound/sox-14.4.2-r1 > 1561390458: === Unmerging... (net-misc/networkmanager-1.16.0) > 1561390464: >>> unmerge success: net-misc/networkmanager-1.16.0 > 1561390464: === Unmerging... (net-dialup/ppp-2.4.7-r7) > 1561390468: >>> unmerge success: net-dialup/ppp-2.4.7-r7 > 1561390468: === Unmerging... (net-misc/dhcp-4.4.1) > 1561390473: >>> unmerge success: net-misc/dhcp-4.4.1 > 1561390473: === Unmerging... (dev-libs/boehm-gc-7.6.4) > 1561390478: >>> unmerge success: dev-libs/boehm-gc-7.6.4 > 1561390478: === Unmerging... (media-sound/gsm-1.0.13-r1) > 1561390482: >>> unmerge success: media-sound/gsm-1.0.13-r1 > 1561390482: === Unmerging... (net-libs/libndp-1.7) > 1561390486: >>> unmerge success: net-libs/libndp-1.7 > 1561390486: === Unmerging... (net-misc/modemmanager-1.8.2-r1) > 1561390493: >>> unmerge success: net-misc/modemmanager-1.8.2-r1 > 1561390493: === Unmerging... (dev-libs/newt-0.52.20) > 1561390497: >>> unmerge success: dev-libs/newt-0.52.20 > 1561390497: === Unmerging... (net-dialup/ppp-scripts-0) > 1561390501: >>> unmerge success: net-dialup/ppp-scripts-0 > 1561390501: === Unmerging... (sys-libs/slang-2.3.2) > 1561390505: >>> unmerge success: sys-libs/slang-2.3.2 > 1561390505: === Unmerging... (net-libs/libqmi-1.20.2) > 1561390510: >>> unmerge success: net-libs/libqmi-1.20.2 > 1561390510: === Unmerging... (net-libs/libmbim-1.16.2) > 1561390515: >>> unmerge success: net-libs/libmbim-1.16.2 > 1561390515: *** exiting successfully. > 1561390515: *** terminating. > 1561390536: Started emerge on: Jun 24, 2019 16:35:36 > 1561390536: *** emerge --ask --verbose @preserved-rebuild > 1561390543: *** exiting successfully. > 1561390543: *** terminating. > > I can't see anything in there. I also uninstalled and reinstalled plasma- > meta, but did not depclean anything. Could there be something in > systemsettings? Yep! Power Management is greyed out: > > "Power management configuration module could not be loaded. The Power > Management Service appears not to be running. This can be solved by starting > or scheduling it inside "Startup and Shutdown". > > What am I supposed to add in "Startup and Shutdown"? There is no Power > Management to start up and no button to add any services. :-/ > I wonder if something is trying to use a old config file. You may want to use checkrestart, needrestart or something to check on that. I still have checkrestart here but needrestart should pick this up. If it is that, logout, got to a console and restart X. I sometimes just go to the boot runlevel, make sure no KDE/sddm processes are still running by killing anything that shouldn't be running and then go back to default runlevel. KDE is bad to leave processes running. If that does nothing, try revdep-rebuild and see if it catches anything. Maybe a emerge -uaDN world will help too. Lots of options. When I did this a good while back, it got a bit dirty before I got things cleaned out. Dale :-) :-)
Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]
On Monday, 24 June 2019 23:41:03 BST Neil Bothwick wrote: > On Mon, 24 Jun 2019 21:19:09 +0100, Mick wrote: > > Can someone please explain how the removal of the 'wireless' USE flag > > from powerdevil ends up with no buttons for Suspend-to-RAM, > > Hibernation, Reboot or Shutdown under the Leave tab of the KMenu? What > > does wireless have to do with those functions which should work > > regardless? > > Those options are still present here. Thanks Neil, these are the packages which were depcleaned following USE="- wireless" for powerdevil, USE="-espeak" for speech-dispatcher and USE="device- mapper-only -thin" for lvm: 1561390348: Started emerge on: Jun 24, 2019 16:32:28 1561390348: *** emerge --ask --verbose --depclean 1561390348: >>> depclean 1561390428: === Unmerging... (virtual/w3m-0) 1561390432: >>> unmerge success: virtual/w3m-0 1561390432: === Unmerging... (virtual/linux-sources-3) 1561390436: >>> unmerge success: virtual/linux-sources-3 1561390436: === Unmerging... (kde-frameworks/networkmanager-qt-5.57.0) 1561390440: >>> unmerge success: kde-frameworks/networkmanager-qt-5.57.0 1561390440: === Unmerging... (sys-block/thin-provisioning-tools-0.7.0) 1561390445: >>> unmerge success: sys-block/thin-provisioning-tools-0.7.0 1561390445: === Unmerging... (app-accessibility/espeak-1.48.04-r1) 1561390449: >>> unmerge success: app-accessibility/espeak-1.48.04-r1 1561390449: === Unmerging... (www-client/w3m-0.5.3_p20180125) 1561390453: >>> unmerge success: www-client/w3m-0.5.3_p20180125 1561390453: === Unmerging... (media-sound/sox-14.4.2-r1) 1561390458: >>> unmerge success: media-sound/sox-14.4.2-r1 1561390458: === Unmerging... (net-misc/networkmanager-1.16.0) 1561390464: >>> unmerge success: net-misc/networkmanager-1.16.0 1561390464: === Unmerging... (net-dialup/ppp-2.4.7-r7) 1561390468: >>> unmerge success: net-dialup/ppp-2.4.7-r7 1561390468: === Unmerging... (net-misc/dhcp-4.4.1) 1561390473: >>> unmerge success: net-misc/dhcp-4.4.1 1561390473: === Unmerging... (dev-libs/boehm-gc-7.6.4) 1561390478: >>> unmerge success: dev-libs/boehm-gc-7.6.4 1561390478: === Unmerging... (media-sound/gsm-1.0.13-r1) 1561390482: >>> unmerge success: media-sound/gsm-1.0.13-r1 1561390482: === Unmerging... (net-libs/libndp-1.7) 1561390486: >>> unmerge success: net-libs/libndp-1.7 1561390486: === Unmerging... (net-misc/modemmanager-1.8.2-r1) 1561390493: >>> unmerge success: net-misc/modemmanager-1.8.2-r1 1561390493: === Unmerging... (dev-libs/newt-0.52.20) 1561390497: >>> unmerge success: dev-libs/newt-0.52.20 1561390497: === Unmerging... (net-dialup/ppp-scripts-0) 1561390501: >>> unmerge success: net-dialup/ppp-scripts-0 1561390501: === Unmerging... (sys-libs/slang-2.3.2) 1561390505: >>> unmerge success: sys-libs/slang-2.3.2 1561390505: === Unmerging... (net-libs/libqmi-1.20.2) 1561390510: >>> unmerge success: net-libs/libqmi-1.20.2 1561390510: === Unmerging... (net-libs/libmbim-1.16.2) 1561390515: >>> unmerge success: net-libs/libmbim-1.16.2 1561390515: *** exiting successfully. 1561390515: *** terminating. 1561390536: Started emerge on: Jun 24, 2019 16:35:36 1561390536: *** emerge --ask --verbose @preserved-rebuild 1561390543: *** exiting successfully. 1561390543: *** terminating. I can't see anything in there. I also uninstalled and reinstalled plasma- meta, but did not depclean anything. Could there be something in systemsettings? Yep! Power Management is greyed out: "Power management configuration module could not be loaded. The Power Management Service appears not to be running. This can be solved by starting or scheduling it inside "Startup and Shutdown". What am I supposed to add in "Startup and Shutdown"? There is no Power Management to start up and no button to add any services. :-/ -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] What the devil?!! [or Plasma teething problems Ia.]
On Mon, 24 Jun 2019 21:19:09 +0100, Mick wrote: > Can someone please explain how the removal of the 'wireless' USE flag > from powerdevil ends up with no buttons for Suspend-to-RAM, > Hibernation, Reboot or Shutdown under the Leave tab of the KMenu? What > does wireless have to do with those functions which should work > regardless? Those options are still present here. -- Neil Bothwick A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? pgp_XMVht9Wx9.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Plasma teething problems - Part II
On Mon, 24 Jun 2019 21:54:20 +0100, Mick wrote: > >>> 'Selected' packages are slated for removal. > >>> 'Protected' and 'omitted' packages will not be removed. > > I need to find a different solution ... The solution I opted for was to create a kde5 set containing the apps I wanted, then emerge -n @kde5. Then it was just a case of running emerge -cp to see if there was anything else I needed to add to the set before depcleaning in anger. -- Neil Bothwick Help a man when he is in trouble and he will remember you when he is in trouble again pgpHcwunti6vw.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Strange behavior of "tab" key with Libreoffice Calc and Plasma
190624 Mick wrote: > It depends on which VLC plugin is used, KDE or Gtk. > Go to Help/About and you can see when loaded with the KDE VLC plugin > the 'tab-losing-cell-focus' bug is present. > With the Gtk VLC plugin loaded, the tab works as it should. I don't see anything re a bug, but it does say 'VLC: gtk3'. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] Plasma teething problems - Part II
On 2019.06.24 16:54, Mick wrote: On Monday, 24 June 2019 21:40:07 BST you wrote: > On Monday, 24 June 2019 21:16:51 BST Dale wrote: > > I went through this a few years ago. I had some large programs > > installed that I didn't use, Kmail and others. I wanted to clean them > > out but at the time I had installed KDE with kde-meta. Basically, that > > installs everything KDE, wanted or not. I uninstalled that and went > > > these instead: > According to the current wiki page these days the kde-meta has been replaced > with plasma-meta. This is how I have configured plasma-meta: > > Installed versions: 5.15.5(5)(12:58:00 14/06/19)(bluetooth browser- > integration crypt desktop-portal display-manager elogind handbook legacy- > systray pam pm-utils sddm wallpapers -consolekit -discover -grub -gtk - > networkmanager -plymouth -pulseaudio -sdk -systemd) > > BUT ... I am thinking of uninstalling it, deplclean-ing my world and > installing kde-plasma/plasma-desktop which is the slim version, while > keeping some select kde-meta packages I need/want. > > > root@fireball / # equery list *kde*meta* > > > > * Searching for *kde*meta* ... > > > > [IP-] [ ] kde-apps/kdeadmin-meta-19.04.2:5 > > I have this installed too. > > > [IP-] [ ] kde-apps/kdebase-meta-19.04.2:5 > > I think the kdebase-meta was meant to be a transitional package from KDE4 to > plasma/KDE5. I suspect this has been superseded by kde-plasma/plasma-meta, > but I'm not sure. In any case, I do not have this installed. > > > [IP-] [ ] kde-apps/kdecore-meta-19.04.2:5 > > I have this installed too. > > > [IP-] [ ] kde-apps/kdegames-meta-19.04.2:5 > > No games for me, thanks. > > > [IP-] [ ] kde-apps/kdegraphics-meta-19.04.2:5 > > [IP-] [ ] kde-apps/kdemultimedia-meta-19.04.2:5 > > I have these two installed, plus: > > [IP-] [ ] kde-apps/kdenetwork-meta-18.12.3:5 > [IP-] [ ] kde-apps/kdepim-meta-18.12.3:5 > [IP-] [ ] kde-apps/kdeutils-meta-18.12.3:5 > > > This is one of the things I like about Gentoo, being able to cut off or > > get rid of things I don't want. USE flags help with that a lot. > > > > Glad you got it sorted out. > > Sadly I'm not there yet. I've got to figure out how to get back my Suspend > to Ram, Hibernate, Reboot, and Shutdown buttons, without re-importing > NetworkManager, or at least without having it being started by powerdevil. Hmm ... plasma-desktop was already installed, dragged in by plasma-meta. So no need to reinstall it. Sadly trying to depclean after removing plasma-meta will get rid of a lot of packages, something I'm not keen to do: >>> These are the packages that would be unmerged: [snip long list of packages] I just chose the specific packages I wanted and explicitly emerged them. You can just add them to your world file (either manually, or with "emerge --noreplace package" so they won't be depcleaned. I have lots of kde stuff (37 items from grep kde worldfile) but kdecore-meta and kdegraphics-meta are the only meta packages in my world file. Jack
Re: [gentoo-user] Plasma teething problems - Part II
On Monday, 24 June 2019 21:40:07 BST you wrote: > On Monday, 24 June 2019 21:16:51 BST Dale wrote: > > I went through this a few years ago. I had some large programs > > installed that I didn't use, Kmail and others. I wanted to clean them > > out but at the time I had installed KDE with kde-meta. Basically, that > > installs everything KDE, wanted or not. I uninstalled that and went > > > these instead: > According to the current wiki page these days the kde-meta has been replaced > with plasma-meta. This is how I have configured plasma-meta: > > Installed versions: 5.15.5(5)(12:58:00 14/06/19)(bluetooth browser- > integration crypt desktop-portal display-manager elogind handbook legacy- > systray pam pm-utils sddm wallpapers -consolekit -discover -grub -gtk - > networkmanager -plymouth -pulseaudio -sdk -systemd) > > BUT ... I am thinking of uninstalling it, deplclean-ing my world and > installing kde-plasma/plasma-desktop which is the slim version, while > keeping some select kde-meta packages I need/want. > > > root@fireball / # equery list *kde*meta* > > > > * Searching for *kde*meta* ... > > > > [IP-] [ ] kde-apps/kdeadmin-meta-19.04.2:5 > > I have this installed too. > > > [IP-] [ ] kde-apps/kdebase-meta-19.04.2:5 > > I think the kdebase-meta was meant to be a transitional package from KDE4 to > plasma/KDE5. I suspect this has been superseded by kde-plasma/plasma-meta, > but I'm not sure. In any case, I do not have this installed. > > > [IP-] [ ] kde-apps/kdecore-meta-19.04.2:5 > > I have this installed too. > > > [IP-] [ ] kde-apps/kdegames-meta-19.04.2:5 > > No games for me, thanks. > > > [IP-] [ ] kde-apps/kdegraphics-meta-19.04.2:5 > > [IP-] [ ] kde-apps/kdemultimedia-meta-19.04.2:5 > > I have these two installed, plus: > > [IP-] [ ] kde-apps/kdenetwork-meta-18.12.3:5 > [IP-] [ ] kde-apps/kdepim-meta-18.12.3:5 > [IP-] [ ] kde-apps/kdeutils-meta-18.12.3:5 > > > This is one of the things I like about Gentoo, being able to cut off or > > get rid of things I don't want. USE flags help with that a lot. > > > > Glad you got it sorted out. > > Sadly I'm not there yet. I've got to figure out how to get back my Suspend > to Ram, Hibernate, Reboot, and Shutdown buttons, without re-importing > NetworkManager, or at least without having it being started by powerdevil. Hmm ... plasma-desktop was already installed, dragged in by plasma-meta. So no need to reinstall it. Sadly trying to depclean after removing plasma-meta will get rid of a lot of packages, something I'm not keen to do: >>> These are the packages that would be unmerged: kde-plasma/plasma-browser-integration selected: 5.15.5 protected: none omitted: none kde-plasma/plasma-vault selected: 5.15.5 protected: none omitted: none kde-plasma/kdeplasma-addons selected: 5.15.5 protected: none omitted: none kde-plasma/kscreen selected: 5.15.5 protected: none omitted: none kde-plasma/kwrited selected: 5.15.5 protected: none omitted: none kde-plasma/kwayland-integration selected: 5.15.5 protected: none omitted: none kde-plasma/xembed-sni-proxy selected: 5.15.5 protected: none omitted: none kde-plasma/plasma-workspace-wallpapers selected: 5.15.5 protected: none omitted: none kde-plasma/bluedevil selected: 5.15.5 protected: none omitted: none kde-plasma/kgamma selected: 5.15.5 protected: none omitted: none kde-plasma/drkonqi selected: 5.15.5 protected: none omitted: none kde-plasma/kwallet-pam selected: 5.15.5 protected: none omitted: none kde-plasma/user-manager selected: 5.15.5 protected: none omitted: none kde-plasma/xdg-desktop-portal-kde selected: 5.15.5-r1 protected: none omitted: none kde-plasma/kinfocenter selected: 5.15.5 protected: none omitted: none kde-plasma/sddm-kcm selected: 5.15.5 protected: none omitted: none kde-plasma/systemsettings selected: 5.15.5 protected: none omitted: none kde-plasma/kmenuedit selected: 5.15.5 protected: none omitted: none kde-plasma/ksshaskpass selected: 5.15.5 protected: none omitted: none sys-fs/cryfs selected: 0.9.9 protected: none omitted: none dev-libs/libpwquality selected: 1.4.0 protected: none omitted: none kde-frameworks/kxmlrpcclient selected: 5.57.0 protected: none omitted: none kde-frameworks/bluez-qt selected: 5.57.0 protected: none omitted: none sys-apps/accountsservice selected: 0.6.50-r1 protected: none omitted: none net-misc/socat selected: 1.7.3.2 protected: none omitted: none kde-plasma/khotkeys selected: 5.15.5 protected: none omitted: none sys-apps/xdg-desktop-portal selected: 1.2.0 protected: none
Re: [gentoo-user] Plasma teething problems - Part II
On Monday, 24 June 2019 21:16:51 BST Dale wrote: > I went through this a few years ago. I had some large programs > installed that I didn't use, Kmail and others. I wanted to clean them > out but at the time I had installed KDE with kde-meta. Basically, that > installs everything KDE, wanted or not. I uninstalled that and went > these instead: According to the current wiki page these days the kde-meta has been replaced with plasma-meta. This is how I have configured plasma-meta: Installed versions: 5.15.5(5)(12:58:00 14/06/19)(bluetooth browser- integration crypt desktop-portal display-manager elogind handbook legacy- systray pam pm-utils sddm wallpapers -consolekit -discover -grub -gtk - networkmanager -plymouth -pulseaudio -sdk -systemd) BUT ... I am thinking of uninstalling it, deplclean-ing my world and installing kde-plasma/plasma-desktop which is the slim version, while keeping some select kde-meta packages I need/want. > root@fireball / # equery list *kde*meta* > * Searching for *kde*meta* ... > [IP-] [ ] kde-apps/kdeadmin-meta-19.04.2:5 I have this installed too. > [IP-] [ ] kde-apps/kdebase-meta-19.04.2:5 I think the kdebase-meta was meant to be a transitional package from KDE4 to plasma/KDE5. I suspect this has been superseded by kde-plasma/plasma-meta, but I'm not sure. In any case, I do not have this installed. > [IP-] [ ] kde-apps/kdecore-meta-19.04.2:5 I have this installed too. > [IP-] [ ] kde-apps/kdegames-meta-19.04.2:5 No games for me, thanks. > [IP-] [ ] kde-apps/kdegraphics-meta-19.04.2:5 > [IP-] [ ] kde-apps/kdemultimedia-meta-19.04.2:5 I have these two installed, plus: [IP-] [ ] kde-apps/kdenetwork-meta-18.12.3:5 [IP-] [ ] kde-apps/kdepim-meta-18.12.3:5 [IP-] [ ] kde-apps/kdeutils-meta-18.12.3:5 > This is one of the things I like about Gentoo, being able to cut off or > get rid of things I don't want. USE flags help with that a lot. > > Glad you got it sorted out. Sadly I'm not there yet. I've got to figure out how to get back my Suspend to Ram, Hibernate, Reboot, and Shutdown buttons, without re-importing NetworkManager, or at least without having it being started by powerdevil. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] What the devil?!! [or Plasma teething problems Ia.]
Can someone please explain how the removal of the 'wireless' USE flag from powerdevil ends up with no buttons for Suspend-to-RAM, Hibernation, Reboot or Shutdown under the Leave tab of the KMenu? What does wireless have to do with those functions which should work regardless? Also, the sddm DM shutdown/reboot buttons now do not work. O_O Is Plasma/KDE trying to emulate the inflexibility of Gnome? (no flamewar intended please). -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Plasma teething problems - Part II
Mick wrote: > On Monday, 24 June 2019 12:44:34 BST Dale wrote: >> Mick wrote: >>> I often find a number of speech-dispatcher processes running: >>> 4732 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy >>> /etc/> >>> speech-dispatcher/modules/dummy.conf >>> >>> 4734 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_generic >>> / >>> >>> etc/speech-dispatcher/modules/generic.conf >>> >>> 4736 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_cicero >>> / >>> >>> etc/speech-dispatcher/modules/cicero.conf >>> >>> 4737 ?Z 0:00 \_ [sd_cicero] >>> 4739 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_espeak >>> / >>> >>> etc/speech-dispatcher/modules/espeak.conf >>> >>> 4744 ?Ssl0:00 /usr/bin/speech-dispatcher --spawn >>> --communication-> >>> method unix_socket --socket-path >>> /run/user/1000/speech-dispatcher/speechd.sock >>> >>> I don't know what is starting these processes or what they have to offer >>> to my desktop. Checking systemsettings5/Accessibility Options/Screen >>> Reader, I can see it is NOT enabled. >>> >>> How can I get rid of these? >> I would start out by finding out what package /usr/bin/speech-dispatcher >> belongs too. Equery can help with that but other tools can as well. >> Once you find that, then check the USE flags to see what can be adjusted >> to get rid if that. I don't have it here so I can't do it on my system. >> >> Dale >> >> :-) :-) > Good call Dale, here's what I found: > > app-accessibility/speech-dispatcher is required by dev-qt/qtspeech, > > which is required by kde-apps/kdepim-runtime and kde-apps/kpimtextedit, > neither of which have a USE flag to stop speech-dispatcher kicking off. > > However, speech-dispatcher has USE="espeak" enabled, which I will try to > disable and see what happens thereafter. > I went through this a few years ago. I had some large programs installed that I didn't use, Kmail and others. I wanted to clean them out but at the time I had installed KDE with kde-meta. Basically, that installs everything KDE, wanted or not. I uninstalled that and went these instead: root@fireball / # equery list *kde*meta* * Searching for *kde*meta* ... [IP-] [ ] kde-apps/kdeadmin-meta-19.04.2:5 [IP-] [ ] kde-apps/kdebase-meta-19.04.2:5 [IP-] [ ] kde-apps/kdecore-meta-19.04.2:5 [IP-] [ ] kde-apps/kdegames-meta-19.04.2:5 [IP-] [ ] kde-apps/kdegraphics-meta-19.04.2:5 [IP-] [ ] kde-apps/kdemultimedia-meta-19.04.2:5 root@fireball / # Of course, there was still things I wanted to remove because I didn't use them. Of course there was things I wanted that I had to install manually as well. I got rid of some things with USE flags and others I just had to live with. Still, I slimmed it down a lot. If I put in more effort, I could slim it down more I suspect but it's close enough. This is one of the things I like about Gentoo, being able to cut off or get rid of things I don't want. USE flags help with that a lot. Glad you got it sorted out. Dale :-) :-)
Re: [gentoo-user] Strange behavior of "tab" key with Libreoffice Calc and Plasma
On Monday, 24 June 2019 21:11:48 BST Philip Webb wrote:
> 190624 Stefano Crocco wrote:
> > On domenica 23 giugno 2019 22:31:33 CEST Philip Webb wrote:
> >> That's what it does for me now, using LO 6.2.4.2 on KDE.
> >> Here, pressing Tab-Tab simply moves 2 cells to the right.
> >
> > Do you have the kde use flag enabled ?
> > This morning I've tried several combinations of flags
> > and only disabling the kde one this issue disappeared.
>
> root:529 ~> eix libreoffice
> [I] app-office/libreoffice
> Available versions: 6.1.5.2 6.2.4.2 **6.2. ** {accessibility
> bluetooth +branding coinmp +cups dbus debug eds firebird googledrive
> gstreamer +gtk gtk2 java kde ldap +mariadb mysql odk pdfimport postgres
> test vlc ELIBC="FreeBSD" LIBREOFFICE_EXTENSIONS="nlpsolver
> scripting-beanshell scripting-javascript wiki-publisher"
> PYTHON_SINGLE_TARGET="python2_7 python3_5 python3_6 python3_7"
> PYTHON_TARGETS="python2_7 python3_5 python3_6 python3_7"} Installed
> versions: 6.2.4.2([2019-06-19 06:18:11])(accessibility cups dbus gtk gtk2
> pdfimport -bluetooth -branding -coinmp -debug -eds -firebird -googledrive
> -gstreamer -java -kde -ldap -mariadb -odk -postgres -test -vlc
> ELIBC="-FreeBSD" LIBREOFFICE_EXTENSIONS="-nlpsolver -scripting-beanshell
> -scripting-javascript -wiki-publisher" PYTHON_SINGLE_TARGET="python3_6
> -python2_7 -python3_5 -python3_7" PYTHON_TARGETS="python2_7 python3_6
> -python3_5 -python3_7")
>
> So, yes (smile).
It depends on which VLC plugin is used, KDE, or Gtk. Go to Help/About and you
can see when loaded with the KDE VLC plugin the 'tab-losing-cell-focus' bug is
present. With the Gtk VLC plugin loaded, the tab works as it should.
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] Strange behavior of "tab" key with Libreoffice Calc and Plasma
190624 Stefano Crocco wrote:
> On domenica 23 giugno 2019 22:31:33 CEST Philip Webb wrote:
>> That's what it does for me now, using LO 6.2.4.2 on KDE.
>> Here, pressing Tab-Tab simply moves 2 cells to the right.
> Do you have the kde use flag enabled ?
> This morning I've tried several combinations of flags
> and only disabling the kde one this issue disappeared.
root:529 ~> eix libreoffice
[I] app-office/libreoffice
Available versions: 6.1.5.2 6.2.4.2 **6.2. ** {accessibility
bluetooth +branding coinmp +cups dbus debug eds firebird googledrive gstreamer
+gtk gtk2 java kde ldap +mariadb mysql odk pdfimport postgres test vlc
ELIBC="FreeBSD" LIBREOFFICE_EXTENSIONS="nlpsolver scripting-beanshell
scripting-javascript wiki-publisher" PYTHON_SINGLE_TARGET="python2_7 python3_5
python3_6 python3_7" PYTHON_TARGETS="python2_7 python3_5 python3_6 python3_7"}
Installed versions: 6.2.4.2([2019-06-19 06:18:11])(accessibility cups dbus
gtk gtk2 pdfimport -bluetooth -branding -coinmp -debug -eds -firebird
-googledrive -gstreamer -java -kde -ldap -mariadb -odk -postgres -test -vlc
ELIBC="-FreeBSD" LIBREOFFICE_EXTENSIONS="-nlpsolver -scripting-beanshell
-scripting-javascript -wiki-publisher" PYTHON_SINGLE_TARGET="python3_6
-python2_7 -python3_5 -python3_7" PYTHON_TARGETS="python2_7 python3_6
-python3_5 -python3_7")
So, yes (smile).
--
,,
SUPPORT ___//___, Philip Webb
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto
TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] why does Udisks require Lvm2 ?
On Mon, 24 Jun 2019 12:22:09 -0600, Grant Taylor wrote: > > Of course it is, a RAID1 device is just a block device on which you > > can put any filesystem you like. RAID and LVM are complementary > > technologies that work well together, but neither needs the others > > (apart from the device-mapper bit). > > Eh. LVM can require RAID (multiple devices) without actually using MD > outside of LVM. Can require, not does require. It is perfectly possible to use LVM on a single disk. There are situations where you use the two together, but no requirement to do so in all use cases. -- Neil Bothwick Top Oxymorons Number 35: Legally drunk pgpPSPhlkrrB9.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Strange behavior of "tab" key with Libreoffice Calc and Plasma
On lunedì 24 giugno 2019 13:44:04 CEST you wrote: > On domenica 23 giugno 2019 21:40:53 CEST Neil Bothwick wrote: > > On Sun, 23 Jun 2019 20:59:34 +0200, Stefano Crocco wrote: > > > a few months ago I started noticing a very annoying behavior when > > > pressing the "tab" key in Libreoffice Calc. Previously, pressing this > > > key would move the cursor by one cell to the right, so that I could > > > immediately start writing into the cell. Now, while the cursor is moved > > > to the correct cell (I can see the black border around it), I can't > > > write in it immediately anymore. To move the cursor to the next cell > > > and be able to immediately write in it, I need to press the tab key > > > twice. It seems that somehow pressing the tab key once gives focus to > > > the menu bar: pressing tab once, then pressing "F" brings down the file > > > menu; pressing tab, then pressing "E" displays the edit menu and so on. > > > > > > Has anyone experienced this behavior? > > > > I see it too and it's annoying as hell. Even more annoying will be that > > when it is solved I will have got into the habit of pressing tab twice > > for each move :( > > I'm (relatively) happy to know I'm not the only one experiencing this issue. > Currently I'm playing around with USE flags to see whether there's a > combination of them which fixes the problem. I think it's somehow caused by > the kde flag: I tried USE="gtk2 kde -gtk", USE="kde -gtk -gtk2" and > USE="gtk -kde -gtk2" and the only configuration where this issue didn't > appear was the one without kde. I've yet to try USE="-gtk2 kde gtk", but I > don't think it'll work. > > I'm getting really annoyed by this, so I think later today I'll file a bug > report. > > Stefano Bug submitted. For anyone interested, here's the link: https://bugs.gentoo.org/688618 Stefano
Re: [gentoo-user] Strange behavior of "tab" key with Libreoffice Calc and Plasma
On domenica 23 giugno 2019 22:31:33 CEST Philip Webb wrote: > 190623 Stefano Crocco wrote: > > a few months ago I started noticing a very annoying behavior > > when pressing the "tab" key in Libreoffice Calc. > > Previously, pressing this key would move the cursor by one cell to the > > right, so that I could immediately start writing into the cell. > > That's what it does for me now, using LO 6.2.4.2 on KDE. > > > Now, while the cursor is moved to the correct cell > > -- I can see the black border around it -- , > > I can't write in it immediately anymore. > > To move the cursor to the next cell and be able to immediately write in > > it, > > I need to press the tab key twice. > > It seems that somehow pressing the tab key once gives focus to the menu > > bar: pressing tab once, then pressing "F" brings down the file menu; > > pressing tab, then pressing "E" displays the edit menu and so on. > > Here, pressing Tab-Tab simply moves 2 cells to the right. Thanks for the answer. Do you have the kde use flag enabled? This morning I've tried several combinations of flags and only disabling the kde one this issue disappeared. Stefano
Re: [gentoo-user] Strange behavior of "tab" key with Libreoffice Calc and Plasma
On domenica 23 giugno 2019 21:40:53 CEST Neil Bothwick wrote: > On Sun, 23 Jun 2019 20:59:34 +0200, Stefano Crocco wrote: > > a few months ago I started noticing a very annoying behavior when > > pressing the "tab" key in Libreoffice Calc. Previously, pressing this > > key would move the cursor by one cell to the right, so that I could > > immediately start writing into the cell. Now, while the cursor is moved > > to the correct cell (I can see the black border around it), I can't > > write in it immediately anymore. To move the cursor to the next cell > > and be able to immediately write in it, I need to press the tab key > > twice. It seems that somehow pressing the tab key once gives focus to > > the menu bar: pressing tab once, then pressing "F" brings down the file > > menu; pressing tab, then pressing "E" displays the edit menu and so on. > > > > Has anyone experienced this behavior? > > I see it too and it's annoying as hell. Even more annoying will be that > when it is solved I will have got into the habit of pressing tab twice > for each move :( I'm (relatively) happy to know I'm not the only one experiencing this issue. Currently I'm playing around with USE flags to see whether there's a combination of them which fixes the problem. I think it's somehow caused by the kde flag: I tried USE="gtk2 kde -gtk", USE="kde -gtk -gtk2" and USE="gtk -kde -gtk2" and the only configuration where this issue didn't appear was the one without kde. I've yet to try USE="-gtk2 kde gtk", but I don't think it'll work. I'm getting really annoyed by this, so I think later today I'll file a bug report. Stefano
Re: [gentoo-user] why does Udisks require Lvm2 ?
On 6/24/19 12:12 PM, Mick wrote: LVM-RAID uses the kernel's mdraid, Yep. You can get device mapper command(s) to show the internal / under the hood MD devices. I feel like what LVM does to mirror (RAID 1) devices is complex. You end up with non-obvious LVs that are then raided together to create another virtual block device that is what you see as the LV. There are options about where and how metadata is mirrored. Some of which is stored in the VG and others is stored in another small hidden LV specifically for this purpose. Which itself can be configured to have multiple copies. At least that's how I remember things from about five years ago. but with less tools to manage the RAID configuration than mdadm offers: That's because the standard LVM tools make calls to the kernel to manage things. I never /needed/ anything other than the LVM tools to administer LVM RAID. But I think that you can find the expected things under device mapper et al. if you know where to go look. When I say "hidden", it seems as if the traditional LVM tools simply don't expose LVs with specific naming patterns unless you go looking for them. Much like dot files are ""hidden by default, but there if you know where and how to look. -- Grant. . . . unix || die
Re: [gentoo-user] Strange behavior of "tab" key with Libreoffice Calc and Plasma
190624 Mick wrote: > On Sunday, 23 June 2019 21:31:33 BST Philip Webb wrote: >> 190623 Stefano Crocco wrote: >>> a few months ago I started noticing a very annoying behavior >>> when pressing the "tab" key in Libreoffice Calc. >>> Previously, pressing this key would move the cursor by one cell to the >>> right, so that I could immediately start writing into the cell. >> That's what it does for me now, using LO 6.2.4.2 on KDE. >> Here, pressing Tab-Tab simply moves 2 cells to the right. > Hmm ... are you running a non-KDE environment by any chance? Plasma-5.15.5 , Frameworks-5.57.0 , Apps-18.12.3 . -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] Plasma teething problems - Part I
On Monday, 24 June 2019 12:31:26 BST Mick wrote: > On Monday, 24 June 2019 12:17:51 BST Neil Bothwick wrote: > > On Mon, 24 Jun 2019 12:00:36 +0100, Mick wrote: > > > Could someone more knowledgeable in Plasma/KDE shenanigans please > > > explain how I can end up with a workable USB wireless dongle, which I > > > can enable/disable at will? > > > > Set USE="-wireless" for powerdevil > > > > I have KDE on this laptop, with no NM. The wireless connection is managed > > by systemd-networkd here, but the same should be possible with openrc and > > no NM. > > Excellent! This is what I was looking for. Thank you Neil. :-) I can attest to the fact powerdevil with its devilish tentacles which dragged in NetworkManager was the cause of my problems, plus KDE's default setting: 'Enable bluetooth integration' was causing all this obex race by dbus. Now I have a 'normal' system to work with. :-) The only thing I noticed after I disabled the wifi, rfkilled it and pulled the USB dongle was this entry in the logs: Jun 24 18:23:51 localhost kernel: usb 1-1: USB disconnect, device number 3 Jun 24 18:23:53 localhost /etc/init.d/net.wlp0s18f2u1[5619]: net.wlp0s18f2u1: not allowed to be hotplugged Jun 24 18:23:53 localhost dhcpcd[3208]: wlp0s18f2u1: removing interface I'm not sure of its meaning ... Is openrc angry with me for unplugging the by definition pluggable and already disabled USB device? :-/ -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] why does Udisks require Lvm2 ?
On 6/24/19 11:47 AM, Neil Bothwick wrote: Of course it is, a RAID1 device is just a block device on which you can put any filesystem you like. RAID and LVM are complementary technologies that work well together, but neither needs the others (apart from the device-mapper bit). Eh. LVM can require RAID (multiple devices) without actually using MD outside of LVM. LVM can do RAID inside of LVM (I think this is fairly atypically done). But it does mean that you can turn physical disks (or better partitions) into Physical Volumes for LVM and then create different Logical Volumes with different RAID properties. I once had a LV w/ RAID 0 striping across multiple PVs with another LV with RAID 5 for redundancy, in the same PVs. This LVM functionality does require RAID (multiple device) support as that's what's used /inside/ (read: under the hood) of LVM. -- Grant. . . . unix || die
Re: [gentoo-user] why does Udisks require Lvm2 ?
On Monday, 24 June 2019 09:40:07 BST Peter Humphrey wrote:
> On Monday, 24 June 2019 08:46:55 BST Neil Bothwick wrote:
> > So the choice is between an unsupported configuration or installing a
> > handful of binaries that you will never use. Unless space was an issue,
> > there's about 6NB difference, I'd go with the latter, although
> > UNSUPPORTED != DOESNOTWORK
>
> Yes, I've done the same on two boxes that have no need of lvm. It does seem
> wasteful though.
>
> I forget the detail now, but a recent-ish version of sys-fs/cryptsetup found
> it needed a hard dependency on some of the code in lvm2. It seems to me
> that we have here an opportunity for redesign of certain packages. ("We"
> the community, that is.)
>
> On this box, which does need lvm for RAID-1 on two SSDs:
>
> $ equery d lvm2
> * These packages depend on lvm2:
> app-emulation/virtualbox-6.0.8 (lvm ? sys-fs/lvm2)
> net-fs/nfs-utils-2.4.1 (nfsv41 ? sys-fs/lvm2)
> sys-block/gparted-0.33.0 (dmraid ? >=sys-fs/lvm2-2.02.45)
> sys-block/parted-3.2_p25 (device-mapper ? >=sys-fs/lvm2-2.02.45)
> sys-fs/cryptsetup-2.1.0 (sys-fs/lvm2[static-libs(+)])
> (sys-fs/lvm2)
> sys-fs/e2fsprogs-1.45.2 (cron ? sys-fs/lvm2[-device-mapper-only(-)])
> sys-fs/udisks-2.8.3 (lvm ? sys-fs/lvm2)
> sys-libs/libblockdev-2.22 (device-mapper ? sys-fs/lvm2)
> (dmraid ? sys-fs/lvm2)
> (lvm ? sys-fs/lvm2)
>
> Other than sys-fs/cryptsetup, those are all conditional dependencies.
Also to mention, the installation following adjustment of the USE flags
completes like so:
* Messages for package sys-fs/lvm2-2.02.184-r4:
* Make sure the "lvm" init script is in the runlevels:
* # rc-update add lvm boot
*
* Make sure to enable lvmetad in /etc/lvm/lvm.conf if you want
* to enable lvm autoactivation and metadata caching.
>>> Auto-cleaning packages...
==
There is no lvm init script left in my system:
# rc-update -s -v | grep -i lvm
#
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] why does Udisks require Lvm2 ?
On Monday, 24 June 2019 18:00:29 BST Peter Humphrey wrote: > On Monday, 24 June 2019 16:59:08 BST Grant Taylor wrote: > > > On this box, which does need lvm for RAID-1 on two SSDs: > > Do you /need/ LVM? Or is it extra that comes with device-mapper? > > No, I do actually use lvm to base a raid-1 file system on. I haven't > considered raid-1 without lvm; is that feasible? Almost totally. They two are separate functions with synergistic interaction. RAID 1 offers redundancy by mirroring data between two block devices. LVM offers a flexible partitioning scheme where you can add space, move, snapshot, etc. data using a logical software layer to manage their storage across partitions and physical disks. I've put together RAID 1 disks with no LVM and used LVM with no RAID. NOTE: To confuse things you can instead use LVM's built in 'RAID functionality' - see below. I recall reading somewhere that SSDs are better used with LVM's natively configured RAID functionality, rather than a separate RAID layer, which in a mirrored RAID it will cause accelerated wear due to the way RAID metadata are mirrored between block devices. I don't think I've ever used LVM's RAID capability, but it would probably boil down to running: lvcreate --mirrors 1 --type raid 1 -n LV_myRAID VG_blah-blah Others more knowledgeable in these technologies could chime in to correct me no doubt. PS. LVM-RAID uses the kernel's mdraid, but with less tools to manage the RAID configuration than mdadm offers: https://unix.stackexchange.com/questions/150644/raiding-with-lvm-vs-mdraid-pros-and-cons -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Strange behavior of "tab" key with Libreoffice Calc and Plasma
On Mon, 24 Jun 2019 17:52:15 +0100, Mick wrote: > > > It seems that somehow pressing the tab key once gives focus to the > > > menu bar: pressing tab once, then pressing "F" brings down the file > > > menu; pressing tab, then pressing "E" displays the edit menu and so > > > on. > > > > Here, pressing Tab-Tab simply moves 2 cells to the right. > > Hmm ... are you running a non-KDE environment by any chance? > > I just tried LO on Englightenment and it works fine, BUT it runs with > GTK icons. Various KDE DEs however exhibit the same behaviour here - > double tab to move to the right cell and select it to be able to enter > data. > > Another thing I tried is to launch it with: > > SAL_USE_VCLPLUGIN=gtk3 soffice > > On a plasma only system, it will not respect this incantation and About > always shows "VCL: kde5; " so this leads me to conclude the problem is > with the KDE compilation flag. Good catch, that one worked for me, bit I have LO installed with both the kde and gtk USE flags. -- Neil Bothwick Knock firmly but softly. I like soft firm knockers. pgpCafiuHbLiZ.pgp Description: OpenPGP digital signature
Re: [gentoo-user] why does Udisks require Lvm2 ?
On Mon, 24 Jun 2019 18:00:29 +0100, Peter Humphrey wrote: > > I feel like device-mapper should be its own package that other things > > depend on; LVM, RAID (mdadm, et al.), multi-path, LUKS (cryptsetup). > > Yes, and that would fit the Unix tradition of doing one thing, and > well. It should also be applied to crypt-setup and its friends. Indeed, all it needs is someone willing to do the work. Now if LVM had been written by Lennart Poettering, there would be a stampede of volunteers to do this, witness eudev. > > > On this box, which does need lvm for RAID-1 on two SSDs: > > Do you /need/ LVM? Or is it extra that comes with device-mapper? > > No, I do actually use lvm to base a raid-1 file system on. I haven't > considered raid-1 without lvm; is that feasible? Of course it is, a RAID1 device is just a block device on which you can put any filesystem you like. RAID and LVM are complementary technologies that work well together, but neither needs the others (apart from the device-mapper bit). -- Neil Bothwick The road to HAL is paved with good intentions. pgp_q0NRPubEI.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Plasma teething problems - Part I
On Mon, 24 Jun 2019 10:53:04 -0400, Philip Webb wrote: > >> Set USE="-wireless" for powerdevil > > Excellent! This is what I was looking for. Thank you Neil. :-) > > Finally, a good example of the value of 'USE-"-* ... "' in make.conf ! Far from it, by knowing which flags are set per package, you have far more control of your system. Of course, if you enjoy investigating random breakages at inconvenient times, USE="-*" is a good way to keep yourself happy ;-) -- Neil Bothwick And then Adam said, "What's a headache? pgpmgwi0212IO.pgp Description: OpenPGP digital signature
Re: [gentoo-user] Plasma teething problems - Part II
On Monday, 24 June 2019 18:04:06 BST Peter Humphrey wrote: > On Monday, 24 June 2019 16:32:19 BST Mick wrote: > > I also found this beauty in /etc/speech-dispatcher/speechd.conf, which I > > uncommented: > > > > # The DisableAutoSpawn option will disable the autospawn mechanism. > > That's the sort of stupid explanation that gives technical authors and other > program documenters a bad name. Gentoo seems to be particularly heavily > afflicted with it. > > > # Thus the server will not start automatically on requests from the > > clients > > DisableAutoSpawn Clearly you have suffered in the hands of USE flag descriptors, which would make even the priestesses of the Oracle of Delphi sound coherent and unambiguous. LOL! -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Plasma teething problems - Part II
On Monday, 24 June 2019 16:32:19 BST Mick wrote: > I also found this beauty in /etc/speech-dispatcher/speechd.conf, which I > uncommented: > > # The DisableAutoSpawn option will disable the autospawn mechanism. That's the sort of stupid explanation that gives technical authors and other program documenters a bad name. Gentoo seems to be particularly heavily afflicted with it. > # Thus the server will not start automatically on requests from the clients > DisableAutoSpawn -- Regards, Peter.
Re: [gentoo-user] why does Udisks require Lvm2 ?
On Monday, 24 June 2019 16:59:08 BST Grant Taylor wrote:
> On 6/24/19 2:40 AM, Peter Humphrey wrote:
> > Yes, I've done the same on two boxes that have no need of lvm. It does
> > seem wasteful though.
>
> Probably.
>
> I dislike the fact that other things that need device mapper have to
> drag LVM along, or apply (what I call) a device-mapper-only /hack/.
>
> I feel like device-mapper should be its own package that other things
> depend on; LVM, RAID (mdadm, et al.), multi-path, LUKS (cryptsetup).
Yes, and that would fit the Unix tradition of doing one thing, and well. It
should also be applied to crypt-setup and its friends.
> > I forget the detail now, but a recent-ish version of sys-fs/cryptsetup
> > found it needed a hard dependency on some of the code in lvm2.
>
> Did you apply (what I call) the device-mapper-only /hack/. Or was LVM
> pulled in for device-mapper?
I didn't know about the hack at the time. I'm hazy about this now, memory not
being what it was, but I think I was trying to get rid of encryption apps as
well as lvm on a box that doesn't use either and never will. I'm stuck with
having both, willy-nilly. As Neil said, though, you could say it's only a
matter of disk space - until someone finds a vulnerability in them and uses it
on me. :(
> > It seems to me that we have here an opportunity for redesign of certain
> > packages. ("We" the community, that is.)
>
> Agreed.
>
> > On this box, which does need lvm for RAID-1 on two SSDs:
> Do you /need/ LVM? Or is it extra that comes with device-mapper?
No, I do actually use lvm to base a raid-1 file system on. I haven't
considered raid-1 without lvm; is that feasible?
--
Regards,
Peter.
Re: [gentoo-user] Strange behavior of "tab" key with Libreoffice Calc and Plasma
On Sunday, 23 June 2019 21:31:33 BST Philip Webb wrote: > 190623 Stefano Crocco wrote: > > a few months ago I started noticing a very annoying behavior > > when pressing the "tab" key in Libreoffice Calc. > > Previously, pressing this key would move the cursor by one cell to the > > right, so that I could immediately start writing into the cell. > > That's what it does for me now, using LO 6.2.4.2 on KDE. Also on the same version, but running Plasma/KDE-5.15.5, single tab moves to the cell on the right AND selects the main menu. :-/ > > Now, while the cursor is moved to the correct cell > > -- I can see the black border around it -- , > > I can't write in it immediately anymore. > > To move the cursor to the next cell and be able to immediately write in > > it, > > I need to press the tab key twice. > > It seems that somehow pressing the tab key once gives focus to the menu > > bar: pressing tab once, then pressing "F" brings down the file menu; > > pressing tab, then pressing "E" displays the edit menu and so on. > > Here, pressing Tab-Tab simply moves 2 cells to the right. Hmm ... are you running a non-KDE environment by any chance? I just tried LO on Englightenment and it works fine, BUT it runs with GTK icons. Various KDE DEs however exhibit the same behaviour here - double tab to move to the right cell and select it to be able to enter data. Another thing I tried is to launch it with: SAL_USE_VCLPLUGIN=gtk3 soffice On a plasma only system, it will not respect this incantation and About always shows "VCL: kde5; " so this leads me to conclude the problem is with the KDE compilation flag. If I remember I'll disable it on the next update and see what happens then. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] why does Udisks require Lvm2 ?
On 6/24/19 2:40 AM, Peter Humphrey wrote:
Yes, I've done the same on two boxes that have no need of lvm. It does
seem wasteful though.
Probably.
I dislike the fact that other things that need device mapper have to
drag LVM along, or apply (what I call) a device-mapper-only /hack/.
I feel like device-mapper should be it's own package that other things
depend on; LVM, RAID (mdadm, et al.), multi-path, LUKS (cryptsetup).
I forget the detail now, but a recent-ish version of sys-fs/cryptsetup
found it needed a hard dependency on some of the code in lvm2.
Did you apply (what I call) the device-mapper-only /hack/. Or was LVM
pulled in for device-mapper?
It seems to me that we have here an opportunity for redesign of certain
packages. ("We" the community, that is.)
Agreed.
On this box, which does need lvm for RAID-1 on two SSDs:
Do you /need/ LVM? Or is it extra that comes with device-mapper?
--
Grant. . . .
unix || die
Re: [gentoo-user] Plasma teething problems - Part II
On Monday, 24 June 2019 16:22:01 BST Mick wrote: > On Monday, 24 June 2019 12:44:34 BST Dale wrote: > > Mick wrote: > > > I often find a number of speech-dispatcher processes running: > > > 4732 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy > > > /etc/> > > > > > > speech-dispatcher/modules/dummy.conf > > > > > > 4734 ?SLl0:00 > > > /usr/lib64/speech-dispatcher-modules/sd_generic > > > / > > > > > > etc/speech-dispatcher/modules/generic.conf > > > > > > 4736 ?SLl0:00 > > > /usr/lib64/speech-dispatcher-modules/sd_cicero > > > / > > > > > > etc/speech-dispatcher/modules/cicero.conf > > > > > > 4737 ?Z 0:00 \_ [sd_cicero] > > > 4739 ?SLl0:00 > > > /usr/lib64/speech-dispatcher-modules/sd_espeak > > > / > > > > > > etc/speech-dispatcher/modules/espeak.conf > > > > > > 4744 ?Ssl0:00 /usr/bin/speech-dispatcher --spawn > > > --communication-> > > > > > > method unix_socket --socket-path > > > /run/user/1000/speech-dispatcher/speechd.sock > > > > > > I don't know what is starting these processes or what they have to offer > > > to my desktop. Checking systemsettings5/Accessibility Options/Screen > > > Reader, I can see it is NOT enabled. > > > > > > How can I get rid of these? > > > > I would start out by finding out what package /usr/bin/speech-dispatcher > > belongs too. Equery can help with that but other tools can as well. > > Once you find that, then check the USE flags to see what can be adjusted > > to get rid if that. I don't have it here so I can't do it on my system. > > > > Dale > > > > :-) :-) > > Good call Dale, here's what I found: > > app-accessibility/speech-dispatcher is required by dev-qt/qtspeech, > > which is required by kde-apps/kdepim-runtime and kde-apps/kpimtextedit, > neither of which have a USE flag to stop speech-dispatcher kicking off. > > However, speech-dispatcher has USE="espeak" enabled, which I will try to > disable and see what happens thereafter. I also found this beauty in /etc/speech-dispatcher/speechd.conf, which I uncommented: # The DisableAutoSpawn option will disable the autospawn mechanism. # Thus the server will not start automatically on requests from the clients DisableAutoSpawn -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Plasma teething problems - Part II
On Monday, 24 June 2019 12:44:34 BST Dale wrote: > Mick wrote: > > I often find a number of speech-dispatcher processes running: > > 4732 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy > > /etc/> > > speech-dispatcher/modules/dummy.conf > > > > 4734 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_generic > > / > > > > etc/speech-dispatcher/modules/generic.conf > > > > 4736 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_cicero > > / > > > > etc/speech-dispatcher/modules/cicero.conf > > > > 4737 ?Z 0:00 \_ [sd_cicero] > > 4739 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_espeak > > / > > > > etc/speech-dispatcher/modules/espeak.conf > > > > 4744 ?Ssl0:00 /usr/bin/speech-dispatcher --spawn > > --communication-> > > method unix_socket --socket-path > > /run/user/1000/speech-dispatcher/speechd.sock > > > > I don't know what is starting these processes or what they have to offer > > to my desktop. Checking systemsettings5/Accessibility Options/Screen > > Reader, I can see it is NOT enabled. > > > > How can I get rid of these? > > I would start out by finding out what package /usr/bin/speech-dispatcher > belongs too. Equery can help with that but other tools can as well. > Once you find that, then check the USE flags to see what can be adjusted > to get rid if that. I don't have it here so I can't do it on my system. > > Dale > > :-) :-) Good call Dale, here's what I found: app-accessibility/speech-dispatcher is required by dev-qt/qtspeech, which is required by kde-apps/kdepim-runtime and kde-apps/kpimtextedit, neither of which have a USE flag to stop speech-dispatcher kicking off. However, speech-dispatcher has USE="espeak" enabled, which I will try to disable and see what happens thereafter. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Plasma teething problems - Part I
On Monday, 24 June 2019 15:53:04 BST Philip Webb wrote: > 190624 Mick wrote: > > On Monday, 24 June 2019 12:17:51 BST Neil Bothwick wrote: > >> On Mon, 24 Jun 2019 12:00:36 +0100, Mick wrote: > >>> Could someone more knowledgeable in Plasma/KDE shenanigans please > >>> explain how I can end up with a workable USB wireless dongle, which I > >>> can enable/disable at will? > >> > >> Set USE="-wireless" for powerdevil > > > > Excellent! This is what I was looking for. Thank you Neil. :-) > > Finally, a good example of the value of 'USE-"-* ... "' in make.conf ! > I had no idea of any of this & don't need 'powerdevil', > but the '-wireless' flag has been set all along anyway (grin). > > Yes, I know there are opposite cases too. TBH the opposite cases must be overwhelmingly more that this one. If it were a single package *and* you know which one it is, then it is easy to look at its USE flags and make a call to affect its functionality. In my example here I couldn't see the wood for the Plasma/KDE trees, until Neil pointed the particular tree I should be barking under ... :-) I still wouldn't apply a 'USE-"-* ... "' approach unless I was looking for a way to spend many hours contemplating the causes of breaking stuff and then breaking them again after an update/upgrade. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Plasma teething problems - Part I
190624 Mick wrote: > On Monday, 24 June 2019 12:17:51 BST Neil Bothwick wrote: >> On Mon, 24 Jun 2019 12:00:36 +0100, Mick wrote: >>> Could someone more knowledgeable in Plasma/KDE shenanigans please >>> explain how I can end up with a workable USB wireless dongle, which I >>> can enable/disable at will? >> Set USE="-wireless" for powerdevil > Excellent! This is what I was looking for. Thank you Neil. :-) Finally, a good example of the value of 'USE-"-* ... "' in make.conf ! I had no idea of any of this & don't need 'powerdevil', but the '-wireless' flag has been set all along anyway (grin). Yes, I know there are opposite cases too. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] Re: why does Udisks require Lvm2 ?
On Mon, 24 Jun 2019 08:32:51 -0500, »Q« wrote: > > > use.local.desc:sys-fs/lvm2:device-mapper-only - Build only > > > device-mapper and not the rest of LVM2 (UNSUPPORTED) > > > > Aha! > > > > So the choice is between an unsupported configuration or installing a > > handful of binaries that you will never use. Unless space was an > > issue, there's about 6MB difference, I'd go with the latter, although > > UNSUPPORTED != DOESNOTWORK > > My guess is that 'unsupported' in this case means upstream won't bother > to make sure the partial installation will continue to work. If it > ever does break, I'd expect the Gentoo maintainers to force the flag > off. Agreed, it basically means it works for now but no guarantees in the future, which should make it reasonably safe to enable the flag now. Although I'd be wary of doing that if the OS is installed on an encrypted filesystem. -- Neil Bothwick If at first you don't succeed you'll get lots of advice. pgp0ylhBZGFrW.pgp Description: OpenPGP digital signature
[gentoo-user] Re: why does Udisks require Lvm2 ?
On Mon, 24 Jun 2019 08:46:55 +0100 Neil Bothwick wrote: > On Mon, 24 Jun 2019 08:36:50 +0100, Peter Humphrey wrote: > > > > > > Which is why the USE flag exists, to avoid installing LVM. > > > > > > > > But it's not supported. > > > > > > In what way. I've just tried emerging lvm2 with > > > USE="device-mapper-only -thin" and it installed the device-mapper > > > stiff but none of the lvm executables, which seems to be exactly > > > what is wanted. > > > > use.local.desc:sys-fs/lvm2:device-mapper-only - Build only > > device-mapper and not the rest of LVM2 (UNSUPPORTED) > > Aha! > > So the choice is between an unsupported configuration or installing a > handful of binaries that you will never use. Unless space was an > issue, there's about 6NB difference, I'd go with the latter, although > UNSUPPORTED != DOESNOTWORK My guess is that 'unsupported' in this case means upstream won't bother to make sure the partial installation will continue to work. If it ever does break, I'd expect the Gentoo maintainers to force the flag off.
[gentoo-user] Migration from 17.0 to 17.1
Hello all, Here is my own experience about migrating from 17.0 to 17.1 profile. I followed the steps 1, 3, 4, 5, 6, 7, 8, 9 and 10 (emerge -1v sys-devel/gcc:8.3.0, emerge -1v sys-devel/gcc:8.2.0-r6) without any issue. Everything works fine but the step 11 (emerge -1v --deep /lib32 /usr/lib32 /usr/lib/llvm/*/lib32) has been pretty painful. Many config phase failed. - dev-libs/glib-2.58.3 Solved by emerging util-linux and libpcre - many x11-libs stuff Solved by emerging some x11-base packages (especially xorg-x11) - dev-libs/libgudev, media-libs/libv4l, x11-misc/colord and media-libs/libcanberra. Solved by emerging virtual/libudev Finally, i could delete the /lib32 (/usr/lib32 was already deleted) and the /usr/local/lib32 symlinks. Now everything seems to work properly. Cheers, -- Jacques
Re: [gentoo-user] Plasma teething problems - Part II
Mick wrote: > I often find a number of speech-dispatcher processes running: > > 4732 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy /etc/ > speech-dispatcher/modules/dummy.conf > 4734 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_generic / > etc/speech-dispatcher/modules/generic.conf > 4736 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_cicero / > etc/speech-dispatcher/modules/cicero.conf > 4737 ?Z 0:00 \_ [sd_cicero] > 4739 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_espeak / > etc/speech-dispatcher/modules/espeak.conf > 4744 ?Ssl0:00 /usr/bin/speech-dispatcher --spawn --communication- > method unix_socket --socket-path /run/user/1000/speech-dispatcher/speechd.sock > > I don't know what is starting these processes or what they have to offer to > my > desktop. Checking systemsettings5/Accessibility Options/Screen Reader, I can > see it is NOT enabled. > > How can I get rid of these? > I would start out by finding out what package /usr/bin/speech-dispatcher belongs too. Equery can help with that but other tools can as well. Once you find that, then check the USE flags to see what can be adjusted to get rid if that. I don't have it here so I can't do it on my system. Dale :-) :-)
Re: [gentoo-user] Plasma teething problems - Part I
On Monday, 24 June 2019 12:17:51 BST Neil Bothwick wrote: > On Mon, 24 Jun 2019 12:00:36 +0100, Mick wrote: > > Could someone more knowledgeable in Plasma/KDE shenanigans please > > explain how I can end up with a workable USB wireless dongle, which I > > can enable/disable at will? > > Set USE="-wireless" for powerdevil > > I have KDE on this laptop, with no NM. The wireless connection is managed > by systemd-networkd here, but the same should be possible with openrc and > no NM. Excellent! This is what I was looking for. Thank you Neil. :-) -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Plasma teething problems - Part I
On Mon, 24 Jun 2019 12:00:36 +0100, Mick wrote: > Well, not Plasma's but mine for sure. I have been chasing my tail > trying to reverse engineer processes/services/applications I do not > want auto-running on a fresh Plasma installation and I'm fast losing > the will to live. > > I've installed plasma-meta plus some kde-apps meta packages as follows: > > kde-apps/kdeadmin-meta > kde-apps/kdecore-meta > kde-apps/kdegraphics-meta > kde-apps/kdemultimedia-meta > kde-apps/kdenetwork-meta > kde-apps/kdepim-meta > kde-apps/kdeutils-meta > kde-apps/kwalletmanager > kde-frameworks/oxygen-icons > kde-plasma/plasma-meta > > One of the above[1] brought in NetworkManager, which I don't use > because for my use case there's nothing wrong with openrc netifrc > scripts. When I plug in a USB wireless adaptor nothing happens since > it stays dormant, although its LED illuminates. Then I enable it by > starting 'net.wlp0s18f2u1' and at that point NM starts fighting over > the wireless adaptor, resulting in the unpleasant phenomenon of > dropping the connection every few minutes and changing its MAC address, > consequently rendering it unusable with APs which implement ACL. > > [1] kde-plasma/plasma-meta requires kde-plasma/powerdevil, which > requires kde- frameworks/networkmanager-qt, which requires > net-misc/networkmanager, which requires net-misc/modemmanager > > So I naively thought, let's try stopping NM (note: the NetworkManager > rc service is not set to run at any level, so something else is > starting it). The moment I stop NM I find my logs being flooded with a > storm of 'dbus failing to start obex', which bluez wants. Note: I have > not started a bluetooth service, or tried running bluetootctl, and BTW > rfkill shows the bluetooth adaptor is soft blocked anyway. > > So I now try to stop dbus and restart it, which results in losing > access to any Plasma menu applications, so I can't launch any > application. It may be worth mentioning when I leave alone NM and just > disable the USB adaptor from openrc, I also lose access to launching > KDE applications (the error message when trying to launch an app from a > terminal mentions a Qt error). > > Could someone more knowledgeable in Plasma/KDE shenanigans please > explain how I can end up with a workable USB wireless dongle, which I > can enable/disable at will? > Set USE="-wireless" for powerdevil I have KDE on this laptop, with no NM. The wireless connection is managed by systemd-networkd here, but the same should be possible with openrc and no NM. -- Neil Bothwick System halted - hit any Microsoft employee to continue. pgpLx8kJUwKsl.pgp Description: OpenPGP digital signature
[gentoo-user] Plasma teething problems - Part II
I often find a number of speech-dispatcher processes running: 4732 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_dummy /etc/ speech-dispatcher/modules/dummy.conf 4734 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_generic / etc/speech-dispatcher/modules/generic.conf 4736 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_cicero / etc/speech-dispatcher/modules/cicero.conf 4737 ?Z 0:00 \_ [sd_cicero] 4739 ?SLl0:00 /usr/lib64/speech-dispatcher-modules/sd_espeak / etc/speech-dispatcher/modules/espeak.conf 4744 ?Ssl0:00 /usr/bin/speech-dispatcher --spawn --communication- method unix_socket --socket-path /run/user/1000/speech-dispatcher/speechd.sock I don't know what is starting these processes or what they have to offer to my desktop. Checking systemsettings5/Accessibility Options/Screen Reader, I can see it is NOT enabled. How can I get rid of these? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] Plasma teething problems - Part I
Well, not Plasma's but mine for sure. I have been chasing my tail trying to reverse engineer processes/services/applications I do not want auto-running on a fresh Plasma installation and I'm fast losing the will to live. I've installed plasma-meta plus some kde-apps meta packages as follows: kde-apps/kdeadmin-meta kde-apps/kdecore-meta kde-apps/kdegraphics-meta kde-apps/kdemultimedia-meta kde-apps/kdenetwork-meta kde-apps/kdepim-meta kde-apps/kdeutils-meta kde-apps/kwalletmanager kde-frameworks/oxygen-icons kde-plasma/plasma-meta One of the above[1] brought in NetworkManager, which I don't use because for my use case there's nothing wrong with openrc netifrc scripts. When I plug in a USB wireless adaptor nothing happens since it stays dormant, although its LED illuminates. Then I enable it by starting 'net.wlp0s18f2u1' and at that point NM starts fighting over the wireless adaptor, resulting in the unpleasant phenomenon of dropping the connection every few minutes and changing its MAC address, consequently rendering it unusable with APs which implement ACL. [1] kde-plasma/plasma-meta requires kde-plasma/powerdevil, which requires kde- frameworks/networkmanager-qt, which requires net-misc/networkmanager, which requires net-misc/modemmanager So I naively thought, let's try stopping NM (note: the NetworkManager rc service is not set to run at any level, so something else is starting it). The moment I stop NM I find my logs being flooded with a storm of 'dbus failing to start obex', which bluez wants. Note: I have not started a bluetooth service, or tried running bluetootctl, and BTW rfkill shows the bluetooth adaptor is soft blocked anyway. So I now try to stop dbus and restart it, which results in losing access to any Plasma menu applications, so I can't launch any application. It may be worth mentioning when I leave alone NM and just disable the USB adaptor from openrc, I also lose access to launching KDE applications (the error message when trying to launch an app from a terminal mentions a Qt error). Could someone more knowledgeable in Plasma/KDE shenanigans please explain how I can end up with a workable USB wireless dongle, which I can enable/disable at will? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] why does Udisks require Lvm2 ?
On Monday, 24 June 2019 08:46:55 BST Neil Bothwick wrote:
> So the choice is between an unsupported configuration or installing a
> handful of binaries that you will never use. Unless space was an issue,
> there's about 6NB difference, I'd go with the latter, although
> UNSUPPORTED != DOESNOTWORK
Yes, I've done the same on two boxes that have no need of lvm. It does seem
wasteful though.
I forget the detail now, but a recent-ish version of sys-fs/cryptsetup found
it needed a hard dependency on some of the code in lvm2. It seems to me that
we have here an opportunity for redesign of certain packages. ("We" the
community, that is.)
On this box, which does need lvm for RAID-1 on two SSDs:
$ equery d lvm2
* These packages depend on lvm2:
app-emulation/virtualbox-6.0.8 (lvm ? sys-fs/lvm2)
net-fs/nfs-utils-2.4.1 (nfsv41 ? sys-fs/lvm2)
sys-block/gparted-0.33.0 (dmraid ? >=sys-fs/lvm2-2.02.45)
sys-block/parted-3.2_p25 (device-mapper ? >=sys-fs/lvm2-2.02.45)
sys-fs/cryptsetup-2.1.0 (sys-fs/lvm2[static-libs(+)])
(sys-fs/lvm2)
sys-fs/e2fsprogs-1.45.2 (cron ? sys-fs/lvm2[-device-mapper-only(-)])
sys-fs/udisks-2.8.3 (lvm ? sys-fs/lvm2)
sys-libs/libblockdev-2.22 (device-mapper ? sys-fs/lvm2)
(dmraid ? sys-fs/lvm2)
(lvm ? sys-fs/lvm2)
Other than sys-fs/cryptsetup, those are all conditional dependencies.
--
Regards,
Peter.
Re: [gentoo-user] Incomplete Bugzilla Search Results?
On Sun, 23 Jun 2019 20:36:35 -0400, wiicontrol...@gmail.com wrote: > On 2019-06-24 01:10, Neil Bothwick wrote: > > > >You are limiting results to those with a resolution of ---, i.e. > >unresolved. You need to select all of the possible resolutions to > >include all bugs in your search. > > Thank you. I mistook “---” to mean any status, not unresolved. So did I at first. Then I tried my usual problem solving method of press every button and it worked. -- Neil Bothwick Cross-country skiing is great in small countries. pgpPIr6U4fK3r.pgp Description: OpenPGP digital signature
Re: [gentoo-user] why does Udisks require Lvm2 ?
On Mon, 24 Jun 2019 08:36:50 +0100, Peter Humphrey wrote: > > > > Which is why the USE flag exists, to avoid installing LVM. > > > > > > But it's not supported. > > > > In what way. I've just tried emerging lvm2 with > > USE="device-mapper-only -thin" and it installed the device-mapper > > stiff but none of the lvm executables, which seems to be exactly what > > is wanted. > > use.local.desc:sys-fs/lvm2:device-mapper-only - Build only > device-mapper and not the rest of LVM2 (UNSUPPORTED) Aha! So the choice is between an unsupported configuration or installing a handful of binaries that you will never use. Unless space was an issue, there's about 6NB difference, I'd go with the latter, although UNSUPPORTED != DOESNOTWORK -- Neil Bothwick I've got a Mickey Mouse PC with a Goofy operating system. pgpZbPdhuFDzt.pgp Description: OpenPGP digital signature
Re: [gentoo-user] why does Udisks require Lvm2 ?
On Monday, 24 June 2019 01:12:07 BST Neil Bothwick wrote: > On Sun, 23 Jun 2019 23:35:33 +0100, Peter Humphrey wrote: > > > > Why isn't device-mapper it's own package‽ One which LVM depends > > > > on. > > > > > > No idea, but I'd guess it's got something to do with not reinventing > > > the wheel. From a maintenance point of view, a USE flag would be less > > > effort than two packages. > > > > > > > Multi-Path (as in dm-multipath) can easily be used without LVM. > > > > > > Which is why the USE flag exists, to avoid installing LVM. > > > > But it's not supported. > > In what way. I've just tried emerging lvm2 with USE="device-mapper-only > -thin" and it installed the device-mapper stiff but none of the lvm > executables, which seems to be exactly what is wanted. use.local.desc:sys-fs/lvm2:device-mapper-only - Build only device-mapper and not the rest of LVM2 (UNSUPPORTED) -- Regards, Peter.
