Bug 19578 - Hexchat fails to connect to server when started from autostart in plasma5
Summary: Hexchat fails to connect to server when started from autostart in plasma5
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Sander Lepik
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-13 12:31 CEST by Barry Jackson
Modified: 2016-12-02 13:22 CET (History)
2 users (show)

See Also:
Source RPM: hexchat-2.12.1-5.mga6
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Barry Jackson 2016-10-13 12:31:47 CEST 
Description of problem:
As summary.

Stopping hexchat and re-starting then connects to servers OK.

It seems that auto-started programs are started too early in plasma5 such that many are up and running before the desktop/panel etc. are up. 

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Marja Van Waes 2016-10-13 15:32:43 CEST 
Assigning to hexchat maintainer and CC'ing the KDE maintainers. Feel free to reassign to the KDE maintainers if that's better, though!

CC: (none) => kde, marja11
Assignee: bugsquad => mageia

Comment 2 Barry Jackson 2016-10-15 01:51:12 CEST 
The message in hexchat GUI on autostart is:

* Looking up %U
* Unknown host. Maybe you misspelt it?

It is not possible to get past this using any menu options AFAICT.

Closing the hexchat window leaves the tray icon, but this no longer responds to left click.

It is possible to quit hexchat from the context (right click on tray icon) menu, after which a restart from the main applications menu works normally.
Comment 3 Barry Jackson 2016-12-02 13:22:39 CET 
This finally seems resolved after recent updates.

Closing as WFM

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME
Note You need to log in before you can comment on or make changes to this bug.