MX Linux, MX Package Installer haven't launched twice, and got also qt error in terminal when tried to launch featherpad to read syslog

Tagiga · 09-09-2022, 12:16 AM

Hello, so

I have fairly new install of MX Linux, few weeks old. MX 21.2 XFCE. And I think I haven't done any major changes (I lack of terminal skills).

I have faced twice that my MX Package Installer won't launch. It gives me Authentication popup but after entering password: nothing, it just goes away, and MX Package Installer does not open. Tried to retry and retry: nothing.

Then tried of course go to check syslog that what's up? In terminal I got both times error with featherpad:

Quote:

No protocol specified
qt.qpa.xcb: could not connect to display :0.0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.

Aborted

And so I cannot read syslog this time.

I reboot and things are fine again, also syslog opens with Featherpad again. BUT syslog has no any idea that I encountered this: there's no error about qt or Package Installer didn't lauch...

With my limited knowledge and skills, I don't have idea what is this and what to do. Any ideas? Otherwise system has worked perfectly.

eight.bit.al · 09-09-2022, 04:46 AM

Open a terminal and type mxpi-launcher, and see what happens.

Tagiga · 09-09-2022, 05:09 AM

Quote:

Originally Posted by eight.bit.al

Open a terminal and type mxpi-launcher, and see what happens.

Currently it works fine but I try to remember do this when I encounter again this same problem.

Quote:

$ mxpi-launcher
Starting /usr/bin/mx-packageinstaller
mx-packageinstaller version: 22.8.02
QMetaObject::connectSlotsByName: Connecting slot on_comboRemote_activated() with the first of the following compatible signals: ("activated(int)", "activated(QString)")
+++ void MainWindow::setProgressDialog() +++
+++ void MainWindow::setup() +++
dpkg-query -f '${Version}' -W flatpak
"1.10.7-0+deb11u1"
cat /etc/debian_version
"11.4"
apt-get update --print-uris | grep -m1 -qE '/mx/testrepo/dists/bullseye/test/'
+++ void MainWindow::loadPmFiles() +++
+++ void MainWindow::refreshPopularApps() +++
+++ QStringList MainWindow::listInstalled() +++
dpkg --get-selections | grep -v deinstall | cut -f1
+++ void MainWindow::displayPopularApps() const +++

Tagiga · 09-10-2022, 12:03 PM

Well, it didn't take long to face again:

Quote:

$ mxpi-launcher
Starting /usr/bin/mx-packageinstaller
No protocol specified
qt.qpa.xcb: could not connect to display :0.0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.

/usr/bin/mxpi-launcher: line 73: 36654 Aborted pkexec /usr/bin/mxpi-launcher

restarting

edit.
And after restart fine again...

Heres the recent part of syslog before restart. I tried twice enter into MX Package Installer, and also in Terminal tried to open syslog with Featherpad, and got those qt errors in Terminal but nothing in here.

Code:

Sep 10 19:05:13 funnycomputername smartd[2161]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 110 to 111
Sep 10 19:17:01 funnycomputername CRON[32797]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Sep 10 19:30:01 funnycomputername CRON[33107]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/dev/null; fi)
Sep 10 19:30:01 funnycomputername anacron[33127]: Anacron 2.3 started on 2022-09-10
Sep 10 19:30:01 funnycomputername anacron[33127]: Normal exit (0 jobs run)
Sep 10 19:35:13 funnycomputername smartd[2161]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 111 to 112
Sep 10 19:41:01 funnycomputername dbus-daemon[2723]: [session uid=1000 pid=2721] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.11' (uid=1000 pid=2868 comm="Thunar --daemon ")
Sep 10 19:41:01 funnycomputername dbus-daemon[2723]: [session uid=1000 pid=2721] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Sep 10 19:41:07 funnycomputername kernel: [52575.829437] radeon_dp_aux_transfer_native: 32 callbacks suppressed
Sep 10 19:51:54 funnycomputername dbus-daemon[2723]: [session uid=1000 pid=2721] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.11' (uid=1000 pid=2868 comm="Thunar --daemon ")
Sep 10 19:51:54 funnycomputername dbus-daemon[2723]: [session uid=1000 pid=2721] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Sep 10 20:01:03 funnycomputername dbus-daemon[2723]: [session uid=1000 pid=2721] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.11' (uid=1000 pid=2868 comm="Thunar --daemon ")
Sep 10 20:01:04 funnycomputername dbus-daemon[2723]: [session uid=1000 pid=2721] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1'
Sep 10 20:06:34 funnycomputername dbus-daemon[2145]: [system] Activating service name='org.freedesktop.systemd1' requested by ':1.3' (uid=0 pid=2259 comm="/lib/systemd/systemd-logind ") (using servicehelper)
Sep 10 20:06:34 funnycomputername dbus-daemon[2145]: [system] Successfully activated service 'org.freedesktop.systemd1'
Sep 10 20:06:36 funnycomputername shutdown[37030]: shutting down for system reboot

Tagiga · 09-11-2022, 01:17 AM

System seemed to receive quite overall update today (not totally sure what was updated, there was grub stuff and so on). Need to observe situation now if this problem still surfaces.

Tagiga · 12-06-2022, 01:10 AM

Okay, after quite long time this happened again. What happened was:
I had updates available sign in clockbar. Clicked. After inputing password, I got errors that repo wasn't reachable or so.

Code:

Err:1 https://mirror.fccn.pt/repos/pub/mxlinux/MX-Packages/mx/repo bullseye/main amd64 mx-tweak amd64 22.12.01mx21
  404  Not Found [IP: 193.136.192.58 443]
E: Failed to fetch https://mirror.fccn.pt/repos/pub/mxlinux/MX-Packages/mx/repo/pool/main/m/mx-tweak/mx-tweak_22.12.01mx21_amd64.deb  404  Not Found [IP: 193.136.192.58 443]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

full upgrade complete (or was canceled)

this terminal window can now be closed

Tried to launch MX Package Installer. Nope. After inputing password, no windows, tried few times.

The green update icon was gone from clockbar, enabled it again from menu (mx updater). I tried again this way updating. But well, repo not reachable.

Wanted to change repo. Tried to launch MX Repo Manager. Nope, didn't launch. No windows after inputing password.

Tried to open log files in terminal, nope. Got these same errors:

Code:

sudo pluma syslog
No protocol specified
Cannot open display: 
Run 'pluma --help' to see a full list of available command line options.
-----
sudo featherpad syslog
No protocol specified
qt.qpa.xcb: could not connect to display :0.0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.

Aborted

AND also this again comes:

Code:

$ mxpi-launcher
Starting /usr/bin/mx-packageinstaller
No protocol specified
qt.qpa.xcb: could not connect to display :0.0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.

/usr/bin/mxpi-launcher: line 73: 368386 Aborted                 pkexec /usr/bin/mxpi-launcher

AND after reboot things are fine again. Could change repo and so on. The previous repo still down. In syslog no info about this hassle. But there was two new lines I didn't see previously:

Code:

Dec  6 09:19:24 funnycomputername kernel: [382204.819194] panel-2-docklik[205820]: segfault at 11 ip 00007fc697ed265f sp 00007ffd8dcb4240 error 4 in libdocklike.so[7fc697ebf000+16000]
Dec  6 09:19:24 funnycomputername kernel: [382204.819207] Code: 75 0b 48 83 c4 38 4c 89 e0 5d 41 5c c3 e8 99 d8 fe ff 48 89 c5 e9 56 f2 fe ff 90 55 89 f5 53 48 89 fb 48 83 ec 08 85 f6 74 31 <48> 8b 7b 10 e8 78 d4 fe ff 48 89 c7 48 85 c0 74 07 89 ee e8 49 da

Not sure is it related, close to the time I had these things.

LinWinux · 12-19-2022, 03:28 AM

Is it possible that you're not using the passwords correctly? There's supposed to be a root password and also your user password. For some things you need one, and for other things the other password, which can be incredibly confusing to new Linux users. Since I'm the only person who uses my machines I always set up the root and user passwords to be the same. That way it's less confusing and easier to get immediate results where passwords are required.

I'm also a little confused about your very first post in this message thread. Are you talking about the MX Package Manager when you go to the Start Menu, followed by MX Tools, followed by clicking with the mouse on the MX Package Manager symbol? Normally that is a very straight forward function. I've been using MX Linux (XFCE) for the past 4+ years on multiple computers and have never seen such a result as what you're describing here. Have you tried reinstalling the MX Package Manager as it states in your message?
Use this command here to do so in the future:

Code:

sudo apt reinstall mx-packageinstaller

Tagiga · 09-05-2023, 11:06 AM

Once again here

Things were drifting nicely for quite a long time but happened again.

LinWinux: Yeah, password must be correct as it would always require retyping if incorrect, correct?

I don't have separate passwords.

Tried to reistall that packagemanager but no avail – it's not launching. I guess restart again fixes this untill next time.

btw, it also gave that "no protocol" and "display problem" during the package reinstall. Dunno was it related also to this not able to launch the Packagemanager. And perhaps I just should raise my hands and just reinstall whole thing finally

My new harddisk has been waiting for its moment to show off.

Code:

Get:1 https://mirror.one.com/mx-packages/mx/repo bullseye/main amd64 mx-packageinstaller amd64 23.9 [384 kB]
Fetched 384 kB in 0s (1,031 kB/s)       
No protocol specified
Unable to init server: Could not connect: Connection refused

(dpkg-preconfigure:68485): Gtk-WARNING **: 18:42:49.728: cannot open display: :0.0
debconf: unable to initialize frontend: Gnome
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog
(Reading database ... 379097 files and directories currently installed.)
Preparing to unpack .../mx-packageinstaller_23.9_amd64.deb ...
......

LinWinux · 09-06-2023, 02:19 AM

A stab in the dark here since there is no mention of any hardware that you're using ...
Old computer or fairly new computer - Desktop PC or a Laptop?
Processor type and speed, amount of RAM installed?
Installed graphic card or GPU, which model?
Knowing these things could be helpful in analyzing bugginess.

I have never heard of anything like what you're describing, especially with installed default primary apps like the package manager. Have you tried using synaptic yet? It should be in the SYSTEM or perhaps ACCESSORIES category from the start menu. If you can't find it, try installing it:

Quote:

sudo apt-get install synaptic

Synaptic is also a package manager and it has options for fixing broken dependencies plus other functions.

I'm beginning to think that perhaps there's something wrong with the installation .iso (usb stick?) that you've been using. Like I said, never heard of issues like this before on a new or fairly new installation of MX. If you end up doing another installation, I would download another newest .iso file and before placing that on the USB stick I would also suggest using MX Tools (format USB) to format the USB stick cleanly, before adding the .iso to it for a fresh installation. After having saved whatever important data you may have, I would also recommend formatting the existing drive again, in order to avoid "confusion" between duplicate files or duplicate system entries.
Let us know if you get it all working properly again.