antiX Xfce Rox Panel Disappeared?

[Anonymous]

Helpful

Up

0

::

post #1

“paneltoggle.sh” (No such directory)

and among the files shown in your /usr/local/bin file manager screenshot, paneltoggle.sh is absent.

paneltoggle.sh is provided by package “desktop-defaults-rox-antix”. Is that package even still installed on your system?
To check:
sudo apt-cache policy desktop-defaults-rox-antix

Whatever has transpired, clearly your system is now “badly broken”.
Tomorrow and the next day and the next…. the “broken packages held” situation is bound to snowball.
So, do yourself a favor — reinstall.
Start from scratch, and during the course of making changes, take careful notes.
Repeatedly, after a successful change (or small batch of changes), perform an interim backup (or snapshot)
while the system is still in good working order.

[Member rej]

Helpful

Up

0

::

rj@antix17:~
$ sudo apt-cache policy desktop-defaults-rox-antix
[sudo] password for rj:
desktop-defaults-rox-antix:
Installed: (none)
Candidate: 0.4.5
Version table:
0.4.5 500
500 http://repo.antixlinux.com/stretch stretch/main amd64 Packages
500 http://repo.antixlinux.com/stretch stretch/main i386 Packages
100 /var/lib/dpkg/status
rj@antix17:~
$

Yes, I totally agree. Good advice.

And I did just that, but here’s the “however” – The new installation had some hiccups – most were easily resolvable, except for “auto-login” in Xfce desktop. On all 5 fresh installs I have since done, this same issue appears.

I “fixed” it so it would log-in, as I had this problem on the broken install also. This newest install did not fix so easily. It may have been because the apt-get update & ugrade was done right away – the only difference.

Here is what I wrote in the above post reply above:
—————————————————

Added these lines below as sudo nano
in:

lightdm-gtk-greeter.conf.d
and
lightdm/lightdm/conf.d /

added (as the 2 last lines in each file as sudo in nano editer):

autologin-user=rj
autologin-user-timeout=0

———————–
Added last 2 entries on both files – it worked and hoping it does not cause further problems from changing both files.

It was not necessary to change the “lightdm/lightdm/conf.d /“ file on the first broken original install (with no rox panel toggle) – only the “dm/lightdm-gtk-greeter.conf.d” file.

————————————————–
Made a snapshot before trying this. There are so many posts in various forums regarding Xfce auto-login issues, about how it was fixed for them. As you can see something that “works” – as with the broken install “fix” – which was apparently removing important directories, later surfaced as unfixable and would not work throughout the system. And maybe I am being a little too over-cautious now. It appears to be working quite well otherwise and I could take a chance and use just this one and see what the future brings with it.

Just wouldn’t want to load another broken installation over the existing ones on 5 machines, that is fraught with more hidden issues and will damage other files, if possible.

As far as the “broken installation” goes – just thought, if I knew what I did wrong, there would not be a repeat. You are right though – give it up and focus on the auto-login fix (it might be okay) on the new install – it is probably not going to snowball, but before loading it, I would like to attempt to be fairly certain. And maybe no-one knows the answer to this, except to try it.

I have been generously provided with enough (valuable and useful) information here, now and for anything that might be needed for the new install, to surmise that this missing panel and what is behind it, is not easily salvagable and would be a waste of time to keep trying.

This should probably be in a separate post regarding “Enable auto-login Xfce”, but if you have any insight into this auto-login fix, please let me know.

Thank you very much!

[Forum Admin rokytnji]

Helpful

Up

0

::

I don’t use auto login on anything. Even my Phone. Might be worth a try maybe leaving that out. Just saying.
As far as apt-get update && apt-get dist-upgrade after a virgin install.
That is my standard practice on my AntiX installs.
If I want XFCE. I go with MX 17 instead.
So the only step you differ from me.
I don’t install xfce and a different login manager that comes with kind of install. Plus the auto login thing.

Pay attention to my different login manager statement. Because I bet that ties in to your auto login snafu’s.

Posted this from a long in the tooth install. That is current and I keep it hard to break.

$ inxi -S
System:    Host: biker Kernel: 4.9.79-antix.1-686-smp-pae i686 bits: 32 Desktop: IceWM 1.3.8
           Distro: antiX-15-V_386-full Killah P 30 June 2015

$ sudo apt-get -f install
[sudo] password for harry: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libqt4-opengl libqt4-script libqt4-xmlpatterns libqtwebkit4
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

That apt-get -f install comes in real handy sometimes when you get that error code 1 message like you have been getting. I have not used the autoremove command. I am the great procrastinator when it comes to certain things on computers. As my inxi -S command, shows. AntiX 15 , 2015, running current.

Sometimes I drive a crooked road to get my mind straight.
Not all who Wander are Lost.
I'm not outa place. I'm from outer space.

Linux Registered User # 475019
How to Search for AntiX solutions to your problems

[Forum Admin Dave]

Helpful

Up

0

::

rej wrote:

The only problem I had a lot of trouble resolving on the new install, is auto-login. Wouldn’t do it through the regular route [control center-maintenence-user manager].

What worked: …….
=================================
As far as installing the “desktop-defaults-rox-antix 0.4.5” directory, I have either done it wrong or ……..
….this is the result:(E: Unable to correct problems, you have held broken packages.)- where are they? could not find any “broken packages” in synaptic

This may be not within-reason fixable.

[Mountbox result – below the panel entry (has been working all along).]

rj@antix17:~
$ su
Password:
root@antix17:/home/rj# =desktop-defaults-rox-antix 0.4.5
Reading package lists… Done
Building dependency tree
Reading state information… Done
Note, selecting ‘libghc-binary-prof-0.8.3.0-4351e’ for regex ‘0.4.5’
Note, selecting ‘libghc-vector-space-dev-0.10.4-5487b:i386’ for regex ‘0.4.5’
Note, selecting ‘libghc-pcap-dev-0.4.5.2-d01ab:i386’ for regex ‘0.4.5’
…. LONG LIST OF PACKAGES …….
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libghc-appar-dev:i386 : Depends: libghc-base-dev-4.9.0.0-1bac3:i386
Depends: libghc-bytestring-dev-0.10.8.1-3ddfb:i386
…. LONG LIST OF PACKAGES …….
E: Unable to correct problems, you have held broken packages.
root@antix17:/home/rj#

==================
rj@antix17:~
$ su
Password:
root@antix17:/home/rj# apt-get install mountbox-antix:amd64 (0.1.5)
bash: syntax error near unexpected token `(‘
root@antix17:/home/rj#

The autologin settings in the control centre will not update lightdm; being designed and built to update the default slim should it? So your manual edit of /etc/lightdm/lightdm.conf to add the autologin lines is the correct way to do this. Could we add the ability for the autologin script to account for the installation of lightdm and set lightdm to autologin as well… Perhaps, should we also add to this for other login managers such as kdm, gdm and xdm? We could… however at what point is it considered outside of the intended design?

As to the missing desktop-defaults-rox-antix you can search for that in synaptic and reinstall it or type as root in terminal
apt-get -f install desktop-defaults-rox-antix
In terminal would probably be better as you can put the output here, but from what you posted above you tried to install half of the repo on a regex search! As you may notice is states
"Note, selecting ‘...Insert package name here...’ for regex ‘0.4.5’"
Likely from copying and pasting the version number “0.4.5” into the terminal along with the package name “desktop-defaults-rox-antix” in the apt-get command. It is hard to say because this
root@antix17:/home/rj# =desktop-defaults-rox-antix 0.4.5
does not make much sense to me. However
root@antix17:/home/rj# apt-get install mountbox-antix:amd64 (0.1.5)
Does and it should be
root@antix17:/home/rj# apt-get install mountbox-antix

I am not sure as I have not done the procedure of installing xfce on antiX lately (as MX now exists) but my guess would be to install antiX, update antiX
apt-get update && apt-get dist-upgrade
then in the package installer Control Centre -> System -> Package installer
Select Desktop Environment -> Check XFCE4 -> Press Install
Then Menu -> Desktop -> Other Desktops -> xfce

• This reply was modified 5 years, 3 months ago by Dave. Reason: Trimmed readout

Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown

[Member rej]

Helpful

Up

0

::

Hi-

Through research, trial and error, I was able to properly configure the lightdm files to auto-login on the fresh install. Even though it worked before, I had edited the wrong file of the two, first. It is now a very good install of antiX17 Xfce.

As far as the old installation goes, it has been successfully resolved. No more errors that I could find. When I realized that the only way I would have removed anything, if I had, would have been only in synaptic. Went back to see if desktop-defaults-rox-antix was there and uninstalled. Yes it was uninstalled. Should have checked this first, instead of going to the websites on the sources list and attempting to install through terminal with my limited experience. This fixed it totally. Lesson learned – log big changes even if giving it your last ditch effort, because it may not be… Never remembered among the many things I tried, specifically uninstalling that package. Afterwards, looking for the directory and did not make the association.

Dave was correct right from the beginning – “My guess is that the package desktop-defaults-rox-antix got removed somehow as it is what contains the paneltoggle.sh script.”

In reference to rokytnji’s first post reply regarding “locate systemd”, I have monitored this on the fresh installs to see where it starts making entries. It appears to have files compiled already and then gets maybe activated with xscreensaver and redshift installs.

How do I ascertain whether I have invoked systemd or not? It certainly appears as though that is what is going on, but I don’t understand what the entries mean.
_________________________________

The following is the wiki procedure for using systemd in MX which I have not done:

——————–

https://mxlinux.org/wiki/system/systemd

Basic steps:

1.in root terminal: apt-get update && apt-get upgrade
reboot
2. when the GRUB screen comes up, click on Advanced options…, then arrow down and select the systemd version.
3. F10 to boot
4. in Step 6, the purge of those packages will take Network Manager with it, and you may not have internet access afterwards. If using a wired connection, that will likely continue. But wireless will be lost, so either connect beforehand an ethernet cable if possible, or install another network application. For example, in root terminal: apt-get install wicd-gtk.
6. still in root terminal: apt-get purge systemd-shim sysvinit
7. launch wicd to restore network connection if it has been lost.
8. reinstall removed packages in root terminal: apt-get install policykit-1-gnome hplip gvfs gvfs-backends gvfs-fuse live-usb-maker-gui grub-customizer mx-apps gufw network-manager network-manager-gnome network-manager-openconnect
9. still in root terminal: apt-get purge wicd-gtk
10.reboot

___________________________________________

Thank you all for the tips and instructions and thank you for the patience you have displayed with someone new to this level. Much appreciation.

Going to mark this “solved” and attempt to become better acquainted with the system and terminology.

• This reply was modified 5 years, 2 months ago by rej. Reason: trying to mark solved - without success

[Author]

Posts