/home/user/.local/share/TelegramDesktop/https:/www.youtube.com/watch?v=: No such file or directory.

Hello.

I've installed TelegramDesktop from the packages and one of my friends gave me to a link to watch a video on youtube. This is what happened when I clicked on top of it to hear the song :

Screenshot_2025-01-06_18-07-45.png


Any idea about how to fix this error ? I'm trying to understand by myself where is the problem,but at the moment I haven't yet fixed it.
 
Who / what is the upstream ?
TelegramDesktop (and it's authors) is the upstream in this case.

Looking at the error message, TD seems to be trying to save the link as a file and then open it. However, the file name contains slashes which aren't allowed in file names. Consequently, it's looking for the file:
Code:
/home
    /marietto
        /.local
            /share
                /TelegramDesktop
                    /https:
                        /www.youtube.com
                            /watch?v=y29kmhnjtc8:

This is not what anyone likely intended. The error, thus, seems to be within TelegramDesktop, or, perhaps, in how the link was sent.
 
TelegramDesktop (and it's authors) is the upstream in this case.

Looking at the error message, TD seems to be trying to save the link as a file and then open it. However, the file name contains slashes which aren't allowed in file names. Consequently, it's looking for the file:
Code:
/home
    /marietto
        /.local
            /share
                /TelegramDesktop
                    /https:
                        /www.youtube.com
                            /watch?v=y29kmhnjtc8:

This is not what anyone likely intended. The error, thus, seems to be within TelegramDesktop, or, perhaps, in how the link was sent.

I don't have any external link or file in that path :

Screenshot_2025-01-08_06-50-09.png
 
I know. It's a totally invalid path/file. TD is, apparently, trying to save a URL as a file and.... URL's contain characters (the slashes) that aren't valid as file names, and other characters that need special handling. This results in a bogus path to a non-existant file.

Why TD is trying to do this?, I have not the slightest idea, but it's a problem (ultimately) with TD and not FreeBSD. Perhaps it's a problem with how the link was sent to you. If it was just a basic message, I'd expect you would simply seen the link as plain text (or a clickable hyperlink) and could use that directly.
 
(As a side note, if TD is a crude port of a windows application, this may have worked in windows as windows uses the other slashes in file paths and so, a URL might be a valid windows file name (though, I'm pretty sure question marks are *not* valid for windows files, and colons denote alternate file streams and are also not allowed, so never mind this dead-end side thought)
 
Back
Top