[ksmserver] [Bug 398199] New: /usr/lib/ksmserver-logout-greeter crashed

2018-09-03 Thread kts
https://bugs.kde.org/show_bug.cgi?id=398199

Bug ID: 398199
   Summary: /usr/lib/ksmserver-logout-greeter crashed
   Product: ksmserver
   Version: 5.13.4
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

Created attachment 114756
  --> https://bugs.kde.org/attachment.cgi?id=114756&action=edit
ksm

see the attachment.

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

[systemsettings] [Bug 397171] New: systemsetting > Printers : Print service unavailable \n bad file descriptor

2018-08-05 Thread kts
https://bugs.kde.org/show_bug.cgi?id=397171

Bug ID: 397171
   Summary: systemsetting > Printers : Print service unavailable
\n bad file descriptor
   Product: systemsettings
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

Created attachment 114300
  --> https://bugs.kde.org/attachment.cgi?id=114300&action=edit
bad file descriptor

it's 5.13.4.

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

[Akonadi] [Bug 394279] /usr/bin/akonadi_indexing_agent coredumps twice

2018-06-21 Thread kts
https://bugs.kde.org/show_bug.cgi?id=394279

kts  changed:

   What|Removed |Added

Version|unspecified |5.8.2

--- Comment #2 from kts  ---
It's kmail 18.04.2.
It's still crashing.
Give some attention.

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

[Touchpad-KCM] [Bug 395348] [Libinput backend] enable/disable touchpad setting is gray out and unavailable since plasma 5.13

2018-06-15 Thread kts
https://bugs.kde.org/show_bug.cgi?id=395348

--- Comment #12 from kts  ---
Love to hear that. Thank you! I always love KDE.

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

[systemsettings] [Bug 395348] enable/disable touchpad setting is gray out and unavailable since plasma 5.13

2018-06-15 Thread kts
https://bugs.kde.org/show_bug.cgi?id=395348

--- Comment #10 from kts  ---
Created attachment 113348
  --> https://bugs.kde.org/attachment.cgi?id=113348&action=edit
input 7

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

[systemsettings] [Bug 395348] enable/disable touchpad setting is gray out and unavailable since plasma 5.13

2018-06-15 Thread kts
https://bugs.kde.org/show_bug.cgi?id=395348

--- Comment #9 from kts  ---
Created attachment 113347
  --> https://bugs.kde.org/attachment.cgi?id=113347&action=edit
input 6

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

[systemsettings] [Bug 395348] enable/disable touchpad setting is gray out and unavailable since plasma 5.13

2018-06-15 Thread kts
https://bugs.kde.org/show_bug.cgi?id=395348

--- Comment #7 from kts  ---
Created attachment 113345
  --> https://bugs.kde.org/attachment.cgi?id=113345&action=edit
input 4

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

[systemsettings] [Bug 395348] enable/disable touchpad setting is gray out and unavailable since plasma 5.13

2018-06-15 Thread kts
https://bugs.kde.org/show_bug.cgi?id=395348

--- Comment #8 from kts  ---
Created attachment 113346
  --> https://bugs.kde.org/attachment.cgi?id=113346&action=edit
input 5

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

[systemsettings] [Bug 395348] enable/disable touchpad setting is gray out and unavailable since plasma 5.13

2018-06-15 Thread kts
https://bugs.kde.org/show_bug.cgi?id=395348

--- Comment #6 from kts  ---
Created attachment 113344
  --> https://bugs.kde.org/attachment.cgi?id=113344&action=edit
input 3

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

[systemsettings] [Bug 395348] enable/disable touchpad setting is gray out and unavailable since plasma 5.13

2018-06-15 Thread kts
https://bugs.kde.org/show_bug.cgi?id=395348

--- Comment #4 from kts  ---
Created attachment 113342
  --> https://bugs.kde.org/attachment.cgi?id=113342&action=edit
input 1

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

[systemsettings] [Bug 395348] enable/disable touchpad setting is gray out and unavailable since plasma 5.13

2018-06-15 Thread kts
https://bugs.kde.org/show_bug.cgi?id=395348

--- Comment #5 from kts  ---
Created attachment 113343
  --> https://bugs.kde.org/attachment.cgi?id=113343&action=edit
input 2

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

[systemsettings] [Bug 395348] enable/disable touchpad setting is gray out and unavailable since plasma 5.13

2018-06-14 Thread kts
https://bugs.kde.org/show_bug.cgi?id=395348

--- Comment #2 from kts  ---
Yes, it's libinput. Some are not grayed out but most are.

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

[systemsettings] [Bug 395348] New: enable/disable touchpad setting is gray out and unavailable since plasma 5.13

2018-06-14 Thread kts
https://bugs.kde.org/show_bug.cgi?id=395348

Bug ID: 395348
   Summary: enable/disable touchpad setting is gray out and
unavailable since plasma 5.13
   Product: systemsettings
   Version: 5.13.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

Created attachment 113299
  --> https://bugs.kde.org/attachment.cgi?id=113299&action=edit
input

Look at the attachment.

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

[Akonadi] [Bug 394279] /usr/bin/akonadi_indexing_agent coredumps twice

2018-05-16 Thread kts
https://bugs.kde.org/show_bug.cgi?id=394279

--- Comment #1 from kts  ---
Created attachment 112683
  --> https://bugs.kde.org/attachment.cgi?id=112683&action=edit
coredump logs

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

[Akonadi] [Bug 394279] New: /usr/bin/akonadi_indexing_agent coredumps twice

2018-05-15 Thread kts
https://bugs.kde.org/show_bug.cgi?id=394279

Bug ID: 394279
   Summary: /usr/bin/akonadi_indexing_agent coredumps twice
   Product: Akonadi
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Indexer
  Assignee: kdepim-b...@kde.org
  Reporter: jeckfer...@gmail.com
CC: chrig...@fastmail.fm, dvra...@kde.org
  Target Milestone: ---

kmail 18.04.1
qt 5.10.1
plasmaframework 5.46
plasma 5.12.5

The coredump log is as follow:
   PID: 845 (akonadi_indexin)
   UID: 1000 (kts)
   GID: 1000 (kts)
Signal: 4 (ILL)
 Timestamp: Tue 2018-05-15 14:25:55 +0630 (6h ago)
  Command Line: /usr/bin/akonadi_indexing_agent --identifier
akonadi_indexing_agent
Executable: /usr/bin/akonadi_indexing_agent
 Control Group: /user.slice/user-1000.slice/session-c2.scope
  Unit: session-c2.scope
 Slice: user-1000.slice
   Session: c2
 Owner UID: 1000 (kts)
   Boot ID: 43a22672bf5445ca8af826e0fc037bf7
Machine ID: b623200976654e82b4d9ebb79566209a
  Hostname: hdd1
   Storage:
/var/lib/systemd/coredump/core.akonadi_indexin.1000.43a22672bf5445ca8af826e0fc037bf7.845.152637095500.lz4
   Message: Process 845 (akonadi_indexin) of user 1000 dumped core.

Stack trace of thread 859:
#0  0x7f75cc3f2fa0 _ZN9QListData11shared_nullE
(libQt5Core.so.5)
#1  0x7f75cd5defec
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5)
#2  0x7f75cd5e69c6
_ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5)
#3  0x7f75cc33fce0
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
#4  0x7f75cc39b678 _ZN14QTimerInfoList14activateTimersEv
(libQt5Core.so.5)
#5  0x7f75cc39be72 n/a (libQt5Core.so.5)
#6  0x7f75c6916368 g_main_context_dispatch
(libglib-2.0.so.0)
#7  0x7f75c69165b1 n/a (libglib-2.0.so.0)
#8  0x7f75c691663e g_main_context_iteration
(libglib-2.0.so.0)
#9  0x7f75cc39c231
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
#10 0x7f75cc33e31b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#11 0x7f75cc14d71e _ZN7QThread4execEv (libQt5Core.so.5)
#12 0x7f75cc152abd n/a (libQt5Core.so.5)
#13 0x7f75c8723075 start_thread (libpthread.so.0)
#14 0x7f75cb83e53f __clone (libc.so.6)

Stack trace of thread 854:
#0  0x7f75cb833ea9 __poll (libc.so.6)
#1  0x7f75c050e180 n/a (libxcb.so.1)
#2  0x7f75c050fe4b xcb_wait_for_event (libxcb.so.1)
#3  0x7f75be74382a n/a (libQt5XcbQpa.so.5)
#4  0x7f75cc152abd n/a (libQt5Core.so.5)
#5  0x7f75c8723075 start_thread (libpthread.so.0)
#6  0x7f75cb83e53f __clone (libc.so.6)

Stack trace of thread 858:
#0  0x7f75cb833ea9 __poll (libc.so.6)
#1  0x7f75c6916523 n/a (libglib-2.0.so.0)
#2  0x7f75c691663e g_main_context_iteration
(libglib-2.0.so.0)
#3  0x7f75cc39c231
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
#4  0x7f75cc33e31b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x7f75cc14d71e _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x7f75cc7bf416 n/a (libQt5DBus.so.5)
#7  0x7f75cc152abd n/a (libQt5Core.so.5)
#8  0x7f75c8723075 start_thread (libpthread.so.0)
#9  0x7f75cb83e53f __clone (libc.so.6)

Stack trace of thread 845:
#0  0x7f75cb82fa07 write (libc.so.6)
#1  0x7f75c695bf8b n/a (libglib-2.0.so.0)
#2  0x7f75cc3436c6
_ZN16QCoreApplication9postEventEP7QObjectP6QEventi (libQt5Core.so.5)
#3  0x7f75cc34bfde
_ZN11QMetaObject16invokeMethodImplEP7QObjectPN9QtPrivate15QSlotObjectBaseEN2Qt14ConnectionTypeEPv
(libQt5Core.so.5)
#4  0x7f75ce2b1c31 n/a (libKF5AkonadiCore.so.5)
#5  0x7f75ce2b1ce9 n/a (libKF5AkonadiCore.so.5)
#6  0x7f75ce2ae5c0 n/a (libKF5AkonadiCore.so.5)
#7  0x7f75cc37072f _ZN11QMetaObject8activateEP7QObjectiiPPv
(libQt5Core.so.5)
#8  0x7f75cc33eb38
_ZN16QCoreApplication11aboutToQuitENS_14QPrivateSignalE (libQt5Core.so.5)
#9  0x7f75cc342f0c

[ksysguard] [Bug 393029] New: ksysguard core dump

2018-04-11 Thread kts
https://bugs.kde.org/show_bug.cgi?id=393029

Bug ID: 393029
   Summary: ksysguard core dump
   Product: ksysguard
   Version: 5.12.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: ksysguard
  Assignee: ksysguard-b...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

PID: 890 (ksysguard)
   UID: 1000 (kts)
   GID: 1000 (kts)
Signal: 11 (SEGV)
 Timestamp: Tue 2018-04-10 20:15:28 +0630 (1 day 17h ago)
  Command Line: /usr/bin/ksysguard
Executable: /usr/bin/ksysguard
 Control Group: /user.slice/user-1000.slice/session-c2.scope
  Unit: session-c2.scope
 Slice: user-1000.slice
   Session: c2
 Owner UID: 1000 (kts)
   Boot ID: 3193d5ef30b24fe4a7728868ad20cbbc
Machine ID: b623200976654e82b4d9ebb79566209a
  Hostname: hdd1
   Storage:
/var/lib/systemd/coredump/core.ksysguard.1000.3193d5ef30b24fe4a7728868ad20cbbc.890.152336792800.lz4
   Message: Process 890 (ksysguard) of user 1000 dumped core.

Stack trace of thread 890:
#0  0x7f412d84950a _ZeqRK7QStringS1_ (libQt5Core.so.5)
#1  0x7f412ed91cf8 _ZN6QLabel7setTextERK7QString
(libQt5Widgets.so.5)
#2  0x7f413254ab57 n/a (libkdeinit5_ksysguard.so)
#3  0x7f41315d895a
_ZN5KSGRD11SensorAgent13processAnswerEPKci (libksgrd.so.7)
#4  0x7f41315dfdc6 n/a (libksgrd.so.7)
#5  0x7f412d9ea73f _ZN11QMetaObject8activateEP7QObjectiiPPv
(libQt5Core.so.5)
#6  0x7f412d93277b
_ZN8QProcess23readyReadStandardOutputENS_14QPrivateSignalE (libQt5Core.so.5)
#7  0x7f412d93949a n/a (libQt5Core.so.5)
#8  0x7f412d939980 n/a (libQt5Core.so.5)
#9  0x7f412d9ea616 _ZN11QMetaObject8activateEP7QObjectiiPPv
(libQt5Core.so.5)
#10 0x7f412d9f6ef9
_ZN15QSocketNotifier9activatedEiNS_14QPrivateSignalE (libQt5Core.so.5)
#11 0x7f412d9f72d4 _ZN15QSocketNotifier5eventEP6QEvent
(libQt5Core.so.5)
#12 0x7f412ec53fec
_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5)
#13 0x7f412ec5b9c6
_ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5)
#14 0x7f412d9b9cf0
_ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5)
#15 0x7f412da16ede n/a (libQt5Core.so.5)
#16 0x7f4124309368 g_main_context_dispatch
(libglib-2.0.so.0)
#17 0x7f41243095b1 n/a (libglib-2.0.so.0)
#18 0x7f412430963e g_main_context_iteration
(libglib-2.0.so.0)
#19 0x7f412da16241
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
#20 0x7f4117fc2482 n/a (libQt5XcbQpa.so.5)
#21 0x7f412d9b832b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#22 0x7f412d9c1728 _ZN16QCoreApplication4execEv
(libQt5Core.so.5)
#23 0x7f413254c893 kdemain (libkdeinit5_ksysguard.so)
#24 0x7f4132142f4a __libc_start_main (libc.so.6)
#25 0x555b1dfd077a _start (ksysguard)

Stack trace of thread 894:
#0  0x7f413220d97b __poll (libc.so.6)
#1  0x7f4124309523 n/a (libglib-2.0.so.0)
#2  0x7f412430963e g_main_context_iteration
(libglib-2.0.so.0)
#3  0x7f412da16241
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
#4  0x7f412d9b832b
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x7f412d7c772e _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x7f412e0cb416 n/a (libQt5DBus.so.5)
#7  0x7f412d7ccacd n/a (libQt5Core.so.5)
#8  0x7f412632d08c start_thread (libpthread.so.0)
#9  0x7f4132217e7f __clone (libc.so.6)

Stack trace of thread 893:
#0  0x7f413220d97b __poll (libc.so.6)
#1  0x7f4126b84180 n/a (libxcb.so.1)
#2  0x7f4126b85e4b xcb_wait_for_event (libxcb.so.1)
#3  0x7f4117f3a82a n/a (libQt5XcbQpa.so.5)
#4  0x7f412d7ccacd n/a (libQt5Core.so.5)
#5  0x7f412632d08c start_thread (libpthread.so.0)
#6  0x7f4132217e7f __clone (libc.so.6)

Stack trace of thread 892:
#0  0x7f4126bd pthread_cond_wait@@GLIBC_2.3.2
(libpthread.so.0)
#1  0x7f412d4495bd __gthread_cond_wait (libstdc++.so.6

[systemsettings] [Bug 393009] systemsettings crashed while searching

2018-04-11 Thread kts
https://bugs.kde.org/show_bug.cgi?id=393009

--- Comment #2 from kts  ---
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f25f11d6800 (LWP 840))]

Thread 8 (Thread 0x7f25b3fff700 (LWP 851)):
#0  0x7f25e67a62f4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f25e675ea39 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f25e675f44e in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f25e675f63e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f25ed559264 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f25ed4fb32b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f25ed30a72e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f25eae58379 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7f25ed30facd in  () at /usr/lib/libQt5Core.so.5
#9  0x7f25e8dc608c in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f25ecc17e7f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f25b8ef5700 (LWP 850)):
#0  0x7f25ecc0d97b in poll () at /usr/lib/libc.so.6
#1  0x7f25e675f523 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f25e675f8e2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#3  0x7f25b9e73348 in  () at /usr/lib/libgio-2.0.so.0
#4  0x7f25e6787a2a in  () at /usr/lib/libglib-2.0.so.0
#5  0x7f25e8dc608c in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f25ecc17e7f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f25b96f6700 (LWP 849)):
#0  0x7f25ecc093d8 in read () at /usr/lib/libc.so.6
#1  0x7f25e67a4ed1 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f25e675eff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f25e675f4c6 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f25e675f63e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f25e675f692 in  () at /usr/lib/libglib-2.0.so.0
#6  0x7f25e6787a2a in  () at /usr/lib/libglib-2.0.so.0
#7  0x7f25e8dc608c in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f25ecc17e7f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f25c2832700 (LWP 846)):
#0  0x7f25ecc0d97b in poll () at /usr/lib/libc.so.6
#1  0x7f25e675f523 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f25e675f63e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f25ed559264 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f25ed4fb32b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f25ed30a72e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f25eae58379 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f25ed30facd in  () at /usr/lib/libQt5Core.so.5
#8  0x7f25e8dc608c in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f25ecc17e7f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f25ca7c2700 (LWP 844)):
#0  0x7f25ecc093d8 in read () at /usr/lib/libc.so.6
#1  0x7f25e67a4ed1 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f25e675eff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f25e675f4c6 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f25e675f63e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f25ed559264 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f25ed4fb32b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f25ed30a72e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f25eae58379 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7f25ed30facd in  () at /usr/lib/libQt5Core.so.5
#10 0x7f25e8dc608c in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f25ecc17e7f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f25d4d37700 (LWP 842)):
#0  0x7f25e67a62f0 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f25e675e3ac in g_main_context_acquire () at
/usr/lib/libglib-2.0.so.0
#2  0x7f25e675f3d7 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f25e675f63e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f25ed559264 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f25ed4fb32b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f25ed30a72e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f25eee76416 in  () at /usr/lib/libQt5DBus.so.5
#8  0x7f25ed30facd in  () at /usr/lib/libQt5Core.so.5
#9  0x7f25e8dc608c in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f25ecc17e7f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f25ddd66700 (LWP 841)):
#0  0x7f25ecc0d97b in poll () at /usr/lib/libc.so.6
#1  0x7f25e8951180 in  () at /usr/lib/libxcb.so.1
#2  0x7f25e8952e4b in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f25e0b1182a in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f25ed30facd in  () a

[systemsettings] [Bug 393009] systemsettings crashed while searching

2018-04-11 Thread kts
https://bugs.kde.org/show_bug.cgi?id=393009

--- Comment #1 from kts  ---
KActivities: Database connection: 
"kactivities_db_resources_139800935753728_readonly" 
query_only:  QVariant(qlonglong, 1) 
journal_mode:QVariant(QString, "wal") 
wal_autocheckpoint:  QVariant(qlonglong, 100) 
synchronous: QVariant(qlonglong, 0)
Nothing to load - the client id is empty
Nothing to load - the client id is empty
checking permissions of  "/usr/share/color-schemes/Breeze.colors"
KActivitiesStats( 0x560d13c0f300 ) ResultModelPrivate::onResultScoreUpdated 
result added: "kcm:colors.desktop" score: 3 last: 1523454870 first: 1523354768
KActivitiesStats( 0x560d13c0f300 ) ResultModelPrivate::onResultScoreUpdated 
result added: "kcm:kwinoptions.desktop" score: 2 last: 1523454883 first:
1523453376
KActivitiesStats( 0x560d13c0f300 ) ResultModelPrivate::onResultScoreUpdated 
result added: "kcm:standard_actions.desktop" score: 2.96923 last: 1523454883
first: 1523354349
KActivitiesStats( 0x560d13c0f300 ) ResultModelPrivate::onResultScoreUpdated 
result added: "kcm:kcm_sddm.desktop" score: 3.63538 last: 1523454885 first:
1522314089
: QML QQuickLayoutAttached: Binding loop detected for property
"minimumHeight"
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = systemsettings5 path = /usr/bin pid = 840
KCrash: Arguments: /usr/bin/systemsettings5 
KCrash: Attempting to start /usr/lib/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0

[1]+  Stopped systemsettings5


The above is observed through terminal.

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

[systemsettings] [Bug 393009] New: systemsettings crashed while searching

2018-04-11 Thread kts
https://bugs.kde.org/show_bug.cgi?id=393009

Bug ID: 393009
   Summary: systemsettings crashed while searching
   Product: systemsettings
   Version: 5.12.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.12.4)

Qt Version: 5.10.1
Frameworks Version: 5.44.0
Operating System: Linux 4.15.15-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Possible regression of earlier resolved bug.
I was just moving around and clicking around. When searching after thus
browsing here and there, it always crashed.
5.12.4 plasma
5.44 framework
5.10.1 qt
17.12.3 application

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f557ae67800 (LWP 855))]

Thread 7 (Thread 0x7f55420e1700 (LWP 873)):
#0  0x7f557689e97b in poll () at /usr/lib/libc.so.6
#1  0x7f55703f0523 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f55703f08e2 in g_main_loop_run () at /usr/lib/libglib-2.0.so.0
#3  0x7f554305f348 in  () at /usr/lib/libgio-2.0.so.0
#4  0x7f5570418a2a in  () at /usr/lib/libglib-2.0.so.0
#5  0x7f5572a5708c in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f55768a8e7f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f55428e2700 (LWP 872)):
#0  0x7f557689e97b in poll () at /usr/lib/libc.so.6
#1  0x7f55703f0523 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f55703f063e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f55703f0692 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f5570418a2a in  () at /usr/lib/libglib-2.0.so.0
#5  0x7f5572a5708c in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f55768a8e7f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f554bfff700 (LWP 861)):
#0  0x7f55703efa05 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7f55703f044e in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f55703f063e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f55771ea264 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f557718c32b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f5576f9b72e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f5574ae9379 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f5576fa0acd in  () at /usr/lib/libQt5Core.so.5
#8  0x7f5572a5708c in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f55768a8e7f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f555430d700 (LWP 860)):
#0  0x7f557689e979 in poll () at /usr/lib/libc.so.6
#1  0x7f55703f0523 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f55703f063e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f55771ea264 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f557718c32b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f5576f9b72e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f5574ae9379 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f5576fa0acd in  () at /usr/lib/libQt5Core.so.5
#8  0x7f5572a5708c in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f55768a8e7f in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f555e974700 (LWP 858)):
#0  0x7f557689a3d8 in read () at /usr/lib/libc.so.6
#1  0x7f5570435ed1 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f55703efff8 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7f55703f04c6 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7f55703f063e in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7f55771ea264 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7f557718c32b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7f5576f9b72e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7f5578b07416 in  () at /usr/lib/libQt5DBus.so.5
#9  0x7f5576fa0acd in  () at /usr/lib/libQt5Core.so.5
#10 0x7f5572a5708c in start_thread () at /usr/lib/libpthread.so.0
#11 0x7f55768a8e7f in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f55679f7700 (LWP 857)):
#0  0x7f557689e97b in poll () at /usr/lib/libc.so.6
#1  0x7f55725e2180 in  () at /usr/lib/libxcb.so.1
#2  0x7f55725e3e4b in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f556a7a282a in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f5576fa0acd in  () at /usr/lib/libQt5Core.so.5
#5  0x7f5572a5708c in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f55768a8e7f in clone () at /usr/lib/libc

[plasmashell] [Bug 391954] application menu on every fresh login, when clicked, switches focus right to "Leave" section instead of "favorite"

2018-03-20 Thread kts
https://bugs.kde.org/show_bug.cgi?id=391954

--- Comment #4 from kts  ---
Thanks for the confirmation.

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

[plasmashell] [Bug 391954] application menu on every fresh login, when clicked, switches focus right to "Leave" section instead of "favorite"

2018-03-19 Thread kts
https://bugs.kde.org/show_bug.cgi?id=391954

kts  changed:

   What|Removed |Added

   Target Milestone|--- |1.0
   Assignee|notm...@gmail.com   |k...@davidedmundson.co.uk
 CC||plasma-b...@kde.org
  Component|components  |Application Launcher
   ||(Kickoff)
Version|5.44.0  |5.12.3
Product|frameworks-plasma   |plasmashell

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

[frameworks-plasma] [Bug 391954] application menu on every fresh login, when clicked, switches focus right to "Leave" section instead of "favorite"

2018-03-18 Thread kts
https://bugs.kde.org/show_bug.cgi?id=391954

--- Comment #1 from kts  ---
Hello! Does anybody experiencing this bug in 5.44? I was experiencing.

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

[kde] [Bug 391944] konqueror crash on plasmashell start-up

2018-03-17 Thread kts
https://bugs.kde.org/show_bug.cgi?id=391944

kts  changed:

   What|Removed |Added

 CC||jeckfer...@gmail.com

--- Comment #1 from kts  ---
I observe the same behavior but I didn't try to report it last couple of months
because I don't use konqueror. Fresh start is OK. Fresh start konqueror, exit
it, restart the computer, on next login it poped up and more often than not,
crashing.

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

[plasmashell] [Bug 343684] kicker switches to "leave" menu when opening when it should not

2018-03-17 Thread kts
https://bugs.kde.org/show_bug.cgi?id=343684

kts  changed:

   What|Removed |Added

 CC||jeckfer...@gmail.com

--- Comment #2 from kts  ---
It's happening again with 5.44.

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

[frameworks-plasma] [Bug 391954] New: application menu on every fresh login, when clicked, switches focus right to "Leave" section instead of "favorite"

2018-03-17 Thread kts
https://bugs.kde.org/show_bug.cgi?id=391954

Bug ID: 391954
   Summary: application menu on every fresh login, when clicked,
switches focus right to "Leave" section instead of
"favorite"
   Product: frameworks-plasma
   Version: 5.44.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: components
  Assignee: notm...@gmail.com
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

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

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

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

2018-03-17 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388287

--- Comment #13 from kts  ---
It dumped core again with 5.12.12 or 5.12.13, I'm not sure as to which because
it happened after update to 5.12.13. The result is same. No crash or
interference just core dump. killall kactivitymanagered and kactivitymanagered
--start-daemon worked smoothly because the crash is intermittent and normally
it's fine only occasionally it manifests. Below is the coredumpctl backtrace:
   PID: 578 (kactivitymanage)
   UID: 1000 (kts)
   GID: 1000 (kts)
Signal: 11 (SEGV)
 Timestamp: Mon 2018-03-12 19:10:29 +0630 (4 days ago)
  Command Line: /usr/bin/kactivitymanagerd start-daemon
Executable: /usr/bin/kactivitymanagerd
 Control Group: /user.slice/user-1000.slice/user@1000.service/dbus.service
  Unit: user@1000.service
 User Unit: dbus.service
 Slice: user-1000.slice
 Owner UID: 1000 (kts)
   Boot ID: eaeb0848f43043d4a6cf26bb262bddc1
Machine ID: b623200976654e82b4d9ebb79566209a
  Hostname: hdd1
   Storage:
/var/lib/systemd/coredump/core.kactivitymanage.1000.eaeb0848f43043d4a6cf26bb262bddc1.578.152085842900.lz4
(inaccessible)
   Message: Process 578 (kactivitymanage) of user 1000 dumped core.

Stack trace of thread 826:
#0  0x7f89fdc4eadc sqlite3DbMallocRawNN (libsqlite3.so.0)
#1  0x7f89fdc8ac95 sqlite3VdbeMemGrow (libsqlite3.so.0)
#2  0x7f89fdc7cfe7 n/a (libsqlite3.so.0)
#3  0x7f89fdc7d8a0 sqlite3VdbeExec (libsqlite3.so.0)
#4  0x7f89fdc84550 sqlite3_step (libsqlite3.so.0)
#5  0x7f89fdee2abe n/a (libqsqlite.so)
#6  0x7f89fdee4333 n/a (libqsqlite.so)
#7  0x7f8a140f7938 _ZN9QSqlQuery4execEv (libQt5Sql.so.5)
#8  0x7f8a14373e26 n/a (kactivitymanagerd_plugin_sqlite.so)
#9  0x7f8a14377c0f n/a (kactivitymanagerd_plugin_sqlite.so)
#10 0x7f8a21bb0b4d n/a (libQt5Core.so.5)
#11 0x7f8a2083c08c start_thread (libpthread.so.0)
#12 0x7f8a214b8e7f __clone (libc.so.6)

Stack trace of thread 586:
#0  0x7f8a214ae97b __poll (libc.so.6)
#1  0x7f8a1e2bfff3 n/a (libglib-2.0.so.0)
#2  0x7f8a1e2c010e g_main_context_iteration
(libglib-2.0.so.0)
#3  0x7f8a21dfa2f1
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
#4  0x7f8a21d9c3db
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x7f8a21bab7ae _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x560eeb4a15db n/a (kactivitymanagerd)
#7  0x7f8a21bb0b4d n/a (libQt5Core.so.5)
#8  0x7f8a2083c08c start_thread (libpthread.so.0)
#9  0x7f8a214b8e7f __clone (libc.so.6)

Stack trace of thread 581:
#0  0x7f8a214ae97b __poll (libc.so.6)
#1  0x7f8a1e2bfff3 n/a (libglib-2.0.so.0)
#2  0x7f8a1e2c010e g_main_context_iteration
(libglib-2.0.so.0)
#3  0x7f8a21dfa2f1
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
#4  0x7f8a21d9c3db
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x7f8a21bab7ae _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x7f8a2271e416 n/a (libQt5DBus.so.5)
#7  0x7f8a21bb0b4d n/a (libQt5Core.so.5)
#8  0x7f8a2083c08c start_thread (libpthread.so.0)
#9  0x7f8a214b8e7f __clone (libc.so.6)

Stack trace of thread 580:
#0  0x7f8a214ae97b __poll (libc.so.6)
#1  0x7f8a20c62180 n/a (libxcb.so.1)
#2  0x7f8a20c63e4b xcb_wait_for_event (libxcb.so.1)
#3  0x7f8a1a1b182a n/a (libQt5XcbQpa.so.5)
#4  0x7f8a21bb0b4d n/a (libQt5Core.so.5)
#5  0x7f8a2083c08c start_thread (libpthread.so.0)
#6  0x7f8a214b8e7f __clone (libc.so.6)

Stack trace of thread 583:
#0  0x7f8a214ae97b __poll (libc.so.6)
#1  0x7f8a1e2bfff3 n/a (libglib-2.0.so.0)
#2  0x7f8a1e2c010e g_main_context_iteration
(libglib-2.0.so.0)
#3  0x7f8a21dfa2f1
_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
(libQt5Core.so.5)
#4  0x7f8a21d9c3db
_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5)
#5  0x7f8a21bab7ae _ZN7QThread4execEv (libQt5Core.so.5)
#6  0x560eeb4a15ab n/a (kactivi

[Discover] [Bug 390427] Unknown Open Collaboration Service API error when clicking on addons in Discover

2018-03-07 Thread kts
https://bugs.kde.org/show_bug.cgi?id=390427

--- Comment #7 from kts  ---
Created attachment 111243
  --> https://bugs.kde.org/attachment.cgi?id=111243&action=edit
notification error 2

Another one. I have many notification errors before 5.12.3 concerning
.knsc.
Now with 5.12.3, I have still a few of those left which I provided in these two
attachments.

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

[Discover] [Bug 390427] Unknown Open Collaboration Service API error when clicking on addons in Discover

2018-03-07 Thread kts
https://bugs.kde.org/show_bug.cgi?id=390427

kts  changed:

   What|Removed |Added

 CC||jeckfer...@gmail.com

--- Comment #6 from kts  ---
Created attachment 111242
  --> https://bugs.kde.org/attachment.cgi?id=111242&action=edit
notification error

Not sure whether it's related but I also have many notification errors
involving knsrc so I'll just leave the attachment here for verification.

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

[dolphin] [Bug 391386] Fake "The device is already mounted" warning

2018-03-05 Thread kts
https://bugs.kde.org/show_bug.cgi?id=391386

kts  changed:

   What|Removed |Added

 CC||jeckfer...@gmail.com

--- Comment #1 from kts  ---
I observed this bug in Arch Linux 17.12.2 (latest dolphin).
The workaround is to mount them from tray removable icon.

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

[konsole] [Bug 390666] ranger file manager doesn't accept in konsole

2018-02-18 Thread kts
https://bugs.kde.org/show_bug.cgi?id=390666

kts  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

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

[konsole] [Bug 390666] New: ranger file manager doesn't accept in konsole

2018-02-17 Thread kts
https://bugs.kde.org/show_bug.cgi?id=390666

Bug ID: 390666
   Summary: ranger file manager doesn't accept  in konsole
   Product: konsole
   Version: 17.12.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

I was using ranger file manager in konsole. I can't use the  shortcut
which is the ranger key binding to show hidden files. I can use other
combination of ctrl command for ranger. I check shortcut in setting and Ctrl+h
is unused in everywhere.
I test it with xterm terminal emulator. It is still unusable in xterm.
So it might not be specific to konsole, i don't know.
I use  fine in tty with nothing but bare tty, no de, no wm.
I do not understand why KDE is suppressing  in ranger in konsole.
I press  in Firefox in which it trigger show history tab. In Firefox,
it is fine. It bugged me.

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

[systemsettings] [Bug 390005] crash during search

2018-02-12 Thread kts
https://bugs.kde.org/show_bug.cgi?id=390005

kts  changed:

   What|Removed |Added

 CC||jeckfer...@gmail.com

--- Comment #6 from kts  ---
I observed this bug yesterday with plasma 5.12, framework 5.42 and qt 5.10.

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

[okular] [Bug 388288] some thumbnail of pdf not shown in dolphin, some are shown

2018-02-10 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388288

--- Comment #13 from kts  ---
Done sending it.

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

[okular] [Bug 388288] some thumbnail of pdf not shown in dolphin, some are shown

2018-02-08 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388288

--- Comment #11 from kts  ---
The attachment provided showed thumbnail with latest KDE. But some other PDFs
did not. I want to email the attachment to someone responsible because it's
above 4MB. Who in this list should I sent it to?

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

[okular] [Bug 388288] some thumbnail of pdf not shown in dolphin, some are shown

2018-01-10 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388288

--- Comment #7 from kts  ---
With the file in attachment, you can test that there's no thumbnail. There
should be but there's not. What's at false here? Dolphin?

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

[okular] [Bug 388288] some thumbnail of pdf not shown in dolphin, some are shown

2018-01-09 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388288

--- Comment #5 from kts  ---
I've already provided the file in question. Which additional info do you need?

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

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

2018-01-09 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388287

--- Comment #11 from kts  ---
Works for whom? With what version?

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

[plasma-pa] [Bug 388480] New: There are two volume control applet: kmix and plasma-pa

2018-01-02 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388480

Bug ID: 388480
   Summary: There are two volume control applet: kmix and
plasma-pa
   Product: plasma-pa
   Version: 5.11.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: applet
  Assignee: now...@gmail.com
  Reporter: jeckfer...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

There happen to be two applet controlling audio volume. One should be
discarded.

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

[plasma-pa] [Bug 388480] There are two volume control applet: kmix and plasma-pa

2018-01-02 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388480

--- Comment #1 from kts  ---
Which is official?

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

[okular] [Bug 388288] some thumbnail of pdf not shown in dolphin, some are shown

2018-01-02 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388288

--- Comment #4 from kts  ---
Created attachment 109642
  --> https://bugs.kde.org/attachment.cgi?id=109642&action=edit
Fail to show thumbnail in dolphin

There are many PDFs that fail to show thumbnails. I've selected one of them
that's small.

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

[okular] [Bug 388288] some thumbnail of pdf not shown in dolphin, some are shown

2018-01-02 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388288

--- Comment #3 from kts  ---
ok, I'll email you the file.

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

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

2018-01-02 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388287

--- Comment #7 from kts  ---
Just right now, I encountered this bug. I was watching a movie in full screen
and when I switch back to normal screen, every application has void of title
bars, unresponsive, and can't be closed. Every animation is gone. I still have
access to start menu and log out and back in. No dr. konqi. Coredumpctl show it
is /bin/kactivitymanagered.

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

[okular] [Bug 388175] core dump while opening a specific PDF document

2017-12-29 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388175

--- Comment #2 from kts  ---
It's above 4mb. To where do i need to upload?

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

[kactivitymanagerd] [Bug 388287] coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

2017-12-29 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388287

--- Comment #2 from kts  ---
I have .lz4 core files. There's no crashes just coredumpctl things.

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

[okular] [Bug 388288] New: some thumbnail of pdf not shown in dolphin, some are shown

2017-12-28 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388288

Bug ID: 388288
   Summary: some thumbnail of pdf not shown in dolphin, some are
shown
   Product: okular
   Version: 1.3.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

I've been seeing this problem since kde plasma 4. Continue seeing it in plasma
5.
I did not take time to report it until now. Now that it'd been reported.

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

[kactivitymanagerd] [Bug 388287] New: coredumpctl confirms /bin/kactivitymanagerd dumps core, everything worked fine

2017-12-28 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388287

Bug ID: 388287
   Summary: coredumpctl confirms /bin/kactivitymanagerd dumps
core, everything worked fine
   Product: kactivitymanagerd
   Version: 5.11.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: ivan.cu...@kde.org
  Reporter: jeckfer...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

It dumps core as in coredumpctl. No crash happened. I've seen the behaviors
before it dumps core albeit every processes work flawlessly. It'd be good I can
be instructed to hunt this happening.

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

[okular] [Bug 388175] New: core dump while opening a specific PDF document

2017-12-23 Thread kts
https://bugs.kde.org/show_bug.cgi?id=388175

Bug ID: 388175
   Summary: core dump while opening a specific PDF document
   Product: okular
   Version: 1.3.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

Okular dumps core with a PDF document. It didn't crash. It keep working
normally.
But coredumpctl says otherwise. The system is with the latest updates as of
this writing. I would send that specified PDF but how? Ask me more.

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

[konqueror] [Bug 385750] It crashes on start

2017-11-25 Thread kts
https://bugs.kde.org/show_bug.cgi?id=385750

kts  changed:

   What|Removed |Added

 CC||jeckfer...@gmail.com

--- Comment #1 from kts  ---
I observed the same behavior. I open Konqueror and use it just fine. But on the
next login, it crashes the kdeinit5 with a dialog saying something related.
coredumpctl confirmed the situation.

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

[systemsettings] [Bug 386009] [search box] Entering into it "gl" for (global) suddenly close(=crashed) the whole of it without showing back trace; coredumpctl confirmed it crashed

2017-10-30 Thread kts
https://bugs.kde.org/show_bug.cgi?id=386009

kts  changed:

   What|Removed |Added

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

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

[kmail2] [Bug 255104] KMail fails to start with: Could not create collection

2017-10-28 Thread kts
https://bugs.kde.org/show_bug.cgi?id=255104

--- Comment #22 from kts  ---
Comment on attachment 108604
  --> https://bugs.kde.org/attachment.cgi?id=108604
a

I'm getting this bug for 2 months now. Everything is latest as of today, in
arch.

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

[kmail2] [Bug 255104] KMail fails to start with: Could not create collection

2017-10-28 Thread kts
https://bugs.kde.org/show_bug.cgi?id=255104

kts  changed:

   What|Removed |Added

 CC||jeckfer...@gmail.com

--- Comment #21 from kts  ---
Created attachment 108604
  --> https://bugs.kde.org/attachment.cgi?id=108604&action=edit
a

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

[systemsettings] [Bug 386009] New: [search box] Entering into it "gl" for (global) suddenly close(=crashed) the whole of it without showing back trace; coredumpctl confirmed it crashed

2017-10-20 Thread kts
https://bugs.kde.org/show_bug.cgi?id=386009

Bug ID: 386009
   Summary: [search box] Entering into it "gl" for (global)
suddenly close(=crashed) the whole of it without
showing back trace; coredumpctl confirmed it crashed
   Product: systemsettings
   Version: 5.11.1
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

I was gonna search "global menu" and typing "gl" into search box of
systemsetting quit and crashed it instantaneously but without the ability to
report it through dr. konqi because it does not trigger dr. konqi. Coredumpctl
had confirmed.

I was on intel HD graphic and latest of plasma.

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

[kwin] [Bug 385641] New: [intel]desktop effects were restarted due to a graphics reset

2017-10-12 Thread kts
https://bugs.kde.org/show_bug.cgi?id=385641

Bug ID: 385641
   Summary: [intel]desktop effects were restarted due to a
graphics reset
   Product: kwin
   Version: 5.11.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

I get the above error. Effects were ok afterward.
Intel graphic
plasma 5.11
archlinux
Is that the regression? I saw the same error in this forum before.

The below is my post on the same problem in kde forums.
https://forum.kde.org/viewtopic.php?f=111&t=142454

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

[kwin] [Bug 385495] kwin crashed at startup

2017-10-09 Thread kts
https://bugs.kde.org/show_bug.cgi?id=385495

--- Comment #2 from kts  ---
dr konqi give it three star meaning useful.

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

[kwin] [Bug 385495] New: kwin crashed at startup

2017-10-08 Thread kts
https://bugs.kde.org/show_bug.cgi?id=385495

Bug ID: 385495
   Summary: kwin crashed at startup
   Product: kwin
   Version: 5.10.5
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

Application: kwin_x11 (5.10.5)

Qt Version: 5.9.1
Frameworks Version: 5.38.0
Operating System: Linux 4.13.4-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I just login in the computer and I am greeted with Kwin had crashed.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f288cf5c840 (LWP 665))]

Thread 4 (Thread 0x7f286adee700 (LWP 779)):
#0  0x7f2889ef62c5 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#1  0x7f2889e9cfdb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#2  0x7f2889cb63ee in QThread::exec() () at /usr/lib/libQt5Core.so.5
#3  0x7f288458a3d9 in  () at /usr/lib/libQt5Qml.so.5
#4  0x7f2889cbb13b in  () at /usr/lib/libQt5Core.so.5
#5  0x7f2885a8c08a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f288c8e01bf in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f2871912700 (LWP 727)):
#0  0x7f288c8d5db6 in ppoll () at /usr/lib/libc.so.6
#1  0x7f2889ef4b83 in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt5Core.so.5
#2  0x7f2889ef631f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#3  0x7f2889e9cfdb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#4  0x7f2889cb63ee in QThread::exec() () at /usr/lib/libQt5Core.so.5
#5  0x7f288372c376 in  () at /usr/lib/libQt5DBus.so.5
#6  0x7f2889cbb13b in  () at /usr/lib/libQt5Core.so.5
#7  0x7f2885a8c08a in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f288c8e01bf in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f2873a86700 (LWP 726)):
#0  0x7f288c8d5cbb in poll () at /usr/lib/libc.so.6
#1  0x7f288b9b98e0 in  () at /usr/lib/libxcb.so.1
#2  0x7f288b9bb679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f2874b6674a in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f2889cbb13b in  () at /usr/lib/libQt5Core.so.5
#5  0x7f2885a8c08a in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f288c8e01bf in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f288cf5c840 (LWP 665)):
[KCrash Handler]
#5  0x7f2889d4fb12 in QtPrivate::QStringList_contains(QStringList const*,
QString const&, Qt::CaseSensitivity) () at /usr/lib/libQt5Core.so.5
#6  0x7f2883735461 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f288373ed15 in  () at /usr/lib/libQt5DBus.so.5
#8  0x7f288372d0a9 in QDBusConnection::asyncCall(QDBusMessage const&, int)
const () at /usr/lib/libQt5DBus.so.5
#9  0x7f288c481f8f in KWin::LogindIntegration::logindServiceRegistered() ()
at /usr/lib/libkwin.so.5
#10 0x7f288c482466 in  () at /usr/lib/libkwin.so.5
#11 0x7f2889ece88f in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#12 0x7f28837852b0 in
QDBusPendingCallWatcher::finished(QDBusPendingCallWatcher*) () at
/usr/lib/libQt5DBus.so.5
#13 0x7f2889ecf1b2 in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#14 0x7f288abbae2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#15 0x7f288abc2906 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#16 0x7f2889e9ebb0 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#17 0x7f2889ea1406 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#18 0x7f2889ef6136 in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#19 0x7f2874bcb0fe in  () at /usr/lib/libQt5XcbQpa.so.5
#20 0x7f2889e9cfdb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#21 0x7f2889ea6028 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#22 0x7f288cba96d3 in kdemain () at /usr/lib/libkdeinit5_kwin_x11.so
#23 0x7f288c80af6a in __libc_start_main () at /usr/lib/libc.so.6
#24 0x5569557f77ca in _start ()

Reported using DrKonqi

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

[frameworks-kirigami] [Bug 385430] New: kirigami .desktop file has no category thus kirigami is placed in lost & found sub menu of start menu

2017-10-05 Thread kts
https://bugs.kde.org/show_bug.cgi?id=385430

Bug ID: 385430
   Summary: kirigami .desktop file has no category thus kirigami
is placed in lost & found sub menu of start menu
   Product: frameworks-kirigami
   Version: 5.38.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: notm...@gmail.com
  Reporter: jeckfer...@gmail.com
  Target Milestone: Not decided

Created attachment 108201
  --> https://bugs.kde.org/attachment.cgi?id=108201&action=edit
lost & found menu is in the lower left corner

Due to the kirigami .desktop file not having category item, it is placed in
lost & found sub menu of start menu. Lost & found menu is called other menu in
other DE like Gnome.

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

[konqueror] [Bug 384376] Konqueror crashing on start of Plasma Desktop

2017-10-03 Thread kts
https://bugs.kde.org/show_bug.cgi?id=384376

kts  changed:

   What|Removed |Added

 CC||jeckfer...@gmail.com

--- Comment #1 from kts  ---
I observed the same behavior.
Konqueror does not close fully when exited through title bar bottom.
Some konqueror processes are still there in task manager.

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

[kwalletmanager] [Bug 384152] New: kwallet focus is not on password field

2017-08-29 Thread kts
https://bugs.kde.org/show_bug.cgi?id=384152

Bug ID: 384152
   Summary: kwallet focus is not on password field
   Product: kwalletmanager
   Version: 17.08
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: va...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

kwallet focus is not on password field.

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

[akregator] [Bug 383710] New: akregator always crashed on next login "with start with the system"

2017-08-19 Thread kts
https://bugs.kde.org/show_bug.cgi?id=383710

Bug ID: 383710
   Summary: akregator always crashed on next login "with start
with the system"
   Product: akregator
   Version: 5.5.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

Application: akregator (5.5.3)

Qt Version: 5.9.1
Frameworks Version: 5.37.0
Operating System: Linux 4.12.8-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
nothing, it just crashed. Manually opening it is fine. But after next login, it
always fails.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fa6b6393900 (LWP 854))]

Thread 21 (Thread 0x7fa619d8e700 (LWP 939)):
#0  0x7fa6ac5f61ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa69ec23b04 in  () at /usr/lib/libQt5Script.so.5
#2  0x7fa69ec23b49 in  () at /usr/lib/libQt5Script.so.5
#3  0x7fa6ac5f0049 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7fa6b21c9f0f in clone () at /usr/lib/libc.so.6

Thread 20 (Thread 0x7fa61b3ac700 (LWP 932)):
#0  0x7fa6ac5f61ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa6a19e10a5 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fa6a19e1587 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fa6a19e2321 in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fa6a19de9eb in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fa6ac5f0049 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fa6b21c9f0f in clone () at /usr/lib/libc.so.6

Thread 19 (Thread 0x7fa62a7fc700 (LWP 915)):
#0  0x7fa6aa35ba69 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7fa6aa316153 in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7fa6aa316b3b in  () at /usr/lib/libglib-2.0.so.0
#3  0x7fa6aa316d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7fa6b2af4084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7fa6b2a97ffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7fa6b28b140e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7fa6b28b615b in  () at /usr/lib/libQt5Core.so.5
#8  0x7fa6ac5f0049 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fa6b21c9f0f in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7fa62affd700 (LWP 914)):
#0  0x7fa6ac5f64ed in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa6a1a0f992 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fa6a19e5ba9 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fa6a19e610b in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fa6a19de9eb in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fa6ac5f0049 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fa6b21c9f0f in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7fa62b7fe700 (LWP 913)):
#0  0x7fa6ac5f64ed in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa6a1a0f992 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fa6a19e5ba9 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fa6a19e610b in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fa6a19de9eb in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fa6ac5f0049 in start_thread () at /usr/lib/libpthread.so.0
#6  0x7fa6b21c9f0f in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7fa62bfff700 (LWP 912)):
#0  0x7fa6ac5f61ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa6a19d6b19 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fa6a19d6b47 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fa6a19b189b in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fa6a19ae168 in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fa6a19cad5b in  () at /usr/lib/libQt5WebEngineCore.so.5
#6  0x7fa6a19e28e6 in  () at /usr/lib/libQt5WebEngineCore.so.5
#7  0x7fa6a19de9eb in  () at /usr/lib/libQt5WebEngineCore.so.5
#8  0x7fa6ac5f0049 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7fa6b21c9f0f in clone () at /usr/lib/libc.so.6

Thread 15 (Thread 0x7fa65cff9700 (LWP 911)):
#0  0x7fa6ac5f61ad in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fa6a19e10a5 in  () at /usr/lib/libQt5WebEngineCore.so.5
#2  0x7fa6a19e1587 in  () at /usr/lib/libQt5WebEngineCore.so.5
#3  0x7fa6a19e2321 in  () at /usr/lib/libQt5WebEngineCore.so.5
#4  0x7fa6a19de9eb in  () at /usr/lib/libQt5WebEngineCore.so.5
#5  0x7fa6ac5f0049 in

[Discover] [Bug 380496] Discover crashes upon opening

2017-08-02 Thread kts
https://bugs.kde.org/show_bug.cgi?id=380496

--- Comment #27 from kts  ---
(In reply to Aleix Pol from comment #26)
> @kts an easy way to fix it is by installing flatpak as mentioned in the
> comments.

We both know it's not a rational solution.

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

[Discover] [Bug 380496] Discover crashes upon opening

2017-08-02 Thread kts
https://bugs.kde.org/show_bug.cgi?id=380496

--- Comment #25 from kts  ---
I hope it get resolved soon.
I have a laptop and a desktop.
The problem cannot be reproduced in laptop.
It can be on desktop, freshly installed Arch Linux.
I got confused because laptop is good and desktop is not.
I reinstalled Arch on desktop in case I made some installation mistakes.
It's not. 
I still love KDE.

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

[Discover] [Bug 383014] New: Plasma Discover crashes everytime I open it

2017-08-01 Thread kts
https://bugs.kde.org/show_bug.cgi?id=383014

Bug ID: 383014
   Summary: Plasma Discover crashes everytime I open it
   Product: Discover
   Version: 5.10.4
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: aleix...@kde.org
  Reporter: jeckfer...@gmail.com
  Target Milestone: ---

Application: plasma-discover (5.10.4)

Qt Version: 5.9.1
Frameworks Version: 5.36.0
Operating System: Linux 4.12.3-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
Archlinux uptodate
My 2th generation dell inspiron laptop is fine.
It is not on my 4th generation desktop.
Both are on integrated intel video card.

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7feb694bce40 (LWP 756))]

Thread 9 (Thread 0x7feb35218700 (LWP 767)):
#0  0x7feb613f64ed in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7feb652ab4a1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7feb652a6586 in  () at /usr/lib/libQt5Core.so.5
#3  0x7feb652aa15b in  () at /usr/lib/libQt5Core.so.5
#4  0x7feb613f0049 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7feb64bbdf0f in clone () at /usr/lib/libc.so.6

Thread 8 (Thread 0x7feb362b3700 (LWP 766)):
#0  0x7feb613f64ed in pthread_cond_timedwait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7feb652ab4a1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7feb652a6586 in  () at /usr/lib/libQt5Core.so.5
#3  0x7feb652aa15b in  () at /usr/lib/libQt5Core.so.5
#4  0x7feb613f0049 in start_thread () at /usr/lib/libpthread.so.0
#5  0x7feb64bbdf0f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7feb36ab4700 (LWP 765)):
#0  0x7feb64bb3e9d in poll () at /usr/lib/libc.so.6
#1  0x7feb5f210c09 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7feb5f210d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7feb654e8084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7feb6548bffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7feb652a540e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7feb652aa15b in  () at /usr/lib/libQt5Core.so.5
#7  0x7feb613f0049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7feb64bbdf0f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7feb37955700 (LWP 764)):
#0  0x7feb5f210578 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#1  0x7feb5f210bb0 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7feb5f210d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7feb654e8084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7feb6548bffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7feb652a540e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7feb652aa15b in  () at /usr/lib/libQt5Core.so.5
#7  0x7feb613f0049 in start_thread () at /usr/lib/libpthread.so.0
#8  0x7feb64bbdf0f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7feb3d5a2700 (LWP 762)):
#0  0x7feb652a1a4f in QMutex::unlock() () at /usr/lib/libQt5Core.so.5
#1  0x7feb654e84aa in  () at /usr/lib/libQt5Core.so.5
#2  0x7feb5f210611 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#3  0x7feb5f210bb0 in  () at /usr/lib/libglib-2.0.so.0
#4  0x7feb5f210d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#5  0x7feb654e8084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#6  0x7feb6548bffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#7  0x7feb652a540e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#8  0x7feb687688d6 in  () at /usr/lib/libQt5Quick.so.5
#9  0x7feb652aa15b in  () at /usr/lib/libQt5Core.so.5
#10 0x7feb613f0049 in start_thread () at /usr/lib/libpthread.so.0
#11 0x7feb64bbdf0f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7feb4ca39700 (LWP 760)):
#0  0x7feb5f255a84 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7feb5f210609 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7feb5f210bb0 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7feb5f210d1c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7feb654e8084 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7feb6548bffb in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7feb652a540e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7feb65e661d5 in  () at /usr/lib/libQt5Qml.so

[akregator] [Bug 374692] Javascript does not work

2017-02-18 Thread kts
https://bugs.kde.org/show_bug.cgi?id=374692

kts  changed:

   What|Removed |Added

 CC||jeckfer...@gmail.com

--- Comment #1 from kts  ---
Confirm it. Need to open the article in external browsers which is annoying.
Even  a minimalist browser like Konquror had js enabled by default.

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

[systemsettings] [Bug 373877] Segfault when returning to root menu from "Screen Locking"

2016-12-21 Thread kts
https://bugs.kde.org/show_bug.cgi?id=373877

kts  changed:

   What|Removed |Added

 CC||jeckfer...@gmail.com

--- Comment #2 from kts  ---
(In reply to patrickrifici from comment #0)
> Created attachment 102869 [details]
> Stack trace of systemsettings5 at time of crash
> 
> OS version: Arch Linux x86_64
> KDE Plasma version: 5.8.4
> KDE Frameworks version: 5.29.0
> Qt version: 5.7.1
> 
> ## DESCRIPTION ##
> When pressing the "All Settings" button at the top left of the System
> Settings window while in the "Screen Locking" section under "Workspace",
> systemsettings will suffer a segmentation fault.
> 
> ## STEPS TO REPLICATE ##
> 1) Open System Settings
> 2) Select "Desktop Behaviour"
> 3) Select "Screen Locking"
> 4) Select "All Settings"
> 5) System Settings will now segfault
> 
> ## EXPECTED BEHAVIOUR ##
> System Settings is returned to the root menu.
> 
> ## ACTUAL BEHAVIOUR ##
> Segmentation fault, program crashes.
> 
> Please see stack trace at time of crash. Unsure if it is complete, I did
> recompile systemsettings with debug symbols and install Qt debug packages
> from repository as instructed in Arch wiki.

I'm on KDE Arch and I confirm exactly this from my updated machine.

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