Bug 354507 - Already running kate will not open any other files opened from elsewhere
Summary: Already running kate will not open any other files opened from elsewhere
Status: RESOLVED FIXED
Alias: None
Product: kate
Classification: Applications
Component: application (show other bugs)
Version: Git
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
: 356829 356878 357523 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-10-28 15:36 UTC by Martin Klapetek
Modified: 2016-11-22 11:28 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
attachment-8356-0.html (5.49 KB, text/html)
2015-12-15 15:55 UTC, Torsten Bielen
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Klapetek 2015-10-28 15:36:21 UTC
I open Dolphin, open some file in Kate. Then switch back to Dolphin and try opening another file in Kate. I am switched to Kate but the file is not opened and there is no error message.

Same thing happens when running it from Konsole.

It would appear that something around the KDBusService got broken perhaps as it looks like Kate is not being passed the filename to open and/or is simply not opening the file.

This happens with recent git version of Kate.
Comment 1 Torsten Bielen 2015-12-15 10:30:18 UTC
Each time you want to open a file from dolphin a new instance is created. Closing kate using the close button of window frame doesn't stop current instance.  Therefore you have multiple instances running in the background. I'm not sure which instance is selected if you try to open the next file from dolphin. If you  force closing the "background" instances it works as expected.

Using File->Exit works.

Kate Version: 15.08.3
Comment 2 Kåre Särs 2015-12-15 11:23:52 UTC
Is it possible that you updated frameworks to 5.17?

There is a fix in Kate for 15.12 for a change in frameworks that triggers this bug in Kate.
Comment 3 Torsten Bielen 2015-12-15 15:55:54 UTC
Created attachment 96090 [details]
attachment-8356-0.html

I use my notebook for daily work. Therefore it don't want to change to the unstable branch of opensuse. I re-check it if 15.12 is available in the offical repositories of opensuse.

Regards
Torsten 
--------------------
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Zuwiderhandlungen werden im Bedarfsfalle geahndet.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.



> https://bugs.kde.org/show_bug.cgi?id=354507
> 
> Kåre Särs <kare.sars@iki.fi> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |kare.sars@iki.fi
> 
> --- Comment #2 from Kåre Särs <kare.sars@iki.fi> ---
> Is it possible that you updated frameworks to 5.17?
> 
> There is a fix in Kate for 15.12 for a change in frameworks that triggers this
> bug in Kate.
> 
>
Comment 4 Kåre Särs 2015-12-15 16:16:28 UTC
15.12 is not officially released yet, but soon :)
Comment 5 Martin Klapetek 2015-12-15 16:25:38 UTC
> There is a fix in Kate for 15.12 for a change in frameworks that triggers this bug in Kate.

Running master here, can confirm it works fine now.

Thanks!
Comment 6 Kåre Särs 2015-12-20 06:39:05 UTC
*** Bug 356829 has been marked as a duplicate of this bug. ***
Comment 7 Kåre Särs 2015-12-20 06:40:12 UTC
*** Bug 356878 has been marked as a duplicate of this bug. ***
Comment 8 Kåre Särs 2016-01-05 07:18:56 UTC
*** Bug 357523 has been marked as a duplicate of this bug. ***