Puppy Linux Discussion Forum

Issues in system code surface in accessing resources. Has someone or something been rewriting system commands?

# mkdir -p /mnt/AnotherPC/Media;mount -o password=woofwoof //192.168.1.10/puppyshare /mnt/AnotherPC/Media
grep: warning: stray \ before -

Odd error

Anyone else run into issues installing SAMBA on these recent PUPs being created without SAMBA? Are you also missing its utilities and @01Micko's SSM? Namely findsmb, smbclient, etc.

The headaches and extra work by any user makes me wonder the value of leaving it out. Its no savings if after you discover and then have to figure how to get tit into the system, in order to provide an access path for debugging info transfer.

This would affect users who come to forum with MACS/Windows PCs on their network OR have newbie knowledge of Linux tool installations. This comes at a time when WoofCE PUPs are maturing in its Package Management.

FYI for this developer's consideration.If he finds value, I'm sure it will resurface in his PUPs of the future.

Clarity wrote: Wed Oct 19, 2022 5:56 am

Issues in system code surface in accessing resources. Has someone or something been rewriting system commands?

Code: Select all

# mkdir -p /mnt/AnotherPC/Media;mount -o password=woofwoof //192.168.1.10/puppyshare /mnt/AnotherPC/Media
grep: warning: stray \ before -

Odd error

This is a bi-product of the new version of grep which needs all such stray \ being purged from puppy code - you've just found another.... it is only a warning and can be ignored until fixed

Thanks @PeeBee!

For everyone, the mount command DOES perform as expected.

peebee wrote: Tue Oct 18, 2022 1:14 pm

@Marv & @one

The problem is ncurses - /usr/share/terminfo is very different in +10 from +9

The attached sfs contains the +9 terminfo

Now need to find out why this has happened.

Hi @peebee,

I downloaded your patch, renamed it to ydrv_...... and booted voidpup32 +10. Save dialog is now fine ...
Thanks

peace

The save dialogue in v10b works perfectly and as expected VoidPUP64 finds all of the saves in the Sessions folder on the system drive Thanks to the current INIT processing employed by WoofCE pups; with no edit of boot parms needed. Booting the ISO file via SG2D makes getting to desktop a breeze. These PUPs do EVERYTHING expected including remaster. Thus booting, finding its session file(s) when present, saving properly on pristine and normal shutdowns, creating remaster(s) when requested...this is a wining combination. All is well with this VoidPUP64.

NOw, if only we could have SAMBA back.(smile )

Thanks for all you've done. My testing of this version completes booting the ISO file via SG2D and QEMU without issues, after circumventing the annoying popping noise captured in the WAV file from earlier post to this thread..

BTW: I did mention that @dimkr v51 for XORG has the same annoyance built into his WoofCE PUPs. His, too, starts the annoyance after the last console message just as this PUP does. But, unlike this PUP, his Dpup does NOT have retrovol to stop/fix the annoyance. As such, I have not found a circumvention as I did for this PUP..

P.S. If it is NOT clear from my posting of the annoying popping noise that accompanies these recent Pups on this PC, Multimedia programs audio work just fine as it overrides the Popping. But, the popping immediately returns after a multimedia completes. And microphone works too and is active as seen in both Retrovol here, as well as in DPup64..when desktop doesn't start.

Status Testing Complete

@Marv @one

With (lots of) help from @dimkr (many thanks) the TERM problem has been fixed.

+10c builds (https://smokey01.com/peebee/downloads/test/) include the fix.

Booted v10c ISO file in QEMU (29 seconds) as well as SG2D bare-metal without issues to desktop.

On bare-metal test PC, I selected this PUP to boot from its 1st entry of its Menu, knowing it will find its SAVESPEC and use it to find the prior session saved (v10b). The popping thru the speakers starts in console until the actual desktop starts; in which the popping stops due to the prior circumvention done in v10b.

All operations are normal with no regression or problems noticed excepting those reported earlier.

2 components added to the running system: @OscarTalks VLC addition and @ETP's GetChromeBrowser. Each of these additions install and work just fine yielding expected behavior.

# dmesg | grep error
[ 1.028344] ACPI Error: Aborting method \_SB.PCI0._OSC due to previous error (AE_ALREADY_EXISTS) (20210730/psparse-529)
# dmesg | grep fail
[ 1.028339] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20210730/dswload2-477)
[ 2.903383] sd 4:0:0:0: [sda] Asking for cache data failed
[ 367.855077] acpi_cpufreq: module verification failed: signature and/or required key missing - tainting kernel
# dmesg | grep snd
[ 368.519996] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC260: line_outs=1 (0x15/0x0/0x0/0x0/0x0) type:line
[ 368.520006] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=1 (0x11/0x0/0x0/0x0/0x0)
[ 368.520010] snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x10/0x0/0x0/0x0/0x0)
[ 368.520013] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 368.520014] snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 368.520016] snd_hda_codec_realtek hdaudioC0D0: Mic=0x14
[ 368.520019] snd_hda_codec_realtek hdaudioC0D0: Line=0x13
[ 368.520021] snd_hda_codec_realtek hdaudioC0D0: Aux=0xf
#

QEMU v7.1 (THANKS!!!) installed via repo; last of the messages are:

qemu-7.1.0_1: configuring ...
Updating GTK+ icon cache for /usr/share/icons/hicolor...
Updating MIME database...
Error in file "usr/share/applications/pmediainfo.desktop": "application_vnd.ms-asf" is an invalid MIME type ("application_vnd.ms-asf" does not contain a subtype)
Warning in file "usr/share/applications/xarchive.desktop": usage of MIME type "multipart/x-zip" is discouraged ("multipart" is a media type that probably does not make sense in this context)
qemu-7.1.0_1: installed successfully.

26 downloaded, 26 installed, 0 updated, 26 configured, 0 removed.
[vpm]  [xbps-install -S qemu] return code: 0 
#

And as reported, SAMBA has shortcomings which did not exist before someone in Woof took issue. Today, its utilities, still, are not present whereas for years of PUPs all features for this important facility by @01micko was present. Many things in our homes & phones take advantage of this in prior PUPs where NO INSTALLATION was necessary/required. The PUPs back then, did everything our MACs and Windows PCs do. I hope it returns removing the burden placed upon users to react to this missing component. (I wont mention this again as I think members have noticed both the missing and the incompleteness)

Examples of the negative impact

[vpm]  [xbps-install -S samba] return code: 0 
# findsmb
bash: findsmb: command not found
# smbclient
bash: smbclient: command not found
# 

... and more.

OK, booting VoidPup64 to the "popping" is specific to only 1 PC used for testing.

Booted SG2D selecting the VoidPUP64 ISO file, pristine, on a different PC; and that problem does NOT exist.

Clarity wrote: Wed Oct 19, 2022 6:04 am

Anyone else run into issues installing SAMBA on these recent PUPs being created without SAMBA? Are you also missing its utilities and @01Micko's SSM? Namely findsmb, smbclient, etc.

No.

# vpm i samba
[vpm]  Installing packages: samba (xbps-install -S samba) ... 
[*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ...
x86_64-repodata: 1790KB [avg rate: 1330KB/s]

Name             Action    Version           New version            Download size
libtdb           install   -                 1.4.5_1                44KB 
lmdb             install   -                 0.9.29_1               81KB 
ldb              install   -                 2.3.2_1                173KB 
samba-libs       install   -                 4.14.12_1              5511KB 
python3          install   -                 3.10.8_1               8143KB 
libpytalloc-util install   -                 2.3.3_1                5477B 
libpyldb-util    install   -                 2.3.2_1                6824B 
samba            install   -                 4.14.12_1              10MB 

Size to download:               24MB
Size required on disk:          88MB
Space available on disk:      3962MB

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

[*] Downloading packages
libtdb-1.4.5_1.x86_64.xbps.sig: 512B [avg rate: 23MB/s]
libtdb-1.4.5_1.x86_64.xbps: 44KB [avg rate: 40KB/s]
libtdb-1.4.5_1: verifying RSA signature...
lmdb-0.9.29_1.x86_64.xbps.sig: 512B [avg rate: 44MB/s]
lmdb-0.9.29_1.x86_64.xbps: 81KB [avg rate: 5364KB/s]
lmdb-0.9.29_1: verifying RSA signature...
ldb-2.3.2_1.x86_64.xbps.sig: 512B [avg rate: 21MB/s]
ldb-2.3.2_1.x86_64.xbps: 173KB [avg rate: 29MB/s]
ldb-2.3.2_1: verifying RSA signature...
samba-libs-4.14.12_1.x86_64.xbps.sig: 512B [avg rate: 44MB/s]
samba-libs-4.14.12_1.x86_64.xbps: 5511KB [avg rate: 4477KB/s]
samba-libs-4.14.12_1: verifying RSA signature...
python3-3.10.8_1.x86_64.xbps.sig: 512B [avg rate: 29MB/s]
python3-3.10.8_1.x86_64.xbps: 8143KB [avg rate: 3384KB/s]
python3-3.10.8_1: verifying RSA signature...
libpytalloc-util-2.3.3_1.x86_64.xbps.sig: 512B [avg rate: 31MB/s]
libpytalloc-util-2.3.3_1.x86_64.xbps: 5477B [avg rate: 22MB/s]
libpytalloc-util-2.3.3_1: verifying RSA signature...
libpyldb-util-2.3.2_1.x86_64.xbps.sig: 512B [avg rate: 49MB/s]
libpyldb-util-2.3.2_1.x86_64.xbps: 6824B [avg rate: 13MB/s]
libpyldb-util-2.3.2_1: verifying RSA signature...
samba-4.14.12_1.x86_64.xbps.sig: 512B [avg rate: 21MB/s]
samba-4.14.12_1.x86_64.xbps: 10MB [avg rate: 3652KB/s]
samba-4.14.12_1: verifying RSA signature...

[*] Collecting package files
libtdb-1.4.5_1: collecting files...
lmdb-0.9.29_1: collecting files...
ldb-2.3.2_1: collecting files...
samba-libs-4.14.12_1: collecting files...
python3-3.10.8_1: collecting files...
libpytalloc-util-2.3.3_1: collecting files...
libpyldb-util-2.3.2_1: collecting files...
samba-4.14.12_1: collecting files...

[*] Unpacking packages
libtdb-1.4.5_1: unpacking ...
lmdb-0.9.29_1: unpacking ...
ldb-2.3.2_1: unpacking ...
samba-libs-4.14.12_1: unpacking ...
python3-3.10.8_1: unpacking ...
python3-3.10.8_1: registered 'python' alternatives group
Creating 'python' alternatives group symlink: idle -> /usr/bin/idle3.10
Creating 'python' alternatives group symlink: 2to3 -> /usr/bin/2to3-3.10
Creating 'python' alternatives group symlink: pydoc -> /usr/bin/pydoc3.10
Creating 'python' alternatives group symlink: python -> /usr/bin/python3.10
Creating 'python' alternatives group symlink: python.1 -> /usr/share/man/man1/python3.10.1
libpytalloc-util-2.3.3_1: unpacking ...
libpyldb-util-2.3.2_1: unpacking ...
samba-4.14.12_1: unpacking ...
File `./etc/samba/smb.conf' exists, installing configuration file to `./etc/samba/smb.conf.new-4.14.12_1'.

[*] Configuring unpacked packages
libtdb-1.4.5_1: configuring ...
libtdb-1.4.5_1: installed successfully.
lmdb-0.9.29_1: configuring ...
lmdb-0.9.29_1: installed successfully.
ldb-2.3.2_1: configuring ...
ldb-2.3.2_1: installed successfully.
samba-libs-4.14.12_1: configuring ...
samba-libs-4.14.12_1: installed successfully.
python3-3.10.8_1: configuring ...
Byte-compiling python code in usr/lib/python3.10...
Byte-compiling python3.10 code for module README.txt...
python3-3.10.8_1: installed successfully.
libpytalloc-util-2.3.3_1: configuring ...
libpytalloc-util-2.3.3_1: installed successfully.
libpyldb-util-2.3.2_1: configuring ...
libpyldb-util-2.3.2_1: installed successfully.
samba-4.14.12_1: configuring ...
samba-4.14.12_1: installed successfully.

8 downloaded, 8 installed, 0 updated, 8 configured, 0 removed.
[vpm]  [xbps-install -S samba] return code: 0 
# 


/etc/samba/smb.conf
/etc/samba/smb.conf.new-4.14.12_1
/etc/samba/smb.conf-sample
/etc/sv/smbd
/lib64/modules/5.15.41/kernel/drivers/i2c/i2c-smbus.ko
/lib64/modules/5.15.41/kernel/drivers/input/rmi4/rmi_smbus.ko
/lib64/modules/5.15.41/kernel/drivers/platform/x86/dell/dell-smbios.ko
/lib64/modules/5.15.41/kernel/fs/smbfs_common
/lib/modules/5.15.41/kernel/drivers/i2c/i2c-smbus.ko
/lib/modules/5.15.41/kernel/drivers/input/rmi4/rmi_smbus.ko
/lib/modules/5.15.41/kernel/drivers/platform/x86/dell/dell-smbios.ko
/lib/modules/5.15.41/kernel/fs/smbfs_common
/usr/bin/mount.smb3
/usr/bin/smb2-quota
/usr/bin/smbcontrol
/usr/bin/smbd
/usr/bin/smbinfo
/usr/bin/smbpasswd
/usr/bin/smbstatus
/usr/bin/smbtorture
/usr/lib/cups/backend/smbw
/usr/lib/libsmbclient.so.0
/usr/lib/libsmbclient.so.0.7.0
/usr/lib/libsmbconf.so.0
/usr/lib/libsmbd-base-samba4.so
/usr/lib/libsmbldaphelper-samba4.so
/usr/lib/libsmbldap.so.2
/usr/lib/libsmbldap.so.2.1.0
/usr/lib/libsmbpasswdparser-samba4.so
/usr/lib/libsmb-transport-samba4.so
/usr/lib/samba/pdb/smbpasswd.so
/usr/sbin/smbd
/usr/share/man/man1/smbcontrol.1
/usr/share/man/man1/smbstatus.1
/usr/share/man/man1/smbtorture.1
/usr/share/man/man5/smb.conf.5
/usr/share/man/man5/smbpasswd.5
/usr/share/man/man7/libsmbclient.7
/usr/share/man/man8/smbd.8
/usr/share/man/man8/smbpasswd.8
/var/log/samba/cores/smbd

Thanks @peebee for your follow-up. I APPRECIATE ALL of the good things you have done and are doing!!!

YES, I did do that on the recent v10c. But, even though it allows SSM to work, the utilities are NOT present in the system. Did I do something wrong?

For example, if ANYONE clicks Menu>Network>SimpleSAMBA... they get a RED message box instructing. That's good, considering, as it is not within the distro.

Running the command as it specifies will get you a working SSM utility, BUT, the other important utilities are NOT present in the system.

This is NOT a complaint and I dont want it viewed that way (even though at least one developer will...this I know). Looking over the past since this 'removal' occurred, there have been several occurrences where you have had to get involved to resurrect something that used to be beneficial within your distro(s) never requiring your attention. The problems, research, and resolvings use to NOT take up developer's time...now, unfortunately it is.

The use of sharing info across our LANs have not, nor will not diminish even as worldwide internet improvements occur.

Questions

• Should I rerun a SAMBA installation because of something new in the REPO? Will take bring the utilities into the system?

• Will this be resolved in a future version beyond v10c?

Thanks in advance

Clarity wrote: Fri Oct 21, 2022 12:58 am

the utilities are NOT present in the system. Did I do something wrong?

looks like you need package smbclient https://voidlinux.pkgs.org/current/void ... .xbps.html

vpm i smbclient

and maybe libsmbclient? https://voidlinux.pkgs.org/current/void ... .xbps.html
vpm i libsmbclient

I knew this, but I am trying as best I can to get you to see what has been dumped on users, now. You and I know I am NOT the only user of SAMBA. Most users have use of this in their homes with all kinds of hardware we have in the home. This 30 year old technology, supported by worldwide developers, continues to keep pace with our changing world and with Linux growth, as well.

This packaging makes every new use a issue for years to come...unless of course new users are knowledgible...first.

Before the internal WoofCE war, this was never a problem since @01micko introduced SAMBA into Slacko years ago. He made it so simple and complete recognizing the need to users.

Oh well, if that what you choose for users...

VoidPup build recipes are now on GitHub:

https://github.com/puppylinux-woof-CE/w ... /voidpup32
https://github.com/puppylinux-woof-CE/w ... /voidpup64

3dc2420c0fef949c423b9f13aa2fb450 VoidPup64-22.02+13.iso

4d5d4dc657d77c629a90af91c7d5d493 VoidPup32-22.02+13.iso

glibc-2.36 & gcc-12.2.0

see post #1

I'm successfully running the April 1 2023 'CE Testing' version in post #1, downloaded from github. No major issues encountered to date. Hardware is the usual Fujitsu S761. Install also the usual frugal grub4dos to SSD. Run first with no savefile but with @peebees LXDE ydrv and then with my scrubbed savefile from +13 and that ydrv. Clean boot and dmesg, the expected nag about possible breakage of savefile updating from WOOF_VERSION=' ' to WOOF_VERSION=9, DISTRO_PUPPYDATE='Apr 2023'. No breakage occurred. I am running both lx-rightclicks and drives-on-desktop using pets from other slackware releases/ydrvs and both work well in my install. Idle resource use excellent with CPU use at idle 4 to 5% less than near identical installs of LxPupSc64 or S15Pup64, both LXDE. I'll take it.

lx_right_clicks-0.7|lx_right_clicks|0.7||Desktop|108K||lx_right_clicks-0.7.pet||Make/Edit Shortcut||||
desktop_drive_icons_x86_64-0.0.5|desktop_drive_icons_x86_64|0.0.5||BuildingBlock|80K||desktop_drive_icons_x86_64-0.0.5.pet||no description provided|slackware|current||

Thanks,

Just tested the latest in a VM.

Initial pristine test - Noticed 2 elements

• SSM directs how to add the SAMBA component to the system. Following those instructions, using the prescribed Menu service, invokes the subsystem to download 39MB SAMBA to the system. Upon completion, the SSM no longer works and its not obvious how to have it operate.

• Should QEMU be added to the Menu installation feature. If I open a terminal and type 'qemu_gui' I get a statement. That statement could instead invoke something similar to what the SSM initially invokes before installation.

VPM seems to be performing OK when used for other add-ons like tldr and neofetch and ... etc

Just getting use to this new PUP with its changes. The "KL" forum series has spoiled me as it had become my VOID benchmark for OOTB usability.

Just some observations

@Clarity

Thank you for the report. There was a build problem on Github for Samba-simple-setup which is now corrected and revised .iso released.

Downloading now.

Note: this attempt to "break out" SAMBA to save 39MB and the introduction of potential user questions-problems does not appear to be in the best interest. It seems to be a decision that is overlooking something obvious: Today's world is one where Ethernet is inherently tied to all modern OS systems including cell-tablet OSes except for a very very few. If it is a secure subsystem, I am failing to see why there is a move to change what had become a stable offering for many years with very few request of it or reports of negative behavioral use of it that is constituting its removal and/or scrutiny.

But, I am not a WoofCE developer and I am sure that there MUST have been some very good reason to add this level of complexity to something that did not require thought before. This is especially true when developers KNOW the dangers of getting users involved in installing stuff.

I am going to go out on a limb that there is something else happening where this is a 1st step toward Linus's plan incorporating smb into the kernel as he and the SAMBA community are working together on..."MAYBE" this is what is happening in WoofCE??? (I really dont know)

If it is published somewhere, I would love to read why.

@Clarity as you know smbclient is broken in Void Linux and we might have to post a message somewhere in Void Linux land to address it. I've been looking for workarounds but not much success yet.

It has stopped NetHood from going forward in KLV

Testing results of sharing.

VM stanza for VoidPUP64 operations. HOST is a QEMU v7.1.

qemu-system-x86_64 -enable-kvm -vga std -m 2G -smp 2 -device ac97 -name 'VoidPUP64 on QEMU' -cdrom VoidPup64-22.02-2.iso

No major issues found in current tests. Again, @peebee this is a VERY responsive PUP. Thanks for this advancement.

Additional tests for smb operations. Expect the smbclient messages to be different when booted on bare-metal.

@rockedge

...smbclient is broken in Void Linux...

Yes, I know. Last night I was playing around on Void's website. Seems they have a few issues that they are addressing.

I haven't tried Arch, yet. Just waiting on a WoofCE ArchPUP64 updated version iff one is forthcoming.

I understand. Thanks!

Clarity wrote: Thu Apr 06, 2023 6:43 pm

I am sure that there MUST have been some very good reason to add this level of complexity to something that did not require thought before.
I am going to go out on a limb that there is something else happening where this is a 1st step toward Linus's plan incorporating smb into the kernel as he and the SAMBA community are working together on..."MAYBE" this is what is happening in WoofCE??? (I really dont know)

Much simpler very good reason:
Samba as available from Void is as you say 10% of the size of the complete distro and is a minority interest....
A bit smaller Samba can be built by petbuild but maintaining this is a PITA as it breaks frequently when system components get updated

yes, I do know of that Void Linux issue they are wrestling with.

The other mainstreams are not in the boat they are in. Debian, Slackware, RedHat, Gentoo, and all of the various Linux-Unix offshoot have had this solved for years/decades.

So, this VoidPup tackles it differently in light of the Void Linux struggles. My Hat's off to you for recognizing and providing a solution for this PUP. Maybe they can learn from you and the talents of this community.

The other forum PUPs/DOGs/distros, over the years, are not in the same position as Void Linux finds itself with this and couple of the other things they are looking at.

Tried VoidPup32-22.02+14, all seems ok, sfs browsers ok, but :

• "ydrv_vpup32_22.02.sfs" is ok when just loaded (sfs load), but at the next reboot, there is no wallpaper anymore. If it is loaded with filemnt, there is a crash at the next reboot (end kernel panic -not syncing ... exit code=0x00000100.)

• Voidpup app install doesn't work, "app not installed".

Thanks.

Screenshot : no wallpaper and trying to install app (terminal)

Welcome @Fredk6 While I haven't tried VoidPup, I have used a few other of peebee's
contributions. If my memory isn't totally gone, I seem to remember that "ydrv" as well as other "alphabet" drives,
are loaded during the boot process, so no need to load using SFSLoad. You may need to boot without a save file
and see if this is still the case. Double loading an SFS may introduce problems and inconsistencies. Once you
have VoidPup 32 booted without a save you can then make your customizations and shutdown, at which point
you should be prompted to create a new save file. Try that an report back to us!
Wiz

Wiz57 wrote: Tue Jul 04, 2023 11:05 pm

Try that an report back to us!
Wiz

Thank you very much for the reply, Wiz.
You are probably right, but if I try that, it crash at boot (end kernel panic -not syncing ... exit code=0x00000100.).
If I rename the "ydrv", no crash, but it is not loaded.
I use grub4dos to boot.

Fredk6 wrote: Tue Jul 04, 2023 9:16 pm

Tried VoidPup32-22.02+14, all seems ok, sfs browsers ok, but :

• "ydrv_vpup32_22.02.sfs" is ok when just loaded (sfs load), but at the next reboot, there is no wallpaper anymore. If it is loaded with filemnt, there is a crash at the next reboot (end kernel panic -not syncing ... exit code=0x00000100.)

• Voidpup app install doesn't work, "app not installed".

Thanks.

Which ydrv? Where did you get it from?

As Wiz57 says, ydrv's should be put into your frugal install directory where your adrv, fdrv and zdrv reside and the system rebooted.

Which app are you trying to install?

+14 is actually a bit old........... see post #1 for where to get the current version from Github

peebee wrote: Wed Jul 05, 2023 6:05 am

Which ydrv? Where did you get it from?

As Wiz57 says, ydrv's should be put into your frugal install directory where your adrv, fdrv and zdrv reside and the system rebooted.

Which app are you trying to install?

+14 is actually a bit old........... see post #1 for where to get the current version from Github

Thank you very much for the reply, peebee.
I get ydrv and +14 from the link from post #1, not from github, but from sourceforge ( + LXDE + XFCE - https://sourceforge.net/projects/vpup/f ... p32/addons). Sorry, I don't find iso file on github.

As I say to Wiz, if I put ydrv's into my frugal install directory, there is a crash at boot (end kernel panic -not syncing ... exit code=0x00000100.).

For "Voidpup app install" (no link with ydrv), I have try many (libreoffice, thunderbird, gnome-player, ...).