The Linux.uk Community Forum

I am looking for the up to date source code for the xv image viewer software originated by John Bradley many years ago.

Does anyone have this code or can supply a link to this code ?

Thanks.

Many thanks for the reply.

To be clearer :-

I have already been running the mentioned Microsoft items on Debian Jessie.

I now wish to update my Linux desktop to use Debian 11 as Jessie is a very outdated distribution.

I just wanted to know about people's experience in running Debian 11 with regard to it's stability.

I am considering running Debian 11 on a desktop.

The desktop will typically be used for office work. A lot of email uses Outlook on the Web, running on Microsoft's
Exchange Server. Microsoft's Teams software is also used.

It is very important that the system is stable. Debian 11 is a fairly new release.

If you have experience in running Debian 11, how stable have you found it ?

Debian 11 would be run with the AMD Ryzen 5 5600x CPU.

Thanks very much for your replies.

My answers to your questions, Keith :-

(1) The rsync command is entered on the computer as a single line
(2) Both full stops are intentionally part of the command
(3) The whole of the home directory is required to be backed up.

I am now suggesting a different procedure to try and overcome the rsync hang :-

Rsync has very recently been run okay on a new FAT32 stick, using the command i previously reported
(the -a option is retained).

(a) I propose to put all the files on the current new stick
into a new directory (using mv *.* backup-dir) outside of my
home directory and then run rsync again on the stick.


Presumably the new run of rsync would delete backup-dir
(as this doesn't exist in my home directory) and then just
copy over all the home directory files again to the stick.


Would rsync run okay on the same stick using step (a) on a periodic basis ?

Rsync has been successfully run for quite a few years on a Debian system. The home directory has been
regularly transferred to a FAT32 USB drive.

Recently, rsync has been hanging.

Rsync just hangs at a particular small file that it gets to and doesn't move on - no
error message, so it doesn't crash, it just hangs.

The command is of the form :-

rsync -v -a --max-size=4GB --delete /home/users-name/.
/media/memstick/.

where users-name is the name of the user.

Can anyone help to solve this problem, please ?

 Rsync has been regularly used to backup files in the home directory on a Linux desktop to a FAT32 USB stick.

Recently rsync has stalled due to problems with Service Worker and Local Storage files being transferred from
the home directory to the stick.

These files were deleted and rsync then rerun.

Rsync then stalled and produced many error messages of the form :-

rsync: chgrp
<file> failed:
Operation not permitted (1)

where <file> represents a filename.

The rsync command is of the form :-

rsync -v -a  --max-size=4GB --delete <home directory> .
<mount point> .

where <home directory> represents the home directory and <mount point> represents
the mount point.

I realise that FAT32 knows nothing about permissions, etc.,
but the above command has worked successfully on previous occasions.

Why are the above error messages appearing ?

Do they have anything to do with the Service Worker and Local Storage files which had been created on the
USB stick in the previous run of rsync ?

What is the best thing to do to get rsync working okay again ?

N.B. I don't want to change the rsync command in any way.

Would it be okay to delete all the files currently on the stick and then rerun rsync ?

Using a Linux Debian desktop.

Used to be able to open PDF email attachments in Opera and Firefox-esr browsers without downloading them.

Suddenly no longer able to open this type of attachment in Opera or Firefox-esr without downloading the attachments.

Also not able to open PDF files from various websites.

No changes at all have been made to the Debian system or any software on that system.

How can this problem be solved, please ?

It is not an option to download attachments on a regular basis.

I have an experience about the auto mounting of USB devices which has been going on for
a long time, but continues to puzzle me.

A Debian desktop is running using an /etc/fstab file in which the mount options for
a couple of USB devices are defined. Both devices use the noauto option.

Both devices are already plugged in when the system is rebooted. It has always been
found after a reboot that both USB devices have become mounted, despite the noauto
option.

I understand that during the reboot process the system issues the 'mount. -a' command,
which mounts filesystems defined in /etc/fstab that are not already mounted, except for
those filesystems that use the noauto option.

So what causes the two USB filesystems to be mounted ?

I know that the system contains the usbmount facility, but I understand that usbmount
automatically mounts filesystems when they are plugged in. Usbmount would not automatically
mount filesystems which are already plugged in.

Can someone please help to solve this problem. Thanks.

Thanks, David.

After further investigation, I agree with what you say.

It now seems to me that the situation is as follows :-

Filesystems in /etc/fstab which have the noauto option are not automatically mounted at boot time, so if these filesystems are already
plugged into USB ports at boot time, they would subsequently have to be manually mounted in order to be used.

Filesystems which are plugged into a port after the system has been booted are automatically mounted.

If a filesystem in /etc/fstab has a noauto entry, can that filesystem only be mounted manually using the mount command or
is there any chance that it will be automatically mounted by
usbmount ?

The filesystem is used in a USB port.

A version of the Opera browser has been working okay in a Debian Jessie system for about 9 months. Suddenly certain features no longer work :-

(1) Can't open attachments in emails, especially PDF attachments.

(2) Can't use ALT-P to clear cache/cookies

Can anyone explain why this has happened, please.

The version of Opera being used is

opera-stable_64.0.3417.73_amd64.deb

Is there an HTML problem now with this version ?

Does the Opera version need to be updated ?

If so, which version is suitable for Debian Jessie ?

 I am still struggling to solve the problem with the malfunctioning USB 3 port on a desktop
running Debian.

I would be very grateful if someone could please give useful answers to the following questions :-

(1) Can the desktop be safely rebooted, if needed, given the USB 3 problem?

(2) Can the USB 3 problem be fixed in some way or is the port now permanently
unavailable?

(3) If the USB 3 port is unavailable, can the new portable hard drive be used to
     do a back-up of the system from the USB 2 port currently occupied by a card reader
     or is there any risk the card reader will be messed up again afterwards ?

     (On a previous occasion, a portable hard drive was plugged into this USB 2 port
      in place of the card reader. The system issued a message indicating the port was busy.
      The card reader was plugged back into the USB 2 port and it was then found that
      a card inserted into the card reader could not be mounted).

Could the problem with the USB port possibly cause a problem if an attempt is made to reboot the system ?

The xhci_hcd driver is present, but I now get the following problem :-

The new flash drive was unplugged from the USB 3 port.

As root, the following command was run

dmesg* |* tail


The output was :

[3974120.938338] usb 1-1: new high-speed USB device number 66 using xhci_hcd
[3974126.430777] usb 1-1: new high-speed USB device number 67 using xhci_hcd
[3974131.923271] usb 1-1: new high-speed USB device number 68 using xhci_hcd
[3974137.415713] usb 1-1: new high-speed USB device number 69 using xhci_hcd
[3974142.908184] usb 1-1: new high-speed USB device number 70 using xhci_hcd
[3974148.400664] usb 1-1: new high-speed USB device number 71 using xhci_hcd
[3974153.893132] usb 1-1: new high-speed USB device number 72 using xhci_hcd
[3974159.385762] usb 1-1: new high-speed USB device number 73 using xhci_hcd
[3974164.878067] usb 1-1: new high-speed USB device number 74 using xhci_hcd
[3974170.370558] usb 1-1: new high-speed USB device number 75 using xhci_hcd


Then the new flash drive was plugged back into the USB 3 port and then, again as root,
the following command was run

dmesg | tail -50

The output was as follows :

[3973945.175272] usb 1-1: new high-speed USB device number 34 using xhci_hcd
[3973950.667736] usb 1-1: new high-speed USB device number 35 using xhci_hcd
[3973956.164234] usb 1-1: new high-speed USB device number 36 using xhci_hcd
[3973961.660705] usb 1-1: new high-speed USB device number 37 using xhci_hcd
[3973967.153175] usb 1-1: new high-speed USB device number 38 using xhci_hcd
[3973972.645644] usb 1-1: new high-speed USB device number 39 using xhci_hcd
[3973978.138108] usb 1-1: new high-speed USB device number 40 using xhci_hcd
[3973983.630571] usb 1-1: new high-speed USB device number 41 using xhci_hcd
[3973989.123038] usb 1-1: new high-speed USB device number 42 using xhci_hcd
[3973994.615532] usb 1-1: new high-speed USB device number 43 using xhci_hcd
[3974000.107987] usb 1-1: new high-speed USB device number 44 using xhci_hcd
[3974005.600444] usb 1-1: new high-speed USB device number 45 using xhci_hcd
[3974011.092914] usb 1-1: new high-speed USB device number 46 using xhci_hcd
[3974016.586439] usb 1-1: new high-speed USB device number 47 using xhci_hcd
[3974022.069876] usb 1-1: new high-speed USB device number 48 using xhci_hcd
[3974027.562378] usb 1-1: new high-speed USB device number 49 using xhci_hcd
[3974033.054785] usb 1-1: new high-speed USB device number 50 using xhci_hcd
[3974038.547262] usb 1-1: new high-speed USB device number 51 using xhci_hcd
[3974044.039723] usb 1-1: new high-speed USB device number 52 using xhci_hcd
[3974049.532213] usb 1-1: new high-speed USB device number 53 using xhci_hcd
[3974055.024682] usb 1-1: new high-speed USB device number 54 using xhci_hcd
[3974060.517132] usb 1-1: new high-speed USB device number 55 using xhci_hcd
[3974066.013620] usb 1-1: new high-speed USB device number 56 using xhci_hcd
[3974071.506102] usb 1-1: new high-speed USB device number 57 using xhci_hcd
[3974076.998569] usb 1-1: new high-speed USB device number 58 using xhci_hcd
[3974082.491021] usb 1-1: new high-speed USB device number 59 using xhci_hcd
[3974087.983486] usb 1-1: new high-speed USB device number 60 using xhci_hcd
[3974093.475956] usb 1-1: new high-speed USB device number 61 using xhci_hcd
[3974098.968439] usb 1-1: new high-speed USB device number 62 using xhci_hcd
[3974104.460916] usb 1-1: new high-speed USB device number 63 using xhci_hcd
[3974109.953390] usb 1-1: new high-speed USB device number 64 using xhci_hcd
[3974115.445836] usb 1-1: new high-speed USB device number 65 using xhci_hcd
[3974120.938338] usb 1-1: new high-speed USB device number 66 using xhci_hcd
[3974126.430777] usb 1-1: new high-speed USB device number 67 using xhci_hcd
[3974131.923271] usb 1-1: new high-speed USB device number 68 using xhci_hcd
[3974137.415713] usb 1-1: new high-speed USB device number 69 using xhci_hcd
[3974142.908184] usb 1-1: new high-speed USB device number 70 using xhci_hcd
[3974148.400664] usb 1-1: new high-speed USB device number 71 using xhci_hcd
[3974153.893132] usb 1-1: new high-speed USB device number 72 using xhci_hcd
[3974159.385762] usb 1-1: new high-speed USB device number 73 using xhci_hcd
[3974164.878067] usb 1-1: new high-speed USB device number 74 using xhci_hcd
[3974170.370558] usb 1-1: new high-speed USB device number 75 using xhci_hcd
[3974189.313961] usb 1-1: new high-speed USB device number 76 using xhci_hcd
[3974194.806428] usb 1-1: new high-speed USB device number 77 using xhci_hcd
[3974200.298916] usb 1-1: new high-speed USB device number 78 using xhci_hcd
[3974205.791363] usb 1-1: new high-speed USB device number 79 using xhci_hcd
[3974211.283830] usb 1-1: new high-speed USB device number 80 using xhci_hcd
[3974216.776300] usb 1-1: new high-speed USB device number 81 using xhci_hcd
[3974222.268794] usb 1-1: new high-speed USB device number 82 using xhci_hcd
[3974227.761269] usb 1-1: new high-speed USB device number 83 using xhci_hcd


Why is the above happening ?

I have now seen a number of cases where USB devices are not detected.

It seems that the xhci_hcd driver needs to be replaced/reinitialised.

Some of the posts recommend that the computer is completely powered down (I.e. all external devices are unmounted,
the computer is switched off and unplugged from the mains). After a wait of, say, up to 30 minutes, the computer is rebooted. The xhci_hcd driver should be reinitialised by the reboot, so the USB 3 port should then work fine.

Other posts suggest that instead of a power down and reboot, the xhci_hcd driver could be disabled and then re-enabled
similar to suggestion in https://zedt.eu/tech/linux/restarting-usb-subsystem-centos/

Does anyone know which directory contains the xhci_hcd driver in Debian, please ?