Bug 24955

Summary:	Clicking on "telegram desktop" does nothing (was:The get-telegram package does not work after the second execution)
Product:	Mageia	Reporter:	Jose Manuel López <joselp>
Component:	RPM Packages	Assignee:	Sander Lepik <mageia>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	7
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	get-telegram	CVE:
Status comment:

Description Jose Manuel López 2019-06-14 11:49:57 CEST

Description of problem: The get-telegram package does not work after the second execution


Version-Release number of selected component (if applicable): Get-telegram 1.4.3


How reproducible: Install the rpm package and ejecute. After the second run, the program crash.


Steps to Reproduce:
1.Install get-telegram
2.Run
3.Close and run again

Comment 1 Jose Manuel López 2019-06-14 11:50:21 CEST

Detailed description:

I have seen a problem with the "get-telegram" package. Once installed and executed, create a folder in the "home / user" directory. But when I run it the second time from konsole, it appears:

[jose @ localhost ~] $ get-telegram
mv: you can not overwrite the 'application / Telegram' directory with the 'Telegram' directory
[jose @ localhost ~] $

If I run it from the start / internet / Telegram Desktop does nothing (I guess it's because of the error that appears in the console).

Comment 2 Marja Van Waes 2019-06-15 11:41:32 CEST

I never used Telegram, but can't you start "telegram" or "telegram-desktop" or so in a terminal instead of "get-telegram"?

You should be able to start from the menu  (internet / Telegram Desktop), though!

Assigning to our get-telegram maintainer.

Assignee: bugsquad => mageia
Summary: The get-telegram package does not work after the second execution => Clicking on "telegram desktop" does nothing (was:The get-telegram package does not work after the second execution)
CC: (none) => marja11

Comment 3 Sander Lepik 2019-06-15 22:14:39 CEST

I've submitted new version that should fix this issue. Please reopen if it doesn't.

Status: NEW => RESOLVED
Resolution: (none) => FIXED