It seems VLC 4.0 beta is the only app with start issues (Segmentation fault (core dumped)).
So I will mark this issue as solved (for now)
Search found 9 matches
- Sun Jan 16, 2022 8:14 am
- Forum: Installation & Boot
- Topic: [Solved] After upgrade to Mint 20.3 several graphical apps no longer start
- Replies: 2
- Views: 1690
- Sun Jan 16, 2022 8:03 am
- Forum: Installation & Boot
- Topic: [Solved] After upgrade to Mint 20.3 several graphical apps no longer start
- Replies: 2
- Views: 1690
Re: After upgrade to Mint 20.3 several graphical apps no longer start
After the "update manager" issue ended up being permissions related, I tried to re-establish ownership of all files in my home directory sudo chown -R ewald:ewald /home/ewald After this a series of apps started to work again, including Chrome and Chromium (but e.g. not VLC). So if you enco...
- Sun Jan 16, 2022 7:55 am
- Forum: Installation & Boot
- Topic: [Solved] After upgrade to Mint 20.3 several graphical apps no longer start
- Replies: 2
- Views: 1690
[Solved] After upgrade to Mint 20.3 several graphical apps no longer start
After (seemingly successful) update from 20.1 to 20.3, several issues popped up. After solving the "update manager can no longer refresh" issue, a series of (3rd party) graphical applications refuse to start. The error messages are sometimes a bit mysterious... When looking at the processe...
- Sun Jan 16, 2022 7:23 am
- Forum: Installation & Boot
- Topic: {SOLVED] After Mint 20.3 upgrade, Update Manager can no longer refresh
- Replies: 1
- Views: 590
Re: After Mint 20.3 upgrade, Update Manager can no longer refresh
Figured out that I can launch update manager from the command line as "mintupdate-launcher" This however hangs and no windows shows. The errors though shed some light: usr/lib/linuxmint/mintUpdate/mintUpdate.py:1285: DeprecationWarning: Gdk.threads_init is deprecated Gdk.threads_init() /us...
- Sun Jan 16, 2022 6:58 am
- Forum: Installation & Boot
- Topic: {SOLVED] After Mint 20.3 upgrade, Update Manager can no longer refresh
- Replies: 1
- Views: 590
{SOLVED] After Mint 20.3 upgrade, Update Manager can no longer refresh
Yesterday I upgraded from 20.1 to 20.3. The upgrade went without errors, yet am facing a number of issues. The first one is with update manager: when hitting refresh, all seems to work but in the end there is an error: "could not refresh". From the "info" menu the cause is listed...
- Thu Feb 04, 2021 5:35 am
- Forum: Installation & Boot
- Topic: upower.service won't start
- Replies: 21
- Views: 2941
Re: upower.service won't start
I have similar issues on a fresh install of Mint 20.1. It seems related to power management of the USB bus (BIOS setting?) but when I boot into Mint 18 all goes well. When I execute '/usr/lib/upower/upowerd -v', it takes about 40 seconds to register the USB subsystem and displays tens of messages of...
- Sat Aug 11, 2018 6:22 am
- Forum: Networking
- Topic: (Mint 19 Beta) dns-nameservers term no longer works
- Replies: 8
- Views: 5164
Re: (Mint 19 Beta) dns-nameservers term no longer works
Another simple solution to fix DNS lookup without the need to install resolvconf... Systemd maintains /run/systemd/resolve/resolv.conf with the proper DNS information as per the new systemd-resolve service. However /etc/resolv.conf is a symbolic link to ../run/resolvconf/resolv.conf which resolves a...
- Sun Oct 08, 2017 12:22 pm
- Forum: Graphics Cards & Monitors
- Topic: LM18.2 - Cinnamon running in software rendering mode
- Replies: 0
- Views: 498
LM18.2 - Cinnamon running in software rendering mode
Many thanks for all the hard work going in these fabulous LM releases! Recently I upgraded from LM18.1 to 18.2. While previous updates went smooth, this one came with a few challenges, most of which were fixed quite easily. For example, /boot/efi got somehow unmounted in the upgrade process, resulti...
- Wed Aug 16, 2017 11:58 am
- Forum: Graphics Cards & Monitors
- Topic: Random (Nearly) Black Screen
- Replies: 2
- Views: 358
Re: Random (Nearly) Black Screen
I am not a Linux Mint expert, but I assume you will need to provide the output of "inxi -Fx" or at least "inxi -Gx" with "uname -a" to know what kernel you are running. Take a look at what "dmesg" tells you (or /var/log/kern.log) as well "/var/log/Xorg.0....