[plasma-nm] [Bug 366830] Network manager on system tray no longer connects/sees wifi networks after suspend/sleep status

2016-09-21 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=366830

--- Comment #3 from Leon  ---
It happened again. Here is the output as requested:

# nmcli device wifi list
*  SSID  MODE  CHAN  RATE  SIGNAL  BARS  SECURITY

-- end of output

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

[dolphin] [Bug 350199] Cannot handle dual DVD drives with similar labels

2016-08-16 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=350199

--- Comment #6 from Leon  ---
When unmounting a drive, it is removed from the listing. but when unmounting
the last drive, it remains on the listing but having the icon change from green
(mounted) to red (unmounted). It should either also disappear from the list, or
the ejected drives should become red (unmounted).

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

[dolphin] [Bug 350199] Cannot handle dual DVD drives with similar labels

2016-08-16 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=350199

--- Comment #5 from Leon  ---
Created attachment 100623
  --> https://bugs.kde.org/attachment.cgi?id=100623=edit
Drive listing as from gnome disk utility

Details on which device is labelled could be added in brackets, eg:
ADATA
(2Gb Ut165 USB2FlashStorage)

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

[dolphin] [Bug 350199] Cannot handle dual DVD drives with similar labels

2016-08-16 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=350199

--- Comment #4 from Leon  ---
Created attachment 100622
  --> https://bugs.kde.org/attachment.cgi?id=100622=edit
Drives listed on the listing view for example KWrite

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

[dolphin] [Bug 350199] Cannot handle dual DVD drives with similar labels

2016-08-16 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=350199

--- Comment #3 from Leon  ---
Created attachment 100621
  --> https://bugs.kde.org/attachment.cgi?id=100621=edit
Drives listed on the Dolphin panel view

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

[dolphin] [Bug 350199] Cannot handle dual DVD drives with similar labels

2016-08-16 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=350199

--- Comment #2 from Leon  ---
This condition is improved. it handles labels of duplicate values between two
mounted drives much better. For DVDs, if the DVD is released without 'releasing
it' or unmounting it, a duplicate name is created on the view panel when a new
DVD is put in with the same label (or the same DVD is re-inserted). This still
causes a minor confusion in the apper application.

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

[dolphin] [Bug 347899] Places Not retaining Network folders links and cannot resolve routes to hosts

2016-08-16 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=347899

--- Comment #2 from Leon  ---
This behaviour is no longer visible in the F23 release

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

[dolphin] [Bug 347899] Places Not retaining Network folders links and cannot resolve routes to hosts

2016-08-16 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=347899

Leon  changed:

   What|Removed |Added

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

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

[apper] [Bug 318960] Apper Crasher

2016-08-16 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=318960

Leon  changed:

   What|Removed |Added

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

--- Comment #1 from Leon  ---
Seems to be resolved. no longer an issue in F23 release

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

[kio] [Bug 327715] File list loading locks when transferring mutliple files at once

2016-08-16 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=327715

Leon  changed:

   What|Removed |Added

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

--- Comment #3 from Leon  ---
This behaviour is no longer visible in F23 release

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

[plasma4] [Bug 327762] Shutdown, Restart and logout items don't work

2016-08-16 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=327762

Leon  changed:

   What|Removed |Added

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

--- Comment #4 from Leon  ---
Works ok in F23 release

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

[knemo] [Bug 366830] New: Network manager on system tray no longer connects/sees wifi networks after suspend/sleep status

2016-08-16 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=366830

Bug ID: 366830
   Summary: Network manager on system tray no longer connects/sees
wifi networks after suspend/sleep status
   Product: knemo
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jst...@mehercule.net
  Reporter: supp...@bb-services.co.za

When the laptop goes into sleep or suspension power state, the network manager
displays irregular behaviour after the machine is resumed. 

It mostly fails to see wireless networks until machine is rebooted from
scratch. Plugging in an alternate USB wireless device allows connection for
that USB device, but the builtin wireless device fails to function after
"sleep" event until restart.

temporarily initialising services like "service network restart", for example,
does not resolve the condition. 

Reproducible: Always

Steps to Reproduce:
1. On the laptop, suspend the machine to sleep power status
2. Awake the machine
3. Wireless connections fails to restore to workable state

Actual Results:  
Wireless networks is no longer valid, visible or continious error messages pops
up stating connects, and disconnect.

Expected Results:  
Wireless connections available should auto connect.

disabling/re-enabling device does not remedy the condition.

Disclaimer:
* This bug has been reported against the "nearest possible" item that seems
logical. I am not a professional bug reporter. Please do not stone me if the
item has been incorrectly selected. In the case the item should move to a
better or more relevant  section in the KDE system, feel free to move it to
that location at free will. It has been logged as good gesture to point a
possible flaw that may cause an annoyence on other equipment and its fix can
provide a more enjoyable fedora experience and a victory to a goal/challenge
for a programmer who loves programming. thanks.

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

[plasmashell] [Bug 365899] Plasma unexpectedly crashes

2016-07-21 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=365899

--- Comment #2 from Leon  ---
Thank you very much. Unlike some responses from bug fixers in the redhat
community for fedora, this has been a pleasant and informative response.
Appreciate it.

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

[plasmashell] [Bug 365899] New: Plasma unexpectedly crashes

2016-07-20 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=365899

Bug ID: 365899
   Summary: Plasma unexpectedly crashes
   Product: plasmashell
   Version: 5.6.5
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: supp...@bb-services.co.za
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.6.5)

Qt Version: 5.6.1
Frameworks Version: 5.23.0
Operating System: Linux 4.5.7-202.fc23.i686+PAE i686
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
- What I was doing when the application crashed:
clicking on (or to quickly) on the taskbar icons in quick successions seems to
cause crashes

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb1855840 (LWP 2010))]

Thread 7 (Thread 0xb05a0b40 (LWP 2013)):
#0  0x in __libc_enable_asynccancel () at /lib/libc.so.6
#1  0x in poll () at /lib/libc.so.6
#2  0x in g_poll () at /lib/libglib-2.0.so.0
#3  0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#4  0x in g_main_context_iteration () at /lib/libglib-2.0.so.0
#5  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQt5Core.so.5
#6  0x in
QEventLoop::processEvents(QFlags) () at
/lib/libQt5Core.so.5
#7  0x in QEventLoop::exec(QFlags) () at
/lib/libQt5Core.so.5
#8  0x in QThread::exec() () at /lib/libQt5Core.so.5
#9  0x in QDBusConnectionManager::run() () at /lib/libQt5DBus.so.5
#10 0x in QThreadPrivate::start(void*) () at /lib/libQt5Core.so.5
#11 0x in start_thread () at /lib/libpthread.so.0
#12 0x in clone () at /lib/libc.so.6

Thread 6 (Thread 0xaf1f4b40 (LWP 2055)):
#0  0x in __vdso_clock_gettime ()
#1  0x in clock_gettime () at /lib/libc.so.6
#2  0x in qt_gettime() () at /lib/libQt5Core.so.5
#3  0x in QTimerInfoList::updateCurrentTime() () at
/lib/libQt5Core.so.5
#4  0x in QTimerInfoList::timerWait(timespec&) () at
/lib/libQt5Core.so.5
#5  0x in timerSourcePrepareHelper(GTimerSource*, int*) () at
/lib/libQt5Core.so.5
#6  0x in timerSourcePrepare(_GSource*, int*) () at
/lib/libQt5Core.so.5
#7  0x in g_main_context_prepare () at /lib/libglib-2.0.so.0
#8  0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#9  0x in g_main_context_iteration () at /lib/libglib-2.0.so.0
#10 0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQt5Core.so.5
#11 0x in
QEventLoop::processEvents(QFlags) () at
/lib/libQt5Core.so.5
#12 0x in QEventLoop::exec(QFlags) () at
/lib/libQt5Core.so.5
#13 0x in QThread::exec() () at /lib/libQt5Core.so.5
#14 0x in QQmlThreadPrivate::run() () at /lib/sse2/libQt5Qml.so.5
#15 0x in QThreadPrivate::start(void*) () at /lib/libQt5Core.so.5
#16 0x in start_thread () at /lib/libpthread.so.0
#17 0x in clone () at /lib/libc.so.6

Thread 5 (Thread 0xac6efb40 (LWP 2073)):
#0  0x in __kernel_vsyscall ()
#1  0x in poll () at /lib/libc.so.6
#2  0x in g_poll () at /lib/libglib-2.0.so.0
#3  0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#4  0x in g_main_context_iteration () at /lib/libglib-2.0.so.0
#5  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQt5Core.so.5
#6  0x in
QEventLoop::processEvents(QFlags) () at
/lib/libQt5Core.so.5
#7  0x in QEventLoop::exec(QFlags) () at
/lib/libQt5Core.so.5
#8  0x in QThread::exec() () at /lib/libQt5Core.so.5
#9  0x in QQmlThreadPrivate::run() () at /lib/sse2/libQt5Qml.so.5
#10 0x in QThreadPrivate::start(void*) () at /lib/libQt5Core.so.5
#11 0x in start_thread () at /lib/libpthread.so.0
#12 0x in clone () at /lib/libc.so.6

Thread 4 (Thread 0xab466b40 (LWP 2075)):
#0  0x in g_main_context_check () at /lib/libglib-2.0.so.0
#1  0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#2  0x in g_main_context_iteration () at /lib/libglib-2.0.so.0
#3  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQt5Core.so.5
#4  0x in
QEventLoop::processEvents(QFlags) () at
/lib/libQt5Core.so.5
#5  0x in QEventLoop::exec(QFlags) () at
/lib/libQt5Core.so.5
#6  0x in QThread::exec() () at /lib/libQt5Core.so.5
#7  0x in QQmlThreadPrivate::run() () at /lib/sse2/libQt5Qml.so.5
#8  0x in QThreadPrivate::start(void*) () at /lib/libQt5Core.so.5
#9  0x in start_thread () at /lib/libpthread.so.0
#10 0x in clone () at /lib/libc.so.6

Thread 3 (Thread 0xaa361b40 (LWP 2081)):
#0  0x

[kontact] [Bug 359445] Kontact crashes in Korganizer calendar search

2016-07-06 Thread Xabi Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359445

Xabi Leon  changed:

   What|Removed |Added

 CC||xabilonm...@yahoo.fr

--- Comment #2 from Xabi Leon  ---
Same crash here, Korganizer 5.1.3, Plasma 5.6.5, KDE Frameworks 5.23.0 with Qt
5.5.1, on Kubuntu 16.04 with Kubuntu-backports activated.

Starting typing in the Korganizer quicj search field crashes the app.
The search window from the "Modify > Search" menu works.

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

[plasmashell] [Bug 361250] New: Plasma randomly freezes and eventually crashes and restarts

2016-03-31 Thread Santiago de Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=361250

Bug ID: 361250
   Summary: Plasma randomly freezes and eventually crashes and
restarts
   Product: plasmashell
   Version: 5.5.5
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sdeleo...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.5)

Qt Version: 5.5.1
Operating System: Linux 4.1.15-8-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- Unusual behavior I noticed:

This happens to me every day without any particular triggers that I can
identify. The taskbar freezes. I can't click or get mouseover feedback from:
the Pager widget; any of the task widgets at the bottom right of my task
manager; the Application Menu (launcher). Sometimes, actions on the folder
views in my desktop are also disabled.

When the plasma environment is frozen I can still use yakuake or krunner to
fire up programs. I can also switch between windows and Virtual Desktops with
my usual hotkeys.

The programs I have up most of the time are PyCharm, VirtualBox/Vagrant,
Firefox, Chrome, Thunderbird, Slack, the hangouts taskbar widget and Amarok.

This all started when I installed a fresh copy of Leap (I kept my home folder
but overwrote previous OS, which was OpenSUSE 13.2). This random bug is really
wrecking my experience with Leap.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fc805ef37c0 (LWP 2018))]

Thread 6 (Thread 0x7fc7ecd05700 (LWP 2049)):
#0  0x7fc7ff402bbd in poll () at /lib64/libc.so.6
#1  0x7fc7fbae3e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc7fbae3f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc7ffd2dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fc7ffcd4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc7ffaf661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fc802e08df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fc7ffafb32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fc7fec0c0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc7ff40afed in clone () at /lib64/libc.so.6

Thread 5 (Thread 0x7fc7db8f7700 (LWP 2051)):
#0  0x7fc7ff402bbd in poll () at /lib64/libc.so.6
#1  0x7fc7fbae3e64 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc7fbae3f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc7ffd2dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#4  0x7fc7ffcd4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#5  0x7fc7ffaf661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x7fc802e08df8 in  () at /usr/lib64/libQt5Qml.so.5
#7  0x7fc7ffafb32f in  () at /usr/lib64/libQt5Core.so.5
#8  0x7fc7fec0c0a4 in start_thread () at /lib64/libpthread.so.0
#9  0x7fc7ff40afed in clone () at /lib64/libc.so.6

Thread 4 (Thread 0x7fc7da092700 (LWP 2053)):
#0  0x7fc7fbae1254 in  () at /usr/lib64/libglib-2.0.so.0
#1  0x7fc7fbae344b in g_main_context_prepare () at
/usr/lib64/libglib-2.0.so.0
#2  0x7fc7fbae3d80 in  () at /usr/lib64/libglib-2.0.so.0
#3  0x7fc7fbae3f7c in g_main_context_iteration () at
/usr/lib64/libglib-2.0.so.0
#4  0x7fc7ffd2dd8b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#5  0x7fc7ffcd4d53 in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#6  0x7fc7ffaf661a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#7  0x7fc802e08df8 in  () at /usr/lib64/libQt5Qml.so.5
#8  0x7fc7ffafb32f in  () at /usr/lib64/libQt5Core.so.5
#9  0x7fc7fec0c0a4 in start_thread () at /lib64/libpthread.so.0
#10 0x7fc7ff40afed in clone () at /lib64/libc.so.6

Thread 3 (Thread 0x7fc7d3fff700 (LWP 2064)):
#0  0x7fc7fec1003f in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1  0x7fc8055d086b in  () at /usr/lib64/libQt5Script.so.5
#2  0x7fc8055d0899 in  () at /usr/lib64/libQt5Script.so.5
#3  0x7fc7fec0c0a4 in start_thread () at /lib64/libpthread.so.0
#4  0x7fc7ff40afed in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fc7d0ebd700 (LWP 2110)):
#0  0x7fc7fec10e8b in pthread_getspecific () at /lib64/libpthread.so.0
#1  0x7fc7fbb09400 in g_thread_self () at /usr/lib64/libglib-2.0.so.0
#2  0x7fc7fbae2ecc in g_main_context_acquire () at
/usr/lib64/libglib-2.0.so.0
#3  0x7fc7fbae3d25 in  () at /usr/lib64/libglib-2.0.so.0
#4  0x7fc7fbae3f7c in g_main_context_iteration () at

[kalarm] [Bug 336738] time zone is miscalculated by 1 hour or ignored

2016-02-28 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=336738

--- Comment #14 from Leon  ---
Local time: Mon 2016-02-29 08:41:12 SAST
Universal time: Mon 2016-02-29 06:41:12 UTC
RTC time: Mon 2016-02-29 06:41:12
Time zone: Africa/Johannesburg (SAST, +0200)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no

Additional note: since upgrading to F22 from F20, various things stopped
working... like the Akonadi service, so I am unable to test further and confirm
if this condition has been resolved in F22/F23

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

[Baloo] [Bug 359208] continious disk activity from baloo_file_indexer

2016-02-21 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359208

--- Comment #2 from Leon  ---
But disabling search does not solve the problem. It takes away the search
function which I need.

I ran the find utility from root and outputted the listing to a text file. It
took 7 minutes. Therefor I propose the indexer utility cannot or should not
index files longer than 10 minutes.

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

[Baloo] [Bug 359208] New: continious disk activity from baloo_file_indexer

2016-02-09 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=359208

Bug ID: 359208
   Summary: continious disk activity from baloo_file_indexer
   Product: Baloo
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: m...@vhanda.in
  Reporter: supp...@bb-services.co.za
CC: pinak.ah...@gmail.com

The disk of the machine remains active continuously after start or hibernation.
Ending the baloo_file_extractor process rectifies the condition

Reproducible: Always

Steps to Reproduce:
1. Start machine
2. observe disk activity

Actual Results:  
The disk is continuously running

Expected Results:  
Disk activity should not continue without end.

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

[plasmashell] [Bug 357178] New: Crash when copying files

2015-12-26 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=357178

Bug ID: 357178
   Summary: Crash when copying files
   Product: plasmashell
   Version: 5.5.0
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: supp...@bb-services.co.za
CC: bhus...@gmail.com, plasma-b...@kde.org

Application: plasmashell (5.5.0)

Qt Version: 5.5.1
Operating System: Linux 4.2.7-300.fc23.i686+PAE i686
Distribution: "Fedora release 23 (Twenty Three)"

-- Information about the crash:
Copied a single folder from an extern hard drive using drag 'n drop. The copy
process when I clicked on the + button on the information screen to track
progress

-- Backtrace:
Application: Plasma (plasmashell), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xb18a8840 (LWP 2052))]

Thread 12 (Thread 0xb1462b40 (LWP 2059)):
#0  0x in __kernel_vsyscall ()
#1  0x in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x in _xcb_conn_wait () at /lib/libxcb.so.1
#3  0x in xcb_wait_for_event () at /lib/libxcb.so.1
#4  0x in QXcbEventReader::run() () at /lib/libQt5XcbQpa.so.5
#5  0x in QThreadPrivate::start(void*) () at /lib/libQt5Core.so.5
#6  0x in start_thread (arg=0xb1462b40) at pthread_create.c:334
#7  0x in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 11 (Thread 0xaff1eb40 (LWP 2078)):
#0  0x in __kernel_vsyscall ()
#1  0x in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x in g_poll () at /lib/libglib-2.0.so.0
#3  0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#4  0x in g_main_context_iteration () at /lib/libglib-2.0.so.0
#5  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQt5Core.so.5
#6  0x in
QEventLoop::processEvents(QFlags) () at
/lib/libQt5Core.so.5
#7  0x in QEventLoop::exec(QFlags) () at
/lib/libQt5Core.so.5
#8  0x in QThread::exec() () at /lib/libQt5Core.so.5
#9  0x in QQmlThreadPrivate::run() () at /lib/sse2/libQt5Qml.so.5
#10 0x in QThreadPrivate::start(void*) () at /lib/libQt5Core.so.5
#11 0x in start_thread (arg=0xaff1eb40) at pthread_create.c:334
#12 0x in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 10 (Thread 0xad352b40 (LWP 2094)):
#0  0x in __vdso_clock_gettime ()
#1  0x in __GI___clock_gettime (clock_id=1, tp=0xad351ed4) at
../sysdeps/unix/clock_gettime.c:115
#2  0x in qt_gettime() () at /lib/libQt5Core.so.5
#3  0x in QTimerInfoList::updateCurrentTime() () at
/lib/libQt5Core.so.5
#4  0x in QTimerInfoList::timerWait(timespec&) () at
/lib/libQt5Core.so.5
#5  0x in timerSourcePrepare(_GSource*, int*) () at
/lib/libQt5Core.so.5
#6  0x in g_main_context_prepare () at /lib/libglib-2.0.so.0
#7  0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#8  0x in g_main_context_iteration () at /lib/libglib-2.0.so.0
#9  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQt5Core.so.5
#10 0x in
QEventLoop::processEvents(QFlags) () at
/lib/libQt5Core.so.5
#11 0x in QEventLoop::exec(QFlags) () at
/lib/libQt5Core.so.5
#12 0x in QThread::exec() () at /lib/libQt5Core.so.5
#13 0x in QQmlThreadPrivate::run() () at /lib/sse2/libQt5Qml.so.5
#14 0x in QThreadPrivate::start(void*) () at /lib/libQt5Core.so.5
#15 0x in start_thread (arg=0xad352b40) at pthread_create.c:334
#16 0x in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 9 (Thread 0xabfb5b40 (LWP 2095)):
#0  0x in __vdso_clock_gettime ()
#1  0x in __GI___clock_gettime (clock_id=1, tp=0xabfb4ed4) at
../sysdeps/unix/clock_gettime.c:115
#2  0x in qt_gettime() () at /lib/libQt5Core.so.5
#3  0x in QTimerInfoList::updateCurrentTime() () at
/lib/libQt5Core.so.5
#4  0x in QTimerInfoList::timerWait(timespec&) () at
/lib/libQt5Core.so.5
#5  0x in timerSourcePrepare(_GSource*, int*) () at
/lib/libQt5Core.so.5
#6  0x in g_main_context_prepare () at /lib/libglib-2.0.so.0
#7  0x in g_main_context_iterate.isra () at /lib/libglib-2.0.so.0
#8  0x in g_main_context_iteration () at /lib/libglib-2.0.so.0
#9  0x in
QEventDispatcherGlib::processEvents(QFlags) ()
at /lib/libQt5Core.so.5
#10 0x in
QEventLoop::processEvents(QFlags) () at
/lib/libQt5Core.so.5
#11 0x in QEventLoop::exec(QFlags) () at
/lib/libQt5Core.so.5
#12 0x in QThread::exec() () at /lib/libQt5Core.so.5
#13 0x in QQmlThreadPrivate::run() () at /lib/sse2/libQt5Qml.so.5
#14 0x in QThreadPrivate::start(void*) () at

[krusader] [Bug 310722] Tried to open another via krusaders KrViewer while

2015-12-22 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=310722

--- Comment #9 from Leon  ---
Created attachment 96271
  --> https://bugs.kde.org/attachment.cgi?id=96271=edit
New crash information added by DrKonqi

krusader (2.4.0-beta3 "Single Step") on KDE Platform 4.14.14 using Qt 4.8.7

Copying and updates files over an SFTP (SCP) functions.

-- Backtrace (Reduced):
#7  0x in KIO::UDSEntry::count() const (this=0x4004) at
/usr/include/QtCore/qhash.h:475
#8  0x in KIO::UDSEntry::count() const (this=this@entry=0x828412a4) at
../../kio/kio/udsentry.cpp:115
#9  0x in PanelViewerBase::readFileInfo(KUrl const&)
(this=this@entry=0x82841278, url=...) at
../../../krusader/KViewer/panelviewer.cpp:81
#10 0x in PanelEditor::openUrl(KUrl const&, KrViewer::Mode)
(this=this@entry=0x82841278, url=..., mode=mode@entry=KrViewer::Text) at
../../../krusader/KViewer/panelviewer.cpp:335
#11 0x in KrViewer::edit(KUrl, KrViewer::Mode, int, QWidget*) (url=...,
mode=mode@entry=KrViewer::Text, new_window=0, new_window@entry=-1,
parent=parent@entry=0xbfe856f8) at ../../../krusader/KViewer/krviewer.cpp:332

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

[gwenview] [Bug 356566] "move to trash" deletes in full-screen-mode

2015-12-13 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=356566

Leon  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from Leon  ---
ok, seems a little strange: I have looked at the behaviour again today:
- until yesterday I had switched off the confirmation question in Dolphin: "Are
you sure, to move file to trash" (or similar...)
- today I have switched it back on and realized, that the image was moved to
trash only AFTER gwenview was closed.
- then I switched the confirmation question back to "off". But the error was
not reproducible. And even the images are moved to trash straight away (before
closing gwenview!)

Therefore I have set this report to solved...

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

[gwenview] [Bug 356566] New: "move to trash" deletes in full-screen-mode

2015-12-12 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=356566

Bug ID: 356566
   Summary: "move to trash" deletes in full-screen-mode
   Product: gwenview
   Version: Other (add details in bug description)
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: gwenview-bugs-n...@kde.org
  Reporter: l...@fairtragen.de
CC: myr...@kde.org

I view images in full screen mode.
When I press DEL the image should be moved to the trash bin.
Instead it is completely deleted!

It works as expected, when I am not in full screen mode. 

Gwenview version: Version 15.08.2


Reproducible: Always

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

[plasmashell] [Bug 344969] Shortcut configuration for Folder View actions not handled by standard keys

2015-12-04 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=344969

--- Comment #18 from Leon  ---
Hi Leslie,
thanks for the link. I have found FolderView.qml (on my system it was here:
/usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/) and added
the else if clause.

But the file foldermodel.h does not seem to be on my system. 
Without those changes STRG+X and STRG+C do not work.
What should I do now?

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

[kwin] [Bug 356144] New: KWin crashed when switching Tasks with +

2015-11-30 Thread Leon via KDE Bugzilla 
https://bugs.kde.org/show_bug.cgi?id=356144

Bug ID: 356144
   Summary: KWin crashed when switching Tasks with +
   Product: kwin
   Version: 5.4.2
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: l...@fairtragen.de

Application: kwin_x11 (5.4.2)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-18-generic i686
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
I was using Konsole and wanted to switch to different program with the
+ and KWin crashed. 

This could be a duplicate of Bug 349174.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb16757c0 (LWP 8635))]

Thread 4 (Thread 0xaefafb40 (LWP 8653)):
#0  0xb776e946 in __vdso_clock_gettime ()
#1  0xb7675740 in __GI___clock_gettime (clock_id=1, tp=0xaefaf064) at
../sysdeps/unix/clock_gettime.c:115
#2  0xb61cb378 in qt_clock_gettime (ts=0xaefaf064, clock=) at
tools/qelapsedtimer_unix.cpp:105
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:161
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:170
#5  0xb635b0a2 in QTimerInfoList::updateCurrentTime (this=0xae600af0) at
kernel/qtimerinfo_unix.cpp:84
#6  0xb635b5b4 in QTimerInfoList::timerWait (this=0xae600af0, tm=...) at
kernel/qtimerinfo_unix.cpp:379
#7  0xb635aba4 in QEventDispatcherUNIX::processEvents (this=0xae600468,
flags=...) at kernel/qeventdispatcher_unix.cpp:594
#8  0xb63002b3 in QEventLoop::processEvents (this=0xaefaf214, flags=...) at
kernel/qeventloop.cpp:128
#9  0xb6300702 in QEventLoop::exec (this=0xaefaf214, flags=...) at
kernel/qeventloop.cpp:204
#10 0xb612923d in QThread::exec (this=0x9bfa620) at thread/qthread.cpp:503
#11 0xb4f443bf in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
#12 0xb612e65b in QThreadPrivate::start (arg=0x9bfa620) at
thread/qthread_unix.cpp:337
#13 0xb725d1aa in start_thread (arg=0xaefafb40) at pthread_create.c:333
#14 0xb7667fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 3 (Thread 0xaddffb40 (LWP 8656)):
#0  0xb776ebe8 in __kernel_vsyscall ()
#1  0xb726225c in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187
#2  0xb7674cf6 in __pthread_cond_wait (cond=0xb5dba8d0, mutex=0xb5dba8b8) at
forward.c:149
#3  0xb5c822fc in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5
#4  0xb5c8233c in ?? () from /usr/lib/i386-linux-gnu/libQt5Script.so.5
#5  0xb725d1aa in start_thread (arg=0xaddffb40) at pthread_create.c:333
#6  0xb7667fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 2 (Thread 0xafa3bb40 (LWP 8918)):
#0  0xb776e946 in __vdso_clock_gettime ()
#1  0xb7675740 in __GI___clock_gettime (clock_id=1, tp=0xafa3afb4) at
../sysdeps/unix/clock_gettime.c:115
#2  0xb61cb378 in qt_clock_gettime (ts=0xafa3afb4, clock=) at
tools/qelapsedtimer_unix.cpp:105
#3  do_gettime (frac=, sec=) at
tools/qelapsedtimer_unix.cpp:161
#4  qt_gettime () at tools/qelapsedtimer_unix.cpp:170
#5  0xb635b0a2 in QTimerInfoList::updateCurrentTime (this=0xaf100af0) at
kernel/qtimerinfo_unix.cpp:84
#6  0xb635a656 in QEventDispatcherUNIXPrivate::doSelect (this=0xaf100478,
flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:171
#7  0xb635abd6 in QEventDispatcherUNIX::processEvents (this=0xaf100468,
flags=...) at kernel/qeventdispatcher_unix.cpp:607
#8  0xb63002b3 in QEventLoop::processEvents (this=0xafa3b214, flags=...) at
kernel/qeventloop.cpp:128
#9  0xb6300702 in QEventLoop::exec (this=0xafa3b214, flags=...) at
kernel/qeventloop.cpp:204
#10 0xb612923d in QThread::exec (this=0x9be4f18) at thread/qthread.cpp:503
#11 0xb4f443bf in ?? () from /usr/lib/i386-linux-gnu/libQt5Qml.so.5
#12 0xb612e65b in QThreadPrivate::start (arg=0x9be4f18) at
thread/qthread_unix.cpp:337
#13 0xb725d1aa in start_thread (arg=0xafa3bb40) at pthread_create.c:333
#14 0xb7667fde in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:122

Thread 1 (Thread 0xb16757c0 (LWP 8635)):
[KCrash Handler]
#7  0xb6641de4 in QScreen::handle (this=0x0) at kernel/qscreen.cpp:85
#8  0xb12ad681 in QXcbWindow::QXcbWindow (this=0xd3e7cd8, window=0xb5584a8) at
qxcbwindow.cpp:260
#9  0xb1298c65 in QXcbIntegration::createPlatformWindow (this=0x9a78ce8,
window=0xb5584a8) at qxcbintegration.cpp:194
#10 0xb661c885 in QWindowPrivate::create (this=0xb186ff0, recursive=false) at
kernel/qwindow.cpp:395
#11 0xb661caad in QWindow::create (this=0xb5584a8) at kernel/qwindow.cpp:546
#12 0xb661ccd9 in QWindow::winId (this=0xb5584a8) at kernel/qwindow.cpp:565
#13 0xa83e5723 in PlasmaQuick::DialogPrivate::updateInputShape (this=0xb39e118)
at ../../../src/plasmaquick/dialog.cpp:544
#14