[frameworks-baloo] [Bug 493109] New: Baloo crashed; only specific thing is: I was was working on my org-roam (Emacs mode) notes, 4k text files in one directory

2024-09-14 Thread Wiktor
https://bugs.kde.org/show_bug.cgi?id=493109

Bug ID: 493109
   Summary: Baloo crashed; only specific thing is: I was was
working on my org-roam (Emacs mode) notes, 4k text
files in one directory
Classification: Frameworks and Libraries
   Product: frameworks-baloo
   Version: 6.5.0
  Platform: Neon
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Baloo File Daemon
  Assignee: baloo-bugs-n...@kde.org
  Reporter: wikt.sztw+kdeb...@protonmail.com
  Target Milestone: ---

Application: baloo_file_extractor (6.5.0)

Qt Version: 6.7.2
Frameworks Version: 6.5.0
Operating System: Linux 6.8.0-40-generic x86_64
Windowing System: X11
Distribution: KDE neon 6.1
DrKonqi: 6.1.4 [CoredumpBackend]

-- Information about the crash:
The only thing I can think of, that might be usefull, is that I have a
directory, where there are about 4000 text files, where 90% of them are in 1
dorectory, remaining are split into 2 additional direcotires. I'm not sure, but
I think that I get baloo crash reports very rarely, when I move note from
sub-dir to main dir

The reporter is unsure if this crash is reproducible.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
Downloading 1.21 MB separate debug info for
/usr/lib/x86_64-linux-gnu/libexec/kf6/baloo_file_extractor...
Downloading 1.16 MB separate debug info for
/home/wicu/.cache/debuginfod_client/216866fffee216abed1bd6054e7f1d0dceb56d49/debuginfo...
[New LWP 195110]
[New LWP 195112]
[New LWP 195113]
[New LWP 195111]
[New LWP 195115]
[New LWP 195118]
[New LWP 195116]
[New LWP 195117]
[New LWP 195119]
[New LWP 195114]
Downloading 1.81 MB separate debug info for
/lib/x86_64-linux-gnu/libKF6FileMetaData.so.3...
Downloading 0.39 MB separate debug info for
/home/wicu/.cache/debuginfod_client/4af3d705cc8556051a9d622c0e516ee8fb085421/debuginfo...
Downloading 2.80 MB separate debug info for
/lib/x86_64-linux-gnu/libKF6ConfigCore.so.6...
Downloading 0.27 MB separate debug info for
/home/wicu/.cache/debuginfod_client/4623d77b86dd559ec91bf71eac95d14bcb65a59c/debuginfo...
Downloading 9.42 MB separate debug info for
/lib/x86_64-linux-gnu/libKF6Solid.so.6...
Downloading 0.15 MB separate debug info for
/home/wicu/.cache/debuginfod_client/78e66e3b206d1ee0f17fc9c5dd40a7deab66ad27/debuginfo...
Downloading 1.90 MB separate debug info for
/lib/x86_64-linux-gnu/libKF6BalooEngine.so.6...
Downloading 0.48 MB separate debug info for
/lib/x86_64-linux-gnu/libKF6Crash.so.6...
Downloading 0.50 MB separate debug info for
/lib/x86_64-linux-gnu/libKF6IdleTime.so.6...
Downloading 0.16 MB separate debug info for
/home/wicu/.cache/debuginfod_client/5d857c84bf82ae8b739113741c34c57af558ca79/debuginfo...
Downloading 1.87 MB separate debug info for
/lib/x86_64-linux-gnu/libKF6I18n.so.6...
Downloading 0.26 MB separate debug info for
/home/wicu/.cache/debuginfod_client/007e6184790a04771e2e23319ca1af6795d25997/debuginfo...
Downloading 6.17 MB separate debug info for
/lib/x86_64-linux-gnu/libKF6CoreAddons.so.6...
Downloading 0.16 MB separate debug info for
/home/wicu/.cache/debuginfod_client/919e2852744ae3ab4b6479c2b688593273291446/debuginfo...
Downloading 64.52 MB separate debug info for
/lib/x86_64-linux-gnu/libQt6Gui.so.6...
Downloading 4.21 MB separate debug info for
/home/wicu/.cache/debuginfod_client/c47aa4ae97eefba92a4417e00c59e7212c39a4d9/debuginfo...
Downloading 18.16 MB separate debug info for
/lib/x86_64-linux-gnu/libQt6Core.so.6...
Downloading 5.99 MB separate debug info for
/lib/x86_64-linux-gnu/libstdc++.so.6...
Downloading 2.96 MB separate debug info for
/lib/x86_64-linux-gnu/libQt6DBus.so.6...
Downloading 0.50 MB separate debug info for
/lib/x86_64-linux-gnu/libQt6Xml.so.6...
Downloading 0.40 MB separate debug info for
/lib/x86_64-linux-gnu/libmount.so.1...
Downloading 0.21 MB separate debug info for
/lib/x86_64-linux-gnu/libimobiledevice-1.0.so.6...
Downloading 0.10 MB separate debug info for
/lib/x86_64-linux-gnu/libplist-2.0.so.3...
Downloading 0.12 MB separate debug info for
/lib/x86_64-linux-gnu/liblmdb.so.0...
Downloading 1.33 MB separate debug info for
/lib/x86_64-linux-gnu/libX11.so.6...
Downloading 0.18 MB separate debug info for
/lib/x86_64-linux-gnu/libgcc_s.so.1...
Downloading 0.10 MB separate debug info for
/lib/x86_64-linux-gnu/libEGL.so.1...
Downloading 0.45 MB separate debug info for
/lib/x86_64-linux-gnu/libfontconfig.so.1...
Downloading 1.45 MB separate debug info for
/lib/x86_64-linux-gnu/libglib-2.0.so.0...
Downloading 0.03 MB separate debug info for
/home/wicu/.cache/debuginfod_client/224ac2a88b72bc8e2fe8566ee28fae789fc69241/debuginfo...
Downloading 0.30 MB separate debug info for
/lib/x86_64-linux-gnu/libxkbcommon.so.0...
Downloading 0.30 MB separate debug info for
/lib/x86_64-linux-gnu

[Akonadi] [Bug 425658] Kmail + Gmail | System reports problem with sending email after typing password

2020-11-29 Thread Wiktor
https://bugs.kde.org/show_bug.cgi?id=425658

--- Comment #5 from Wiktor  ---
Well… in fact shortly after one of the updates my Gmail configuration totally
broke. Only now I've got time to clean my email situation and unfortunately not
only my account stopped working, also I'm unable to connect

I'm sorry that I didn't answer earlier or now am not that helpful.

I think, we could just close this ticket now.

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

[yakuake] [Bug 429526] New: Yakuake crashed when tried to install new colors scheme

2020-11-22 Thread Wiktor
https://bugs.kde.org/show_bug.cgi?id=429526

Bug ID: 429526
   Summary: Yakuake crashed when tried to install new colors
scheme
   Product: yakuake
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: h...@kde.org
  Reporter: drudan.for...@gmail.com
  Target Milestone: ---

Application: yakuake (20.08.3)

Qt Version: 5.15.1
Frameworks Version: 5.76.0
Operating System: Linux 5.4.0-54-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.20

-- Information about the crash:
- What I was doing when the application crashed:
searching for colors scheme that have less unreadable colors in popular
applications. I was using Get New… to download https://store.kde.org/p/1220066/
. After clicking Install yakuake crashed

- Custom settings of the application:
I've got already 3 themes installed

The crash does not seem to be reproducible.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Content of s_kcrashErrorMessage: (null)
[New LWP 1277]
[New LWP 1304]
[New LWP 1333]
[New LWP 1334]
[New LWP 1335]
[New LWP 1336]
[New LWP 15390]
[New LWP 15391]
[New LWP 15394]
[New LWP 15395]
[New LWP 15396]
[New LWP 16515]
[New LWP 24683]
[New LWP 24684]
[New LWP 24685]
[New LWP 24686]
[New LWP 24687]
[New LWP 24688]
[New LWP 24712]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f3d4015caff in __GI___poll (fds=fds@entry=0x7fffae99c428,
nfds=nfds@entry=1, timeout=timeout@entry=1000) at
../sysdeps/unix/sysv/linux/poll.c:29
[Current thread is 1 (Thread 0x7f3d3c61df40 (LWP 1240))]

Thread 20 (Thread 0x7f3ce9e00700 (LWP 24712)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7f3ce9dffc90, clockid=, expected=0,
futex_word=0x7f3cec0065a4) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7f3ce9dffc90, clockid=, mutex=0x7f3cec006550, cond=0x7f3cec006578) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x7f3cec006578, mutex=0x7f3cec006550,
abstime=0x7f3ce9dffc90) at pthread_cond_wait.c:656
#3  0x7f3d404edc78 in QWaitConditionPrivate::wait_relative
(this=0x7f3cec006550, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x7f3cec006550) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=this@entry=0x7f3cec006230,
mutex=mutex@entry=0x7f3cec005ec8, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#6  0x7f3d404eb121 in QThreadPoolThread::run (this=0x7f3cec006220) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:270
#7  0x7f3d404e7b1c in QThreadPrivate::start (arg=0x7f3cec006220) at
thread/qthread_unix.cpp:329
#8  0x7f3d3f651609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f3d40169293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 19 (Thread 0x7f3cfd498700 (LWP 24688)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7f3cfd497c90, clockid=, expected=0,
futex_word=0x55dc54fe7c00) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7f3cfd497c90, clockid=, mutex=0x55dc54fe7bb0, cond=0x55dc54fe7bd8) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x55dc54fe7bd8, mutex=0x55dc54fe7bb0,
abstime=0x7f3cfd497c90) at pthread_cond_wait.c:656
#3  0x7f3d404edc78 in QWaitConditionPrivate::wait_relative
(this=0x55dc54fe7bb0, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x55dc54fe7bb0) at
thread/qwaitcondition_unix.cpp:144
#5  QWaitCondition::wait (this=this@entry=0x55dc54f80550,
mutex=mutex@entry=0x55dc54fb1708, deadline=...) at
thread/qwaitcondition_unix.cpp:225
#6  0x7f3d404eb121 in QThreadPoolThread::run (this=0x55dc54f80540) at
../../include/QtCore/../../src/corelib/thread/qmutex.h:270
#7  0x7f3d404e7b1c in QThreadPrivate::start (arg=0x55dc54f80540) at
thread/qthread_unix.cpp:329
#8  0x7f3d3f651609 in start_thread (arg=) at
pthread_create.c:477
#9  0x7f3d40169293 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 18 (Thread 0x7f3cfec9b700 (LWP 24687)):
#0  futex_abstimed_wait_cancelable (private=,
abstime=0x7f3cfec9ac90, clockid=, expected=0,
futex_word=0x55dc54f82370) at ../sysdeps/nptl/futex-internal.h:320
#1  __pthread_cond_wait_common (abstime=0x7f3cfec9ac90, clockid=, mutex=0x55dc54f82320, cond=0x55dc54f82348) at pthread_cond_wait.c:520
#2  __pthread_cond_timedwait (cond=0x55dc54f82348, mutex=0x55dc54f82320,
abstime=0x7f3cfec9ac90) at pthread_cond_wait.c:656
#3  0x7f3d404edc78 in QWaitConditionPrivate::wait_relative
(this=0x55dc54f82320, deadline=...) at thread/qwaitcondition_unix.cpp:136
#4  QWaitConditionPrivate::wait (deadline=..., this=0x55dc54f823

[Akonadi] [Bug 425658] Kmail + Gmail | System reports problem with sending email after typing password

2020-08-26 Thread Wiktor
https://bugs.kde.org/show_bug.cgi?id=425658

--- Comment #2 from Wiktor  ---
(In reply to Ahmad Samir from comment #1)
> This might be a duplicate of bug 425658.

You just linked this this bug :P

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

[Akonadi] [Bug 425658] Kmail + Gmail | System reports problem with sending email after typing password

2020-08-21 Thread Wiktor
https://bugs.kde.org/show_bug.cgi?id=425658

Wiktor  changed:

   What|Removed |Added

Version|unspecified |5.15.0

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

[Akonadi] [Bug 425658] New: Kmail + Gmail | System reports problem with sending email after typing password

2020-08-21 Thread Wiktor
https://bugs.kde.org/show_bug.cgi?id=425658

Bug ID: 425658
   Summary: Kmail + Gmail | System reports problem with sending
email after typing password
   Product: Akonadi
   Version: unspecified
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: Mail Dispatcher Agent
  Assignee: kdepim-b...@kde.org
  Reporter: drudan.for...@gmail.com
  Target Milestone: ---

Application: akonadi_maildispatcher_agent (5.15.0 (20.08.0))

Qt Version: 5.14.2
Frameworks Version: 5.73.0
Operating System: Linux 5.4.0-42-generic x86_64
Windowing system: X11
Distribution: KDE neon User Edition 5.19

-- Information about the crash:
- What I was doing when the application crashed:

Sending first email from Gmail just after configuring Kmail.

Gmail with 2-step auth. On sending it ask for Gmail password and then I got
system notification:
Failed to transport message. The remote host closed connection

The crash can be reproduced every time.

-- Backtrace:
Application: akonadi_maildispatcher_agent (akonadi_maildispatcher_agent),
signal: Segmentation fault
Content of s_kcrashErrorMessage: (null)
[KCrash Handler]
#6  0x7f2eb3ba3385 in KCoreConfigSkeleton::findItem (this=0xd20064656c,
name=...) at ./src/core/kcoreconfigskeleton.cpp:1544
#7  0x7f2eb3ba33cd in KCoreConfigSkeleton::isImmutable (this=, name=...) at ./src/core/kcoreconfigskeleton.cpp:1538
#8  0x7f2ea570149f in MailTransport::TransportBase::isUserNameImmutable
(this=) at
./obj-x86_64-linux-gnu/src/kmailtransport/transportbase.h:219
#9  MailTransport::TransportBase::setUserName (v=..., this=) at
./obj-x86_64-linux-gnu/src/kmailtransport/transportbase.h:202
#10 MailTransport::SmtpJob::startLoginJob (this=0x561e96d7b400) at
./src/kmailtransport/plugins/smtp/smtpjob.cpp:256
#11 0x7f2ea5702390 in MailTransport::SmtpJob::startPasswordRetrieval
(this=0x561e96d7b400, forceRefresh=) at
./src/kmailtransport/plugins/smtp/smtpjob.cpp:208
#12 0x7f2eb316251e in QtPrivate::QSlotObjectBase::call (a=0x7ffd3d97f650,
r=0x561e96d7b400, this=0x561e96cc2b70) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#13 doActivate (sender=0x561e96d68090, signal_index=3,
argv=0x7ffd3d97f650) at kernel/qobject.cpp:3870
#14 0x7f2eb315caf7 in QMetaObject::activate (sender=,
m=m@entry=0x7f2ea56dbb40 ,
local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffd3d97f650)
at kernel/qobject.cpp:3930
#15 0x7f2ea56cb632 in KSmtp::Session::stateChanged (this=,
_t1=) at
./obj-x86_64-linux-gnu/src/KPimSMTP_autogen/EWIEGA46WW/moc_session.cpp:166
#16 0x7f2ea56d11a9 in KSmtp::SessionPrivate::setState (s=,
this=0x561e96d67050) at ./src/session.cpp:257
#17 KSmtp::SessionPrivate::setState (this=0x561e96d67050, s=) at
./src/session.cpp:250
#18 0x7f2ea56d248f in KSmtp::SessionPrivate::socketConnected
(this=0x561e96d67050) at ./src/session.cpp:322
#19 0x7f2eb315a2a9 in QObject::event (this=0x561e96d67050,
e=0x7f2e7c004380) at kernel/qobject.cpp:1339
#20 0x7f2eb357ccc3 in QApplicationPrivate::notify_helper
(this=this@entry=0x561e96bd5750, receiver=receiver@entry=0x561e96d67050,
e=e@entry=0x7f2e7c004380) at kernel/qapplication.cpp:3685
#21 0x7f2eb3585f40 in QApplication::notify (this=0x7ffd3d97fcc0,
receiver=0x561e96d67050, e=0x7f2e7c004380) at kernel/qapplication.cpp:3431
#22 0x7f2eb312c78a in QCoreApplication::notifyInternal2
(receiver=0x561e96d67050, event=0x7f2e7c004380) at
../../include/QtCore/../../src/corelib/kernel/qobject.h:153
#23 0x7f2eb312ef74 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x561e96bd1200) at
kernel/qcoreapplication.cpp:1815
#24 0x7f2eb3185b87 in postEventSourceDispatch (s=0x561e96c3a230) at
kernel/qeventdispatcher_glib.cpp:277
#25 0x7f2eb110ffbd in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x7f2eb1110240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x7f2eb11102e3 in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x7f2eb31851e2 in QEventDispatcherGlib::processEvents
(this=0x561e96c43790, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#29 0x7f2eb312b24b in QEventLoop::exec (this=this@entry=0x7ffd3d97fc10,
flags=..., flags@entry=...) at
../../include/QtCore/../../src/corelib/global/qflags.h:136
#30 0x7f2eb3133296 in QCoreApplication::exec () at
../../include/QtCore/../../src/corelib/global/qflags.h:118
#31 0x7f2eb21722a0 in QGuiApplication::exec () at
kernel/qguiapplication.cpp:1860
#32 0x7f2eb357cc39 in QApplication::exec () at kernel/qapplication.cpp:2825
#33 0x7f2eb40e0282 in Akonadi::AgentBase::init (r=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qcoreapplication.h:116
#34 0x561e95e49639 in Akonadi::AgentBase::init
(argc=, argv=) at
/usr/include/KF5/Akonadi

[konsole] [Bug 373232] Horizontal lines with fractional HiDPI scaling

2020-05-12 Thread Wiktor
https://bugs.kde.org/show_bug.cgi?id=373232

Wiktor  changed:

   What|Removed |Added

 CC||drudan.for...@gmail.com

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

[klipper] [Bug 54212] freeze and export items

2020-04-02 Thread Wiktor
https://bugs.kde.org/show_bug.cgi?id=54212

Wiktor  changed:

   What|Removed |Added

 CC||drudan.for...@gmail.com

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

[Spectacle] [Bug 372464] New: Simple edition (drawing Arrows / Text / Highlighting) after doing screenshot

2016-11-14 Thread Wiktor
https://bugs.kde.org/show_bug.cgi?id=372464

Bug ID: 372464
   Summary: Simple edition (drawing Arrows / Text / Highlighting)
after doing screenshot
   Product: Spectacle
   Version: unspecified
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: drudan.for...@gmail.com
  Target Milestone: ---

Let Spectacle add simple elements like Arrows, Text and Highlighting to created
screenshots.

One option would be to add edition options into spectacle.

The other option could be creating a separate application or extending
KolourPaint to let drawing pretty arrows.

Currently the closest way of achieving something like this in KDE eco is to
open screenshot in KolourPaint and try to draw arrow using lines which becomes
quite ugly in result.

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

[kexi] [Bug 370090] Kexi crash when trying to add script in new project

2016-10-07 Thread Wiktor via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370090

--- Comment #6 from Wiktor  ---
(In reply to Jarosław Staniek from comment #4)
> By the way, if you're interesting in scripting, we're planning to have a
> completely new Scripting module and the language will be Javascript;
> functionally it would still use similar editor and approach.
> The home page of Scripting development is
> https://community.kde.org/Kexi/Plugins/Scripts.

I read yesterday on Postgres wiki that Kexi can operate on existing DB. I was
searching for an app that could be used to prepare some report / visualization
and checked if Kexi is OK. Then clicked 'Scripts' and it crashed so I decided
to report bug.

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

[kexi] [Bug 370090] Kexi crash when trying to add script in new project

2016-10-07 Thread Wiktor via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370090

--- Comment #5 from Wiktor  ---
It's a know problem for years and nothings shows that Arch will gain
precompiled debugging symbols.

Also, I've got now Kexi 3 after today's upgrade, and now I don's see 'Scripts'
button. Should I close this ticket?

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


[kexi] [Bug 370090] Kexi crash when trying to add script in new project

2016-10-05 Thread Wiktor via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370090

--- Comment #2 from Wiktor  ---
> I don't see a full backtrace
Unfortunately users of Arch Linux don't get pre-compiled packages with KDE
debug symbols. I try to build kexi myself with them. Until then I won't be able
to provide more useful output :( .

> you may miss a 3rd-party KTextEditor
KWrite is working and Kate is my default editor, which I use all the time.

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


[kexi] [Bug 370090] New: Kexi crash when trying to add script in new project

2016-10-05 Thread Wiktor via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=370090

Bug ID: 370090
   Summary: Kexi crash when trying to add script in new project
   Product: kexi
   Version: 2.9.11
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: General
  Assignee: kexi-b...@kde.org
  Reporter: drudan.for...@gmail.com
CC: a...@piggz.co.uk, in...@fables.co.za

Application: kexi (2.9.11)
KDE Platform Version: 4.14.24
Qt Version: 4.8.7
Operating System: Linux 4.7.6-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I open newly created project. Then click button creating new object of type
"Script". Kexi crash every time when I do it.

The crash can be reproduced every time.

-- Backtrace:
Application: Kexi (kexi), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[KCrash Handler]
#6  0x02051468 in ?? ()
#7  0x7f0be720901f in KexiEditor::defaultContextMenu() () from
/usr/lib/libkexiextendedwidgets.so.14
#8  0x7f0bc2d060c8 in KexiScriptDesignView::KexiScriptDesignView(QWidget*,
Kross::Action*) () from /usr/lib/kde4/kexihandler_script.so
#9  0x7f0bc2d02584 in KexiScriptPart::createView(QWidget*, KexiWindow*,
KexiPart::Item&, Kexi::ViewMode, QMap*) () from
/usr/lib/kde4/kexihandler_script.so
#10 0x7f0be9198eed in KexiWindow::switchToViewMode(Kexi::ViewMode,
QMap*, bool&) () from /usr/lib/libkexicore.so.14
#11 0x7f0be91a669d in KexiPart::Part::openInstance(QWidget*,
KexiPart::Item&, Kexi::ViewMode, QMap*) () from
/usr/lib/libkexicore.so.14
#12 0x7f0be918f463 in KexiProject::openObject(QWidget*, KexiPart::Item&,
Kexi::ViewMode, QMap*) () from /usr/lib/libkexicore.so.14
#13 0x7f0be946d203 in KexiMainWindow::openObject(KexiPart::Item*,
Kexi::ViewMode, bool&, QMap*, QString*) () from
/usr/lib/libkeximain.so.14
#14 0x7f0be945577e in KexiMainWindow::newObject(KexiPart::Info*, bool&) ()
from /usr/lib/libkeximain.so.14
#15 0x7f0be94713fc in ?? () from /usr/lib/libkeximain.so.14
#16 0x7f0be7bcec50 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/libQtCore.so.4
#17 0x7f0be919f9a2 in
KexiPart::Manager::newObjectRequested(KexiPart::Info*) () from
/usr/lib/libkexicore.so.14
#18 0x7f0be7bcec50 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/libQtCore.so.4
#19 0x7f0be91a487f in
KexiNewObjectAction::newObjectRequested(KexiPart::Info*) () from
/usr/lib/libkexicore.so.14
#20 0x7f0be7bcec50 in QMetaObject::activate(QObject*, QMetaObject const*,
int, void**) () from /usr/lib/libQtCore.so.4
#21 0x7f0be8122082 in QAction::triggered(bool) () from
/usr/lib/libQtGui.so.4
#22 0x7f0be81233e3 in QAction::activate(QAction::ActionEvent) () from
/usr/lib/libQtGui.so.4
#23 0x7f0be84fe2f3 in ?? () from /usr/lib/libQtGui.so.4
#24 0x7f0be84fe444 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
from /usr/lib/libQtGui.so.4
#25 0x7f0be85c3a7a in QToolButton::mouseReleaseEvent(QMouseEvent*) () from
/usr/lib/libQtGui.so.4
#26 0x7f0be817e840 in QWidget::event(QEvent*) () from
/usr/lib/libQtGui.so.4
#27 0x7f0be8127f2c in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQtGui.so.4
#28 0x7f0be81305b7 in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQtGui.so.4
#29 0x7f0be5bf32fa in KApplication::notify(QObject*, QEvent*) () from
/usr/lib/libkdeui.so.5
#30 0x7f0be7bbab2d in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib/libQtCore.so.4
#31 0x7f0be812e5db in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool) () from
/usr/lib/libQtGui.so.4
#32 0x7f0be81a9a89 in ?? () from /usr/lib/libQtGui.so.4
#33 0x7f0be81a843c in QApplication::x11ProcessEvent(_XEvent*) () from
/usr/lib/libQtGui.so.4
#34 0x7f0be81d0db2 in ?? () from /usr/lib/libQtGui.so.4
#35 0x7f0be3bd2e67 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#36 0x7f0be3bd30d0 in ?? () from /usr/lib/libglib-2.0.so.0
#37 0x7f0be3bd317c in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#38 0x7f0be7beaeee in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQtCore.so.4
#39 0x7f0be81d0e86 in ?? () from /usr/lib/libQtGui.so.4
#40 0x7f0be7bb93ff in
QEventLoop::processEvents(QFlags) () from
/usr/lib/libQtCore.so.4
#41 0x7f0be7bb9765 in
QEventLoop::exec(QFlags) () from
/usr/lib/libQtCore.so.4
#42 0x7f0be7bbf1c9 in QCoreApplication::exec() () from
/usr/lib/libQtCore.so.4
#43 0x00400979 in main ()

Reported using DrKonqi

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


[kdeplasma-addons] [Bug 366827] Widget location configuration is lost after reboot

2016-09-13 Thread Wiktor via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366827

Wiktor  changed:

   What|Removed |Added

 CC||drudan.for...@gmail.com

--- Comment #7 from Wiktor  ---
Arch user here. I have not yet current Plasma 5.7 update so I'm not sure if
it's already fixed but I'd like to throw ma 0,02 cents.

In my case when I start my computer there is ethernet connection established
but with no access to outside world due to my company policy. Only after I
login company firewall gives me access to internet.

I've found that the problem only happens on my workstation were I have to deal
with firewall, but at home I also use Arch on laptop and there it works
flawlessly.

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


[plasma-pa] [Bug 365031] MPD stream has no icon

2016-07-09 Thread Wiktor via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=365031

Wiktor  changed:

   What|Removed |Added

 CC||drudan.for...@gmail.com

--- Comment #1 from Wiktor  ---
Created attachment 99964
  --> https://bugs.kde.org/attachment.cgi?id=99964&action=edit
FMOD Ex… = Broforce (Steam) sound stream

This issue applies to any sound source without icon in applet.

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

[plasmashell] [Bug 363647] panel doesn't render (update display) after starting an OpenGL application

2016-06-12 Thread Wiktor via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363647

Wiktor  changed:

   What|Removed |Added

 CC||drudan.for...@gmail.com

--- Comment #1 from Wiktor  ---
The same problem happens in my case. I'm using open source Intel drivers.

$ uname -a
Linux arch 4.6.2-1-ARCH #1 SMP PREEMPT Wed Jun 8 08:40:59 CEST 2016 x86_64
GNU/Linux


But, I can't say if it breaks after starting OpenGL application or there is
other reason as I don't remember starting any of it when the problem occurred.

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


[plasma-pa] [Bug 356605] Audio applet not visible, only empty space with no reaction to mouse

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

--- Comment #1 from Wiktor  ---
As you can see here
https://www.reddit.com/r/kde/comments/3winhb/plasma_55_issues_broken_widget_frames_sound/cxwh41j
I'm not the only one that encountered this.

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


[plasma-pa] [Bug 356605] New: Audio applet not visible, only empty space with no reaction to mouse

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

Bug ID: 356605
   Summary: Audio applet not visible, only empty space with no
reaction to mouse
   Product: plasma-pa
   Version: 5.5.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: drudan.for...@gmail.com

Audio applet in tray is not visible. There is only empty space with no reaction
to mouse clicks.

The interesting thing is that every new system tray applet contains working
audio applet only till next system reboot.

Reproducible: Always

Steps to Reproduce:
1. Add new system tray applet.
2. Experience working audio applet :) .
3. Reboot system.
4. Experience not working audio applet :( .

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


[plasmashell] [Bug 355683] Upgraded from 5.15 to 5.16. Now hangs just before sddm should show logging in GUI.

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

Wiktor  changed:

   What|Removed |Added

Version|5.4.3   |5.4.95

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


[plasmashell] [Bug 355683] Upgraded from 5.15 to 5.16. Now hangs just before sddm should show logging in GUI.

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

Wiktor  changed:

   What|Removed |Added

Version|5.4.95  |5.4.3

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


[plasmashell] [Bug 355683] Upgraded from 5.15 to 5.16. Now hangs just before sddm should show logging in GUI.

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

--- Comment #2 from Wiktor  ---
There is updated package now in Arch, 5.16.0-2 which seems to have fix for this
bug. Or it was something different in Plasma 5.5 Beta which I've decided to
test.

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


[plasmashell] [Bug 355683] Upgraded from 5.15 to 5.16. Now hangs just before sddm should show logging in GUI.

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

Wiktor  changed:

   What|Removed |Added

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

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