Page 2 of 3

Re: QV version 240423 pre-alpha uploaded

Posted: Thu Apr 25, 2024 1:25 am
by BarryK
BarryK wrote: Wed Apr 24, 2024 1:14 pm
ghoen wrote: Wed Apr 24, 2024 12:48 pm

Update devx :

Try the following steps te reproduce it.
- pkg on desktop
- PKGget
- Find: devx / GO / search all repositories
- select devx-240423
- Install

Message : you declined to install this package : devx-240423

then it stops.

It is not a big problem (for me), just reporting it.

Hmmm, strange.
The only different thing I did was select "pet-void" radiobutton, then "utility" radiobutton, then clicked on the devx package, and install worked.

It seems that PKGget has a problem if don't go to the "pet-void" repo where the pkg is.

I have used the search box to find Void packages and that has worked. But then, "void-current" is the default repo.

OK, figured it out. Changes for QV in /usr/local/petget/installpreview.sh caused the breakage.

There have been lots of fixes since the 23rd, better to bring out a new release of QV, rather than just post fixed script here.


Re: QV version 240423 pre-alpha uploaded

Posted: Thu Apr 25, 2024 1:29 am
by BarryK
don570 wrote: Wed Apr 24, 2024 11:09 pm

QV 240423 - installed with qv-installer using fatdog64
______________________________
-recorded audio
_______________
-I was able to set up samba server to transfer files with my chromebook
However easyshare app gave an error message when I clicked 'Apply'
testparm.log had strange message but services did launch which is why the share was made with my chromebook

Code: Select all

Load smb config files from GЏzU
Error loading services.

Screenshot-samba.png

I have only done a basic test with samba, which worked.
Booted EasyOS Pyro-series on my old Compaq PC and exported a folder via samba.
In QV was able to mount the folder and transfer files, no error messages.


Re: QV version 240423 pre-alpha uploaded

Posted: Thu Apr 25, 2024 12:00 pm
by ghoen

Ok. I will wait before I continue trying.


Re: QV version 240423 pre-alpha uploaded

Posted: Thu Apr 25, 2024 3:58 pm
by BarryK

Re: QV version 240423 pre-alpha uploaded

Posted: Thu Apr 25, 2024 9:08 pm
by ghoen
ghoen wrote: Thu Apr 25, 2024 12:00 pm

Ok. I will wait before I continue trying.

Problem solved in QV version 240425.


Re: QV version 240425 pre-alpha uploaded

Posted: Thu Apr 25, 2024 9:13 pm
by don570

I noticed that older pet packages don't install properly
My baconrecorder didn't show in menu and older wine app didn't install code in /opt

When I made pets in qv they installed perfectly.

For instance here is wine pet...
viewtopic.php?t=11358
________________________________________________________


Re: QV version 240425 pre-alpha uploaded

Posted: Thu Apr 25, 2024 11:13 pm
by nnriyer

Sir, We need proper installer for qv etc. It should be easy to install without manual intervention


QV version 240425

Posted: Fri Apr 26, 2024 7:27 am
by Caramel
BarryK wrote: Thu Apr 25, 2024 3:58 pm

QV 240425 release:

https://bkhome.org/news/202404/qv-versi ... eased.html

Just installed.
After first creation of a snapshot, the information on desktop has changed, but the number is 3 instead 2 (btrfs subvolume list / confirm 2 subvolumes was created) and the date is a day in advance.
After second snapshot, the number is 4 (increased by 1) and the date has not changed (still a day in advance)


QV version 240425 - problem Anydesk with Pam

Posted: Fri Apr 26, 2024 9:02 am
by Caramel

Return of the problem with Pam and flatpak Anydesk (see viewtopic.php?t=10439 for the problem in EasyVoid)

Pam prevents the launch of the flatpak Anydesk with the error message :

The logged in user differs from the (non-root) user this process runs as

It does not like the "run-as-client" trick

For test, I moved many files installed by the pakages pam, pam-libs and rebooted. Then Anydesk started.

For the deactivation to take effect, a reboot is necessary. So it's difficult to know which files moved are enough to prevent pam

EDIT: the move of the 6 .so files libpam libpamc lipam_misc in /usr/lib is enough to block pam
EDIT2: the move of the 2 .so files libpam in /usr/lib is enough to block pam

EDIT3: Ultimately the move of the symlink libpam.so.0 is sufficient for blocking pam


Re: QV version 240425

Posted: Fri Apr 26, 2024 11:04 am
by BarryK
Caramel wrote: Fri Apr 26, 2024 7:27 am
BarryK wrote: Thu Apr 25, 2024 3:58 pm

QV 240425 release:

https://bkhome.org/news/202404/qv-versi ... eased.html

Just installed.
After first creation of a snapshot, the information on desktop has changed, but the number is 3 instead 2 (btrfs subvolume list / confirm 2 subvolumes was created) and the date is a day in advance.
After second snapshot, the number is 4 (increased by 1) and the date has not changed (still a day in advance)

Yes, at first bootup. snapshot 2 is created, as a backup of pristine conditions.
You can see it in /mnt/${WKG_DEV}/quantumvis/snapshot-record

The date is only yymmdd
Regarding being a day in advance, I attempted to obtain the accurate date in the initrd. This code in 'init' script:

Code: Select all

###set date and time###
#see TZ set early in script.
#20240320 settimeofday() error, see: https://bkhome.org/news/202402/hwclock-fail-in-easyvoid-603.html
# getting this error in initrd. now have static hwclock with old musl
# ...it does not accept -l requires --localtime
CLKflg=1
if [ -e /sys/class/rtc/rtc0 ];then
 #20240424 get timezone...
 if [ -e /tempmnt/${QV}/etc/localtime ];then
  NEWTZ="$(readlink /tempmnt/${QV}/etc/localtime)" #ex: /usr/share/zoneinfo/Etc/GMT-8
  mkdir -p ${NEWTZ%/*}
  cp -a ${NEWTZ} ${NEWTZ%/*}/
  cp -a /tempmnt/${QV}/etc/localtime /etc/
  unset TZ #otherwise it will override /etc/localtime
  export TZ
 fi
 if [ -s /tempmnt/${QV}/etc/clock ];then
. /tempmnt/${QV}/etc/clock #has HWCLOCKTIME=localtime or utc
  case "$HWCLOCKTIME" in
   localtime) hwclock -s --localtime -f /dev/rtc0; CLKflg=$? ;;
   utc)       hwclock -s -u -f /dev/rtc0; CLKflg=$? ;;
  esac
 else #first bootup, assume hw clock is localtime...
  hwclock -s -l -f /dev/rtc0
 fi
fi
if [ $CLKflg -ne 0 ];then
 if [ -s /tempmnt/${QV}/var/local/shutdown_date_saved ];then
  date -s "$(cat /tempmnt/${QV}/var/local/shutdown_date_saved)" > /dev/null
 fi
fi
#rpi does not have a hardware clock, set it to something sane at 1st bootup...
YEAR=$(date +%Y) #ex: 1970
if [ $YEAR -lt 2020 ];then
 #set date same as init file...
 fDATE="$(stat -c %y /init | cut -f 1,2 -d ':')"
 DATE="$(date -s "$fDATE")"
else
 DATE="$(date)"
fi
export DATE #ex: Tue Mar  3 07:09:34 +08 2020

At first bootup, assumes hw clock is local time.
Subsequent bootups, reads /etc/localtime symlink in the @qv folder and copies it, as well as what it points to, into the initrd.
Then, it is hoped, the date will be set correctly.

But maybe the code has a problem, if you are getting a day ahead.


Re: QV version 240425 - problem Anydesk with Pam

Posted: Fri Apr 26, 2024 11:41 am
by BarryK
Caramel wrote: Fri Apr 26, 2024 9:02 am

Return of the problem with Pam and flatpak Anydesk (see viewtopic.php?t=10439 for the problem in EasyVoid)

Pam prevents the launch of the flatpak Anydesk with the error message :

The logged in user differs from the (non-root) user this process runs as

It does not like the "run-as-client" trick

For test, I moved many files installed by the pakages pam, pam-libs and rebooted. Then Anydesk started.

For the deactivation to take effect, a reboot is necessary. So it's difficult to know which files moved are enough to prevent pam

EDIT: the move of the 6 .so files libpam libpamc lipam_misc in /usr/lib is enough to block pam
EDIT2: the move of the 2 .so files libpam in /usr/lib is enough to block pam

EDIT3: Ultimately the move of the symlink libpam.so.0 is sufficient for blocking pam

OK, I'll go back to how it was before. This was the change:

https://github.com/bkauler/woof-quantum ... 752a797033

I will revert it.


Re: QV version 240425

Posted: Fri Apr 26, 2024 1:58 pm
by Caramel
BarryK wrote: Fri Apr 26, 2024 11:04 am
Caramel wrote: Fri Apr 26, 2024 7:27 am

Just installed.
After first creation of a snapshot, the information on desktop has changed, but the number is 3 instead 2 (btrfs subvolume list / confirm 2 subvolumes was created) and the date is a day in advance.

The date is only yymmdd
Regarding being a day in advance, I attempted to obtain the accurate date in the initrd. This code in 'init' script:

Code: Select all

###set date and time###
#see TZ set early in script.
#20240320 settimeofday() error, see: https://bkhome.org/news/202402/hwclock-fail-in-easyvoid-603.html
# getting this error in initrd. now have static hwclock with old musl
# ...it does not accept -l requires --localtime
CLKflg=1
if [ -e /sys/class/rtc/rtc0 ];then
 #20240424 get timezone...
 if [ -e /tempmnt/${QV}/etc/localtime ];then
  NEWTZ="$(readlink /tempmnt/${QV}/etc/localtime)" #ex: /usr/share/zoneinfo/Etc/GMT-8
  mkdir -p ${NEWTZ%/*}
  cp -a ${NEWTZ} ${NEWTZ%/*}/
  cp -a /tempmnt/${QV}/etc/localtime /etc/
  unset TZ #otherwise it will override /etc/localtime
  export TZ
 fi
 if [ -s /tempmnt/${QV}/etc/clock ];then
. /tempmnt/${QV}/etc/clock #has HWCLOCKTIME=localtime or utc
  case "$HWCLOCKTIME" in
   localtime) hwclock -s --localtime -f /dev/rtc0; CLKflg=$? ;;
   utc)       hwclock -s -u -f /dev/rtc0; CLKflg=$? ;;
  esac
 else #first bootup, assume hw clock is localtime...
  hwclock -s -l -f /dev/rtc0
 fi
fi
if [ $CLKflg -ne 0 ];then
 if [ -s /tempmnt/${QV}/var/local/shutdown_date_saved ];then
  date -s "$(cat /tempmnt/${QV}/var/local/shutdown_date_saved)" > /dev/null
 fi
fi
#rpi does not have a hardware clock, set it to something sane at 1st bootup...
YEAR=$(date +%Y) #ex: 1970
if [ $YEAR -lt 2020 ];then
 #set date same as init file...
 fDATE="$(stat -c %y /init | cut -f 1,2 -d ':')"
 DATE="$(date -s "$fDATE")"
else
 DATE="$(date)"
fi
export DATE #ex: Tue Mar  3 07:09:34 +08 2020

At first bootup, assumes hw clock is local time.
Subsequent bootups, reads /etc/localtime symlink in the @qv folder and copies it, as well as what it points to, into the initrd.
Then, it is hoped, the date will be set correctly.

But maybe the code has a problem, if you are getting a day ahead.

I'm having trouble understanding the code.

Previously the variable TZ is initialized by export TZ='XXX-23'
In the code shown here TZ seems not changed.

I do not really understand the lines:

unset TZ #otherwise it will override /etc/localtime
export TZ


Encryption on QV version 240425

Posted: Fri Apr 26, 2024 2:42 pm
by gcav

Is this working?

At first run, I get prompted for a password but afterwards I see a message that working folders cannot be encrypted and password will be root's passwd.

gc...


Re: QV version 240425

Posted: Fri Apr 26, 2024 5:25 pm
by williwaw
BarryK wrote: Fri Apr 26, 2024 11:04 am

At first bootup, assumes hw clock is local time.
Subsequent bootups, reads /etc/localtime symlink in the @qv folder and copies it, as well as what it points to, into the initrd.
Then, it is hoped, the date will be set correctly.

But maybe the code has a problem, if you are getting a day ahead.

when quicksetup > "hardwareclock set to UTC" box is ticked, I have the day ahead dating, but it is just a note in snapshot-record so not obvious. the time and date in the taskbar is OK

when changing desktop backgrounds the snapshot version message seems to scale different


Re: Encryption on QV version 240425

Posted: Sat Apr 27, 2024 12:30 am
by TerryH
gcav wrote: Fri Apr 26, 2024 2:42 pm

Is this working?

At first run, I get prompted for a password but afterwards I see a message that working folders cannot be encrypted and password will be root's passwd.

gc...

Entering a password at that prompt is intended to have 2 purposes, the encryption function doesn't work with btrfs. The other purpose sets the root password, so that function still works.


Re: QV version 240425

Posted: Sat Apr 27, 2024 8:56 am
by BarryK
Caramel wrote: Fri Apr 26, 2024 1:58 pm

I do not really understand the lines:

unset TZ #otherwise it will override /etc/localtime
export TZ

Earlier in the code, TZ was exported.
I thought that if TZ is unset, it would have to be exported again, as unset.


Re: QV version 240425 pre-alpha uploaded

Posted: Sat Apr 27, 2024 9:22 am
by BarryK

Sorry, I might be a bit slow to respond to QV bug reports for a few days.
I'm finally giving EasyOS Kirkstone some TLC. A complete recompile with updated packages.


Re: QV version 240425 pre-alpha uploaded

Posted: Sat Apr 27, 2024 5:30 pm
by don570

I reinstalled qv again in the same partition to check SAMBA

I was able to get a samba server to run but
there is definitely something wrong with Easy share app.

Here is my install method

-install fresh qv
-booted and set samba daemon with first set up
-ran easy share app and clicked 'Apply' button
-warning message that services aren't running
-chromebook doesn't list the server
-I went to /etc and ran

Code: Select all

rc.samba start

Checked in terminal that samba is running
-checked my chromebook that sever is now running properly.


Re: QV version 240425 pre-alpha uploaded

Posted: Sun Apr 28, 2024 4:04 am
by BarryK
don570 wrote: Sat Apr 27, 2024 5:30 pm

I reinstalled qv again in the same partition to check SAMBA

I was able to get a samba server to run but
there is definitely something wrong with Easy share app.

Here is my install method

-install fresh qv
-booted and set samba daemon with first set up
-ran easy share app and clicked 'Apply' button
-warning message that services aren't running
-chromebook doesn't list the server
-I went to /etc and ran

Code: Select all

rc.samba start

Checked in terminal that samba is running
-checked my chromebook that sever is now running properly.

Why didn't you start samba from within EasyShare?
That does more things than just run "/etc/init.d/rc.samba start"


Re: Encryption on QV version 240425

Posted: Sun Apr 28, 2024 4:56 pm
by gcav
TerryH wrote: Sat Apr 27, 2024 12:30 am
gcav wrote: Fri Apr 26, 2024 2:42 pm

Is this working?

At first run, I get prompted for a password but afterwards I see a message that working folders cannot be encrypted and password will be root's passwd.

gc...

Entering a password at that prompt is intended to have 2 purposes, the encryption function doesn't work with btrfs. The other purpose sets the root password, so that function still works.

Aww.. shucks...
I see that BTRFS does not have native encryption, only with LUKS and the sorts..

I will play with having F2FS on QV...

gc


Re: Encryption on QV version 240425

Posted: Mon Apr 29, 2024 2:34 am
by BarryK
gcav wrote: Sun Apr 28, 2024 4:56 pm
TerryH wrote: Sat Apr 27, 2024 12:30 am
gcav wrote: Fri Apr 26, 2024 2:42 pm

Is this working?

At first run, I get prompted for a password but afterwards I see a message that working folders cannot be encrypted and password will be root's passwd.

gc...

Entering a password at that prompt is intended to have 2 purposes, the encryption function doesn't work with btrfs. The other purpose sets the root password, so that function still works.

Aww.. shucks...
I see that BTRFS does not have native encryption, only with LUKS and the sorts..

I will play with having F2FS on QV...

gc

The btrfs developers were working on fscrypt, same that ext4 and f2fs have. But the kernel patches caused a crash.
Also, the developers have put it on the back-burner. Hopefully, they will get enthused enough sometime to keep working on it.
I gather, from reading their mail-list, that fscrypt is very complicated to implement in btrfs.

f2fs won't work on QV, as the whole thing is built around the snapshot feature of btrfs. f2fs is a copy-on-write f.s., but snapshots were never implemented.


Samba green icon

Posted: Mon Apr 29, 2024 10:33 pm
by don570

I did fresh install of qv to test samba . Here are my notes...

-a fresh install of QV
qv-240423-amd64.img
-bootup
-Firewall is automatically setup
-In the first setup app I set the samba deamon to always run at bottup
-clicked yes for keyboard changes
-there is message that the firewall is running
-I check tray and I see that ethernet wired connection is active
-I launch EasyShare app and there is message that firewall is starting
(this is third message that a firewall is starting. A lot of firewall messages???)
-I choose Samba option and then click 'Samba setup' button (see image)

Screenshot (1).png
Screenshot (1).png (25.36 KiB) Viewed 1589 times

-
I see green Samba icon.(see image)

Screenshot(3).png
Screenshot(3).png (71.54 KiB) Viewed 1589 times

I right click on it to read instructions.
Instructions say that if green then samba is running.
-I assume samba is running and click 'Apply' button
-I get error message that samba isn't running

-So I go to /etc/init.d folder and run

Code: Select all

./rc.samba start

I check with my chromebook that a samba server is available
__________________________________________________

Note that with other versions of puppy linux I have seen
a red samba icon used by EasyShare app.
___________________________________________


Re: QV version 240425 - problem Anydesk with Pam

Posted: Sun May 05, 2024 5:39 pm
by BarryK
Caramel wrote: Fri Apr 26, 2024 9:02 am

Return of the problem with Pam and flatpak Anydesk (see viewtopic.php?t=10439 for the problem in EasyVoid)

Pam prevents the launch of the flatpak Anydesk with the error message :

The logged in user differs from the (non-root) user this process runs as

It does not like the "run-as-client" trick

For test, I moved many files installed by the pakages pam, pam-libs and rebooted. Then Anydesk started.

For the deactivation to take effect, a reboot is necessary. So it's difficult to know which files moved are enough to prevent pam

EDIT: the move of the 6 .so files libpam libpamc lipam_misc in /usr/lib is enough to block pam
EDIT2: the move of the 2 .so files libpam in /usr/lib is enough to block pam

EDIT3: Ultimately the move of the symlink libpam.so.0 is sufficient for blocking pam

I have reverted the pam/shadow change in 240425, released 240506:

https://bkhome.org/news/202405/qv-versi ... eased.html

That's the only change.


Re: QV version 240425 pre-alpha uploaded

Posted: Thu May 16, 2024 7:45 pm
by Federico

At the end, is the official name "Quirky Void" or "Quantum Vis" ?

It follows my report (V 240506).

HARDWARE:

Video --> working
Audio --> working
Network --> working
Bluetooth --> NOT working
CPU frequency scaling --> working (Intel i5-1135G7)
Access to NTFS drives --> working
Keyboard lighting --> working
Hibernation --> NOT working
Screen shutdown when lid is closed --> NOT working
Battery monitoring --> working
3D acceleration --> working
- could not test the touchpad, 'cause it's physically broken on my laptop
- the CPU runs 4 °C cooler when idling (the kernel is more efficient: it now hits just 38 °C @ idle on my laptop)

SOFTWARE:

German locale --> not working (pay attention --> causes severe issues with the X server. Only select english locale)
KDE Dolphin --> working (just execute /usr/bin/dolphin.bin0 to get system wide root access)
KDE Okular --> working
KDE Kate --> working
KDE Konqueror --> working (works only as internet browser)
Ungoogled Chromium as AppImage --> working
XArchive --> working
GIMP --> working
AnyDesk --> working (use the flatpak from https://flathub.org/apps/com.anydesk.Anydesk ; rename or remove the symlink /usr/lib/libpam.so.0)


Re: QV version 240425 pre-alpha uploaded

Posted: Thu May 16, 2024 8:06 pm
by williwaw
Federico wrote: Thu May 16, 2024 7:45 pm

SOFTWARE:

German translation --> working (I think that "Befehl" is more suitable for translating "command")
KDE Dolphin --> working (there's an issue with version 24.02.2: there's no way to gain root privileges. I tried to install a pair of versions of the package kio-admin, to no avail)
KDE Okular --> working
KDE Kate --> working
KDE Konqueror --> NOT working (no files or folders are shown)
Ungoogled Chromium as AppImage --> working
XArchive --> working
GIMP --> working
AnyDesk --> NOT working (the window doesn't show up, the tray icon disappears after 5 seconds and no errors are reported)

Did you install the kde meta package?
viewtopic.php?p=116899#p116899
hoping to learn more about this, although maybe a kde topic is deserved


Re: QV version 240425 pre-alpha uploaded

Posted: Thu May 16, 2024 9:36 pm
by Federico
williwaw wrote: Thu May 16, 2024 8:06 pm
Federico wrote: Thu May 16, 2024 7:45 pm

SOFTWARE:

German translation --> working (I think that "Befehl" is more suitable for translating "command")
KDE Dolphin --> working (there's an issue with version 24.02.2: there's no way to gain root privileges. I tried to install a pair of versions of the package kio-admin, to no avail)
KDE Okular --> working
KDE Kate --> working
KDE Konqueror --> NOT working (no files or folders are shown)
Ungoogled Chromium as AppImage --> working
XArchive --> working
GIMP --> working
AnyDesk --> NOT working (the window doesn't show up, the tray icon disappears after 5 seconds and no errors are reported)

Did you install the kde meta package?
viewtopic.php?p=116899#p116899
hoping to learn more about this, although maybe a kde topic is deserved

Thank you for the tip but unfortunately I cannot try right now because I noticed that I have a much more severe issue: the X server does not start any more: either the screen stays totally black or the server says that there was a << Fatal server error: no screens found >>. It doesn't matter how I set the xorgwizard: I've tried the Vesa driver, the Modesetting driver, the auto detection again, uxa and uma acceleration and nothing works. When the screen is black, I can press the combination Ctrl+Alt+F2 to stop the X server, go back to the command prompt and repeat the xorgwizard procedure, but nothing seems to solve the issue.
If I format the USB stick and reinstall QV from scratch, it works again, but only for a couple of boots. So, it looks that there may be something wrong either with the Intel video driver itself or with the shut-down procedure of the system (which somehow concerns the X server). It would be useful if someone else with Intel Iris Xe would confirm this problematic.


Re: QV version 240425 pre-alpha uploaded

Posted: Fri May 17, 2024 10:13 am
by Caramel
Federico wrote: Thu May 16, 2024 7:45 pm

It follows my report (V 240506).

SOFTWARE:

AnyDesk --> NOT working (the window doesn't show up, the tray icon disappears after 5 seconds and no errors are reported)

I confirm.
Still the PAM problem. with the same solution: rename (or move) /usr/lib/libpam.so.0 and reboot.


Re: QV version 240425 pre-alpha uploaded

Posted: Fri May 17, 2024 11:16 am
by Federico
Caramel wrote: Fri May 17, 2024 10:13 am
Federico wrote: Thu May 16, 2024 7:45 pm

It follows my report (V 240506).

SOFTWARE:

AnyDesk --> NOT working (the window doesn't show up, the tray icon disappears after 5 seconds and no errors are reported)

I confirm.
Still the PAM problem. with the same solution: rename (or move) /usr/lib/libpam.so.0 and reboot.

Thank you Caramel. I'm going to format once again my testing USB stick, so that I can at least test this solution for AnyDesk.
But obviously I need to understand why my X server stops working after a couple of boots.
At least we should understand if I'm doing anything wrong, or if it's only me (my hardware) or if this is a general problem of this version.


Re: QV version 240425 pre-alpha uploaded

Posted: Fri May 17, 2024 3:27 pm
by Federico

@ Caramel

/usr/lib/libpam.so.0 is a symbolic link to libpam.so.0.85.1. I renamed it and rebooted. This time AnyDesk still does not work, but I do get some errors:

Code: Select all

# ./anydesk

(process:5806): GLib-GObject-CRITICAL **: 17:21:47.008: invalid (NULL) pointer instance

(process:5806): GLib-GObject-CRITICAL **: 17:21:47.008: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:5806): GLib-GObject-CRITICAL **: 17:21:47.008: invalid (NULL) pointer instance

(process:5806): GLib-GObject-CRITICAL **: 17:21:47.008: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:5818): GLib-GObject-CRITICAL **: 17:21:47.060: invalid (NULL) pointer instance

(process:5818): GLib-GObject-CRITICAL **: 17:21:47.060: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:5818): GLib-GObject-CRITICAL **: 17:21:47.060: invalid (NULL) pointer instance

(process:5818): GLib-GObject-CRITICAL **: 17:21:47.060: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
# 
(process:5835): GLib-GObject-CRITICAL **: 17:21:50.346: invalid (NULL) pointer instance

(process:5835): GLib-GObject-CRITICAL **: 17:21:50.346: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:5835): GLib-GObject-CRITICAL **: 17:21:50.346: invalid (NULL) pointer instance

(process:5835): GLib-GObject-CRITICAL **: 17:21:50.346: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

# ./anydesk

(process:5988): GLib-GObject-CRITICAL **: 17:26:25.184: invalid (NULL) pointer instance

(process:5988): GLib-GObject-CRITICAL **: 17:26:25.185: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:5988): GLib-GObject-CRITICAL **: 17:26:25.185: invalid (NULL) pointer instance

(process:5988): GLib-GObject-CRITICAL **: 17:26:25.185: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:6000): GLib-GObject-CRITICAL **: 17:26:25.236: invalid (NULL) pointer instance

(process:6000): GLib-GObject-CRITICAL **: 17:26:25.236: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:6000): GLib-GObject-CRITICAL **: 17:26:25.236: invalid (NULL) pointer instance

(process:6000): GLib-GObject-CRITICAL **: 17:26:25.236: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

I'm also installing the KDE meta package:

Code: Select all

262 packages will be downloaded:

262 packages will be installed:
  libmd4c-0.4.8_1 libb2-0.98.1_1 qt6-core-6.6.0_1 qt6-dbus-6.6.0_1 
  qt6-network-6.6.0_1 tslib-1.22_1 xcb-util-cursor-0.1.4_1 
  qt6-gui-6.6.0_1 kf6-kdbusaddons-6.1.0_1 qt6-widgets-6.6.0_1 
  qt6-sql-6.6.0_1 qt6-declarative-6.6.0_2 kf6-ki18n-6.1.0_1 
  qt6-xml-6.6.0_1 kf6-kconfig-6.1.0_1 kf6-kcoreaddons-6.1.0_1 
  kf6-kservice-6.1.0_1 kf6-kcrash-6.1.0_1 polkit-qt6-0.200.0_1 
  qt6-wayland-6.6.0_1 kf6-kwindowsystem-6.1.0_1 kf6-kauth-6.1.0_1 
  xmlcatmgr-2.2_4 docbook-xml-4.5_5 docbook-xsl-1.79.2_2 
  kf6-karchive-6.1.0_1 kf6-kdoctools-6.1.0_1 libupower-glib3-1.90.4_1 
  libimobiledevice-1.3.0_6 upower-1.90.4_1 media-player-info-24_2 
  kf6-solid-6.1.0_1 kf6-kwidgetsaddons-6.1.0_1 
  kf6-knotifications-6.1.0_1 kf6-kguiaddons-geo-uri-handler-6.1.0_1 
  kf6-kguiaddons-6.1.0_1 kf6-kcolorscheme-6.1.0_1 botan-2.19.3_3 
  libqt6shadertools-6.6.0_1 qt6-qt5compat-6.6.0_1 qca-qt6-2.3.8_1 
  kf6-kwallet-6.1.0_1 kf6-kjobwidgets-6.1.0_1 kf6-kcodecs-6.1.0_1 
  kf6-kcompletion-6.1.0_1 kf6-kconfigwidgets-6.1.0_1 
  kf6-kiconthemes-6.1.0_1 kf6-kitemviews-6.1.0_1 kf6-kbookmarks-6.1.0_1 
  kf6-kio-6.1.0_2 kf6-bluez-qt-6.1.0_1 kf6-kglobalaccel-6.1.0_1 
  qt6-printsupport-6.6.0_1 kf6-kxmlgui-6.1.0_1 kf6-kcmutils-6.1.0_1 
  bluedevil-6.0.4_1 breeze-gtk-6.0.4.1_1 kf6-kparts-6.1.0_1 
  qt6-svg-6.6.0_1 kf6-kpty-6.1.0_1 kf6-kdesu-6.1.0_1 
  kde-cli-tools-6.0.4_2 kf6-kdecoration-6.0.4_1 kde-gtk-config-6.0.4_1 
  plasma5support-6.0.4_1 kf6-kunitconversion-6.1.0_1 
  kf6-kpackage-6.1.0_1 kf6-kitemmodels-6.1.0_1 kf6-krunner-6.1.0_1 
  kf6-sonnet-6.1.0_1 kf6-kirigami-6.1.0_1 qt6-plugin-sqlite-6.6.0_1 
  plasma-activities-6.0.4_2 kf6-ksvg-6.1.0_1 libplasma-6.0.4_1 
  kf6-kholidays-6.1.0_1 kf6-kdeclarative-6.1.0_1 
  kdeplasma-addons-6.0.4_1 kgamma-6.0.4_1 kinfocenter-6.0.4_1 
  libkf6screen-6.0.4_1 qt6-sensors-6.6.0_1 layer-shell-qt-6.0.4_1 
  kscreen-6.0.4_1 ksshaskpass-6.0.4_1 qt5-core-5.15.11+20231124_3 
  qt5-dbus-5.15.11+20231124_3 qt5-network-5.15.11+20231124_3 
  qt5-gui-5.15.11+20231124_3 qt5-widgets-5.15.11+20231124_3 
  qt5-sql-5.15.11+20231124_3 qt5-test-5.15.11+20231124_3 
  qt5-declarative-5.15.11+20231124_3 
  qt5-graphicaleffects-5.15.11+20231124_3 
  qt5-quickcontrols2-5.15.11+20231124_3 kirigami2-5.115.0_1 
  kf6-qqc2-desktop-style-6.1.0_1 kf6-kquickcharts-6.1.0_1 
  libksysguard-6.0.4_1 kf6-networkmanager-qt-6.1.0_1 
  ksystemstats-6.0.4_1 kf6-attica-6.1.0_1 kf6-syndication-6.1.0_1 
  kf6-knewstuff-6.1.0_1 plasma-systemmonitor-6.0.4_2 socat-1.7.4.4_2 
  kwallet-pam-6.0.4_1 qt5-x11extras-5.15.11+20231124_3 
  kwindowsystem-5.115.0_1 qt5-wayland-5.15.11+20231124_3 
  kwayland-5.115.0_1 kwayland-integration-6.0.4_1 kwrited-6.0.4_1 
  kf6-frameworkintegration-6.1.0_1 oxygen-qt6-6.0.4_1 
  kcoreaddons-5.115.0_3 polkit-qt5-0.200.0_1 kauth-5.115.0_1 
  kcodecs-5.115.0_1 qt5-xml-5.15.11+20231124_3 kconfig-5.115.0_1 
  kguiaddons-5.115.0_2 ki18n-5.115.1_1 kwidgetsaddons-5.115.0_1 
  kconfigwidgets-5.115.0_1 karchive-5.115.0_1 qt5-svg-5.15.11+20231124_3 
  kiconthemes-5.115.0_1 attica-5.115.0_1 kcompletion-5.115.0_1 
  kglobalaccel-5.115.0_3 kdbusaddons-5.115.0_1 kservice-5.115.0_1 
  kcrash-5.115.0_1 libksolid-5.115.0_1 kdoctools-5.115.0_3 
  libdbusmenu-qt5-0.9.3+16.04.20160218_3 qt5-speech-5.15.11_1 
  knotifications-5.115.0_1 qca-qt5-2.3.8_1 kwallet-5.115.0_2 
  kitemviews-5.115.0_1 sonnet-5.115.0_1 ktextwidgets-5.115.0_1 
  kjobwidgets-5.115.0_1 qt5-printsupport-5.15.11+20231124_3 
  kxmlgui-5.115.0_1 kbookmarks-5.115.0_1 kio-5.115.0_2 
  kpackage-5.115.0_1 kdeclarative-5.115.0_1 
  qt5-quickcontrols-5.15.11+20231124_3 syndication-5.115.0_1 
  knewstuff-5.115.0_1 frameworkintegration-5.115.0_1 oxygen-qt5-6.0.4_1 
  oxygen-6.0.4_1 kmenuedit-6.0.4_1 polkit-kde-agent-6.0.4_1 
  kf6-kidletime-6.1.0_1 kworkspace-6.0.4_2 i2c-tools-4.3_5 
  ddcutil-2.1.4_1 powerdevil-6.0.4_1 systemsettings-6.0.4_1 
  accountsservice-0.6.55_3 xdg-user-dirs-0.18_1 noto-fonts-emoji-2.042_1 
  qt6-concurrent-6.6.0_1 kf6-knotifyconfig-6.1.0_1 
  plasma-activities-stats-6.0.4_1 poppler-qt6-23.12.0_1 taglib-1.13.1_1 
  ebook-tools-0.2.2_3 libqmobipocket6-24.02.2_1 
  kf6-kfilemetadata-6.1.0_2 kf6-baloo-6.1.0_1 signond-8.61_2 
  signon-plugin-oauth2-0.25_1 signon-kwallet-extension-24.02.2_1 
  minizip-1.3_1 qt6-pdf-6.6.0_3 qt6-plugin-tls-openssl-6.6.0_1 
  qt6-plugin-tls-qcertonly-6.6.0_1 qt6-serialport-6.6.0_1 
  qt6-position-6.6.0_1 qt6-webchannel-6.6.0_1 re2-2023.03.01_1 
  snappy-1.1.10_1 qt6-webengine-6.6.0_3 libaccounts-glib-1.26_1 
  libaccounts-qt6-1.17_1 signon-ui-0.17_1 
  kf6-kaccounts-integration-24.02.2_1 kactivitymanagerd-6.0.4_1 
  breeze-icons-6.1.0_1 breeze-qt6-6.0.4_1 breeze-qt5-6.0.4_2 
  breeze-6.0.4_1 kglobalacceld-6.0.4_2 qt6-opengl-widgets-6.6.0_1 
  qt6-ui-tools-6.6.0_2 kf6-kwayland-6.0.4_1 kscreenlocker-6.0.4_1 
  libdisplay-info-0.1.1_1 libqaccessibilityclient-0.6.0_1 kwin-6.0.4_2 
  milou-6.0.4_1 noto-fonts-ttf-24.5.1_1 font-hack-ttf-3.003_2 
  qqc2-desktop-style-5.115.0_1 kf6-kstatusnotifieritem-6.1.0_1 
  plasma-integration-6.0.4_1 xorg-server-xwayland-23.2.4_2 
  gumbo-parser-0.10.1_3 clang17-headers-17.0.6_2 libclang-cpp17-17.0.6_2 
  libclang17-17.0.6_2 qt6-designer-6.6.0_2 qt6-help-6.6.0_2 
  qt6-tools-6.6.0_2 kirigami-addons-1.1.0_1 kpipewire-6.0.4_1 
  libkexiv2-24.02.2_1 libqalculate-5.1.1_1 libdmtx-0.7.5_1 
  libassimp-5.2.5_1 qt6-quicktimeline-6.6.0_1 qt6-quick3d-6.6.0_1 
  qt6-multimedia-6.6.0_2 kf6-prison-6.0.0_1 qt6-speech-6.6.0_1 
  kf6-ktextwidgets-6.1.0_1 kf6-kuserfeedback-6.1.0_1 
  phonon-locale-4.12.0_2 phonon-4.12.0_2 kf6-syntax-highlighting-6.1.0_1 
  editorconfig-0.12.6_1 kf6-ktexteditor-6.1.0_1 plasma-workspace-6.0.4_2 
  libibus-1.5.28_4 ibus-gtk+3-1.5.28_4 python3-xdg-0.28_4 
  ibus-1.5.28_4 plasma-desktop-6.0.4_1 kf6-modemmanager-qt-6.1.0_1 
  libnm-1.46.0_2 vpnc-scripts-20220510_1 openconnect-9.12_1 
  qt6-websockets-6.6.0_1 qcoro-qt6-0.10.0_1 plasma-nm-6.0.4_1 
  sound-theme-freedesktop-0.8_3 plasma-pa-6.0.4_1 
  plasma-workspace-wallpapers-6.0.4_1 sddm-0.21.0_1 sddm-kcm-6.0.4_1 
  xdg-desktop-portal-kde-6.0.4_1 bolt-0.9.5_1 plasma-thunderbolt-6.0.4_1 
  kf6-kded-6.1.0_1 kde5-6.0.4_2 

Size to download:              512MB
Size required on disk:        1381MB
Space available on disk:        56GB

Do you want to continue? [Y/n] Y


Re: QV version 240425 pre-alpha uploaded

Posted: Fri May 17, 2024 4:00 pm
by Caramel
Federico wrote: Fri May 17, 2024 3:27 pm

@ Caramel

/usr/lib/libpam.so.0 is a symbolic link to libpam.so.0.85.1. I renamed it and rebooted. This time AnyDesk still does not work, but I do get some errors:

Code: Select all

# ./anydesk

(process:5806): GLib-GObject-CRITICAL **: 17:21:47.008: invalid (NULL) pointer instance

(process:5806): GLib-GObject-CRITICAL **: 17:21:47.008: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:5806): GLib-GObject-CRITICAL **: 17:21:47.008: invalid (NULL) pointer instance

(process:5806): GLib-GObject-CRITICAL **: 17:21:47.008: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:5818): GLib-GObject-CRITICAL **: 17:21:47.060: invalid (NULL) pointer instance

(process:5818): GLib-GObject-CRITICAL **: 17:21:47.060: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:5818): GLib-GObject-CRITICAL **: 17:21:47.060: invalid (NULL) pointer instance

(process:5818): GLib-GObject-CRITICAL **: 17:21:47.060: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
# 
(process:5835): GLib-GObject-CRITICAL **: 17:21:50.346: invalid (NULL) pointer instance

(process:5835): GLib-GObject-CRITICAL **: 17:21:50.346: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:5835): GLib-GObject-CRITICAL **: 17:21:50.346: invalid (NULL) pointer instance

(process:5835): GLib-GObject-CRITICAL **: 17:21:50.346: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

# ./anydesk

(process:5988): GLib-GObject-CRITICAL **: 17:26:25.184: invalid (NULL) pointer instance

(process:5988): GLib-GObject-CRITICAL **: 17:26:25.185: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:5988): GLib-GObject-CRITICAL **: 17:26:25.185: invalid (NULL) pointer instance

(process:5988): GLib-GObject-CRITICAL **: 17:26:25.185: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:6000): GLib-GObject-CRITICAL **: 17:26:25.236: invalid (NULL) pointer instance

(process:6000): GLib-GObject-CRITICAL **: 17:26:25.236: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

(process:6000): GLib-GObject-CRITICAL **: 17:26:25.236: invalid (NULL) pointer instance

(process:6000): GLib-GObject-CRITICAL **: 17:26:25.236: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

I tested with the flatpak