https://bugs.kde.org/show_bug.cgi?id=411259
Méven Car <meven....@enioka.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |FIXED
--- Comment #15 from Méven Car <meven....@enioka.com> ---
(In reply to Chris from comment #14)
> (In reply to Bug Janitor Service from comment #13)
> > Dear Bug Submitter,
> >
> > This bug has been in NEEDSINFO status with no change for at least
> > 15 days. Please provide the requested information as soon as
> > possible and set the bug status as REPORTED. Due to regular bug
> > tracker maintenance, if the bug is still in NEEDSINFO status with
> > no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
> > due to lack of needed information.
> >
> > For more information about our bug triaging procedures please read the
> > wiki located here:
> > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging
> >
> > If you have already provided the requested information, please
> > mark the bug as REPORTED so that the KDE team knows that the bug is
> > ready to be confirmed.
> >
> > Thank you for helping us make KDE software even better for everyone!
>
> Sorry about the slow response. I didn't release it has been so long. Thanks
> for the reminder email.
>
> Operating System: Slackware64-current
> KDE Plasma Version: 5.20.4
> KDE Frameworks Version: 5.77.0
> Qt Version: 5.15.2
> Kernel Version: 5.4.83
> OS Type: 64-bit
> Processors: 4 × AMD Phenom(tm) II X4 840 Processor
> Memory: 7.8 GiB of RAM
> Graphics Processor: GeForce GT 730/PCIe/SSE2
>
> Ark Version 20.12.0
>
> I have tried opening (Preview) several bash scripts in various archive from
> Ark. All are now acting correctly, opening (Preview) Kate instead of a
> binary viewer.
>
> It appears somewhere along the way this issue has been fixed. As you can see
> from my version list above, compared to my last post. There have been many
> upgrades. So as far as I am concerned the issue is been resolved.
>
I am very glad.
> If two people cannot reproduce, it probably is due to a state / particular
> setting on your system.
Given how behind your versions were, we could have just considered the bug as
fixed because non-reproducible by two other people.
>
>
> Again sorry for the late input on this. Also thanks for keeping up on this,
> I had pretty much given up with this being resolved.
Thanks for keeping us posted, no worries.
--
You are receiving this mail because:
You are watching all bug changes.
