Page 1 of 1

[DONE] - Login Screen Issue

PostPosted: Mar 17th, '14, 18:43
by cyber-dragon-14
OK, I recently installed the E-17 DE, just to test. Decided to remove it after discovering a large percentage of the modules just plain don't work. Found out via Bug site basically E-17 is at one version and the modules are just a small step behind, but causes them to not be seen.
Anyway, I removed E17, and as far as I know it is completely gone.
Now, on the login screen, when you click on the little pencil and paper icon to select desktop environment, E17 still shows.
Basically, I just 2 things to resolve this:
1. Need to verify that E17 is indeed completely gone. And,
2. How do I edit the login screens entries to remove E17 so it is gone there as well.

Tried searching, but kept finding predominantly entries concerning GNOME and the login screen.

Thanks.

Re: Login Screen Issue

PostPosted: Mar 17th, '14, 22:27
by doktor5000
First question: Why do you need to remove it again, and also make sure that every single package has been removed?
Why not simply leave the session entry there, it doesn't do any harm.

The package that you want to remove is called e and contains the desktop session:
Code: Select all
[doktor5000@Mageia4 4]$ rpm -qf /etc/X11/wmsession.d/23E17
e-0.17.5-2.mga4


Some related information about this at https://wiki.mageia.org/en/How_to_add_a ... ay_Manager

Re: Login Screen Issue

PostPosted: Mar 17th, '14, 22:31
by cyber-dragon-14
Just call me anal, OK? I don not like having "loose ends" it just becomes annoying. I aim (usually) for a "clean" display setup.
I have been that way since using old Windows (as in PRE Win 3.0).

Re: Login Screen Issue

PostPosted: Mar 17th, '14, 23:04
by cyber-dragon-14
OK, as far as I can tell all traces of E17 have been removed..BUT..
On the login screen E17 is still there. :?
I am just SO confused. I made sure all items that I can find are gone, and I even rebooted.
Please help. Does anyone know where else the E17 item(s) may still be hiding/lurking on this machine? :?:

Re: Login Screen Issue

PostPosted: Mar 17th, '14, 23:14
by doktor5000
Did you actually read my previous post? What about that package?

Also you didn't mention which login manager you're currently using.

Re: Login Screen Issue

PostPosted: Mar 17th, '14, 23:45
by cyber-dragon-14
doktor5000 wrote:Did you actually read my previous post? What about that package?

Also you didn't mention which login manager you're currently using.


Yes I did, and it was removed a bit ago...and it STILL appears in the login area.
Are there any other areas, no matter how remote, that may hold any sway here?
All the data you sent and even went following some of the links from those pages as well.
As far as I can tell E17 does not exist anymore on this machine, yet according to that pesky login window entry is has to,
since I believe the one page I read it is like a trigger event or trigger item. If it "sees" something it will show up.

Re: Login Screen Issue

PostPosted: Mar 18th, '14, 01:13
by martinw
You haven't yet answered doktor5000's question about which login manager you are using (if you don't know, start the Mageia Control Centre, go to the "Boot" tab, and select "Set up display manager").

Also, please show the output of
Code: Select all
ls /etc/X11/wmsession.d/

Re: Login Screen Issue

PostPosted: Mar 18th, '14, 02:09
by cyber-dragon-14
martinw wrote:You haven't yet answered doktor5000's question about which login manager you are using (if you don't know, start the Mageia Control Centre, go to the "Boot" tab, and select "Set up display manager").

Also, please show the output of
Code: Select all
ls /etc/X11/wmsession.d/


KDM. Considering my "primary" desktop environment is KDE.
And under LOGIN SCREEN in SYSTEM SETTINGS, the actual theme is referred to as Mageia KDE4.

Re: Login Screen Issue

PostPosted: Mar 18th, '14, 02:11
by cyber-dragon-14
Now on to my further "escapades" in try to solve this. FIY, it rather long.
==============================================================


rpm -qa | grep e17

found this item only: e17-themes-extra-0.4-8.mga4

Even after using Qt4urpm to remove the "orpans" after I removed e17

then I entered this command (as root):
Code: Select all
[root@localhost richardhowell]# rpm -evv e17-themes-extra-0.4-8.mga4


Output from it:

Code: Select all
D: loading keyring from pubkeys in /var/lib/rpm/pubkeys/*.key
D: couldn't find any keys in /var/lib/rpm/pubkeys/*.key
D: loading keyring from rpmdb
D: opening  db environment /var/lib/rpm cdb:0x401
D: opening  db index       /var/lib/rpm/Packages 0x400 mode=0x0
D: locked   db index       /var/lib/rpm/Packages
D: opening  db index       /var/lib/rpm/Name 0x400 mode=0x0
D:  read h#       1 Header SHA1 digest: OK (9ec63328fc787234c19a736fba9882d0f45856c7)
D: added key gpg-pubkey-80420f66-4d4fe123 to keyring
D: Using legacy gpg-pubkey(s) from rpmdb
D:  read h#    2747 Header V3 RSA/SHA1 Signature, key ID 80420f66: OK
D: opening  db index       /var/lib/rpm/Conflictname 0x400 mode=0x0
D: ========== --- e17-themes-extra-0.4-8.mga4 noarch/linux 0x0
D: opening  db index       /var/lib/rpm/Requirename 0x400 mode=0x0
D: ========== recording tsort relations
D: ========== tsorting packages (order, #predecessors, #succesors, depth)
D:     0    0    0    1   -e17-themes-extra-0.4-8.mga4.noarch
D: erasing packages
D: Selinux disabled.
D: closed   db index       /var/lib/rpm/Conflictname
D: closed   db index       /var/lib/rpm/Requirename
D: closed   db index       /var/lib/rpm/Name
D: closed   db index       /var/lib/rpm/Packages
D: closed   db environment /var/lib/rpm
D: opening  db environment /var/lib/rpm cdb:0x401
D: opening  db index       /var/lib/rpm/Packages (none) mode=0x42
D: sanity checking 1 elements
D: running pre-transaction scripts
D: computing 10 file fingerprints
D: opening  db index       /var/lib/rpm/Name (none) mode=0x42
D: opening  db index       /var/lib/rpm/Basenames (none) mode=0x42
D: opening  db index       /var/lib/rpm/Group (none) mode=0x42
D: opening  db index       /var/lib/rpm/Requirename (none) mode=0x42
D: opening  db index       /var/lib/rpm/Providename (none) mode=0x42
D: opening  db index       /var/lib/rpm/Conflictname (none) mode=0x42
D: opening  db index       /var/lib/rpm/Obsoletename (none) mode=0x42
D: opening  db index       /var/lib/rpm/Triggername (none) mode=0x42
D: opening  db index       /var/lib/rpm/Dirnames (none) mode=0x42
D: opening  db index       /var/lib/rpm/Installtid (none) mode=0x42
D: opening  db index       /var/lib/rpm/Sigmd5 (none) mode=0x42
D: opening  db index       /var/lib/rpm/Sha1header (none) mode=0x42
Preparing packages...
D: computing file dispositions
D: 0x00000818     4096      2227819       965686 /
D: ========== +++ e17-themes-extra-0.4-8.mga4 noarch-linux 0x0
D:  read h#    2747 Header V3 RSA/SHA1 Signature, key ID 80420f66: OK
D:     erase: e17-themes-extra-0.4-8.mga4 has 10 files
e17-themes-extra-0.4-8.mga4.noarch
D: erase      100644  1 (   0,   0)6361383 /usr/share/enlightenment/data/themes/A-revolution-V2.edj
D: erase      100644  1 (   0,   0)7282346 /usr/share/enlightenment/data/themes/A-Vision-V3.edj
D: erase      100644  1 (   0,   0)7057161 /usr/share/enlightenment/data/themes/A-Red-Night-V3.edj
D: erase      100644  1 (   0,   0)6887834 /usr/share/enlightenment/data/themes/A-ElectricV2.edj
D: erase      100644  1 (   0,   0)1907611 /usr/share/enlightenment/data/themes/A-EBlack-V2.edj
D: erase      100644  1 (   0,   0)4837532 /usr/share/enlightenment/data/themes/A-E1-Moonlight.edj
D: erase      100644  1 (   0,   0)7015770 /usr/share/enlightenment/data/themes/A-BlingBlack-V3.edj
D: erase      100644  1 (   0,   0)7968520 /usr/share/enlightenment/data/themes/A-Angelic-v2.edj
D: erase      100644  1 (   0,   0)9276192 /usr/share/enlightenment/data/themes/A-Angelic-Sky-V5.edj
D: erase      100644  1 (   0,   0)5551958 /usr/share/enlightenment/data/themes/A-Agust-V3.edj
D:   --- h#    2747 e17-themes-extra-0.4-8.mga4.noarch
D: removing "e17-themes-extra" from Name index.
D: removing 10 entries from Basenames index.
D: removing "Graphical desktop/Enlightenment" from Group index.
D: removing 4 entries from Requirename index.
D: removing 2 entries from Providename index.
D: removing 1 entries from Obsoletename index.
D: removing 1 entries from Dirnames index.
D: removing 1 entries from Installtid index.
D: removing 1 entries from Sigmd5 index.
D: removing "3375bdda08aa9b8d30622ff1292c93acb79ece3c" from Sha1header index.
D: [filetriggers] starting
D: [filetriggers] matches-any regexp is ^./etc/rc.d/init.d/|^.(/usr/share/fonts/|/usr/lib/X11/fonts/|/usr/X11R6/lib/X11/fonts|/opt/ttfonts/)|^\+/etc/gconf/schemas/[^/]*\.schemas$|^./usr/lib/gio/modules/*.so$|^./usr/share/glib-2.0/schemas/[^/]*\.xml$|^./usr/share/icons/gnome/|^./usr/share/icons/hicolor/|^./usr/share/icons/mate/|^./usr/share/icons/oxygen/|^.((/lib|/usr/lib)(32|64)?/[^/]*\.so\.|/etc/ld.so.conf.d/[^/]*\.conf)|^.(/usr/share/X11/dm\.d/|/etc/X11/wmsession\.d/)|^./usr/share/mime/packages/[^/]*\.xml$|^./usr/share/omf/.*\.omf$|^./usr/lib/systemd/system/|^./usr/share/applications/.*\.desktop$|^.(/usr/share/applications/.*\.desktop|/etc/menu.d/)$
D: running post-transaction scripts
D: closed   db index       /var/lib/rpm/Sha1header
D: closed   db index       /var/lib/rpm/Sigmd5
D: closed   db index       /var/lib/rpm/Installtid
D: closed   db index       /var/lib/rpm/Dirnames
D: closed   db index       /var/lib/rpm/Triggername
D: closed   db index       /var/lib/rpm/Obsoletename
D: closed   db index       /var/lib/rpm/Conflictname
D: closed   db index       /var/lib/rpm/Providename
D: closed   db index       /var/lib/rpm/Requirename
D: closed   db index       /var/lib/rpm/Group
D: closed   db index       /var/lib/rpm/Basenames
D: closed   db index       /var/lib/rpm/Name
D: closed   db index       /var/lib/rpm/Packages
D: closed   db environment /var/lib/rpm
[root@localhost richardhowell]#



re-rean rpm -qa | grep e17 as user and root both, not one hit on the e17 criteria

And the e17 is STILL in the login screen.

And even did further searching using thr FIND command, did a restart of the KDM service, etc.

And, yep, it is STILL there.

Re: Login Screen Issue

PostPosted: Mar 18th, '14, 11:17
by martinw
It would be easier to help you if you provided the information you are asked for. Our crystal balls don't work that well.

However, as doktor5000 has already said, the package you want to remove is called *e* not *e17*, so try
Code: Select all
rpm -qa | grep e-0.17

If this shows nothing, then please provide the information I asked for.

Re: Login Screen Issue

PostPosted: Mar 18th, '14, 15:13
by cyber-dragon-14
martinw wrote:It would be easier to help you if you provided the information you are asked for. Our crystal balls don't work that well.

However, as doktor5000 has already said, the package you want to remove is called *e* not *e17*, so try
Code: Select all
rpm -qa | grep e-0.17

If this shows nothing, then please provide the information I asked for.


[richardhowell@localhost ~]$ rpm -qa | grep e-0.17
e-0.17.5-2.mga4

Re: Login Screen Issue

PostPosted: Mar 18th, '14, 15:30
by cyber-dragon-14
@martinw:
Sad part is, it says it is "installed", but when I last checked, there is no actually still installed.
Then ran find / -name e-0.17*
Still found nothing.
Is it possible for that to be sort of a "orphan" of a sorts? I mean when I run Qt4urpm it lists nothing at all.


@doktor5000:

Here is a continuation of all I have been doing:

I was just "relaxing" looking thru my Applications and to my utter surprise, I actually saw 2 items left over...ePhoto, and Terminology. Both from Enlightenment., So, off to the terminal in root mode I went:
the 2 commands used were:

find / -name ephoto*
find / -name terminology*

Here was th results:
Code: Select all
EPHOTO

[root@localhost richardhowell]# find / -name ephoto*
/usr/bin/ephoto
/usr/bin/ephoto_ql
/usr/share/pixmaps/ephoto.png
/usr/share/ephoto
/usr/share/ephoto/themes/default/ephoto.edj
/usr/share/applications/ephoto.desktop
/usr/share/doc/ephoto
/usr/lib/ephoto_ql.so


TERMINOLOGY

[root@localhost richardhowell]# find / -name terminology*
/usr/bin/terminology
/usr/share/terminology
/usr/share/terminology/images/terminology.png
/usr/share/applications/terminology.desktop
/usr/share/icons/terminology.png
/usr/share/doc/terminology

Also along the way I actually found several items that said enlightenment.
Please note I used Krusader in too mode to delete all items found, then restarted.

I am now VERY happy. The E17 entry on the login screen is now completely GONE! :mrgreen:

Re: Login Screen Issue

PostPosted: Mar 18th, '14, 23:28
by doktor5000
What you did is wreck your system - you only mentioned previously "I removed this and that" but what you probably did is
simply delete the files, whereas you would only need to uninstall the rpm packages. So far for your previous comment:

cyber-dragon-14 wrote:Just call me anal, OK? I don not like having "loose ends" it just becomes annoying. I aim (usually) for a "clean" display setup.

Clean desk on top at first glance - but the trashcan spilled on the floor beneath it and the desk is rotting from the bottom up. Good luck with that,
the loose ends that you ignore will probably twist together and strangle you one time in the distant future.

But look - Oooh shiny :|

Please mark the thread accordingly by editing the topic of the first post and prefix it by [DONE].
EOT for me.

Re: Login Screen Issue

PostPosted: Mar 18th, '14, 23:37
by cyber-dragon-14
OK. Will mark as done.
But know this:
I DID do the uninstall packages, and like a herd of feral rabbits, I ended up with a BOAT-LOAD of "droppings", which I IMO "cleaned up". I have rebooted and restarted numerous times since the cleanup, and did all my normal routine, and NO problems anywhere.
Thanks for the help tho.

Re: Login Screen Issue

PostPosted: Mar 18th, '14, 23:54
by doktor5000
cyber-dragon-14 wrote:I DID do the uninstall packages, and like a herd of feral rabbits, I ended up with a BOAT-LOAD of "droppings", which I IMO "cleaned up". I have rebooted and restarted numerous times since the cleanup, and did all my normal routine, and NO problems anywhere.


Whatever you think you did is irrelevant, if you can't provide proof that you did it or the output shows something else, then you didn't do it or you did the wrong thing.
As you provided no details how exactly you uninstalled (HINT: find / -name -delete does NOT uninstall packages, and rpm -evv only provides useless output - whereas the one package you should have removed was still installed, so whatever you installed was the wrong package)
And however you "cleaned up" what you called a BOAT-LOAD of "droppings" (whatever you mean by that) - I don't even want to know.