Bug 356341 - Opening Gwenview with picture causes "Request time on server expired <IP_ADDR>" message
Summary: Opening Gwenview with picture causes "Request time on server expired <IP_ADDR...
Status: RESOLVED FIXED
Alias: None
Product: gwenview
Classification: Applications
Component: general (show other bugs)
Version: Other (add details in bug description)
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Gwenview Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-06 20:07 UTC by Peter K.
Modified: 2016-01-03 22:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter K. 2015-12-06 20:07:25 UTC
Using openSUSE Leap 42.1, Gwenview version 15.08.3, KDE Frameworks 5.16.0, Qt 5.5.0
When opening  Gwenview with picture, after few seconds is shown message window "Request time on server expired <IP_ADDR>" 
IP_ADDR is defined numeric format and server was defined in dolphin. From ~/.local/share/user-places.xbel
 <bookmark href="smb://<domain>%5C<username>@<IP_ADDR>/">
  <title>TITLE</title>
  <info>
   <metadata owner="http://freedesktop.org">
    <bookmark:icon name="folder-remote"/>
   </metadata>
   <metadata owner="http://www.kde.org">
    <ID>1447646013/1 (V2)</ID>
    <IsHidden>false</IsHidden>
   </metadata>
  </info>
 </bookmark>

When opening Gwenview without picture, message window does not appear. Until now I did not opened pictures from that location. In ~/.local/share/user-places.xbel are defined also other SMB bookmarks, but only for defined one is message shown. After pressing OK button, Gwenview works normally.

Reproducible: Always

Steps to Reproduce:
1. Open Gwenview with image (from command line or from Dolphin)
2. Wait few seconds

Actual Results:  
Error message "Request time on server expired <IP_ADDR>" is coming

Expected Results:  
No error message is shown.
Comment 1 Peter K. 2016-01-03 22:40:16 UTC
gwenview5 updated to 15.12.0, bug disappeared.