Bug 918074

Summary:	Remmina - start tray icon automatically does not work
Product:	[Fedora] Fedora	Reporter:	BK <redhat-bugzilla>
Component:	remmina	Assignee:	Christoph Wickert <christoph.wickert>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	18	CC:	christoph.wickert
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-06 20:28:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description BK 2013-03-05 12:32:03 UTC

Description of problem:
Having remmina start iconified automatically at login does ot work

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

remmina-1.0.0-5.fc18.x86_64
(also remmina-1.0.0-4.fc17.x86_64)

How reproducible:
Happend every time at startup once configured to autostart

Steps to Reproduce:
1. Login, ttart remmina
2. Open preferences, select Applet tab, check "start tray icon automatically"
3. Close remmina, logout and login again
  
Actual results:

This entry appears in ~/.cache/gdm/session.log (~/.xsession-errors in F17):

option parsing failed: Unknown option -i

and the remmina tray icon does not appear, nor can I find any remmina process

Expected results:

The remmina tray icon should appear, and the process be running and ready to open VNC sessions etc


Additional info:

This is a known problem, and is supposedly fixed upsteam. I was surprised to see that the remmina version is the 1.0 release (which I believe should have the fix applied), and this problem still present, so I assume it must be due to some fedora specific patches applied to it.

Comment 1 Christoph Wickert 2013-03-05 12:58:25 UTC

This has nothing to do with any Fedora patches, the option did not work in 1.0 and was reintroduced later. See bug 834883 for more info

Comment 2 Christoph Wickert 2013-05-06 20:28:38 UTC


*** This bug has been marked as a duplicate of bug 834883 ***