[EN] LXQt, PCManFM-QT connect to server fails silently

[dibl]

Sometime in recent days the "GO ---> Connect to Server" function in PCManFM-QT has stopped working, on my one and only LXQt laptop.  It fails silently.  I don't see a log file in /var/log that would reveal what is happening.  Does anyone else see this problem?

[melmarker]

Should i know this functionality?

Code: [Select]

(process:23729): GLib-GIO-CRITICAL **: 00:34:26.010: g_app_info_launch_uris: assertion 'G_IS_APP_INFO (appinfo)' failed
[1]    23729 segmentation fault  pcmanfm-qt
Might be that one, but unlikely - which version do you use?

[dibl]

Ahhhhhh ---  Alf, you are the man!  :-)

Any idea about the cause of the seg fault?

Thanks!

QT is 5.10.1

[melmarker]

Right now i can't say nothing without knowing the version you are using - there are reasons why libfm-qt and pcmanfm-qt still are in experimental. We have rewritten big parts of it and had to release it in case that Debian is really fast and release Qt 5.11  - the 0.12.x sources will just not build with Qt 5.11 - so i think i should try a fresh patience image.

One can expect some faults in 0.13.0, of course - there should be none, but ...

[dibl]

PCManFM-QT is 0.13.0

[dibl]

This is not a disaster for me.  If I can help troubleshoot, I will be happy to do so.

Code: [Select]

don@n5110:~$ inxi -Fz
System:
  Host: n5110 Kernel: 4.17.0-towo.1-siduction-amd64 x86_64 bits: 64
  Desktop: LXQT 0.13.0
  Distro: siduction 17.1.0 Patience - lxqt - (201703051830)
Machine:
  Type: Portable System: Dell product: Inspiron N5110 v: N/A serial: <filter>
  Mobo: Dell model: 034W60 v: A11 serial: <filter> BIOS: Dell v: A11
  date: 08/03/2012
Battery:
  ID-1: BAT0 charge: 68.4 Wh condition: 85.0/81.3 Wh (104%)
CPU:
  Topology: Dual Core model: Intel Core i3-2330M bits: 64 type: MT MCP
  L2 cache: 3072 KiB
  Speed: 798 MHz min/max: 800/2200 MHz Core speeds (MHz): 1: 798 2: 798
  3: 798 4: 798
Graphics:
  Card-1: Intel 2nd Generation Core Processor Family Integrated Graphics
  driver: i915 v: kernel
  Display: x11 server: X.Org 1.20.0 driver: modesetting unloaded: fbdev,vesa
  resolution: 1366x768~60Hz
  OpenGL: renderer: Mesa DRI Intel Sandybridge Mobile v: 3.3 Mesa 18.0.5
Audio:
  Card-1: Intel 6 Series/C200 Series Family High Definition Audio
  driver: snd_hda_intel
  Sound Server: ALSA v: k4.17.0-towo.1-siduction-amd64
Network:
  Card-1: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet
  driver: r8169
  IF: enp5s0 state: down mac: <filter>
  Card-2: Intel Centrino Wireless-N 1030 [Rainbow Peak] driver: iwlwifi
  IF: wlp9s0 state: up mac: <filter>
Drives:
  HDD Total Size: 74.53 GiB used: 10.69 GiB (14.3%)
  ID-1: /dev/sda vendor: Intel model: SSDSA2CW080G3 size: 74.53 GiB
Partition:
  ID-1: / size: 15.62 GiB used: 9.87 GiB (63.2%) fs: ext4 dev: /dev/sda1
  ID-2: swap-1 size: 2.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2
Sensors:
  System Temperatures: cpu: 55.0 C mobo: N/A
  Fan Speeds (RPM): cpu: 0
Info:
  Processes: 188 Uptime: 1h 06m Memory: 3.76 GiB used: 1.59 GiB (42.2%)
  Shell: bash inxi: 3.0.11

[melmarker]

Cool - first regression we know right now. you might downgrade to sid. (libfm-qt, pcmanfm-qt, lxqt-qtplugin and lximage-qt and pin the packages)

Reason:
We have rewritten big parts of it and had to release it because of the release Qt 5.11  - the 0.12.x sources will just not build with Qt 5.11. Used the packages in the development process, but no one noticed that regression. One can expect some faults in 0.13.0, of course - there should be none, but ... If you look into the latest changes - it will look like a chain saw massacre - it is a ongoing battle - next big changes are just merged. Ok, the next big undertaking should™ not introduce regressions, but who knows.
(https://github.com/lxqt/lxqt/issues/1497) - after that i will merge and test some things that are new in libfm-qt and pcmanfm-qt. Right now we are bleeding edge regarding pcmanfm-qt in siduction.

EDIT: And yes, any help is appreciated. Should not be a big deal, it was expected that some things will break, we thought that we fixed the most of them, shit happend. It's not a everyday job to replace the old libfm c code with libfm-qt c++ one However, will look into it soon, after i've merged the latest changes.

[dibl]

OK thank you very much!

This issue is not important to my daily work -- I have an easy workaround (named e-mail to myself).

So I will simply leave my system in its current configuration and wish the LXQt dev team "bon fortune".

;-)

[melmarker]

@dibl - very good catch - https://github.com/lxqt/pcmanfm-qt/issues/693

Reproducible in Arch with Qt 5.11 too - latest git.

[dibl]

Thanks Alf.  Best wishes to you and the LXQt development team -- it's a very good desktop for my old, weak hardware.

[melmarker]

Ack, for my weak 8core too