deleting Bunsenlabs gui

tekutofuari · 2024-01-14 13:37:17

Hello!
I have installed gnome gui and I prefere to uninstall bunsenlabs gui.
Can someone help me ?

ps. I'm new in bunsenlabs.

rbh · 2024-01-14 15:01:10

Are you also new to Linux?, then I recommend you to backup your $HOME and reinstall.

If you by some reasen prefer not to reinstall, maybe you have learned not to experiment on productive system?

To uninstall BunsenLab, back up your $HOME.
Turn to an tty console (Ctrl+Alt+F1).
Uninstall all BL packages:

$ sudo apt remove --purge bunsen-*

I have not done that, I don't know what (or any) problems you will encounter after reboot.

If you aren't low on disk-space, can´t you just leave the BL-packages and choose to login to Gnome instead?
If you wan´t to use gnome instead of BL, is it because BL is unfamiliar to you? Leaving BL gives you opportunity to examine and learn an much more resource friendly system than gnome...

hhh · 2024-01-14 16:24:33

rbh wrote:

I recommend you to backup your $HOME and reinstall.

Reinstall what? No.

rbh wrote:

To uninstall BunsenLab, back up your $HOME.
Turn to an tty console (Ctrl+Alt+F1).
Uninstall all BL packages:
$ sudo apt remove --purge bunsen-*

No need to back up home or switch to TTY, running apt doesn't touch the home directory at all and running that command isn't messing with xorg or graphics drivers, so why tty? Also, I'd use...

sudo apt purge --autoremove bunsen-* xfce4-* tint2 jgmenu

That will get rid of the BL desktop components. You can add conky to that if you don't use it. If you're now using GNOME Files (nautilus) as your file manager you can also add thunar* to that command. Any other programs that will duplicates of are GNOME uses (terminal, text editor, media player, etc...) you can also remove if you want, just post back and we can tell you what to remove. You don't really need to remove configuration files in your home directory, they take up barely any disk space.

@rbh is right about not really needing to remove anything though, the two sessions (GNOME and BunsenLabs Openbox) won't interfere with each other at all, and you'll not gain much disk space back by removing the BL packages.

rbh · 2024-01-14 16:47:49

hhh wrote:

rbh wrote:
I recommend you to backup your $HOME and reinstall.
Reinstall what? No.

I wrote; "Are you also new to Linux?". If he is, then it's a good advice.

hhh · 2024-01-14 20:58:29

True!

By the way, if --autoremove removes stuff you need, just run the command without switch. If you've already done it, you can reinstall the necessary packages by running the install command for GNOME again with the --reinstall switch...

sudo apt install --reinstall gnome

... or whatever you used to install GNOME (gnome-core, task-gnome-desktop, gnome-session...)

johnraff · 2024-01-15 02:49:52

hhh wrote:

@rbh is right about not really needing to remove anything though, the two sessions (GNOME and BunsenLabs Openbox) won't interfere with each other at all, and you'll not gain much disk space back by removing the BL packages.

This. At least for a while, why not keep both sessions installed, so you can see which one you like better?

The login screen should show icons for both Gnome and BunsenLabs - click the one you want to start up.

hhh · 2024-01-15 08:50:58

johnraff wrote:

The login screen should show icons for both Gnome and BunsenLabs - click the one you want to start up.

Gah! I totally forgot about lightdm vs GDM. If the OP has installed GNOME, they were prompted to choose a display manager. If he (giving up on being gender neutral here) went with GDM, he might as well lose lightdm...

sudo apt purge --autoremove lightdm*

GDM is weird, the session manager options don't appear until you've clicked or Entered the user. Then a menu icon appears (bottom right, a hamburger icon appears, three stacked lines) and you can choose your session from there, and then enter your password.

-edit- If you are on a laptop with a touchpad, you can enable tap-to-click for GDM via dconf-editor. Install dconf-editor...

sudo apt install dconf-editor

Open dconf Editor. Navigate to /org/gnome/desktop/peripherals/touchpad and enable tap-to-click

walter · 2024-01-15 18:23:29

If you deleted the packages 'bunsen-*' then you have no longer a 'BunsenLabs install' but a 'Debian install', correct?

hhh · 2024-01-16 01:47:49

Yes. A BunsenLabs install is a Debian install.

johnraff · 2024-01-16 01:55:18

walter wrote:

If you deleted the packages 'bunsen-*'...

Of course done through apt: 'sudo apt remove <package>' not just deleting the files.

rbh · 2024-01-16 15:45:09

walter wrote:

If you deleted the packages 'bunsen-*' then you have no longer a 'BunsenLabs install' but a 'Debian install', correct?

I would call a system installed with Debian iso an "Debian system". Any Debian derivative will revert to an Debian system when packages specific for the derivate is removed.
(Some derivates like Kali Linux", is not so easy to revert, as the only relies on ther own repositories...)
On the other hand, on a Debian system, where you install packages for a specific debian derivate, that system will be transformed to an derivate system.

Sector11 · 2024-01-16 16:54:07

rbh wrote:

On the other hand, on a Debian system, where you install packages for a specific debian derivate, that system will be transformed to an derivate system.

I would call it a fine line.

True, install from a Debian ISO and "It's Debian", no argument here.

But Install from a BL ISO and remove "all" things BL and you have a Debian system with no derivative elements. That is a Debian system.

I did not use a Debian ISO or BL ISO to install this:

 16 Jan 24 @ 13:51:58 ~
   $ neo
       _,met$$$$$gg.          sector11@SoxDog 
    ,g$$$$$$$$$$$$$$$P.       --------------- 
  ,g$$P"     """Y$$.".        OS: Debian GNU/Linux 12 (bookworm) x86_64 
 ,$$P'              `$$$.     Kernel: 6.1.0-17-amd64 
',$$P       ,ggs.     `$$b:   Uptime: 3 hours, 45 mins 
`d$$'     ,$P"'   .    $$$    Packages: 1657 (dpkg) 
 $$P      d$'     ,    $$P    Shell: bash 5.2.15 
 $$:      $$.   -    ,d$$'    Resolution: 1920x1080 
 $$;      Y$b._   _,d$P'      WM: Openbox 
 Y$$.    `.`"Y$$$$P"'         WM Theme: Lilidog-Taupebox 
 `$$b      "-.__              Theme: Lilidog-Taupe [GTK2/3] 
  `Y$$                        Icons: nouveGnomeGray [GTK2/3] 
   `Y$$.                      Terminal: terminator 
     `$$b.                    CPU: AMD Ryzen 3 2200G (4) @ 3.500GHz 
       `Y$$b.                 GPU: AMD ATI Radeon Vega Series / Radeon Vega Mo 
          `"Y$b._             Memory: 2160MiB / 13902MiB 
              `"""
                                                      
                                                      


 
 16 Jan 24 @ 13:52:02 ~
   $

But it is Debian.

#deb cdrom:[Debian GNU/Linux 12 _Bookworm_ - Official Snapshot amd64 LIVE/INSTALL Binary 20231017-08:37]/ bookworm contrib main non-free non-free-firmware

deb https://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware
# deb-src https://deb.debian.org/debian/ bookworm main contrib non-free non-free-firmware

deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
# deb-src http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware

# bookworm-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb https://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware
# deb-src https://deb.debian.org/debian/ bookworm-updates main contrib non-free non-free-firmware

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

Beardog of Lilydog fame.

johnraff · 2024-01-17 05:42:50

^as you say, a fine line.

BL doesn't do any modification of the basic system files, except via packages, which is why if you remove all the BL packages you end up with Debian.

But that's not true of every Debian derivative - some of them use modified Debian packages, for example, and some don't use packages at all but put files - or overwrite existing files - in the system directly.

Sector11 · 2024-01-17 17:21:45

johnraff wrote:

But that's not true of every Debian derivative - some of them use modified Debian packages, for example, and some don't use packages at all but put files - or overwrite existing files - in the system directly.

And that's where the line thickens and it's no longer Debian (opinion).

Also: This discussion would NOT go over well on the Debian form.

#1 2024-01-14 13:37:17

deleting Bunsenlabs gui

#2 2024-01-14 15:01:10

Re: deleting Bunsenlabs gui

#3 2024-01-14 16:24:33

Re: deleting Bunsenlabs gui

#4 2024-01-14 16:47:49

Re: deleting Bunsenlabs gui

#5 2024-01-14 20:58:29

Re: deleting Bunsenlabs gui

#6 2024-01-15 02:49:52

Re: deleting Bunsenlabs gui

#7 2024-01-15 08:50:58

Re: deleting Bunsenlabs gui

#8 2024-01-15 18:23:29

Re: deleting Bunsenlabs gui

#9 2024-01-16 01:47:49

Re: deleting Bunsenlabs gui

#10 2024-01-16 01:55:18

Re: deleting Bunsenlabs gui

#11 2024-01-16 15:45:09

Re: deleting Bunsenlabs gui

#12 2024-01-16 16:54:07

Re: deleting Bunsenlabs gui

#13 2024-01-17 05:42:50

Re: deleting Bunsenlabs gui

#14 2024-01-17 17:21:45

Re: deleting Bunsenlabs gui

Board footer