[dolphin] [Bug 347916] Search does not work when performed from $HOMEDIR/$USER

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347916

Rewarp  changed:

   What|Removed |Added

 CC||rew...@thestrayworld.com

--- Comment #8 from Rewarp  ---
(In reply to Bron Mach from comment #4)
> Going to: System Settings > Search > File Search, and unselecting "Enable
> file search" let Dolphin find files in my home directory and subdirectories. 
> 
> Otherwise with "Enable file search" selected, the behaviour was the same as
> described by Edward: no files found unless searching outside of my home
> directory.
> 
> Dolphin 15.08.2 on Kubuntu 15.10 with updates from backports PPA

I can confirm this behavior in openSUSE Tumbleweed. I have tried resetting
Baloo for reindexing many times, but oddly, the Search settings automatically
exclude my secondary hard drives containing my user files from being indexed.

I have tried forcing the reindexing by deleting the baloo config files via:

balooctl stop
rm ~/.config/baloo*
rm -rf ~/.local/share/baloo
baloo start

However, when I check the Search settings, my external drives are once again
excluded from being indexed. It is very ironic that unselecting Enable File
Search allows me to search for files.

-- 
You are receiving this mail because:
You are watching all bug changes.

[akregator] [Bug 360448] Visual artefact appearing in Akregator

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360448

Rewarp  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Rewarp  ---
I don't see this issue anymore in Kontact 5.3, so I presume it has been
properly fixed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 350059] Filters in kmail no longer functional

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=350059

Rewarp  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from Rewarp  ---
Since this issue is no longer occurring, I am closing this report. Thanks for
all the help!

-- 
You are receiving this mail because:
You are watching all bug changes.

[ktorrent] [Bug 371203] New: ktorrent immediately crashes

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=371203

Bug ID: 371203
   Summary: ktorrent immediately crashes
   Product: ktorrent
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: joris.guis...@gmail.com
  Reporter: rew...@thestrayworld.com

Application: ktorrent (5.0.1)

Qt Version: 5.7.0
Frameworks Version: 5.26.0
Operating System: Linux 4.7.6-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
ktorrent fails to properly launch and crashes as soon as it loads up. This
behavior occurs whether it is launched on its own, or when used to open torrent
links.

The crash can be reproduced every time.

-- Backtrace:
Application: KTorrent (ktorrent), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fab968f2940 (LWP 22295))]

Thread 6 (Thread 0x7fab4f41b700 (LWP 22315)):
#0  0x7fab909aeb39 in syscall () from /lib64/libc.so.6
#1  0x7fab915b86c5 in QBasicMutex::lockInternal() () from
/usr/lib64/libQt5Core.so.5
#2  0x7fab915b8782 in QMutex::lock() () from /usr/lib64/libQt5Core.so.5
#3  0x7fab9615cba9 in net::SocketMonitor::lock (this=) at
/usr/src/debug/libktorrent-2.0.1/src/net/socketmonitor.cpp:108
#4  0x7fab9615db8c in net::UploadThread::update (this=0x224a180) at
/usr/src/debug/libktorrent-2.0.1/src/net/uploadthread.cpp:49
#5  0x7fab9615e3d9 in net::NetworkThread::run (this=0x224a180) at
/usr/src/debug/libktorrent-2.0.1/src/net/networkthread.cpp:48
#6  0x7fab915c1558 in ?? () from /usr/lib64/libQt5Core.so.5
#7  0x7fab8c40e454 in start_thread () from /lib64/libpthread.so.0
#8  0x7fab909b33ff in clone () from /lib64/libc.so.6

Thread 5 (Thread 0x7fab4fc1c700 (LWP 22314)):
[KCrash Handler]
#6  0x7fab9164a52c in QString::indexOf(QChar, int, Qt::CaseSensitivity)
const () from /usr/lib64/libQt5Core.so.5
#7  0x7fab96199036 in HttpResponseHeader::parseLine
(this=this@entry=0x7fab4fc1b9b0, line=..., number=number@entry=14) at
/usr/src/debug/libktorrent-2.0.1/src/download/httpresponseheader.cpp:27
#8  0x7fab96199af2 in HttpResponseHeader::parse
(this=this@entry=0x7fab4fc1b9b0, str=...) at
/usr/src/debug/libktorrent-2.0.1/src/download/httpresponseheader.cpp:88
#9  0x7fab96197911 in HttpResponseHeader::HttpResponseHeader (str=...,
this=0x7fab4fc1b9b0) at
/usr/src/debug/libktorrent-2.0.1/src/download/httpresponseheader.h:27
#10 bt::HttpConnection::HttpGet::onDataReady (this=0x2c0f600,
buf=buf@entry=0x7fab9648dba0  "HTTP/1.1 302
Found\r\nCache-Control: no-cache, no-store, must-revalidate\r\nPragma:
no-cache\r\nContent-Type: text/html; charset=utf-8\r\nExpires: -1\r\nLocation:
http://201406.jb-dl.cdn.scaleengine.net/las/201;..., size=size@entry=665) at
/usr/src/debug/libktorrent-2.0.1/src/download/httpconnection.cpp:386
#11 0x7fab961984fb in bt::HttpConnection::onDataReady (this=0x2c0e270,
buf=0x7fab9648dba0  "HTTP/1.1 302 Found\r\nCache-Control:
no-cache, no-store, must-revalidate\r\nPragma: no-cache\r\nContent-Type:
text/html; charset=utf-8\r\nExpires: -1\r\nLocation:
http://201406.jb-dl.cdn.scaleengine.net/las/201;..., size=665) at
/usr/src/debug/libktorrent-2.0.1/src/download/httpconnection.cpp:158
#12 0x7fab9616269f in net::TrafficShapedSocket::read (this=0x2bfce80,
max_bytes_to_read=106230, now=1476859486396) at
/usr/src/debug/libktorrent-2.0.1/src/net/trafficshapedsocket.cpp:142
#13 0x7fab9615f4e3 in net::SocketGroup::processLimited (this=0x224a0d0,
up=false, now=1476859486396, allowance=@0x7fab4fc1bbb4: 106230) at
/usr/src/debug/libktorrent-2.0.1/src/net/socketgroup.cpp:79
#14 0x7fab9615f750 in net::SocketGroup::process (this=0x224a0d0,
up=, now=, global_allowance=@0x7fab4fc1bbb4:
106230) at /usr/src/debug/libktorrent-2.0.1/src/net/socketgroup.cpp:188
#15 0x7fab9615e627 in net::NetworkThread::doGroupsLimited
(this=this@entry=0x2249e50, num_ready=num_ready@entry=1,
now=now@entry=1476859486396, allowance=@0x7fab4fc1bc10: 106230) at
/usr/src/debug/libktorrent-2.0.1/src/net/networkthread.cpp:111
#16 0x7fab9615e921 in net::NetworkThread::doGroups
(this=this@entry=0x2249e50, num_ready=num_ready@entry=1,
now=now@entry=1476859486396, limit=) at
/usr/src/debug/libktorrent-2.0.1/src/net/networkthread.cpp:190
#17 0x7fab9615e396 in net::DownloadThread::update (this=0x2249e50) at
/usr/src/debug/libktorrent-2.0.1/src/net/downloadthread.cpp:83
#18 0x7fab9615e3d9 in net::NetworkThread::run (this=0x2249e50) at
/usr/src/debug/libktorrent-2.0.1/src/net/networkthread.cpp:48
#19 0x7fab915c1558 in ?? () from /usr/lib64/libQt5Core.so.5
#20 0x7fab8c40e454 in start_thread () from /lib64/libpthread.so.0
#21 0x7fab909b33ff in clone () from /lib64/libc.so.6

Thread 4 (Thread 0x7fab5f6ab700 (LWP 22302)):
#0  0x7fab8c41410f 

[kmail2] [Bug 339360] offline accounts should try to reconnect automatically

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=339360

Rewarp  changed:

   What|Removed |Added

 CC||rew...@thestrayworld.com

--- Comment #2 from Rewarp  ---
I am experiencing this error with KMail 5.3.0. nd in prior versions.

When I login, I have a cryptographic key setup to unlock kwallet, which means
there is a delay in the credentials for signing onto the available networks.

This delay means autoconnect usually fails unless I unlock my wallet fast
enough. The failure to connect stops KMail from retrieving new messages. After
connecting, KMail fails to detect the change in the network status, and will
remain so until I manually restart the IMAP connection.

Prior to noticing this issue, I went for days without receiving or responding
to emails, simply because I was trying to connect to networks requiring
authentication.

-- 
You are receiving this mail because:
You are watching all bug changes.

[frameworks-kwallet] [Bug 366040] libkf5wallet5: timeout when using GPG and gpg-agent

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=366040

Rewarp  changed:

   What|Removed |Added

 CC||rew...@thestrayworld.com

--- Comment #1 from Rewarp  ---
I would like to add, that my gpg-protected kwallet does not provide ample time
to type in my passphrase before proceeding with authentication procedures after
logging in. This causes two major issues which are:

1. Connection to an encrypted WiFI network fails as the saved password is not
provided because kwallet has yet to be unlocked immediately after logging in. I
have to manually cancel the password dialogue box after unlocking kwallet
before attempting to connect.

2. Failure to connect to the WiFi network always results in KMail failing to
connect to my email servers, whose status will remain unchanged unless I
manually restart the connection to my email servers.

I am running kwallet 5.24 on opensuse Tumbleweed.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 347740] Encrypted message not detected as encrypted message

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347740

--- Comment #13 from Rewarp  ---
Created attachment 99662
  --> https://bugs.kde.org/attachment.cgi?id=99662=edit
Message as plain text

By full message, I assume you mean the entire source view of the message. I
have included it in this attachment, and would also like to confirm that this
correspondence also uses Apple Mail, as mentioned in the bug report you
attached.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 347740] Encrypted message not detected as encrypted message

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347740

--- Comment #11 from Rewarp  ---
I have confirmed that messages sent with the attachment above are still not
being decrypted. I am at a loss as what is wrong here.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 345992] Keyboard shortcut assigned to "archive mail" works once, unconfigures itself

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=345992

Rewarp  changed:

   What|Removed |Added

 CC||rew...@thestrayworld.com

--- Comment #4 from Rewarp  ---
Since this is a keyboard shortcut issue, I am adding my own custom shortcut
problem here as well.
 I have assigned the "Right" and "Left" key to Next and Previous message
respectively.

For some odd reason, The shortcut for "Focus on Next Message" is not the
default Alt+Right, but is Right. This conflicts with my custom key for "Next
Message".

After changing "Focus on Next Message" to the default Alt+Right, the Right key
works once to move to the next message, but on the second tap is suddenly
reassigned to "Focus on Next Message again"

Steps to reproduce:

1. Reassign shortcut for "Focus on Next Message" to default Alt+Right
2. Assign shortcut for "Next Message" to Right.
3. Press Right.

Expected:

The next email message should be selected.

Instead:

1. The next message is selected.
2. The custom shortcut fails and is reassigned to "Focus on Next Message".

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 347740] Encrypted message not detected as encrypted message

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347740

--- Comment #10 from Rewarp  ---
(In reply to tomaggio from comment #8)
> Hi;
> With kmail 5.1.3 it works again. So  for me, this Bug is solved.

Thanks. I will wait and see if it works on 5.1.3.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 347740] Encrypted message not detected as encrypted message

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347740

--- Comment #7 from Rewarp  ---
I am now running KMail 5.1.2, and the workaround method no longer works.

I am back to downloading the message separately before I am able to decrypt the
message.

Here's a screenshot as proof.

https://imgur.com/sY3XrQl

-- 
You are receiving this mail because:
You are watching all bug changes.

[akregator] [Bug 360448] New: Visual artefact appearing in Akregator

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360448

Bug ID: 360448
   Summary: Visual artefact appearing in Akregator
   Product: akregator
   Version: unspecified
  Platform: Other
   URL: http://imgur.com/OWAZySV
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: rew...@thestrayworld.com

A short period after I launch Kontact, visual artefacts with seemingly random
snippets of whatever has been on the screen previously will cover up a portion
of Akregator in Kontact.

A screenshot illustrating the problem is included.

Reproducible: Always

Steps to Reproduce:
1. Launch Kontact
2. Switch to Akregator

Actual Results:  
Visual artifact blocking part of the screen.

Expected Results:  
Visual artefact should not be there.

Problem disappears after restarting Kontact in the same session. But will
reoccur.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kmail2] [Bug 358501] New: New Message shortcut not working correctly

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358501

Bug ID: 358501
   Summary: New Message shortcut not working correctly
   Product: kmail2
   Version: 5.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-b...@kde.org
  Reporter: rew...@thestrayworld.com

After successfully moving my KMail4 to KMail5, I discovered the Ctrl+N shortcut
threw up an error.

"The key sequence 'Ctrl+N' is ambiguous. Use 'Configure Shortcuts' from the 
'Settings' menu to solve the ambiguity. No action will be triggered."

The shortcut settings had not been changed from the default setting and no
other application was in conflict with it.

After assigning nothing to the custom shortcut to New Message, the actual
shortcut for New Message worked again. Attempts to reassign the shortcut back
to the default setting threw up this error:

"The 'Ctrl+N' key combination is already used by the New Message... action.
Please select a different one."

It is possible that remnants of the shortcuts in KMail4 are still being run,
hence resulting in a conflict.

Reproducible: Always

Steps to Reproduce:
1. Tries to use (default setting) Ctrl+N in KMail5 after upgrading from KMail4

Actual Results:  
Error message given.

Expected Results:  
New message window should have launched.

The computer is running openSUSE Tumbleweed with subscriptions to the
Frameworks, Applications, and Extras repositories taking priority over stock
repositories.

-- 
You are receiving this mail because:
You are watching all bug changes.