19.2 buggy? Gnome Commander not launching as root

All Gurus once were Newbies
Forum rules
There are no such things as "stupid" questions. However if you think your question is a bit stupid, then this is the right place for you to post it. Please stick to easy to-the-point questions that you feel people can answer fast. For long and complicated questions prefer the other forums within the support section.
Before you post please read how to get help
Vilsen
Level 4
Level 4
Posts: 201
Joined: Thu Nov 16, 2017 4:45 am

19.2 buggy? Gnome Commander not launching as root

Post by Vilsen » Tue Aug 20, 2019 10:32 am

I installed 19.2 (MINT MATE) on a separate disk .

Many things did NOT work at all.

Everything was updated and still.....

I installed Gnome Commander but could not open as root. 3 things said was missing.

Anyone ?

athi
Level 6
Level 6
Posts: 1461
Joined: Sun Mar 30, 2014 10:15 am
Location: USA

Re: 19.2 buggy ?

Post by athi » Tue Aug 20, 2019 10:48 am

Need more details about your setup and problems.

Please run below command in Terminal to output system information and post results. And describe the problems that you are having, providing as much details as possible.

Code: Select all

inxi -Fxz
Mint Mate 19.1. Main rig is HP 800G2 I5 6500 16GB ram, 120GB boot drive, 2x3TB, 1x4TB data drives. Oldest rig is Mate 18.3 on Dell D620 with 32bits core duo.

oldgranola
Level 4
Level 4
Posts: 357
Joined: Fri Sep 05, 2014 1:39 am

Re: 19.2 buggy ?

Post by oldgranola » Wed Aug 21, 2019 12:25 am

Vilsen wrote:
Tue Aug 20, 2019 10:32 am
I installed 19.2 (MINT MATE) on a separate disk .

Many things did NOT work at all.

Everything was updated and still.....

I installed Gnome Commander but could not open as root. 3 things said was missing.

Anyone ?
Going to need to be explicit on 'many things not working'. Just to confirm that you are actually booting (when you want) from the LM19.2 on that separate disk, please check by typing into your shell

Code: Select all

uname -r
. That will return your current booted OS and version. In addition to above, while in LM, also provide the output to

Code: Select all

lsblk
. That will provide your HD and partition situation.

Please also describe the over all situation. What is the first OS? Was it windows first or hopefully an other linux distro? What utility from which OS is managing your boot or do you choose via your BIOS?
comadore, pcDOS, hpux, solaris, vms-vax ....blah blah blah..
Yet I'm still a fn nooob

User avatar
zcot
Level 5
Level 5
Posts: 520
Joined: Wed Oct 19, 2016 6:08 pm

Re: 19.2 buggy ?

Post by zcot » Wed Aug 21, 2019 12:58 am

gnome-commander has a dependency on gksudo and is not provided with a modern polkit setup.

https://gitlab.gnome.org/GNOME/gnome-co ... /issues/79

decrepit
Level 3
Level 3
Posts: 184
Joined: Mon Dec 03, 2018 4:07 am

Re: 19.2 buggy ?

Post by decrepit » Wed Aug 21, 2019 6:52 am

Just checked on software manager, it had good reviews up till April 2017, then went rapidly downhill

Vilsen
Level 4
Level 4
Posts: 201
Joined: Thu Nov 16, 2017 4:45 am

Re: 19.2 buggy ?

Post by Vilsen » Wed Aug 21, 2019 7:16 am

Code: Select all

nitton2@nitton2-desktop:~$ inxi -Fxz
System:
  Host: nitton2-desktop Kernel: 4.15.0-55-generic x86_64 bits: 64 
  compiler: gcc v: 7.4.0 Desktop: MATE 1.22.0 Distro: Linux Mint 19.2 Tina 
  base: Ubuntu 18.04 bionic 
Machine:
  Type: Desktop Mobo: ASRock model: Z77 Pro4 serial: <filter> 
  BIOS: American Megatrends v: P1.40 date: 07/13/2012 
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325 charge: 100% 
  status: Discharging 
CPU:
  Topology: Quad Core model: Intel Core i5-3570K bits: 64 type: MCP 
  arch: Ivy Bridge rev: 9 L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 27201 
  Speed: 1601 MHz min/max: 1600/3800 MHz Core speeds (MHz): 1: 1639 2: 1606 
  3: 1620 4: 1684 
Graphics:
  Device-1: Intel Xeon E3-1200 v2/3rd Gen Core processor Graphics 
  vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 
  Display: x11 server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel Ivybridge Desktop v: 4.2 Mesa 19.0.2 
  direct render: Yes 
Audio:
  Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: ASRock 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Sound Server: ALSA v: k4.15.0-55-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASRock driver: r8169 v: 2.3LK-NAPI port: e000 bus ID: 04:00.0 
  IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 4.55 TiB used: 23.62 GiB (0.5%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB 
  ID-2: /dev/sdb vendor: Western Digital model: WD40EFRX-68N32N0 
  size: 3.64 TiB 
Partition:
  ID-1: / size: 58.89 GiB used: 23.62 GiB (40.1%) fs: ext4 dev: /dev/sda8 
  ID-2: swap-1 size: 14.96 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-0 
Sensors:
  System Temperatures: cpu: 39.0 C mobo: N/A 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 191 Uptime: 46m Memory: 14.64 GiB used: 1.31 GiB (8.9%) 
  Init: systemd runlevel: 5 Compilers: gcc: 7.4.0 Shell: bash v: 4.4.20 
  inxi: 3.0.32 
nitton2@nitton2-desktop:~$ 

Code: Select all

uname -r
nitton2@nitton2-desktop:~$ uname -r
4.15.0-55-generic
nitton2@nitton2-desktop:~$ 

Code: Select all

nitton2@nitton2-desktop:~$ lsblk
NAME                MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda                   8:0    0 931,5G  0 disk 
├─sda1                8:1    0   243M  0 part 
├─sda2                8:2    0  58,7G  0 part 
├─sda3                8:3    0  48,8G  0 part 
├─sda4                8:4    0   184G  0 part 
├─sda5                8:5    0 232,7G  0 part 
│ ├─mint--vg-swap_1 253:0    0    15G  0 lvm  [SWAP]
│ └─mint--vg-root   253:1    0 217,7G  0 lvm  
├─sda6                8:6    0  97,7G  0 part 
├─sda7                8:7    0  88,5G  0 part 
├─sda8                8:8    0  60,1G  0 part /
├─sda9                8:9    0  59,5G  0 part 
└─sda10               8:10   0 101,3G  0 part 
sdb                   8:16   0   3,7T  0 disk 
└─sdb1                8:17   0   3,7T  0 part 
nitton2@nitton2-desktop:~$ 
nitton2@nitton2-desktop:~$ 
nitton2@nitton2-desktop:~$ 
nitton2@nitton2-desktop:~$ 
nitton2@nitton2-desktop:~$ 
When I was told to update the Updater I did so but the same messages
came every time but today suddenly something happened.



Code: Select all

mintupdate (1:5.7.9~gm10) bionic; urgency=medium

* Fix non-mainline kernel installation failing
* Fix mainline kernel changelogs not getting displayed in the update details
pane anymore.
* Fix being able to add invalid refresh schedule values via dconf
Example of strange behavior:


When I tried to start GNOME-COMMANDER AS ROOT

I got this:


xdg-su, gnomesu, kdesu eller beesu hittades inte

in english:

xdg-su, gnomesu, kdesu or beesu was not found


Let's start with that only ; I have installed GNOME-Commander since
at least 17.3 and I am an old fan of Norton Commander so I want it
but never before have I gotten this strange message.

Vilsen
Level 4
Level 4
Posts: 201
Joined: Thu Nov 16, 2017 4:45 am

Re: 19.2 buggy ?

Post by Vilsen » Wed Aug 21, 2019 7:27 am

Code: Select all

nitton2@nitton2-desktop:~$ systemd-analyze blame
         12.615s apt-daily.service
           526ms dev-sda8.device
           519ms apt-daily-upgrade.service
           507ms udisks2.service
           322ms NetworkManager.service
           214ms ubuntu-system-adjustments.service
           210ms networkd-dispatcher.service
           190ms systemd-logind.service
           183ms lvm2-pvscan@8:5.service
           169ms systemd-udevd.service
           152ms lvm2-monitor.service
           151ms upower.service
           149ms ModemManager.service
           142ms accounts-daemon.service
           142ms grub-common.service
           141ms lightdm.service
           137ms plymouth-quit-wait.service
           102ms systemd-resolved.service
           100ms systemd-journal-flush.service
            99ms apparmor.service
            90ms keyboard-setup.service
            83ms colord.service
            80ms thermald.service
lines 1-23...skipping...
         12.615s apt-daily.service
           526ms dev-sda8.device
           519ms apt-daily-upgrade.service
           507ms udisks2.service
           322ms NetworkManager.service
           214ms ubuntu-system-adjustments.service
           210ms networkd-dispatcher.service
           190ms systemd-logind.service
           183ms lvm2-pvscan@8:5.service
           169ms systemd-udevd.service
           152ms lvm2-monitor.service
           151ms upower.service
           149ms ModemManager.service
           142ms accounts-daemon.service
           142ms grub-common.service
           141ms lightdm.service
           137ms plymouth-quit-wait.service
           102ms systemd-resolved.service
           100ms systemd-journal-flush.service
            99ms apparmor.service
            90ms keyboard-setup.service
            83ms colord.service
            80ms thermald.service
            70ms polkit.service
            69ms systemd-udev-trigger.service
            69ms systemd-tmpfiles-setup.service
            67ms systemd-journald.service
            48ms networking.service
            47ms pppd-dns.service
            44ms gpu-manager.service
            43ms dns-clean.service
            40ms avahi-daemon.service
            40ms alsa-restore.service
            38ms speech-dispatcher.service
            37ms packagekit.service
            36ms kerneloops.service
            33ms user@1000.service
            33ms hddtemp.service
            32ms lm-sensors.service
            30ms plymouth-read-write.service
            29ms systemd-modules-load.service
            26ms systemd-tmpfiles-setup-dev.service
            24ms systemd-sysctl.service
            24ms rsyslog.service
            15ms plymouth-start.service
            14ms blk-availability.service
            14ms ufw.service
            13ms dev-hugepages.mount
            13ms systemd-remount-fs.service
            12ms ntp.service
            12ms systemd-tmpfiles-clean.service
            11ms dev-mapper-mint\x2d\x2dvg\x2dswap_1.swap
            11ms setvtrgb.service
            10ms sys-kernel-debug.mount
             9ms kmod-static-nodes.service
             8ms ureadahead-stop.service
             6ms console-setup.service
             6ms sys-fs-fuse-connections.mount
             5ms systemd-update-utmp.service
             5ms systemd-update-utmp-runlevel.service
             4ms sys-kernel-config.mount
             3ms systemd-user-sessions.service
             3ms dev-mqueue.mount
             3ms wpa_supplicant.service
             3ms rtkit-daemon.service
             3ms systemd-random-seed.service
             2ms openvpn.service
lines 10-67/67 (END)

User avatar
karlchen
Level 20
Level 20
Posts: 11340
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: 19.2 buggy ?

Post by karlchen » Wed Aug 21, 2019 7:31 am

Hi, Vilsen.
Vilsen wrote:
Wed Aug 21, 2019 7:27 am

Code: Select all

nitton2@nitton2-desktop:~$ systemd-analyze blame
         12.615s apt-daily.service
           526ms dev-sda8.device
           519ms apt-daily-upgrade.service
           507ms udisks2.service
           322ms NetworkManager.service
           214ms ubuntu-system-adjustments.service
           210ms networkd-dispatcher.service
           190ms systemd-logind.service
           183ms lvm2-pvscan@8:5.service
           169ms systemd-udevd.service
           152ms lvm2-monitor.service
           151ms upower.service
           149ms ModemManager.service
           142ms accounts-daemon.service
           142ms grub-common.service
           141ms lightdm.service
           137ms plymouth-quit-wait.service
           102ms systemd-resolved.service
           100ms systemd-journal-flush.service
            99ms apparmor.service
            90ms keyboard-setup.service
            83ms colord.service
            80ms thermald.service
lines 1-23...skipping...
         12.615s apt-daily.service
           526ms dev-sda8.device
           519ms apt-daily-upgrade.service
           507ms udisks2.service
           322ms NetworkManager.service
           214ms ubuntu-system-adjustments.service
           210ms networkd-dispatcher.service
           190ms systemd-logind.service
           183ms lvm2-pvscan@8:5.service
           169ms systemd-udevd.service
           152ms lvm2-monitor.service
           151ms upower.service
           149ms ModemManager.service
           142ms accounts-daemon.service
           142ms grub-common.service
           141ms lightdm.service
           137ms plymouth-quit-wait.service
           102ms systemd-resolved.service
           100ms systemd-journal-flush.service
            99ms apparmor.service
            90ms keyboard-setup.service
            83ms colord.service
            80ms thermald.service
            70ms polkit.service
            69ms systemd-udev-trigger.service
            69ms systemd-tmpfiles-setup.service
            67ms systemd-journald.service
            48ms networking.service
            47ms pppd-dns.service
            44ms gpu-manager.service
            43ms dns-clean.service
            40ms avahi-daemon.service
            40ms alsa-restore.service
            38ms speech-dispatcher.service
            37ms packagekit.service
            36ms kerneloops.service
            33ms user@1000.service
            33ms hddtemp.service
            32ms lm-sensors.service
            30ms plymouth-read-write.service
            29ms systemd-modules-load.service
            26ms systemd-tmpfiles-setup-dev.service
            24ms systemd-sysctl.service
            24ms rsyslog.service
            15ms plymouth-start.service
            14ms blk-availability.service
            14ms ufw.service
            13ms dev-hugepages.mount
            13ms systemd-remount-fs.service
            12ms ntp.service
            12ms systemd-tmpfiles-clean.service
            11ms dev-mapper-mint\x2d\x2dvg\x2dswap_1.swap
            11ms setvtrgb.service
            10ms sys-kernel-debug.mount
             9ms kmod-static-nodes.service
             8ms ureadahead-stop.service
             6ms console-setup.service
             6ms sys-fs-fuse-connections.mount
             5ms systemd-update-utmp.service
             5ms systemd-update-utmp-runlevel.service
             4ms sys-kernel-config.mount
             3ms systemd-user-sessions.service
             3ms dev-mqueue.mount
             3ms wpa_supplicant.service
             3ms rtkit-daemon.service
             3ms systemd-random-seed.service
             2ms openvpn.service
lines 10-67/67 (END)
What is the issue which you see in your systemd-analyze blame output? I do not spot any. So why did you post it? Nothing exciting or extra-ordinary in it.

Regards,
Karl
Image
Linux Mint 19.2 32-bit xfce Desktop, Total Commander 9.22a 32-bit
Haß gleicht einer Krankheit, dem Miserere, wo man vorne herausgibt, was eigentlich hinten wegsollte. (Goethe)

Vilsen
Level 4
Level 4
Posts: 201
Joined: Thu Nov 16, 2017 4:45 am

Re: 19.2 buggy ?

Post by Vilsen » Wed Aug 21, 2019 7:41 am

OK, sorry - I thought the item at the top was a little time consuming though.

Anyway : another example of strange behavior: When I make a screen-capture and save the pictur to
the desktop it does not show up .

When I start the filemanager : THEN IT SHOWS on the desktop !

athi
Level 6
Level 6
Posts: 1461
Joined: Sun Mar 30, 2014 10:15 am
Location: USA

Re: 19.2 buggy ?

Post by athi » Wed Aug 21, 2019 7:45 am

Your inxi -Fxz output looks OK, strange partitions layout but should still work. Older desktop hardware, using Intel integrated graphic but no unusual components or wifi.

zcot provided link https://gitlab.gnome.org/GNOME/gnome-co ... /issues/79 have a solution to your gnome-commander problem at bottom of page.
Mint Mate 19.1. Main rig is HP 800G2 I5 6500 16GB ram, 120GB boot drive, 2x3TB, 1x4TB data drives. Oldest rig is Mate 18.3 on Dell D620 with 32bits core duo.

ColdBootII
Level 4
Level 4
Posts: 483
Joined: Wed Aug 02, 2017 8:19 am

Re: 19.2 buggy ?

Post by ColdBootII » Wed Aug 21, 2019 7:52 am

Vilsen wrote:
Wed Aug 21, 2019 7:41 am

Anyway : another example of strange behavior: When I make a screen-capture and save the pictur to
the desktop it does not show up .

When I start the filemanager : THEN IT SHOWS on the desktop !
Not so here, works every time, without any need for file manager intervention...

User avatar
karlchen
Level 20
Level 20
Posts: 11340
Joined: Sat Dec 31, 2011 7:21 am
Location: Germany

Re: 19.2 buggy ?

Post by karlchen » Wed Aug 21, 2019 8:31 am

Hi, vilsen.

12 seconds consumed by apt-daily.service is not unusual. I will read much longer times here, especially if this is during the first startup on a given day.
The time which apt-daily.service consumes does not have any influence on the overall system startup time (time between power on => login screen => desktop fully functional).

Regards,
Karl
Image
Linux Mint 19.2 32-bit xfce Desktop, Total Commander 9.22a 32-bit
Haß gleicht einer Krankheit, dem Miserere, wo man vorne herausgibt, was eigentlich hinten wegsollte. (Goethe)

User avatar
Flemur
Level 17
Level 17
Posts: 7209
Joined: Mon Aug 20, 2012 9:41 pm
Location: Potemkin Village

Re: 19.2 buggy ?

Post by Flemur » Wed Aug 21, 2019 8:39 am

Vilsen wrote:
Wed Aug 21, 2019 7:16 am
Let's start with that only ; I have installed GNOME-Commander since
at least 17.3 and I am an old fan of Norton Commander so I want it
but never before have I gotten this strange message.
"They" (probably 'freedesktop'**) decided that 'gksu/gksudo' are too simple and replaced them with some complicated stuff, which FWIW, has never worked for me. ("This incident will be reported!" LOL)

Here's how to fix that so you can use your preferred software:
viewtopic.php?t=285675
I replaced gksudo as soon as it was removed, no problems at all since then.

** Edit: yup.
https://www.freedesktop.org/software/po ... xec.1.html
Please edit your original post title to include [SOLVED] if/when it is solved!
Your data and OS are backed up....right?
Mint 19.1 Xfce/fluxbox
Manjaro openbox/fluxbox

Vilsen
Level 4
Level 4
Posts: 201
Joined: Thu Nov 16, 2017 4:45 am

Re: 19.2 buggy ?

Post by Vilsen » Fri Aug 23, 2019 3:36 am

Karlchen wrote:

12 seconds consumed by apt-daily.service is not unusual. I will read much longer times here, especially if this is during the first startup on a given day.
The time which apt-daily.service consumes does not have any influence on the overall system startup time (time between power on => login screen => desktop fully functional).


I think we have discussed this matter before ? Remember - I have a perfectly running Linux MINT Mate 17.3 that starts
lightning fast and then I moved to 18.3 with all that timeconsuming work to make all settings and installation of all programs
I need and all the settings of those programs and all the tweaks and firefox-settings and thunderbird-settings and all other
time-consuming things and so forth and then it did not start as fast as 17.3.

Now everybody is saying : leave 18.3 and jump to 19.2 ! So I have to make all these time-consuming things all over again
just to be sure that I have the latest and smartest version.

and then it starts far more slower..................again.

ColdBootII
Level 4
Level 4
Posts: 483
Joined: Wed Aug 02, 2017 8:19 am

Re: 19.2 buggy ?

Post by ColdBootII » Fri Aug 23, 2019 3:48 am

Yes, it does seem that we have not gained much in booting speed since introduction of systemd. But than again, newer software never gets "lean and mean" and thereby faster, starting from kernel, ending with everything else.

Still, your booting time is not bad at all and given we boot once a day anyway, what does it matter if it's +/- few seconds?

User avatar
Moem
Level 19
Level 19
Posts: 9372
Joined: Tue Nov 17, 2015 9:14 am
Location: The Netherlands
Contact:

Re: 19.2 buggy ?

Post by Moem » Fri Aug 23, 2019 3:51 am

If your home is a separate partition (not a directory inside of root), you can simply leave it unformatted* during a reinstallation and bring pretty much all of your tweaks along. Saves tons of time and is pretty safe.

*and also make a backup of it before you start, just in case
Image

If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!

Vilsen
Level 4
Level 4
Posts: 201
Joined: Thu Nov 16, 2017 4:45 am

Re: 19.2 buggy ?

Post by Vilsen » Sat Aug 24, 2019 6:07 am

It is strange how some want to claim that startup time is of little importance: Here I have shown my acquaintances how exceptionally good linux MINT Mate is (17.3) in ALL regards and how effective it is and how useless Windows is. Plus it's free! And all the programs you need in your day-to-day work are available without having to get insecure "pirated" copies of Windows; Something that has been going on for more than 35 years! All the hell problems Windows has brought so far with us - now that Windows 10 is where they are sharpened properly -
all of us with RESPONSIBILITY have had to spend considerable time on all the frills and hassles that this OS's
entailed, all the "patches" and updates and something like that
most people agree: A nauseating SOUP from too many chefs.



Having a separate /home-partition I have also tried on different occasions which is one of the explanations for "the strange partitioning" that someone commented on (the remainder is just for tests of different versions as you can not trust that everything works directly ) but I couldn't understand how this would make me get rid of all the time consuming settings and everything else I need to do to get the new version to mimic the previously well functioning in all respects.

I am a novice, ie I am USER not a programmer but I have had to spend a lot of time on everything from DOS time through the Windows misery to
the happy day when I put my teeth in
Ubuntu sometime in 2005 but when they danced to the look of something that fit well in kindergarten
then - thankfully - I went to Linux MINT Mate.

Since then I have been able to spend all my time on the work instead of the hassle of the computer.

Someone remarked that I had an old computer:
Yes, not everyone is made of money and in my world you do not buy a new computer every two years and if I could afford I would buy a package of thunder in the style of
Apple's MAC PRO which costs between 4000 and 8000 Euro. But I have to settle for what I have, with the graphics inside the CPU chip!

At least I have 16 GB of RAM, something that the common store-computer rarely comes with as standard.

And this RAM's size I have, among other things. used to put things like in the past the ham in the Swap partition and so on. I read the tips on IMPROVEMENT and REFINING and CUTTING that you can do and then I get advice & tips from you: YOU WHO KNOW ! (sorry about the bad language - google translate is a joke )

All these "tweaks" I want with me when I change from t.e.x. 18.3 to 19.3 (though now there are only 19.2) and then I make as many "tweaks" too
Firefox & Thunderbird.

I make sure my work environment is clean and the
appearance is beautiful & appropriate.

I hate what has become standard in Windows 10 with a faded background and sharp corners on all windows and patches.

Everything is blown away and you have to start from scratch when you install the new version of Mint Mate.


I don't mind new ideas regarding looks and so but let me choose, thank you!
etc.
Then we have Libre -Office, above all: Write then
which is also set in the way I wish. How do I get this with me when I installed 19.2? The scanner, VLC, smart and fast bookmarks to certain URL:s directly on the PANEL ! Differnet tools like Mintstick etc. dconf-editor , Root-Gnome-Commander for expert-file-management etc.

I can keep and enumerate all the programs I use daily and the special settings that are made for these but no one can hear this without you probably understand what I mean.

Here I have spent hours and days and years refining this fantastic work tool and putting up highways on the "panel", removing a troublesome background and everything, everything else.

I like Linux. My friends condemn Linux.
My acquaintances who all use windows (but many of them who curse everything after windows 7 !!!)
says it's not smart with the macro-kernel / monolithic kernel that linux runs with unlike the micro kernel that windows uses - I don't agree with that.

This makes me - as a layman - think that maybe it would be possible to keep all the settings / tweaks you made and just update the kernel
every time this is needed?

Am I out cycling now?


Can you please clarify what / how you mean by:


"If your home is a separate partition (not a directory inside of root), you can simply leave it unformatted * during a reinstall and bring pretty much all of your tweaks along. Saves tons of time and is pretty safe.

* and also make a backup of it before you start, just in case "


Aren't all settings are under / root ??


Best regards: A lost novice but daily user of the best OS provided free of charge

ColdBootII
Level 4
Level 4
Posts: 483
Joined: Wed Aug 02, 2017 8:19 am

Re: 19.2 buggy ?

Post by ColdBootII » Sat Aug 24, 2019 7:09 am

In short, if you keep /home on a separate partition and don't format it, all your beautiful & appropriate appearance will survive an install/upgrade provided that the themes you use, have been also installed and reside in your /home. The same goes for application settings. Ever tried looking in ~/.config folder? They're there...

As per booting times and how they/whether they matter, I was booting Mint 18.x with Cinnamon and 4.10 kernel, Nvidia 380.x driver in 4.5s. Now, in 19.2 with Mate and 4.15 kernel & Nvidia 390 I get 6-6.2s booting time and I don't feel the difference, still less would I moan about 2s difference. You also seem to have a SSD as the booting disk and except for occasional apt-daily-service, you have nothing to moan about either.

Cheers.

User avatar
Moem
Level 19
Level 19
Posts: 9372
Joined: Tue Nov 17, 2015 9:14 am
Location: The Netherlands
Contact:

Re: 19.2 buggy ?

Post by Moem » Sat Aug 24, 2019 7:12 am

No, user settings are generally under home. I have brought my old home partition along from 17.3 32-bits to 18.1 64-bits and pretty much all settings I had tweaked followed me to my new version of Mint with very few and small problems (2, duplicate programs, easily fixed). Now this same partition holds all my data and stuff under 19.2. I did have to reinstall my software, but the settings for the OS and for Cinnamon, and for the software once installed, came right back.

System settings will often be in /etc. You could also copy that over and see what happens.

I must confess that I did not read all of your post (most of it seemed more like venting than part of an answerable question) but this question jumped out at me. You may get more/better responses if you keep the questions clear and brief, and the venting separate.
Image

If your issue is solved, kindly indicate that by editing the first post in the topic, and adding [SOLVED] to the title. Thanks!

Vilsen
Level 4
Level 4
Posts: 201
Joined: Thu Nov 16, 2017 4:45 am

Re: 19.2 buggy ?

Post by Vilsen » Sun Sep 15, 2019 2:41 am

The question must be asked:

Who decides which programs
may live on when each new one
version is released and opportunities disappear:


Someone mentioned the "popularity" associated with
the reason Gnome-Commander quit
to operate in ROOT mode.

We have now introduced a system where the mob is going
decide which programs may be available?

Freedom of choice is watered down on the basis of
a "voting policy"?

The reason why Gnome-Commander no longer
can be run in ROOT mode is that some programs
NO LONGER exists in version 19 of Linux MINT Mate.

WHY IS THIS NO LONGER?

WHO HAVE DECIDED THAT THEY WILL BE REMOVED?

What does the Ubuntu gang have to do with it?

I left Ubuntu on the basis of that
the imitations of what happened in the MS-WINDOWS world
and that the interface was childish and found
MINT that was AWESOME and expedient.

Now I see trends here too that there is one
change for the worse.

What sense then has programs like TIMESHIFT about
I, as a user, can NOT use any longer
programs that I have used for 35 years?

All the functionality that was in the Norton sedan
Commander was created has been incrementally improved via
some versions that have gone under Windows and now
has become perfect in the Linux environment.

Do you take this / anyone / who? away from us users!

It is incomprehensible how to remove the "subprograms"
like this and other programs are needed to be able to
work.

Who made this decision?
WHY DID xdg-su, gnomesu, kdesu or beesu DISAPPEAR ???


Google tanslate should apologize for making
such a bad language when translating from Swedish
to English .

Post Reply

Return to “Newbie Questions”