[kalendar] [Bug 465729] New: Location autocomplete OBNOXIOUS and CAN'T be turned OFF!!

2023-02-14 Thread Arthur
https://bugs.kde.org/show_bug.cgi?id=465729

Bug ID: 465729
   Summary: Location autocomplete OBNOXIOUS and CAN'T be turned
OFF!!
Classification: Applications
   Product: kalendar
   Version: 22.12.1
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: claudio.cam...@kde.org
  Reporter: arthur_tor...@comcast.net
CC: c...@carlschwan.eu
  Target Milestone: ---

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug
symbols.
See
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. enter new event, or attempt to edit existing one
2. start entering a location in the location field
3. See annoying pop-up list of undesired locations interrupt every effort to
enter the desired one, requiring clicking outside the field to get rid of the
list after EACH LETTER!
4. Search all available settings, and find NO option to turn off the
anti-feature.

OBSERVED RESULT
Annoying popup of locations that hides data entry field with no way to turn it
off.

EXPECTED RESULT
Having an option in the settings menu that would enable turning the popup
function OFF (or on if one is SERIOUSLY masochistic) 


SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 5.15.91-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 12 × Intel® Core™ i7-3930K CPU @ 3.20GHz
Memory: 47.0 GiB of RAM
Graphics Processor: NV92
Manufacturer: Dedicated Computing
Product Name: OEM-S4040-00


ADDITIONAL INFORMATION

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

[ksysguard] [Bug 432616] crash in libksgrdbackend.so

2022-10-05 Thread Arthur
https://bugs.kde.org/show_bug.cgi?id=432616

Arthur  changed:

   What|Removed |Added

 CC||moz@liebesgedichte.siteware
   ||.ch

--- Comment #1 from Arthur  ---
Same segfault on Debian stable with kded5 5.78.0:
ksystemstats[11801]: segfault at 70 ip 7f619b12251b sp 7fff116cc970
error 4 in libksgrdbackend.so[7f619b121000+5000]
No flaky network or anything like that. Seems to occur more often when
hibernating or resuming from hibernation. So far had one oom-killer kill
ksystemstats (possibly unrelated?).

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

[ksysguard] [Bug 428266] ksystem stats crashes often

2022-10-05 Thread Arthur
https://bugs.kde.org/show_bug.cgi?id=428266

Arthur  changed:

   What|Removed |Added

 CC||moz@liebesgedichte.siteware
   ||.ch

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

[krita] [Bug 424341] New: Tablet buttons aren't doing what I made them do on Krita specifically.

2020-07-17 Thread Arthur
https://bugs.kde.org/show_bug.cgi?id=424341

Bug ID: 424341
   Summary: Tablet buttons aren't doing what I made them do on
Krita specifically.
   Product: krita
   Version: 4.3.0
  Platform: Other
OS: Other
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: tablet support
  Assignee: krita-bugs-n...@kde.org
  Reporter: 13579arthur13...@gmail.com
  Target Milestone: ---

SUMMARY
Hello, when I use my tablet buttons (tablet is XP pen 15.6 pro), the shortcuts
that are happening when I click them are the tablet's default ones, not the
ones I set the tablet to do. The buttons do do what I had set out of krita
though.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

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

[konsole] [Bug 398214] New: text lines does not rearange themself on window resizing

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

Bug ID: 398214
   Summary: text lines does not rearange themself on window
resizing
   Product: konsole
   Version: 17.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: berko...@gmail.com
  Target Milestone: ---

when i have long lines command output in the console i like to resize the
window in order that the output lines will re-arange themself one line after
another, but unfortunatlly i need to repeat the command to see the desired
ordered output.

will be glad if you fix it.

thank you a lot!

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

[plasmashell] [Bug 381235] New: Plasma craches after install input audio tools

2017-06-15 Thread Arthur
https://bugs.kde.org/show_bug.cgi?id=381235

Bug ID: 381235
   Summary: Plasma craches after install input audio tools
   Product: plasmashell
   Version: 5.10.2
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: sec.abco...@gmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.10.2)

Qt Version: 5.9.0
Frameworks Version: 5.35.0
Operating System: Linux 4.9.31-1-lts x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed: I was having problems with
audio and I installed some tools like pavucontrol-qt and alsa packages
(alsa-plugins,alsa-tools, alsa-utils) and when I started to watch a video on
youtube (in chromium) I can not hear nothing. So, when I clicked on audio
settings on plasma notifications icons, the error occured.

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

Thread 19 (Thread 0x7f4625811700 (LWP 12149)):
#0  0x7f46e4ac52bd in poll () at /usr/lib/libc.so.6
#1  0x7f46df680bf9 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f46df680d0c in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f46e53ede9b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f46e539421a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f46e51b640a in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f46e8325645 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f46e51bacbd in  () at /usr/lib/libQt5Core.so.5
#8  0x7f46e4383297 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f46e4acf25f in clone () at /usr/lib/libc.so.6

Thread 18 (Thread 0x7f46017fa700 (LWP 8052)):
#0  0x7f46e438939d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f46e51bc0eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f4621a093cd in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f4621a0e2b8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f4621a08913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f4621a0e312 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f4621a08913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f4621a0e312 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f4621a08913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7f4621a0bb6b in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#10 0x7f46e51bacbd in  () at /usr/lib/libQt5Core.so.5
#11 0x7f46e4383297 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7f46e4acf25f in clone () at /usr/lib/libc.so.6

Thread 17 (Thread 0x7f4601ffb700 (LWP 8051)):
#0  0x7f46e438939d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f46e51bc0eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f4621a093cd in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f4621a0e2b8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f4621a08913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7f4621a0e312 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7f4621a08913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7f4621a0bb6b in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7f46e51bacbd in  () at /usr/lib/libQt5Core.so.5
#9  0x7f46e4383297 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f46e4acf25f in clone () at /usr/lib/libc.so.6

Thread 16 (Thread 0x7f46027fc700 (LWP 8050)):
#0  0x7f46e438939d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f46e51bc0eb in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7f4621a093cd in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7f4621a0e2b8 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7f4621a08913 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.s

[gwenview] [Bug 414766] When playing a video, no longer possible to navigate with left / right arrow keys

2025-03-16 Thread Arthur
https://bugs.kde.org/show_bug.cgi?id=414766

Arthur  changed:

   What|Removed |Added

 CC||ream-send-audie...@duck.com

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

[gwenview] [Bug 414766] When playing a video, no longer possible to navigate with left / right arrow keys

2025-03-16 Thread Arthur
https://bugs.kde.org/show_bug.cgi?id=414766

--- Comment #5 from Arthur  ---
Still reproducible on Gwenview version 24.12.3

Operating System: Arch Linux 
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.11.0
Qt Version: 6.8.2
Kernel Version: 6.13.6-arch1-1 (64-bit)
Graphics Platform: Wayland

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

[kdevelop] [Bug 454685] updated kdevelop on debian today, crashed while parsing a just imported project

2022-06-01 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=454685

--- Comment #1 from Arthur Gruzauskas  ---
Created attachment 149368
  --> https://bugs.kde.org/attachment.cgi?id=149368&action=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[kdevelop] [Bug 454685] New: updated kdevelop on debian today, crashed while parsing a just imported project

2022-06-01 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=454685

Bug ID: 454685
   Summary: updated kdevelop on debian today, crashed while
parsing a just imported project
   Product: kdevelop
   Version: unspecified
  Platform: Debian testing
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: deb...@gruz.net
  Target Milestone: ---

Application: kdevelop (5.8.220401 (22.04.1))

Qt Version: 5.15.2
Frameworks Version: 5.94.0
Operating System: Linux 5.17.0-1-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux bookworm/sid
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
just updated kdevelop. 
cleared all caches i know about :  rm -r /home/artg/.local/share/kdevelop/; rm
-r /home/artg/.cache/kdevduchain/; rm /home/artg/.config/kdeveloprc'
partway through background parsing it crashed. did this 3 times in a row.
uninstalled kdevelop & dependancies, removed some older versions of libraries.
reinstalled. same crash.

here is the terminal output:

artg~/alocal/ajg_stuff: Qt WebEngine seems to be initialized from a plugin.
Please set Qt::AA_ShareOpenGLContexts using QCoreApplication::setAttribute
before constructing QGuiApplication.
qrc:/qml/storage.js:10: TypeError: Cannot call method 'openDatabaseSync' of
undefined
qrc:/qml/storage.js:10: TypeError: Cannot call method 'openDatabaseSync' of
undefined
kdevplatform.shell: Could not load plugin "kdevperforce" , it reported the
error: "The variable P4CONFIG is not set. Is perforce installed on the system?"
Disabling the plugin now.
Qt WebEngine seems to be initialized from a plugin. Please set
Qt::AA_ShareOpenGLContexts using QCoreApplication::setAttribute before
constructing QGuiApplication.
/usr/bin/cat:
/home/artg/.local/share/kdevelop/sessions/{8c305343-2f93-407d-9ede-6483394887e6}/default.sh:
No such file or directory
qrc:/qml/storage.js:10: TypeError: Cannot call method 'openDatabaseSync' of
undefined
qrc:/qml/storage.js:10: TypeError: Cannot call method 'openDatabaseSync' of
undefined
Running kdevelop instance (PID: 12,873) detected, making this one visible
instead of starting a new one
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2245, resource
id: 27263325, major code: 40 (TranslateCoords), minor code: 0
register count: 0, destroy count: 0
kdevplatform.shell: Could not load plugin "kdevperforce" , it reported the
error: "The variable P4CONFIG is not set. Is perforce installed on the system?"
Disabling the plugin now.
Qt WebEngine seems to be initialized from a plugin. Please set
Qt::AA_ShareOpenGLContexts using QCoreApplication::setAttribute before
constructing QGuiApplication.
/usr/bin/cat:
/home/artg/.local/share/kdevelop/sessions/{23506f92-cb71-44c5-aafe-efb135d50319}/default.sh:
No such file or directory
qrc:/qml/storage.js:10: TypeError: Cannot call method 'openDatabaseSync' of
undefined
qrc:/qml/storage.js:10: TypeError: Cannot call method 'openDatabaseSync' of
undefined
kf.kio.widgets.kdirmodel: No node found for item that was just removed:
QUrl("file:///home/artg/2021-01-21-09-41-05.086-VBoxSVC-17823.log")
qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 2823, resource
id: 2726, major code: 40 (TranslateCoords), minor code: 0
kf.kio.slaves.file: copy()
QUrl("file:///home/artg/alocal/ajg_stuff/ajg_stuff.kdev4") to
QUrl("file:///tmp/kdevelop.TWjTqj") mode= -1
kf.kio.slaves.file: the file doesn't have any xattr
kdevelop.plugins.cmake: couldn't open CMakeCache.txt
"/home/artg/alocal/ajg_stuff/build-debug/CMakeCache.txt"
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
kdevelop.plugins.clang: Unhandled type: Dependent 
k

[kdevelop] [Bug 454685] updated kdevelop on debian today, crashed while parsing a just imported project

2022-06-01 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=454685

--- Comment #3 from Arthur Gruzauskas  ---
I am running KDevelop-5.6.1-x86_64.AppImage, so no source to play with.

I had compiled git master for a decade or so, then a year ago this crashing
while importing started to happen. The above AppImage worked, so I used it. A
few months ago I tried the version in debian testing, which worked perfectly
till an upgrade arrived today.

I suspect I was using LLVM11 a year ago when the crashing started, but not
certain.

It is now past midnight, and I have to stop. Tomorrow I will add your trial fix
to my git clone and will be compiling with LLVM13 and report back.

Thank you for looking at this issue, I love KDevelop!

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

[kdevelop] [Bug 454685] updated kdevelop on debian today, crashed while parsing a just imported project

2022-06-01 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=454685

--- Comment #4 from Arthur Gruzauskas  ---
Well Igor, that worked! 

Patched builder.cpp in my updated master git clone as suggested, compiled with
LLVM13 on debian testing, all dependencies satisfied. Loaded 3 projects,
parsed, compiled, ran all projects. no issues.

Its worked for 45 mins, before it was always 1~5 mins. I'll be using kdevelop
for a couple hours a day for the next few days and will report back if any
problems.

Assuming all is well, is there anything further I need to do to close this?
This looks like an uncommon issue, specific to some systems, perhaps too few
for it to be a priority. If you want to use my system as a crash test dummy,
I'm happy to try any experiments.

Now I really really need to go to bed. Thank you Igor.

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

[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project

2022-06-01 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=438249

--- Comment #6 from Arthur Gruzauskas  ---
Igor,

I don't use wxWidgets.

What was installed before the crash with the latest debian kdevelop:

2022-05-29 17:57:53 install libkf5configqml5:amd64  5.94.0-3
2022-05-29 17:57:54 install libkf5kcmutilscore5:amd64  5.94.0-2
2022-05-31 01:06:36 install qtbase5-examples:amd64  5.15.2+dfsg-16+b1
2022-05-31 10:05:07 install libqt6multimedia6:amd64  6.2.4-2
2022-05-31 10:05:07 install libqt6multimediaquick6:amd64  6.2.4-2
2022-05-31 10:05:08 install libqt6multimediawidgets6:amd64  6.2.4-2
2022-05-31 10:05:08 install qt6-image-formats-plugins:amd64  6.2.4-2
2022-05-31 10:05:08 install qt6-multimedia-dev:amd64  6.2.4-2
2022-05-31 10:05:08 install qt6-xdgdesktopportal-platformtheme:amd64 
 6.2.4+dfsg-5
2022-06-01 15:45:09 install libsnapd-glib1:amd64  1.60-1
2022-06-01 15:45:10 install kdevelop58-libs:amd64  4:22.04.1-2
2022-06-01 15:45:13 install libkf5prisonscanner5:amd64  5.94.0-2
2022-06-01 16:01:40 install kdevelop-dbgsym:amd64  4:22.04.1-2
2022-06-01 16:01:42 install kdevelop-pg-qt-dbgsym:amd64  2.2.1-2
2022-06-01 16:01:42 install plasma-kdevelop-dbgsym:amd64  4:22.04.1-2
2022-06-01 16:37:47 install kdevelop-data:all  4:22.04.1-2
2022-06-01 16:37:47 install kdevelop58-libs:amd64  4:22.04.1-2
2022-06-01 16:37:48 install kdevelop:amd64  4:22.04.1-2
2022-06-01 16:37:48 install kdevelop-dbgsym:amd64  4:22.04.1-2
2022-06-01 16:37:49 install kdevelop58-libs-dbgsym:amd64  4:22.04.1-2
2022-06-01 16:51:11 install libclang-common-13-dev-dbgsym:amd64  
1:13.0.1-4
2022-06-01 16:51:11 install libclang1-13-dbgsym:amd64  1:13.0.1-4
2022-06-01 16:51:12 install libkf5threadweaver5-dbgsym:amd64  
5.94.0-1
2022-06-01 16:51:12 install libkf5xmlgui-bin-dbgsym:amd64  5.94.0-1
2022-06-01 16:51:12 install libkf5xmlgui-dev-dbgsym:amd64  5.94.0-1
2022-06-01 16:51:13 install libqt5dbus5-dbgsym:amd64  
5.15.2+dfsg-16+b1
2022-06-01 16:51:13 install libqt5qmlmodels5-dbgsym:amd64  
5.15.2+dfsg-10
2022-06-01 16:51:13 install libqt5qmlworkerscript5-dbgsym:amd64  
5.15.2+dfsg-10
2022-06-01 16:51:13 install libqt5widgets5-dbgsym:amd64  
5.15.2+dfsg-16+b1
2022-06-01 16:51:13 install libusbmuxd6-dbgsym:amd64  2.0.2-3
2022-06-01 16:51:13 install qml-module-qtquick-xmllistmodel-dbgsym:amd64 
 5.15.2-3

Arthur

On 2/6/22 5:25 am, Igor Kushnir wrote:
> https://bugs.kde.org/show_bug.cgi?id=438249
>
> --- Comment #5 from Igor Kushnir  ---
>> Hi, I assume the workaround was applying this patch:
> Yes, thank you for confirming.
>
> Since blaming some specific LLVM versions does not figure, we need to find
> something else in common that may be the root cause of this crash. The 
> reporter
> of Bug 431811 indicated that the crash occurred with wxWidgets-3.1.4 but not
> wxWidgets-3.0.4. Arthur, Andrei, do your projects use wxWidgets? Also, when 
> you
> write that the crash started occurring after an update/rebuild of KDevelop,
> were your projects or some libraries they use updated at the same time too?
>
On 2/6/22 5:25 am, Igor Kushnir wrote:
> https://bugs.kde.org/show_bug.cgi?id=438249
>
> --- Comment #5 from Igor Kushnir  ---
>> Hi, I assume the workaround was applying this patch:
> Yes, thank you for confirming.
>
> Since blaming some specific LLVM versions does not figure, we need to find
> something else in common that may be the root cause of this crash. The 
> reporter
> of Bug 431811 indicated that the crash occurred with wxWidgets-3.1.4 but not
> wxWidgets-3.0.4. Arthur, Andrei, do your projects use wxWidgets? Also, when 
> you
> write that the crash started occurring after an update/rebuild of KDevelop,
> were your projects or some libraries they use updated at the same time too?
>

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

[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project

2022-06-02 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=438249

--- Comment #12 from Arthur Gruzauskas  ---
Hi Igor,

Delays in responding to your problem solving request.

Having issues trying to compile clang13 with debian  'apt build-dep', 
which is my first approach as I am somewhat familiar with it.

=> "No ffs implementation found" is the current temporary roadblock. My 
problem, not yours. Unless you already know an obvious solution, of course.

I'm not after any hand holding, I am not just presenting you with the 
original issue and then whining at every small roadblock and then going 
away leaving you with my problem. I'm just saying your request for a 
debugging clang13 requires me to to fill in my own gaps in knowledge, 
which will take as long as it takes.

My motivation is I want a native kdevelop, not some bloody AppImage!

Sorry for the waffling, you can always skim past it 😉

Arthur, who babbles when on an intellectual hunt


On 2/6/22 5:12 pm, Igor Kushnir wrote:
> https://bugs.kde.org/show_bug.cgi?id=438249
>
> --- Comment #7 from Igor Kushnir  ---
> Could someone try to get the backtrace of this crash with assertions enabled?
> (NDEBUG not defined)
> When I navigate through the crash call stacks from
> https://code.woboq.org/llvm/clang/tools/libclang/CXType.cpp.html#374, I see
> several assert() calls, especially here:
> https://code.woboq.org/llvm/clang/lib/AST/ExprConstant.cpp.html#_ZNK5clang4Expr21EvaluateKnownConstIntERKNS_10ASTContextEPN4llvm15SmallVectorImplISt4pairINS_14SourceLocationENS_17PartialDiagnostic
>

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

[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project

2023-02-27 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=438249

Arthur Gruzauskas  changed:

   What|Removed |Added

Version|unspecified |git master
   Platform|Debian stable   |Debian testing

--- Comment #27 from Arthur Gruzauskas  ---
Have been using kdevelop git master successfully for the last 8 months with the
following patch suggested by Igor:

---
--- kdevelop-22.04.1-orig/plugins/clang/duchain/builder.cpp 2022-06-01
21:11:28.907037431 +0300
+++ kdevelop-22.04.1/plugins/clang/duchain/builder.cpp  2022-06-01
21:12:48.177035132 +0300
@@ -1080,7 +1080,7 @@
 #endif

 #if CINDEX_VERSION_MINOR >= 16
-decl->setBitWidth(clang_getFieldDeclBitWidth(cursor));
+decl->setBitWidth(-1);
 #endif

 if (clang_isCursorDefinition(cursor)) {
---

The other day had to reinstall Debian testing, and again the same crash on a
freshly compiled kdevelop git master doing an initial source parse. The above
patch worked yet again.

Happy to supply any info, or do any suggested bug hunting.

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

[Haruna] [Bug 466803] New: Haruna doesn't open .TS videos on startup

2023-03-03 Thread Arthur Kasimov
https://bugs.kde.org/show_bug.cgi?id=466803

Bug ID: 466803
   Summary: Haruna doesn't open .TS videos on startup
Classification: Applications
   Product: Haruna
   Version: 0.10.3
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: generic
  Assignee: georgefb...@gmail.com
  Reporter: kodemeis...@outlook.com
  Target Milestone: ---

SUMMARY
Haruna doesn't play any .TS videos if I open them from a file manager or supply
them via command line. No picture, no sound. It basically acts as if no videos
were opened at all. However, it does play .TS files well when I use "Open File"
from the app itself.

STEPS TO REPRODUCE
1. Download any .TS file, e.g. from https://filesamples.com/formats/ts
2. Try to open the downloaded file via command line: haruna
~/Videos/sample_1280x720_surfing_with_audio.ts

OBSERVED RESULT
Video is not loaded and played.

EXPECTED RESULT
Playback should start upon startup.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux / KDE Plasma on X11
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
This doesn't seem to be related to https://bugs.kde.org/show_bug.cgi?id=464963
I tried different filenames without fancy characters - no luck. The latest
version from master also has the same issue.

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

[Haruna] [Bug 456482] hardware decoding doesn't work

2023-03-03 Thread Arthur Kasimov
https://bugs.kde.org/show_bug.cgi?id=456482

Arthur Kasimov  changed:

   What|Removed |Added

 CC||kodemeis...@outlook.com

--- Comment #16 from Arthur Kasimov  ---
Just wanted to note that QT_XCB_GL_INTEGRATION="xcb_egl" works perfectly for me
on discrete graphics (AMD Radeon RX 6700 XT). Without this variable, Haruna
falls back to suboptimal "vaapi-copy" driver instead of proper "vaapi".

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

[systemsettings] [Bug 488760] New: systemsetting crashes after opening sound twice

2024-06-19 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=488760

Bug ID: 488760
   Summary: systemsetting crashes after opening sound twice
Classification: Applications
   Product: systemsettings
   Version: 6.1.0
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: art...@bols.dev
  Target Milestone: ---

Application: systemsettings (6.1.0)

Qt Version: 6.7.1
Frameworks Version: 6.3.0
Operating System: Linux 6.9.4-200.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora release 40 (Forty)"
DrKonqi: 6.1.0 [CoredumpBackend]

-- Information about the crash:
Systemsettings crashes after opening sound -> switching to a different module
-> sound. This does not seem to occur on other modules.

Not sure if related, but after the update to 6.1.0 the device names in the
sound applet are different. However they have not changed in the settings
module. For example:
HDMI / DisplayPort (GP104 High Definition ...) -> HDMI 0

The crash can be reproduced every time.

-- Backtrace (Reduced):
#5  operator() (__closure=0x55c8d4806090) at
/usr/src/debug/qt6-qtdeclarative-6.7.1-2.fc40.x86_64/src/qmlmodels/qqmldelegatemodel.cpp:1915
#8 
QtPrivate::QCallableObject,
QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=, this_=0x55c8d4806080, r=, a=, ret=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:555
#9  0x7fcfd37fa752 in QtPrivate::QSlotObjectBase::call
(this=0x55c8d4806080, r=, a=0x7ffd929e65b0) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qobjectdefs_impl.h:469
#10 doActivate (sender=0x55c8d50a7c30, signal_index=21,
argv=0x7ffd929e65b0) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qobject.cpp:4086
[...]
#12 0x7fcfd3a00ba0 in QAbstractItemModel::modelReset (this=,
_t1=...) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/redhat-linux-build/src/corelib/Core_autogen/include/moc_qabstractitemmodel.cpp:1112


Reported using DrKonqi

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

[krita] [Bug 489390] New: Dragging and dropping multiple images creates a condition whereby only the 1st file can have an Image > Scale Image To New Size action performed on it

2024-06-28 Thread Arthur K
https://bugs.kde.org/show_bug.cgi?id=489390

Bug ID: 489390
   Summary: Dragging and dropping multiple images creates a
condition whereby only the 1st file can have an Image
> Scale Image To New Size action performed on it
Classification: Applications
   Product: krita
   Version: 5.2.3-beta1
  Platform: Other
OS: Microsoft Windows
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Resize/Scale Image/Layer
  Assignee: krita-bugs-n...@kde.org
  Reporter: akkoz...@gmail.com
  Target Milestone: ---

Version 5.2.3 is not shown as an option but this also reproduces in Beta 5.2.3

SUMMARY
Selecting multiple image files (in my case JPG files) and then drag+dropping
into Krita creates a condition whereby only the 1st file can have an Image >
Scale Image To New Size action performed on it.

STEPS TO REPRODUCE
1. Select multiple test image files (5 or more should do it) and drag and drop
them into Krita for editing
2. Once Krita has loaded all files, perform an Image > Scale Image To New
Size... action on the first test file, save it, then close it with the [X]
close button to move on to the next file
3. Now, try to perform an Image > Scale Image To New Size... action on the next
file

OBSERVED RESULT
The Image > Scale Image To New Size... action is unavailable on subsequent
files

EXPECTED RESULT
The Image > Scale Image To New Size... action is available on all subsequent
files

SOFTWARE/OS VERSIONS
Windows: Win 10 x64 fully patched June 2024

ADDITIONAL INFORMATION
Don't remember this being an issue in 5.2.2

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

[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel

2023-12-11 Thread Arthur Huillet
https://bugs.kde.org/show_bug.cgi?id=452219

--- Comment #49 from Arthur Huillet  ---
Can you try setting __GL_HWSTATE_PER_CTX=1?

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

[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel

2023-12-11 Thread Arthur Huillet
https://bugs.kde.org/show_bug.cgi?id=452219

--- Comment #50 from Arthur Huillet  ---
(In reply to Arthur Huillet from comment #49)
> Can you try setting __GL_HWSTATE_PER_CTX=1?

Sorry, I notice I had asked a similar question back in October already.

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

[kcalc] [Bug 488462] modulo dividing button text is too long to fit in desired button width

2024-06-13 Thread Arthur Tadier
https://bugs.kde.org/show_bug.cgi?id=488462

Arthur Tadier  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||art...@atadier.net
 Resolution|--- |DUPLICATE

--- Comment #1 from Arthur Tadier  ---
This translation issue has already been reported in Bug 452828. Thanks

*** This bug has been marked as a duplicate of bug 452828 ***

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

[i18n] [Bug 452828] Fedora 35

2024-06-13 Thread Arthur Tadier
https://bugs.kde.org/show_bug.cgi?id=452828

Arthur Tadier  changed:

   What|Removed |Added

 CC||krz.piechow...@outlook.com

--- Comment #1 from Arthur Tadier  ---
*** Bug 488462 has been marked as a duplicate of this bug. ***

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

[dolphin] [Bug 488458] error when MTP device name contains slash

2024-06-13 Thread Arthur Tadier
https://bugs.kde.org/show_bug.cgi?id=488458

Arthur Tadier  changed:

   What|Removed |Added

 CC||art...@atadier.net
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Arthur Tadier  ---
Confirmed in Frameworks 6.2.0, it seems to me that there is a wrongful
assumption the device name will be a valid path name.

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

[Haruna] [Bug 488468] Settings dialog has no minimum width and height

2024-06-13 Thread Arthur Tadier
https://bugs.kde.org/show_bug.cgi?id=488468

Arthur Tadier  changed:

   What|Removed |Added

 CC||art...@atadier.net

--- Comment #1 from Arthur Tadier  ---
I could reproduce the issue in GNOME Wayland but not in Plasma, so the issue is
specific to that environment.

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

[Haruna] [Bug 485720] Freezes completely when opening a video

2024-04-18 Thread Arthur Kasimov
https://bugs.kde.org/show_bug.cgi?id=485720

Arthur Kasimov  changed:

   What|Removed |Added

 CC||kodemeis...@outlook.com

--- Comment #1 from Arthur Kasimov  ---
I have the same issue. After updating to MPV 0.38 all videos are played in a
separate MPV window that appears above the main Haruna window. It seems like
QML <=> MPV integration is broken. Downgrading to MPV 0.37 fixes the bug.

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

[konsole] [Bug 484386] New: Solarised theme inconsistent black/gray

2024-03-24 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=484386

Bug ID: 484386
   Summary: Solarised theme inconsistent black/gray
Classification: Applications
   Product: konsole
   Version: 23.08.5
  Platform: unspecified
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: font
  Assignee: konsole-de...@kde.org
  Reporter: art...@bols.dev
  Target Milestone: ---

SUMMARY
Solarised theme doesn't show "gray/bright black" `\x1b[90m` color. This color
is shown on all other themes, where "black" `\x1b[30m` is used as background
color.

This issue is a duplicate of #366143 but I believe it should be solved. It is
really difficult for CLI developers to be compatible with all themes and
terminals, and inconsistency doesn't help. For example, in the python termcolor
library, "black/grey" is invisible on most dark themes, but "dark_grey" is
shown, except when using the Solarised theme. So this means to be compatible
with all Konsole themes, it is not possible to use a greyish color.

This also causes a different problem where my cursor is sometimes not visible.
Overall it's not a good experience.


STEPS TO REPRODUCE
1. Switch to breeze theme
2. echo -ne '\x1b[30mBLACK\x1b[0m' 
3. echo -ne '\x1b[90mGREY\x1b[0m'
4. Switch to Solarised theme

OBSERVED RESULT
- They "BLACK" text is invisible and GREY is visible when using the breeze
theme
- They "BLACK" text is slightly visible and GREY is invisible when using the
solarised theme

EXPECTED RESULT
- They "BLACK" text is invisible and GREY is visible when using the solarised
theme

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora Linux 39
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12

ADDITIONAL INFORMATION

I would be happy to open a pull request with the needed changes, if this issue
is accepted.

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

[konsole] [Bug 484386] Solarised theme inconsistent black/gray

2024-03-24 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=484386

--- Comment #2 from Arthur Bols  ---
(In reply to Tammes Burghard from comment #1)
> I can confirm that these colors are visible/invisible as you describe. But,
> as far as I know, Solarized is a third party theme not provided by KDE, so
> we can't do anything about it here and you will have to ask the theme's
> developer instead. Where did you get the theme from?

I believe this is built-in?
https://invent.kde.org/utilities/konsole/-/blob/release/24.02/data/color-schemes/Solarized.colorscheme

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

[plasmashell] [Bug 446379] New: Accidental resizing

2021-12-02 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=446379

Bug ID: 446379
   Summary: Accidental resizing
   Product: plasmashell
   Version: 5.23.4
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: art...@bols.dev
CC: mikel5...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 144148
  --> https://bugs.kde.org/attachment.cgi?id=144148&action=edit
Example screenshots

SUMMARY
Often, I open kickoff by pressing the meta key accidentally when I want to move
a window with meta+left/up/right/down. This causes kickoff to be moved and
resized as if it's a window. When closing and reopening kickoff, it will be in
it's original place, but resized to the new size. This can only be fixed when
logging out and back in. 


STEPS TO REPRODUCE
1. Open kickoff
2. Press meta+left/up/right/down
3. Close kickoff
4. Reopen kickoff

OBSERVED RESULT
Kickoff is moved as if it's a windows according to meta+left/up/right/down and
resized.
After reopening, kickoff is back in it's original place, but still at the
modified size.

EXPECTED RESULT
2 options:
- Kickoff would not be moved and resized
- after reopening, it would be back to it's original size.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.14.18-200.fc34.x86_64 / KDE Plasma 
(available in About System)
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
I'm not using the official fedora RPMs, but a copr repo for newer plasma
versions: https://copr.fedorainfracloud.org/coprs/zawertun/kde/

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

[plasmashell] [Bug 446379] Resizing with snapping/tiling shortcuts

2021-12-02 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=446379

Arthur Bols  changed:

   What|Removed |Added

Summary|Accidental resizing |Resizing with
   ||snapping/tiling shortcuts

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

[plasmashell] [Bug 446379] Resizing with snapping/tiling shortcuts

2021-12-03 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=446379

--- Comment #2 from Arthur Bols  ---
(In reply to Nate Graham from comment #1)
> 
> *** This bug has been marked as a duplicate of bug 411462 ***

I think it's similar to bug 402614. I looked more into it and it seems the fix
was removed when Kickoff was rewritten. I'm trying to test it, but I'm
currently stuck trying to build plasma-workspace.

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

[plasmashell] [Bug 444880] New: Unfolded icon only applet does not close after drag-and-dropping a Firefox tab

2021-11-03 Thread Arthur Schiwon
https://bugs.kde.org/show_bug.cgi?id=444880

Bug ID: 444880
   Summary: Unfolded icon only applet does not close after
drag-and-dropping a Firefox tab
   Product: plasmashell
   Version: 5.23.2
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager and Icons-Only Task Manager
  Assignee: h...@kde.org
  Reporter: bli...@arthur-schiwon.de
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 143170
  --> https://bugs.kde.org/attachment.cgi?id=143170&action=edit
Window picker when open, after it was supposed to be closed

SUMMARY

When a firefox tab is moved to a different windows via the icon-only task
manager, the window selection does not close again.

STEPS TO REPRODUCE
1. Have two or more Firefox (94) windows open
2. Drag a tab from one firefox window…
3. …hover over the icon-only task manager entry of firefox until the window
selector unfolds…
4. …drop the tab over the selected window

OBSERVED RESULT

The tab is moved to the new window and the window picker of the icon-only task
manager is closed again.

EXPECTED RESULT

The window picker stays open. Clicking elsewhere, clicking on one of the
windows, or pressing escape does not close it. 
Changing to a different virtual desktop and back closes it though.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

On Wayland, Intel graphics.

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

[plasmashell] [Bug 444880] Unfolded icon only applet does not close after drag-and-dropping a Firefox tab

2021-11-08 Thread Arthur Schiwon
https://bugs.kde.org/show_bug.cgi?id=444880

--- Comment #2 from Arthur Schiwon  ---
(In reply to Nate Graham from comment #1)
> Hmm, on Wayland I can't even make the popup appear at all by dragging a tab
> over it. :/

This still works for me. Would screencast, but cannot find anything to
screencast with (that does not pull in several gnome deps at least).

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

[konsole] [Bug 437689] Konsole crashed on exit

2021-06-12 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=437689

--- Comment #1 from Arthur Bols  ---
Created attachment 139259
  --> https://bugs.kde.org/attachment.cgi?id=139259&action=edit
New crash information added by DrKonqi

konsole (21.04.2) using Qt 5.15.2

- What I was doing when the application crashed:

Exiting Konsole by pressing CTRL+D or `exit`

-- Backtrace (Reduced):
#4  Konsole::PlainTextDecoder::decodeLine (this=,
characters=, count=) at
/usr/src/debug/konsole5-21.04.2-1.fc34.x86_64/src/decoders/PlainTextDecoder.cpp:106
#5  0x7fd8e373fffd in Konsole::TerminalDisplay::inputMethodQuery
(this=0x557e2cf02ca0, query=) at
/usr/src/debug/konsole5-21.04.2-1.fc34.x86_64/src/terminalDisplay/TerminalDisplay.cpp:2375
#6  0x7fd8e2bf8d3c in QWidget::event(QEvent*) () from
/lib64/libQt5Widgets.so.5
#7  0x7fd8e2bb7e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /lib64/libQt5Widgets.so.5
#8  0x7fd8e3c3ff48 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /lib64/libQt5Core.so.5

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

[konsole] [Bug 437689] Konsole crashed on exit

2021-06-12 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=437689

Arthur Bols  changed:

   What|Removed |Added

 CC||art...@bols.dev

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

[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project

2021-06-14 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=438249

Arthur Gruzauskas  changed:

   What|Removed |Added

 CC||deb...@gruz.net

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

[konsole] [Bug 417326] The cursor is drawn one pixel off its expected Y-coordinate

2020-11-04 Thread Arthur Kasimov
https://bugs.kde.org/show_bug.cgi?id=417326

--- Comment #7 from Arthur Kasimov  ---
Hi Justin, I can still reproduce the issue using the latest git master. It is
not very noticeable though. There is just 1-pixel gap after all, so I used to
live with it :)

Looking at the code, character classes were recently moved to new
terminalDisplay directory. Nevertheless, the cursor adjustment code that
produces a gap is still there - in TerminalPainter::drawCursor.

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

[systemsettings] [Bug 428461] System setting crashed after closing it while at screen locker appearance settings.

2020-11-18 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=428461

Arthur Bols  changed:

   What|Removed |Added

 CC||art...@bols.dev

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

[systemsettings] [Bug 428461] System setting crashed after closing it while at screen locker appearance settings.

2020-11-18 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=428461

--- Comment #4 from Arthur Bols  ---
Created attachment 133445
  --> https://bugs.kde.org/attachment.cgi?id=133445&action=edit
New crash information added by DrKonqi

systemsettings5 (5.20.2) using Qt 5.15.1

- What I was doing when the application crashed:

After opening "Screen Locking" Appearance, closing or switching to anything
else than "Screen Locking" crashes systemsettings

Full disclosure, I'm using the zawertun/kde copr repo.
https://copr.fedorainfracloud.org/coprs/zawertun/kde/

-- Backtrace (Reduced):
#4  0x7f39adf67fba in QQmlData::wasDeleted (object=0x55c8ea8e6990) at
../../include/QtQml/5.15.1/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:338
#5  QV4::QObjectWrapper::getQmlProperty (engine=0x55c8ea251a50,
qmlContext=0x55c8e83cf000, object=0x55c8ea8e6990, name=0x7f396dfb05e8,
revisionMode=QV4::QObjectWrapper::CheckRevision, hasProperty=0x7ffe84b45e58,
property=0x7ffe84b45e60) at jsruntime/qv4qobjectwrapper.cpp:360
#6  0x7f39adf4bde1 in QV4::QQmlContextWrapper::getPropertyAndBase
(resource=, id=..., receiver=,
hasProperty=0x7ffe84b45f07, base=0x0, lookup=0x0) at
jsruntime/qv4qmlcontext.cpp:316
#7  0x7f39adf4d703 in
QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter
(l=0x55c8eaaa3e00, engine=0x55c8ea251a50, base=0x0) at
jsruntime/qv4qmlcontext.cpp:481
#8  0x7f39adf81348 in QV4::Moth::VME::interpret (frame=0x7ffe84b46220,
engine=0x55c8ea251a50, code=0x7f397499ca0b "\030\n(N\030\r\247a\001") at
jsruntime/qv4vme_moth.cpp:585

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

[konqueror] [Bug 24820] visited links don't change colour until after they are hovered over with the mouse.

2023-12-26 Thread Arthur Tadier
https://bugs.kde.org/show_bug.cgi?id=24820

Arthur Tadier  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED
 CC||art...@atadier.net

--- Comment #39 from Arthur Tadier  ---
Cannot reproduce in 22.12.3, it most certainly has been fixed.

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

[kwin] [Bug 452219] Low fps and high CPU usage on external monitor connected to NVIDIA when default GPU is Intel

2023-10-16 Thread Arthur Huillet
https://bugs.kde.org/show_bug.cgi?id=452219

Arthur Huillet  changed:

   What|Removed |Added

 CC||arthur.huillet+kdebugs@free
   ||.fr

--- Comment #40 from Arthur Huillet  ---
Does the problem go away if you set __GL_HWSTATE_PER_CTX=2?

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

[kdevelop] [Bug 475924] New: kdevelop recently crashing while editing

2023-10-21 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=475924

Bug ID: 475924
   Summary: kdevelop recently crashing while editing
Classification: Applications
   Product: kdevelop
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: deb...@gruz.net
  Target Milestone: ---

Application: kdevelop (5.13.231170 (23.11.70))

Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.0-13-amd64 x86_64
Windowing System: X11
Distribution: Debian GNU/Linux 12 (bookworm)
DrKonqi: 5.27.5 [KCrashBackend]

-- Information about the crash:
Recently seen repeated crashes while editing code. Every few hours. 
In the last week or two, have seen the top crash trace entries seem to been
dealing with an atomic value whenever I looked at the trace. I'm guessing it is
the same error.
compiled from git master on clang-16 on debian stable. 
Happy to supply any info or do any tests, as I love kdevelop.

The crash can be reproduced sometimes.

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault

[KCrash Handler]
#4  std::__atomic_base::load (__m=std::memory_order_relaxed,
this=0x2a0038) at /usr/include/c++/12/bits/atomic_base.h:486
#5  QAtomicOps::loadRelaxed (_q_value=) at
../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239
#6  QBasicAtomicInteger::loadRelaxed (this=0x2a0038) at
../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107
#7  QWeakPointer::internalData (this=0x55ff79472470) at
../../include/QtCore/../../src/corelib/tools/qsharedpointer_impl.h:698
#8  QPointer::data (this=0x55ff79472470) at
../../include/QtCore/../../src/corelib/kernel/qpointer.h:77
#9  QPointer::operator QObject* (this=0x55ff79472470) at
../../include/QtCore/../../src/corelib/kernel/qpointer.h:83
#10 QAccessibleObject::object (this=0x55ff79472440) at
accessible/qaccessibleobject.cpp:100
#11 0x7f2b003b618a in QAccessibleWidget::isValid (this=0x55ff79472440) at
accessible/qaccessiblewidget.cpp:219
#12 0x7f2aff906848 in QAccessibleEvent::accessibleInterface
(this=0x7ffcb4b13610) at accessible/qaccessible.cpp:1764
#13 0x7f2aff906d6d in QAccessible::updateAccessibility
(event=0x7ffcb4b13610) at accessible/qaccessible.cpp:861
#14 0x7f2afcdf84ae in KateViewInternal::cursorMoved (this=)
at ./src/view/kateviewinternal.cpp:4637
#15 KateViewInternal::cursorMoved (this=) at
./src/view/kateviewinternal.cpp:4630
#16 0x7f2afcdfefb6 in KateViewInternal::updateCursor
(this=this@entry=0x55ff76c472d0, newCursor=newCursor@entry=...,
force=force@entry=false, center=center@entry=false,
calledExternally=calledExternally@entry=false, scroll=scroll@entry=true) at
./src/view/kateviewinternal.cpp:2786
#17 0x7f2afce01378 in KateViewInternal::placeCursor (this=0x55ff76c472d0,
p=..., keepSelection=, updateSelection=) at
./src/view/kateviewinternal.cpp:3051
#18 0x7f2afce069f8 in KateViewInternal::mousePressEvent
(this=0x55ff76c472d0, e=0x7ffcb4b13c90) at ./src/view/kateviewinternal.cpp:3498
#19 0x7f2b001a4db8 in QWidget::event (this=0x55ff76c472d0,
event=0x7ffcb4b13c90) at kernel/qwidget.cpp:9044
#20 0x7f2b00162fae in QApplicationPrivate::notify_helper
(this=this@entry=0x55ff72e99760, receiver=receiver@entry=0x55ff76c472d0,
e=e@entry=0x7ffcb4b13c90) at kernel/qapplication.cpp:3640
#21 0x7f2b0016b552 in QApplication::notify (this=,
receiver=0x55ff76c472d0, e=) at kernel/qapplication.cpp:3084
#22 0x7f2aff4b16f8 in QCoreApplication::notifyInternal2
(receiver=0x55ff76c472d0, event=0x7ffcb4b13c90) at
kernel/qcoreapplication.cpp:1064
#23 0x7f2aff4b18ce in QCoreApplication::sendSpontaneousEvent
(receiver=, event=) at
kernel/qcoreapplication.cpp:1474
#24 0x7f2b0016965e in QApplicationPrivate::sendMouseEvent
(receiver=receiver@entry=0x55ff76c472d0, event=event@entry=0x7ffcb4b13c90,
alienWidget=, nativeWidget=0x55ff735528d0,
buttonDown=buttonDown@entry=0x7f2b006a69f0 ,
lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at
kernel/qapplication.cpp:2622
#25 0x7f2b001bdbd8 in QWidgetWindow::handleMouseEvent
(this=this@entry=0x55ff746eec00, event=event@entry=0x7ffcb4b13f40) at
kernel/qwidgetwindow.cpp:683
#26 0x7f2b001c0f60 in QWidgetWindow::event (this=0x55ff746eec00,
event=0x7ffcb4b13f40) at kernel/qwidgetwindow.cpp:300
#27 0x7f2b00162fae in QApplicationPrivate::notify_helper (this=, receiver=0x55ff746eec00, e=0x7ffcb4b13f40) at
kernel/qapplication.cpp:3640
#28 0x7f2aff4b16f8 in QCoreApplication::notifyInternal2
(receiver=0x55ff746eec00, event=0x7ffcb4b13f40) at
kernel/qcoreapplication.cpp:1064
#29 0x7f2aff4b18ce in QCoreApplication::sendSpontaneousEvent
(receiver=, event=) at
kernel/qcoreapplication.cpp:1474
#30 0x7f2aff93d3ed in QGuiApplicationPrivate::processMouseEvent
(e=0x55ff7

[kdeplasma-addons] [Bug 448606] New: Alt+Tab to fullscreen app keeps visualization

2022-01-16 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=448606

Bug ID: 448606
   Summary: Alt+Tab to fullscreen app keeps visualization
   Product: kdeplasma-addons
   Version: 5.23.5
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: General
  Assignee: plasma-b...@kde.org
  Reporter: art...@bols.dev
  Target Milestone: ---

SUMMARY
When switching tasks using Alt+Tab with the "Thumbnail Grid" visualization
(wait a bit until the visualization pops up) to a fullscreen application, the
visualization doesn't go completely away until something changes on the screen
(try scrolling). It only fades a bit.

This does not occur with the "breeze" visualization.

STEPS TO REPRODUCE
1. Set Task Switcher visualization to "Thumbnail Grid"
2. Open an application as fullscreen (for example okular)
3. Switch to a different application
4. Try switching to the fullscreen application. Only release alt-tab when the
visualization is completely shown.

OBSERVED RESULT
Visualization doesn't go away completely.

EXPECTED RESULT
Visualization goes away

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 35
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2
Kernel Version: 5.15.13-200.fc35.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 7,5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

ADDITIONAL INFORMATION
I was unable to screenshot it with spectacle (even using a timer).

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

[plasmashell] [Bug 442543] "Unable to assign [undefined] to bool" warnings all over journalctl

2022-01-02 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=442543

Arthur Bols  changed:

   What|Removed |Added

 CC||art...@bols.dev

--- Comment #1 from Arthur Bols  ---
Have the same problem, it's a wayland issue.

The problem is that the KModifierKeyInfoProvider for wayland is unfinished and
only hardcodes 3 keys:
https://github.com/KDE/kwayland-integration/blob/master/src/kmodifierkeyinfoprovider/kmodifierkeyinfoprovider_wayland.cpp#L33

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

[kdeplasma-addons] [Bug 448606] Alt+Tab to fullscreen app keeps visualization

2022-01-22 Thread Arthur Bols
https://bugs.kde.org/show_bug.cgi?id=448606

--- Comment #2 from Arthur Bols  ---
I can reproduce it with all switchers except for "breeze" and "fedora". I tried
to test it with different applications, and I thought I could reproduce it with
firefox, but currently it only occurs with okular, but consistently (100% of
the time).

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

[ktimetracker] [Bug 416693] Moving a subtask to another higher-order task scrambles time data of all tasks

2020-09-07 Thread Arthur Schiwon
https://bugs.kde.org/show_bug.cgi?id=416693

Arthur Schiwon  changed:

   What|Removed |Added

 CC||bli...@arthur-schiwon.de

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

[kdevelop] [Bug 438249] New: fresh kdevelop build from git master source crashes while importing a project

2021-06-08 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=438249

Bug ID: 438249
   Summary: fresh kdevelop build from git master source crashes
while importing a project
   Product: kdevelop
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: deb...@gruz.net
  Target Milestone: ---

Application: kdevelop (5.6.40)

Qt Version: 5.15.2
Frameworks Version: 5.78.0
Operating System: Linux 5.10.0-7-amd64 x86_64
Windowing system: X11
Distribution: Debian GNU/Linux 11 (bullseye)

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

i used 'rm -r $HOME/.local/share/kdevelop/; rm -r /$HOME/.cache/kdevduchain/;
rm $HOME/.config/kdeveloprc' to get rid of all state that I know about.

build kdevelop from git master source using a shell script that has worked for
years. No missing Recommendations.

set my usual defaults in Settings. Then import a known project. Crashes while
importing the project doing an initial source file parse.

Been crashing for months. The same project loaded into a clean environment like
the first line above using KDevelop-5.6.1-x86_64.AppImage works fine. Been
using the AppImage successfully for many months now.

The help page in the crash handler was not clear to me, but today worked out
how to find the dbgsym files needed for this report.

I'm happy to help with any info or testing, I love kdevelop!

Arthur

The crash can be reproduced every time.

-- Backtrace (Reduced):
#4  __memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:405
#5  0x7fbf02cd02d7 in APInt () at
/build/llvm-toolchain-11-HMpQvg/llvm-toolchain-11-11.0.1/llvm/include/llvm/ADT/APInt.h:325
#6  APSInt () at
/build/llvm-toolchain-11-HMpQvg/llvm-toolchain-11-11.0.1/llvm/include/llvm/ADT/APSInt.h:21
#7  EvaluateKnownConstInt() () at
/build/llvm-toolchain-11-HMpQvg/llvm-toolchain-11-11.0.1/clang/lib/AST/ExprConstant.cpp:14368
#8  0x7fbf02c76345 in getBitWidthValue() () at
/build/llvm-toolchain-11-HMpQvg/llvm-toolchain-11-11.0.1/clang/lib/AST/Decl.cpp:4030


Possible duplicates by query: bug 436863, bug 434799, bug 431811, bug 410586,
bug 386527.

Reported using DrKonqi

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

[kdevelop] [Bug 438249] fresh kdevelop build from git master source crashes while importing a project

2021-06-08 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=438249

--- Comment #1 from Arthur Gruzauskas  ---
Created attachment 139104
  --> https://bugs.kde.org/attachment.cgi?id=139104&action=edit
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.

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

[Akonadi] [Bug 358267] Incoming mail moved to Trash immediately

2021-03-09 Thread Arthur Schiwon
https://bugs.kde.org/show_bug.cgi?id=358267

--- Comment #3 from Arthur Schiwon  ---
Hi Justin,

thanks to getting back to me five years after reporting a data-loosing issue. I
am sure you understand I stopped using kmail and lost trust in the
maintainership in the meantime. I do not know whether the issue persists.

Cheers
Arthur

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

[kdevelop] [Bug 409561] New: kdevelop crashes while using the menu item Commit...

2019-07-06 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=409561

Bug ID: 409561
   Summary: kdevelop crashes while using the menu item Commit...
   Product: kdevelop
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: deb...@gruz.net
  Target Milestone: ---

Application: kdevelop (5.3.40)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.19.0-5-amd64 x86_64
Distribution: Debian GNU/Linux 10 (buster)

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

start up kdevelop, wait for any parsing to finish, attempt Commit..., and it
crashes

-- Backtrace:
Application: KDevelop (kdevelop), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fe6ba3471c0 (LWP 57624))]

Thread 44 (Thread 0x7fe5f97fa700 (LWP 57805)):
#0  0x7fe6cd66a00c in futex_wait_cancelable (private=0, expected=0,
futex_word=0x55979c647f74) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fe6cd66a00c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55979c647f20, cond=0x55979c647f48) at pthread_cond_wait.c:502
#2  0x7fe6cd66a00c in __pthread_cond_wait (cond=0x55979c647f48,
mutex=0x55979c647f20) at pthread_cond_wait.c:655
#3  0x7fe6ce8b825b in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fe6d1305d30 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fe6d1309ae8 in  () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fe6d1304e3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fe6d1307bb9 in ThreadWeaver::Thread::run() () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fe6ce8b7aa7 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fe6cd663fa3 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fe6ce40a4cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 43 (Thread 0x7fe5f9ffb700 (LWP 57804)):
#0  0x7fe6cd66a00c in futex_wait_cancelable (private=0, expected=0,
futex_word=0x55979c647f74) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fe6cd66a00c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55979c647f20, cond=0x55979c647f48) at pthread_cond_wait.c:502
#2  0x7fe6cd66a00c in __pthread_cond_wait (cond=0x55979c647f48,
mutex=0x55979c647f20) at pthread_cond_wait.c:655
#3  0x7fe6ce8b825b in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fe6d1305d30 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fe6d1309ae8 in  () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fe6d1304e3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fe6d1307bb9 in ThreadWeaver::Thread::run() () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fe6ce8b7aa7 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fe6cd663fa3 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fe6ce40a4cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 42 (Thread 0x7fe5fa7fc700 (LWP 57803)):
#0  0x7fe6cd66a00c in futex_wait_cancelable (private=0, expected=0,
futex_word=0x55979c647f74) at ../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fe6cd66a00c in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55979c647f20, cond=0x55979c647f48) at pthread_cond_wait.c:502
#2  0x7fe6cd66a00c in __pthread_cond_wait (cond=0x55979c647f48,
mutex=0x55979c647f20) at pthread_cond_wait.c:655
#3  0x7fe6ce8b825b in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7fe6d1305d30 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7fe6d1309ae8 in  () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7fe6d1304e3d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7fe6d1307bb9 in ThreadWeaver::Thread::run() () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7fe6ce8b7aa7 in  () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fe6cd663fa3 in start_thread (arg=) at
pthread_create.c:486
#10 0x7fe6ce40a4cf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 41 (Thread 0x7fe5faffd700 (LWP 57802)):
#0  0x7fe

[kdevelop] [Bug 409561] kdevelop crashes while using the menu item Commit...

2019-07-06 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=409561

--- Comment #1 from Arthur Gruzauskas  ---
running kdevelop from git master. this crash is consistently happening the last
few weeks.

Im on debian buster. tried recompiling from a fresh git master, same crash.

Previous crashes generated ~300k files, so couldn't send due to the 65K limit
for a bug report. Crash seems to be in the same place in those larger files.

doing a commit via gitk works, so may not be a git issue directly.

Happy to help with more info.

Arthur

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

[kdevelop] [Bug 409561] kdevelop crashes while using the menu item Commit...

2019-07-06 Thread Arthur Gruzauskas
https://bugs.kde.org/show_bug.cgi?id=409561

Arthur Gruzauskas  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|REPORTED|RESOLVED

--- Comment #2 from Arthur Gruzauskas  ---
a kdevelop update just minutes ago, which included a patchreview update, seems
to have resolved this issue.

Thank you,

Arthur

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

[ksmserver] [Bug 364593] Crash on logout after Nvidia driver update

2020-05-05 Thread Arthur Huillet
https://bugs.kde.org/show_bug.cgi?id=364593

Arthur Huillet  changed:

   What|Removed |Added

 CC||arthur.huillet+kdebugs@free
   ||.fr

--- Comment #23 from Arthur Huillet  ---
I am not sure what is being referred to as "the driver announcing that it
supports OpenGL". I assume this is from interpreting the values of some
glGetString queries.
Note that GL context creation can legally fail for various reasons, regardless
of what glGetString returns. It not valid to assume that because glGetString
returns anything specific, then context creation will or must not fail.
The application therefore ought to handle the context creation error
gracefully, and it seems invalid - at least with the evidence on this thread -
to call that a NVIDIA driver bug.
It is certainly less than optimal behavior that the context creation fails, but
that is not a bug, and, unfortunately, unlikely to change in the near future.

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

[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting

2020-01-07 Thread Arthur Moore
https://bugs.kde.org/show_bug.cgi?id=385880

Arthur Moore  changed:

   What|Removed |Added

 CC||arthur.moore@cd-net.net

--- Comment #22 from Arthur Moore  ---
I also experience this issue.  Everything works correctly on Plasma, but not
Plasma Wayland.

Of interest is there is a little menu button in the left hand corner of each
window.  When clicking that it opens a small window with each of the menu
options.  Clicking on sub menus opens up additional windows.

Operating System: KDE neon Testing Edition
KDE Plasma Version: 5.17.4
KDE Frameworks Version: 5.66.0
Qt Version: 5.13.2
Kernel Version: 4.15.0-74-generic
OS Type: 64-bit

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

[konsole] [Bug 417326] New: The cursor is drawn one pixel off its expected Y-coordinate

2020-02-09 Thread Arthur Kasimov
https://bugs.kde.org/show_bug.cgi?id=417326

Bug ID: 417326
   Summary: The cursor is drawn one pixel off its expected
Y-coordinate
   Product: konsole
   Version: master
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: konsole-de...@kde.org
  Reporter: kodemeis...@outlook.com
  Target Milestone: ---

Created attachment 125775
  --> https://bugs.kde.org/attachment.cgi?id=125775&action=edit
Screenshot of gap 1

When Konsole draws the cursor, it always shifts down cursor Y position by one
pixel. Usually it is not noticeable but in some applications, e.g. Vim, it
produces an annoying gap on highlighted background.

For example, when you search a text in Vim, it highlights all occurrences of
that text in a file. When you place the cursor over the highlighted text, a
small but noticeable gap appears. Another example is highlighting of matching
parentheses which reveals the same gap. Please check the attached screenshots.

The adjustment of cursor position is located in TerminalDisplay::drawCursor:

// shift rectangle top down one pixel to leave some space
// between top and bottom
QRectF cursorRect = rect.adjusted(0, 1, 0, 0);

Not sure whether this adjustment is still useful for some purposes or not. 
Shouldn't we simply remove it?

Thanks!

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

[konsole] [Bug 417326] The cursor is drawn one pixel off its expected Y-coordinate

2020-02-09 Thread Arthur Kasimov
https://bugs.kde.org/show_bug.cgi?id=417326

--- Comment #1 from Arthur Kasimov  ---
Created attachment 125776
  --> https://bugs.kde.org/attachment.cgi?id=125776&action=edit
Screenshot of gap 2

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

[konsole] [Bug 417326] The cursor is drawn one pixel off its expected Y-coordinate

2020-02-09 Thread Arthur Kasimov
https://bugs.kde.org/show_bug.cgi?id=417326

--- Comment #2 from Arthur Kasimov  ---
Created attachment 125777
  --> https://bugs.kde.org/attachment.cgi?id=125777&action=edit
Remove adjustment of the cursor rectangle to avoid unwanted gaps

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

[konsole] [Bug 417326] The cursor is drawn one pixel off its expected Y-coordinate

2020-02-10 Thread Arthur Kasimov
https://bugs.kde.org/show_bug.cgi?id=417326

--- Comment #4 from Arthur Kasimov  ---
Indeed, the comment to the code says it is intentional but the result looks
buggy. In most other terminal emulators the cursor height is the same as line
height without any gaps.

I checked further and seems like this code was added while fixing another bug
https://bugs.kde.org/show_bug.cgi?id=343283

The last commenter also wonders why the cursor is shifted down by one pixel.
Seems like it was just an arbitrary choice without a clear reason. I believe it
would be better to remove the gap and draw the cursor just like other terminal
emulators do.

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

[konsole] [Bug 407915] The "Custom character color" option is required in "Cursor" tab

2020-02-11 Thread Arthur Kasimov
https://bugs.kde.org/show_bug.cgi?id=407915

Arthur Kasimov  changed:

   What|Removed |Added

 Resolution|--- |FIXED
  Latest Commit||https://invent.kde.org/kde/
   ||konsole/commit/a7f23d216e80
   ||20020e9061b058a44d48b39f9f0
   ||8
   Version Fixed In||20.04
 Status|CONFIRMED   |RESOLVED

--- Comment #3 from Arthur Kasimov  ---
Git commit a7f23d216e8020020e9061b058a44d48b39f9f08 by Arthur Kasimov.
Committed on 10/02/2020 at 20:57.
Pushed by hindenburg into branch 'master'.

Add an option to set the custom color of text under the cursor

Current version of Konsole allows to select the custom color of the
cursor (Settings -> Edit Current Profile -> Appearance -> Cursor ->
Custom cursor color). This works well for I-Beam and Underline cursor
shapes. But for block-shaped cursors the text under the cursor is often
hard to read, e.g. bright text under the bright cursor or dark text
under the dark cursor.

This patch adds an ability to select the custom color of the character
under the cursor. The character uses this color only when the cursor
shape is Block and Konsole window is focused. Otherwise the character
uses its foreground color as usual.
FIXED-IN: 20.04

M  +72   -31   src/EditProfileAppearancePage.ui
M  +11   -6src/EditProfileDialog.cpp
M  +1-0src/EditProfileDialog.h
M  +3-1src/Profile.cpp
M  +12   -1src/Profile.h
M  +23   -17   src/TerminalDisplay.cpp
M  +21   -2src/TerminalDisplay.h
M  +2-0src/autotests/ProfileTest.cpp

https://invent.kde.org/kde/konsole/commit/a7f23d216e8020020e9061b058a44d48b39f9f08

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

[konsole] [Bug 407915] The "Custom character color" option is required in "Cursor" tab

2020-02-11 Thread Arthur Kasimov
https://bugs.kde.org/show_bug.cgi?id=407915

Arthur Kasimov  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/kde/ |https://commits.kde.org/kon
   |konsole/commit/a7f23d216e80 |sole/a7f23d216e8020020e9061
   |20020e9061b058a44d48b39f9f0 |b058a44d48b39f9f08
   |8   |

--- Comment #4 from Arthur Kasimov  ---
Git commit a7f23d216e8020020e9061b058a44d48b39f9f08 by Arthur Kasimov.
Committed on 10/02/2020 at 20:57.
Pushed by scmsync into branch 'master'.

Add an option to set the custom color of text under the cursor

Current version of Konsole allows to select the custom color of the
cursor (Settings -> Edit Current Profile -> Appearance -> Cursor ->
Custom cursor color). This works well for I-Beam and Underline cursor
shapes. But for block-shaped cursors the text under the cursor is often
hard to read, e.g. bright text under the bright cursor or dark text
under the dark cursor.

This patch adds an ability to select the custom color of the character
under the cursor. The character uses this color only when the cursor
shape is Block and Konsole window is focused. Otherwise the character
uses its foreground color as usual.
FIXED-IN: 20.04

M  +72   -31   src/EditProfileAppearancePage.ui
M  +11   -6src/EditProfileDialog.cpp
M  +1-0src/EditProfileDialog.h
M  +3-1src/Profile.cpp
M  +12   -1src/Profile.h
M  +23   -17   src/TerminalDisplay.cpp
M  +21   -2src/TerminalDisplay.h
M  +2-0src/autotests/ProfileTest.cpp

https://commits.kde.org/konsole/a7f23d216e8020020e9061b058a44d48b39f9f08

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

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

2019-12-07 Thread Arthur Peters
https://bugs.kde.org/show_bug.cgi?id=373232

--- Comment #157 from Arthur Peters  ---
(In reply to Ahmad Samir from comment #156)
> Shouldn't that be "1.299"? (. vs ,); I haven't looked at the code, but
> "1,299" is most likely either going to be treated as invalid or as just
> integer 1.

Locale affects parsing as well as printing, so in the, say, de_DE locale a ','
may well parse as a decimal separator instead of a "thousands" separator. This
is true of most European locales I think. So the original poster of the config
was probably correct for their own machine, but for yours you might need to use
a '.' (if you are in en_US for instance).

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

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

2019-12-02 Thread Arthur Peters
https://bugs.kde.org/show_bug.cgi?id=373232

--- Comment #150 from Arthur Peters  ---
(In reply to lukebenes from comment #149)
> (In reply to Nate Graham from comment #140)
> > Because of the nature of floating point math and various Qt and X11 bugs,
> > limiting the
> > scale factor increment to 0.0625 (6.25% in percentage form) will improve 
> > the display in many apps.
> 
> Was  0.0625 found by trial and error? Any experts in floating point math on
> this list? Wondering if this is the right magic number or if the correct
> solution is to convert everything to integer math. If so, what would the
> right magic number/flick[1] be for this case.  
> 
> [1]
> https://mux.com/blog/in-defense-of-flicks-or-how-i-learned-to-stop-worrying-
> and-love-70560/

0.0625 is exactly 1/16. This makes it representable in very few bits in binary
floating point. This is very different from 0.1 which must be approximated and
that approximation contains information in all of the mantissa bits. For
example, in 64-bit floating point 0.1 + 0.1 + 0.1 == 0.30004. This
kind of very slight difference is an issue since it tends to *change* as you
add or subtract from the number. This means that certain arithmetic is
"numerically unstable" meaning (roughly) that small errors due to floating
point compound through an algorithm. For example,

(0.1 - 1024 + 1024) / 0.1 = 1.2274
(0.1 - 1100 + 1100) / 0.1 - 0.0905

However if we use 1/16 this is much better,

>>> (0.0625 - 1024 + 1024) / 0.0625
1.0
>>> (0.0625 - 1100 + 1100) / 0.0625
1.0

This is where the "various Qt and X11 bugs" come in: display code should not do
much in floating point (as you recommend), or it should avoid accumulating
values and even be careful with multiplication. However, the code probably does
all these things (accumulating the height of lines to find where the next line
should be placed maybe be part of this specific bug). 

By limiting using scaling factors that are less susceptible to these issues
will help avoid the bugs. I don't know how 1/16 was chosen though, using 1/32
or 1/64 would have similar results but have less of a safety margin to resist
numerical instability. That said, I think 1/16 is plenty small for real use. I
doubt any one needs a scaling of 33/32 and will not be happy with 34/32 =
17/16.

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

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

2018-08-21 Thread Arthur Peters
https://bugs.kde.org/show_bug.cgi?id=373232

Arthur Peters  changed:

   What|Removed |Added

 CC||a...@singingwizard.org

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

[kde] [Bug 391326] New: konqueror crashes on plasma startup

2018-03-03 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=391326

Bug ID: 391326
   Summary: konqueror crashes on plasma startup
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: arthur.ma...@internode.on.net
  Target Milestone: ---

Application: kdeinit5 (5.0.97)

Qt Version: 5.9.2
Frameworks Version: 5.42.0
Operating System: Linux 4.16.0-rc3+ x86_64
Distribution: Debian GNU/Linux testing/unstable

-- Information about the crash:
Similar to recently, although I don't remember leaving konqueror running when
closing downa a previous session, konqueror attempted to start and crashed when
I logged into plasma desktop

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konqueror (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3dc695c780 (LWP 4302))]

Thread 26 (Thread 0x7f3d2d7fa700 (LWP 4504)):
#0  0x7f3db7476188 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#1  0x7f3db74790ab in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#2  0x7f3db7479449 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#3  0x7f3db7479ccf in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#4  0x7f3db78e2338 in pa_mainloop_dispatch () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f3db78e270e in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f3db78e2790 in pa_mainloop_run () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7f3db78f05f9 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#8  0x7f3db7489c58 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#9  0x7f3dc2f0051a in start_thread (arg=0x7f3d2d7fa700) at
pthread_create.c:465
#10 0x7f3dc4a7f3ef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 25 (Thread 0x7f3d2dffb700 (LWP 4503)):
#0  0x7f3dc2f06b2c in futex_reltimed_wait_cancelable (private=, reltime=0x7f3d2dffa9d0, expected=0, futex_word=0x7f3d2dffab58) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f3dc2f06b2c in __pthread_cond_wait_common (abstime=0x7f3d2dffaa70,
mutex=0x7f3d2dffab08, cond=0x7f3d2dffab30) at pthread_cond_wait.c:533
#2  0x7f3dc2f06b2c in __pthread_cond_timedwait (cond=0x7f3d2dffab30,
mutex=0x7f3d2dffab08, abstime=0x7f3d2dffaa70) at pthread_cond_wait.c:667
#3  0x7f3d6e561fa2 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f3d6e5291be in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f3d6e503ddb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f3d6e500658 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f3d6e51d09b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f3d6e534d96 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f3d6e530e9b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7f3dc2f0051a in start_thread (arg=0x7f3d2dffb700) at
pthread_create.c:465
#11 0x7f3dc4a7f3ef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 24 (Thread 0x7f3d2e7fc700 (LWP 4502)):
#0  0x7f3dc2f067fd in futex_wait_cancelable (private=,
expected=0, futex_word=0x560fb55e95b8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f3dc2f067fd in __pthread_cond_wait_common (abstime=0x0,
mutex=0x560fb55e94f8, cond=0x560fb55e9590) at pthread_cond_wait.c:502
#2  0x7f3dc2f067fd in __pthread_cond_wait (cond=0x560fb55e9590,
mutex=0x560fb55e94f8) at pthread_cond_wait.c:655
#3  0x7f3d6ecb6f50 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f3d6e5347d1 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f3d6e530e9b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f3dc2f0051a in start_thread (arg=0x7f3d2e7fc700) at
pthread_create.c:465
#7  0x7f3dc4a7f3ef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 23 (Thread 0x7f3d2effd700 (LWP 4501)):
#0  0x7f3dc2f067fd in futex_wait_cancelable (private=,
expected=0, futex_word=0x560fb56d4ab8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f3dc2f067fd in __pthread_cond_wait_common (abstime=0x0,
mutex=0x560fb56d4a68, cond=0x560fb56d4a90) at pthread_cond_wait.c:502
#2  0x7f3dc2f067fd in __pthread_cond_wait (cond=0x560fb56d4a90,
mutex=0x560fb56d4a68) at pthread_cond_wait.c:655
#3  0x7f3d6e533555 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f3d6e533a37 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f3d6e5347d1 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngine

[frameworks-kxmlgui] [Bug 337491] KDEPlatformTheme plugin causes text artifacts in Qt 5 application

2018-03-05 Thread Arthur Schiwon
https://bugs.kde.org/show_bug.cgi?id=337491

Arthur Schiwon  changed:

   What|Removed |Added

 CC||bli...@arthur-schiwon.de

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

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

2018-03-16 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=391944

Bug ID: 391944
   Summary: konqueror crash on plasmashell start-up
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: arthur.ma...@internode.on.net
  Target Milestone: ---

Application: kdeinit5 (5.0.97)

Qt Version: 5.9.2
Frameworks Version: 5.42.0
Operating System: Linux 4.16.0-rc5+ x86_64
Distribution: Debian GNU/Linux testing/unstable

-- Information about the crash:
even though I hadn't been running konqueror in previous session, found a crash
after  starting plasmashell after a reboot.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konqueror (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0981f54780 (LWP 4242))]

Thread 27 (Thread 0x7f08ecff9700 (LWP 4506)):
#0  0x7f097e4fa4ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x55f975f9362c) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f097e4fa4ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55f975f935d8, cond=0x55f975f93600) at pthread_cond_wait.c:502
#2  0x7f097e4fa4ec in __pthread_cond_wait (cond=0x55f975f93600,
mutex=0x55f975f935d8) at pthread_cond_wait.c:655
#3  0x7f0929c86ba5 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f0929c87087 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f0929c87e21 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f0929c844fb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f097e4f45aa in start_thread (arg=0x7f08ecff9700) at
pthread_create.c:463
#8  0x7f0980074cbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7f08ed7fa700 (LWP 4500)):
#0  0x7f0972a24165 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#1  0x7f0972a2509d in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#2  0x7f0972a25449 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#3  0x7f0972a25ccf in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#4  0x7f0972e8e338 in pa_mainloop_dispatch () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f0972e8e70e in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f0972e8e790 in pa_mainloop_run () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7f0972e9c5f9 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#8  0x7f0972a35c58 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#9  0x7f097e4f45aa in start_thread (arg=0x7f08ed7fa700) at
pthread_create.c:463
#10 0x7f0980074cbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 25 (Thread 0x7f08edffb700 (LWP 4499)):
#0  0x7f097e4fa81a in futex_reltimed_wait_cancelable (private=, reltime=0x7f08edffa9d0, expected=0, futex_word=0x7f08edffab58) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f097e4fa81a in __pthread_cond_wait_common (abstime=0x7f08edffaa70,
mutex=0x7f08edffab08, cond=0x7f08edffab30) at pthread_cond_wait.c:533
#2  0x7f097e4fa81a in __pthread_cond_timedwait (cond=0x7f08edffab30,
mutex=0x7f08edffab08, abstime=0x7f08edffaa70) at pthread_cond_wait.c:667
#3  0x7f0929cb5552 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f0929c7c82e in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f0929c574bb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f0929c53d38 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f0929c7070b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f0929c883e6 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f0929c844fb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7f097e4f45aa in start_thread (arg=0x7f08edffb700) at
pthread_create.c:463
#11 0x7f0980074cbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 24 (Thread 0x7f08ee7fc700 (LWP 4498)):
#0  0x7f097e4fa4ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x55f975f2d8b8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f097e4fa4ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55f975f2d7f8, cond=0x55f975f2d890) at pthread_cond_wait.c:502
#2  0x7f097e4fa4ec in __pthread_cond_wait (cond=0x55f975f2d890,
mutex=0x55f975f2d7f8) at pthread_cond_wait.c:655
#3  0x7f092a40c8b0 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f0929c87e21 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f0929c844fb in  () at
/usr/lib/x86_64-l

[kde] [Bug 392348] New: konqueror crashes on plasma desktop startup

2018-03-26 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=392348

Bug ID: 392348
   Summary: konqueror crashes on plasma desktop startup
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: arthur.ma...@internode.on.net
  Target Milestone: ---

Application: kdeinit5 (5.0.97)

Qt Version: 5.9.2
Frameworks Version: 5.44.0
Operating System: Linux 4.16.0-rc7 x86_64
Distribution: Debian GNU/Linux testing/unstable

-- Information about the crash:
although I had been running konqueror in the previous plasma desktop session, I
had quit konqueror before logging out.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konqueror (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fde2e352780 (LWP 26049))]

Thread 28 (Thread 0x7fdd67fff700 (LWP 26369)):
#0  0x7fde2a8f84ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x55bf472e51a8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fde2a8f84ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55bf472e5158, cond=0x55bf472e5180) at pthread_cond_wait.c:502
#2  0x7fde2a8f84ec in __pthread_cond_wait (cond=0x55bf472e5180,
mutex=0x55bf472e5158) at pthread_cond_wait.c:655
#3  0x7fddd2be3ba5 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fddd2be4087 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fddd2be4e21 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fddd2be14fb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fde2a8f25aa in start_thread (arg=0x7fdd67fff700) at
pthread_create.c:463
#8  0x7fde2c473cbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 27 (Thread 0x7fdd98ff9700 (LWP 26368)):
#0  0x7fde2a8f84ec in futex_wait_cancelable (private=,
expected=0, futex_word=0x55bf472e51a8) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7fde2a8f84ec in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55bf472e5158, cond=0x55bf472e5180) at pthread_cond_wait.c:502
#2  0x7fde2a8f84ec in __pthread_cond_wait (cond=0x55bf472e5180,
mutex=0x55bf472e5158) at pthread_cond_wait.c:655
#3  0x7fddd2be3ba5 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fddd2be4087 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fddd2be4e21 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fddd2be14fb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fde2a8f25aa in start_thread (arg=0x7fdd98ff9700) at
pthread_create.c:463
#8  0x7fde2c473cbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 26 (Thread 0x7fdd997fa700 (LWP 26367)):
#0  0x7fde2c4695d9 in __GI___poll (fds=0x7fdd74007030, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7fde1f28f6b1 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#2  0x7fde1f281070 in pa_mainloop_poll () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#3  0x7fde1f281700 in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7fde1f281790 in pa_mainloop_run () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7fde1f28f5f9 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7fde1ee28c58 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#7  0x7fde2a8f25aa in start_thread (arg=0x7fdd997fa700) at
pthread_create.c:463
#8  0x7fde2c473cbf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 25 (Thread 0x7fdd99ffb700 (LWP 26366)):
#0  0x7fde2a8f881a in futex_reltimed_wait_cancelable (private=, reltime=0x7fdd99ffa9d0, expected=0, futex_word=0x7fdd99ffab58) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7fde2a8f881a in __pthread_cond_wait_common (abstime=0x7fdd99ffaa70,
mutex=0x7fdd99ffab08, cond=0x7fdd99ffab30) at pthread_cond_wait.c:533
#2  0x7fde2a8f881a in __pthread_cond_timedwait (cond=0x7fdd99ffab30,
mutex=0x7fdd99ffab08, abstime=0x7fdd99ffaa70) at pthread_cond_wait.c:667
#3  0x7fddd2c12552 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7fddd2bd982e in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7fddd2bb44bb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7fddd2bb0d38 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7fddd2bcd70b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7fddd2be53e6 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7fddd2be14fb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7fde2a8f25aa in start_thread (arg=0x7fdd99ffb700) at

[kde] [Bug 390603] New: konqueror crash on plasma start-up

2018-02-17 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=390603

Bug ID: 390603
   Summary: konqueror crash on plasma start-up
   Product: kde
   Version: unspecified
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: unassigned-b...@kde.org
  Reporter: arthur.ma...@internode.on.net
  Target Milestone: ---

Application: kdeinit5 (5.0.97)

Qt Version: 5.9.2
Frameworks Version: 5.42.0
Operating System: Linux 4.16.0-rc1+ x86_64
Distribution: Debian GNU/Linux testing/unstable

-- Information about the crash:
- What I was doing when the application crashed: Logged into plasma desktop -
as far as I known konqueror wasn't set to automatically start but it did and
crashed.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konqueror (kdeinit5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8ada850780 (LWP 4288))]

Thread 26 (Thread 0x7f8a39ffb700 (LWP 4501)):
#0  0x7f8ad6dfa7fd in futex_wait_cancelable (private=,
expected=0, futex_word=0x560b6107bb78) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f8ad6dfa7fd in __pthread_cond_wait_common (abstime=0x0,
mutex=0x560b6107bb28, cond=0x560b6107bb50) at pthread_cond_wait.c:502
#2  0x7f8ad6dfa7fd in __pthread_cond_wait (cond=0x560b6107bb50,
mutex=0x560b6107bb28) at pthread_cond_wait.c:655
#3  0x7f8a7ebb6555 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f8a7ebb6a37 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f8a7ebb77d1 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f8a7ebb3e9b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f8ad6df451a in start_thread (arg=0x7f8a39ffb700) at
pthread_create.c:465
#8  0x7f8ad89733ef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 25 (Thread 0x7f8a3a7fc700 (LWP 4500)):
#0  0x7f8acb3780bd in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#1  0x7f8acb378449 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#2  0x7f8acb378ccf in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#3  0x7f8acb7e1338 in pa_mainloop_dispatch () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f8acb7e170e in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f8acb7e1790 in pa_mainloop_run () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f8acb7ef5f9 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7f8acb388c58 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so
#8  0x7f8ad6df451a in start_thread (arg=0x7f8a3a7fc700) at
pthread_create.c:465
#9  0x7f8ad89733ef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 24 (Thread 0x7f8a3affd700 (LWP 4499)):
#0  0x7f8ad6dfab2c in futex_reltimed_wait_cancelable (private=, reltime=0x7f8a3affc9d0, expected=0, futex_word=0x7f8a3affcb58) at
../sysdeps/unix/sysv/linux/futex-internal.h:142
#1  0x7f8ad6dfab2c in __pthread_cond_wait_common (abstime=0x7f8a3affca70,
mutex=0x7f8a3affcb08, cond=0x7f8a3affcb30) at pthread_cond_wait.c:533
#2  0x7f8ad6dfab2c in __pthread_cond_timedwait (cond=0x7f8a3affcb30,
mutex=0x7f8a3affcb08, abstime=0x7f8a3affca70) at pthread_cond_wait.c:667
#3  0x7f8a7ebe4fa2 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f8a7ebac1be in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f8a7eb86ddb in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f8a7eb83658 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#7  0x7f8a7eba009b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#8  0x7f8a7ebb7d96 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#9  0x7f8a7ebb3e9b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#10 0x7f8ad6df451a in start_thread (arg=0x7f8a3affd700) at
pthread_create.c:465
#11 0x7f8ad89733ef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 23 (Thread 0x7f8a3b7fe700 (LWP 4498)):
#0  0x7f8ad6dfa7fd in futex_wait_cancelable (private=,
expected=0, futex_word=0x560b6117e528) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f8ad6dfa7fd in __pthread_cond_wait_common (abstime=0x0,
mutex=0x560b6117e468, cond=0x560b6117e500) at pthread_cond_wait.c:502
#2  0x7f8ad6dfa7fd in __pthread_cond_wait (cond=0x560b6117e500,
mutex=0x560b6117e468) at pthread_cond_wait.c:655
#3  0x7f8a7f339f50 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#4  0x7f8a7ebb77d1 in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#5  0x7f8a7ebb3e9b in  () at
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
#6  0x7f8ad6df451a i

[kde] [Bug 390603] konqueror crash on plasma start-up

2018-02-23 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=390603

--- Comment #1 from Arthur Marsh  ---
Created attachment 110932
  --> https://bugs.kde.org/attachment.cgi?id=110932&action=edit
New crash information added by DrKonqi

kdeinit5 (5.0.97) using Qt 5.9.2

- What I was doing when the application crashed: started plasma desktop from
lxdm with konsole as the only automatically restarted application.

-- Backtrace (Reduced):
#6  0x7fb7f1e53058 in KonqView::url() const () at
/usr/lib/x86_64-linux-gnu/libkdeinit5_konqueror.so
#7  0x7fb7f1e88867 in KonqMainWindow::isPreloaded() const () at
/usr/lib/x86_64-linux-gnu/libkdeinit5_konqueror.so
#8  0x7fb7f1ebded9 in
KonqSessionManager::saveCurrentSessionToFile(KConfig*, QList
const&) () at /usr/lib/x86_64-linux-gnu/libkdeinit5_konqueror.so
#9  0x7fb7f1ebe185 in KonqSessionManager::autoSaveSession() () at
/usr/lib/x86_64-linux-gnu/libkdeinit5_konqueror.so
[...]
#11 0x7fb8027e2827 in QTimer::timeout(QTimer::QPrivateSignal) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

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

[kde] [Bug 390603] konqueror crash on plasma start-up

2018-02-23 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=390603

Arthur Marsh  changed:

   What|Removed |Added

 CC||arthur.ma...@internode.on.n
   ||et

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

[filelight] [Bug 339037] Filelight still scan across filesystem boudaries if that opinion is not checked

2017-01-19 Thread Arthur Flôr
https://bugs.kde.org/show_bug.cgi?id=339037

Arthur Flôr  changed:

   What|Removed |Added

 CC||arthurflo...@gmail.com

--- Comment #2 from Arthur Flôr  ---
Same problem. Using 1.21 on Arch Linux with KDE.

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

[filelight] [Bug 375324] New: Do not scan folders function

2017-01-19 Thread Arthur Flôr
https://bugs.kde.org/show_bug.cgi?id=375324

Bug ID: 375324
   Summary: Do not scan folders function
   Product: filelight
   Version: 1.21
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: martin.sandsm...@kde.org
  Reporter: arthurflo...@gmail.com
  Target Milestone: ---

The function "Do not scan these folders:" doesn't work on 1.21 version.

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

[plasmashell] [Bug 375605] New: plasmashell crash and restart when quitting transmission and firefox

2017-01-27 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=375605

Bug ID: 375605
   Summary: plasmashell crash and restart when quitting
transmission and firefox
   Product: plasmashell
   Version: 5.8.5
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: arthur.ma...@internode.on.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.10.0-rc5+ x86_64
Distribution: Debian GNU/Linux 9.0 (stretch)

-- Information about the crash:
- What I was doing when the application crashed:
Quit transmission and firefox then plasmashell panel disappeared.

The crash can be reproduced sometimes.

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

Thread 9 (Thread 0x7fa19d71d700 (LWP 4564)):
#0  0x7fa24e3be010 in g_mutex_unlock (mutex=0x7fa19990) at
././glib/gthread-posix.c:1349
#1  0x7fa24e377ed0 in g_main_context_prepare
(context=context@entry=0x7fa19990, priority=priority@entry=0x7fa19d71ccc0)
at ././glib/gmain.c:3499
#2  0x7fa24e37891b in g_main_context_iterate
(context=context@entry=0x7fa19990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909
#3  0x7fa24e378b0c in g_main_context_iteration (context=0x7fa19990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7fa25331002b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa2532b998a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa2530e70f3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa2530ebda8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa2521ff424 in start_thread (arg=0x7fa19d71d700) at
pthread_create.c:333
#9  0x7fa252a059bf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 8 (Thread 0x7fa19df1e700 (LWP 4563)):
#0  0x7fa24e3bdfe9 in g_mutex_lock (mutex=mutex@entry=0x7fa198000990) at
././glib/gthread-posix.c:1336
#1  0x7fa24e378576 in g_main_context_dispatch
(context=context@entry=0x7fa198000990) at ././glib/gmain.c:3850
#2  0x7fa24e378a60 in g_main_context_iterate
(context=context@entry=0x7fa198000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3929
#3  0x7fa24e378b0c in g_main_context_iteration (context=0x7fa198000990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7fa25331002b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa2532b998a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa2530e70f3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa19e36ea35 in  () at
/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#8  0x7fa2530ebda8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7fa2521ff424 in start_thread (arg=0x7fa19df1e700) at
pthread_create.c:333
#10 0x7fa252a059bf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7fa22db54700 (LWP 4559)):
#0  0x7fa25220514f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa22f00d40b in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7fa22f00d267 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7fa2521ff424 in start_thread (arg=0x7fa22db54700) at
pthread_create.c:333
#4  0x7fa252a059bf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7fa238bb7700 (LWP 4558)):
#0  0x7fa25220514f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa257b6c2c4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fa257b6c309 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fa2521ff424 in start_thread (arg=0x7fa238bb7700) at
pthread_create.c:333
#4  0x7fa252a059bf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7fa23a9b7700 (LWP 4557)):
#0  0x7fa2529f85bd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa24e3bcc40 in read (__nbytes=16, __buf=0x7fa23a9b6bc0,
__fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x7fa24e3bcc40 in g_wakeup_acknowledge (wakeup=0x7fa230002390) at
././glib/gwakeup.c:210
#3  0x7fa24e3784be in g_main_context_check
(context=context@entry=0x7fa228000990, max_priority=2147483647,
fds=fds@entry=0x7fa228003070, n_fds=n_fds@entry=

[telepathy] [Bug 365990] Taskbar Entry does not work for messages in incoming chat

2017-02-11 Thread Arthur Schiwon
https://bugs.kde.org/show_bug.cgi?id=365990

Arthur Schiwon  changed:

   What|Removed |Added

 CC||bli...@arthur-schiwon.de

--- Comment #2 from Arthur Schiwon  ---
I confirm. Also same behaviour with Konversation and Quassel. So I assume it is
not Telepathy related but … somewhere deeper in KDE. Plasma perhaps?

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

[kdenlive] [Bug 375713] Kdenlive crashes if GPU processing (Movit library) is enabled

2018-01-18 Thread Arthur Huillet
https://bugs.kde.org/show_bug.cgi?id=375713

Arthur Huillet  changed:

   What|Removed |Added

 CC||arthur.huillet+kdebugs@free
   ||.fr

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

[yakuake] [Bug 385882] Yakuake Wayland: when launching Yakuake the second time it appears in the middle of the screen

2017-11-10 Thread Arthur Schiwon
https://bugs.kde.org/show_bug.cgi?id=385882

Arthur Schiwon  changed:

   What|Removed |Added

 CC||bli...@arthur-schiwon.de

--- Comment #4 from Arthur Schiwon  ---
Also similar strange behaviour (from Arch packages): first time it is almost
okay,  it starts too high, first 2½ lines are behind my the panel (it's on the
top), subsequentially the height is OK, however it is not centered anymore, but
on the left edge.

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

[frameworks-kwayland] [Bug 373907] Implement Wayland Primary Selection Protocol (middle-click paste)

2017-11-10 Thread Arthur Schiwon
https://bugs.kde.org/show_bug.cgi?id=373907

Arthur Schiwon  changed:

   What|Removed |Added

 CC||bli...@arthur-schiwon.de

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

[plasmashell] [Bug 372789] Plasma freezes with black screen when logging out

2017-11-10 Thread Arthur Schiwon
https://bugs.kde.org/show_bug.cgi?id=372789

Arthur Schiwon  changed:

   What|Removed |Added

 CC||bli...@arthur-schiwon.de

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

[kwin] [Bug 386811] No way to change cursor speed in Wayland

2017-11-12 Thread Arthur Țițeică
https://bugs.kde.org/show_bug.cgi?id=386811

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@cloud.titeica.ro

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

[krunner] [Bug 385693] krunner text input broken with wayland

2017-11-12 Thread Arthur Țițeică
https://bugs.kde.org/show_bug.cgi?id=385693

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@cloud.titeica.ro

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

[Touchpad-KCM] [Bug 387153] libinput-backend touchpad KCM only used on Wayland

2017-11-25 Thread Arthur Țițeică
https://bugs.kde.org/show_bug.cgi?id=387153

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@cloud.titeica.ro

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

[systemsettings] [Bug 404175] New: System settings crashes on startup

2019-02-10 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=404175

Bug ID: 404175
   Summary: System settings crashes on startup
   Product: systemsettings
   Version: 5.14.5
  Platform: Debian unstable
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: arthur.ma...@internode.on.net
  Target Milestone: ---

Application: systemsettings5 (5.14.5)

Qt Version: 5.11.3
Frameworks Version: 5.54.0
Operating System: Linux 4.20.0 x86_64
Distribution: Devuan GNU/Linux beowulf/ceres

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

I had only attempted to open system settings from plasmashell and it crashed
immediately.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f13b8930cc0 (LWP 4982))]

Thread 10 (Thread 0x7f139e7fc700 (LWP 4991)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x5600fafc45e0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5600fafc4590,
cond=0x5600fafc45b8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5600fafc45b8, mutex=0x5600fafc4590) at
pthread_cond_wait.c:655
#3  0x7f13ae8e0052 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f13ae8dfc17 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f13bc144fa3 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f13bdaa580f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 9 (Thread 0x7f139effd700 (LWP 4990)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x5600fafc45e0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5600fafc4590,
cond=0x5600fafc45b8) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5600fafc45b8, mutex=0x5600fafc4590) at
pthread_cond_wait.c:655
#3  0x7f13ae8e0052 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f13ae8dfc17 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f13bc144fa3 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f13bdaa580f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 8 (Thread 0x7f139f7fe700 (LWP 4989)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x5600fafc4060) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5600fafc4010,
cond=0x5600fafc4038) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5600fafc4038, mutex=0x5600fafc4010) at
pthread_cond_wait.c:655
#3  0x7f13ae8e0052 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f13ae8dfc17 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f13bc144fa3 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f13bdaa580f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7f139700 (LWP 4988)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x5600fafc4064) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5600fafc4010,
cond=0x5600fafc4038) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5600fafc4038, mutex=0x5600fafc4010) at
pthread_cond_wait.c:655
#3  0x7f13ae8e0052 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f13ae8dfc17 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f13bc144fa3 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f13bdaa580f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7f13acf19700 (LWP 4987)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x5600fafc4064) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5600fafc4010,
cond=0x5600fafc4038) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5600fafc4038, mutex=0x5600fafc4010) at
pthread_cond_wait.c:655
#3  0x7f13ae8e0052 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f13ae8dfc17 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f13bc144fa3 in start_thread (arg=) at
pthread_create.c:486
#6  0x7f13bdaa580f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7f13ad71a700 (LWP 4986)):
#0  futex_wait_cancelable (private=0, expected=0, futex_word=0x5600fa84e868) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x5600fa84e818,
cond=0x5600fa84e840) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x5600fa84e840, mutex=0x5600fa84e818) at
pthread_cond_wait.c:655

[kdeplasma-addons] [Bug 379347] Long filenames get truncated in the Recent Documents section

2017-05-22 Thread Arthur Țițeică
https://bugs.kde.org/show_bug.cgi?id=379347

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@titeica.ro

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

[kdeplasma-addons] [Bug 369064] Application Dashboard isn't always showing icons under "Applications" area (screenshot included)

2017-05-22 Thread Arthur Țițeică
https://bugs.kde.org/show_bug.cgi?id=369064

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@titeica.ro

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

[kwin] [Bug 380902] kwin effects like "present windows" can't be exited with the keyboard

2017-06-11 Thread Arthur Schiwon
https://bugs.kde.org/show_bug.cgi?id=380902

Arthur Schiwon  changed:

   What|Removed |Added

 CC||bli...@arthur-schiwon.de

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

[plasmashell] [Bug 402010] New: Plasma Panel Freezes in "grayed-out" state

2018-12-11 Thread Arthur Peters
https://bugs.kde.org/show_bug.cgi?id=402010

Bug ID: 402010
   Summary: Plasma Panel Freezes in "grayed-out" state
   Product: plasmashell
   Version: 5.13.5
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: a...@singingwizard.org
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.13.5)

Qt Version: 5.11.1
Frameworks Version: 5.50.0
Operating System: Linux 4.18.0-12-generic x86_64
Distribution: Ubuntu 18.10

-- Information about the crash:
- What I was doing when the application crashed:
Clicking "Disable this popup" on the special clipboard handling popup menu that
appears when Ctrl-C is pressed.
I killed plasma with "kquitapp5 plasmashell"

- Unusual behavior I noticed:
The panel was in the "grayed-out" state where no buttons work; as if it has
displayed a model dialog. The K menu could still be activated using the hotkey
for it (windows key for me), but I could not select any items in that menu and
had to hit the hot key again to get it to disappear.

The crash can be reproduced sometimes.

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

Thread 37 (Thread 0x7f9c17fff700 (LWP 12948)):
#0  0x7f9c7ae298e2 in pa_pstream_unref () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so
#1  0x7f9c7ae29e19 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so
#2  0x7f9c7ae2a66a in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so
#3  0x7f9c7ae94568 in pa_mainloop_dispatch () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#4  0x7f9c7ae9483c in pa_mainloop_iterate () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#5  0x7f9c7ae948e0 in pa_mainloop_run () at
/usr/lib/x86_64-linux-gnu/libpulse.so.0
#6  0x7f9c7aea28f9 in  () at /usr/lib/x86_64-linux-gnu/libpulse.so.0
#7  0x7f9c7ae3a6f8 in  () at
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-12.2.so
#8  0x7f9d585a8164 in start_thread (arg=) at
pthread_create.c:486
#9  0x7f9d5872adef in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 36 (Thread 0x7f9c317fa700 (LWP 21987)):
#0  0x7f9d585ae2eb in futex_wait_cancelable (private=,
expected=0, futex_word=0x55a54f42cec4) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  0x7f9d585ae2eb in __pthread_cond_wait_common (abstime=0x0,
mutex=0x55a54f42ce70, cond=0x55a54f42ce98) at pthread_cond_wait.c:502
#2  0x7f9d585ae2eb in __pthread_cond_wait (cond=0x55a54f42ce98,
mutex=0x55a54f42ce70) at pthread_cond_wait.c:655
#3  0x7f9d58a5343b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9c8002c810 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f9c800305c8 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f9c8002b91d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f9c80030622 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f9c8002b91d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f9c80030622 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f9c8002b91d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7f9c80030622 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#12 0x7f9c8002b91d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#13 0x7f9c80030622 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#14 0x7f9c8002b91d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#15 0x7f9c80030622 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#16 0x7f9c8002b91d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#17 0x7f9c80030622 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#18 0x7f9c8002b91d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#19 0x7f9c80030622 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#20 0x7f9c8002b91d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-g

[plasmashell] [Bug 402010] Plasma Panel Freezes in "grayed-out" state after attempting to disable copy popup menu

2018-12-11 Thread Arthur Peters
https://bugs.kde.org/show_bug.cgi?id=402010

Arthur Peters  changed:

   What|Removed |Added

Summary|Plasma Panel Freezes in |Plasma Panel Freezes in
   |"grayed-out" state  |"grayed-out" state after
   ||attempting to disable copy
   ||popup menu

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

[plasmashell] [Bug 402010] Plasma Panel Freezes in "grayed-out" state after attempting to disable copy popup menu

2018-12-11 Thread Arthur Peters
https://bugs.kde.org/show_bug.cgi?id=402010

Arthur Peters  changed:

   What|Removed |Added

 CC||a...@singingwizard.org

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

[konsole] [Bug 196998] Konsole should reflow the text when resizing

2017-08-13 Thread Arthur Țițeică
https://bugs.kde.org/show_bug.cgi?id=196998

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@titeica.ro

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

[telepathy] [Bug 365990] Taskbar Entry does not work for messages in incoming chat

2017-02-13 Thread Arthur Schiwon
https://bugs.kde.org/show_bug.cgi?id=365990

--- Comment #3 from Arthur Schiwon  ---
(In reply to Arthur Schiwon from comment #2)
> I confirm. Also same behaviour with Konversation and Quassel. So I assume it
> is not Telepathy related but … somewhere deeper in KDE. Plasma perhaps?

Ah, sorry, I need to withdraw that statement. I expected the icons in the tray
to change, because I am not using a taskbar. Misread this option :(

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

[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration

2017-02-18 Thread Arthur Țițeică
https://bugs.kde.org/show_bug.cgi?id=179678

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@titeica.ro

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

[plasmashell] [Bug 376743] New: plasmashell crashed when quitting firefox

2017-02-20 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=376743

Bug ID: 376743
   Summary: plasmashell crashed when quitting firefox
   Product: plasmashell
   Version: 5.8.5
  Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: arthur.ma...@internode.on.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.10.0 x86_64
Distribution: Debian GNU/Linux 9.0 (stretch)

-- Information about the crash:
I have about 1000 tabs open across about 20 windows in firefox. When I quit
firefox, the plasmashell crashed and restarted.

The crash can be reproduced sometimes.

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

Thread 17 (Thread 0x7f590e7fc700 (LWP 4808)):
#0  0x7f59f2b0d14f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f59f39f4c6b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f594062ad50 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f594062ef88 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f5940629ecd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f594062efe2 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f5940629ecd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f594062efe2 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f5940629ecd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9  0x7f594062cd99 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f59f39f3da8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f59f2b07424 in start_thread (arg=0x7f590e7fc700) at
pthread_create.c:333
#12 0x7f59f330d9bf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 16 (Thread 0x7f590effd700 (LWP 4807)):
#0  0x7f59f2b0d14f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f59f39f4c6b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f594062ad50 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f594062ef88 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f5940629ecd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f594062efe2 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f5940629ecd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f594062cd99 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f59f39f3da8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f59f2b07424 in start_thread (arg=0x7f590effd700) at
pthread_create.c:333
#10 0x7f59f330d9bf in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 15 (Thread 0x7f590f7fe700 (LWP 4806)):
#0  0x7f59f2b0d14f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f59f39f4c6b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f594062ad50 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#3  0x7f594062ef88 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#4  0x7f5940629ecd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#5  0x7f594062efe2 in  () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6  0x7f5940629ecd in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7  0x7f594062cd99 in ThreadWeaver::Thread::run() () at
/usr/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8  0x7f59f39f3da8 in  () at /u

[Akonadi] [Bug 342498] akonadi_archivemail_agent crashed while archiving shortly befor ending

2017-02-26 Thread Arthur Țițeică
https://bugs.kde.org/show_bug.cgi?id=342498

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@titeica.ro

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

[systemsettings] [Bug 383379] Modernize Input Devices section to work with Libinput

2017-10-11 Thread Arthur Țițeică
https://bugs.kde.org/show_bug.cgi?id=383379

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@cloud.titeica.ro

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

[kde-gtk-config] [Bug 382291] System settings GTK apps configurations resets.

2017-10-14 Thread Arthur Țițeică
https://bugs.kde.org/show_bug.cgi?id=382291

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur+...@cloud.titeica.ro

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

[plasmashell] [Bug 373326] New: chromium lock-up, killing chromium kills plasma

2016-12-05 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=373326

Bug ID: 373326
   Summary: chromium lock-up, killing chromium kills plasma
   Product: plasmashell
   Version: 5.8.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: arthur.ma...@internode.on.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.9.0-rc7+ x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
I've had plasma desktop locking up a lot recently, sometimes when shutting down
iceweasel or chromium when they have several windows/tabs open.

The crash can be reproduced sometimes.

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

Thread 9 (Thread 0x7f7137fff700 (LWP 15374)):
#0  0x7f71f19e556d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f71ed5879f6 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7f7130002e70, timeout=, context=0x7f713990)
at ././glib/gmain.c:4228
#2  0x7f71ed5879f6 in g_main_context_iterate
(context=context@entry=0x7f713990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924
#3  0x7f71ed587b0c in g_main_context_iteration (context=0x7f713990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f71f23036fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f71f22ad07a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f71f20cf0d3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f71f20d3d88 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f71f11e8464 in start_thread (arg=0x7f7137fff700) at
pthread_create.c:333
#9  0x7f71f19ee9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 8 (Thread 0x7f713c99a700 (LWP 15372)):
#0  0x7f71f19e556d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f71ed5879f6 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7f71380013c0, timeout=, context=0x7f7138000990)
at ././glib/gmain.c:4228
#2  0x7f71ed5879f6 in g_main_context_iterate
(context=context@entry=0x7f7138000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924
#3  0x7f71ed587b0c in g_main_context_iteration (context=0x7f7138000990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f71f23036fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f71f22ad07a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f71f20cf0d3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f713cddaa35 in  () at
/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#8  0x7f71f20d3d88 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f71f11e8464 in start_thread (arg=0x7f713c99a700) at
pthread_create.c:333
#10 0x7f71f19ee9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7f71453e0700 (LWP 15313)):
#0  0x7f71f11ee18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f71ce0302ab in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f71ce030107 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f71f11e8464 in start_thread (arg=0x7f71453e0700) at
pthread_create.c:333
#4  0x7f71f19ee9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7f71cf9c3700 (LWP 15294)):
#0  0x7f71f11ee18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f71f6b652c4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f71f6b65309 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f71f11e8464 in start_thread (arg=0x7f71cf9c3700) at
pthread_create.c:333
#4  0x7f71f19ee9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7f71d997c700 (LWP 15287)):
#0  0x7f71f19fb1e0 in __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:59
#1  0x7f71f19e5562 in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0x7f71ed5879f6 in g_main_context_iterate (priority=,
n_fds=1, fds=0x7f71c8003070, timeout=, context=0x7f71c8000990)
at ././glib/gmain.c:4228
#3  0x7f71ed5879f6 in g_main_context_iterate
(context=context@entry=0x7f71c8000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ./

[plasmashell] [Bug 373455] New: plasmashell crash/restart when quitting chromium

2016-12-09 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=373455

Bug ID: 373455
   Summary: plasmashell crash/restart when quitting chromium
   Product: plasmashell
   Version: 5.8.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: arthur.ma...@internode.on.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.9.0-rc8+ x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
I quit chromium which had several windows/tabs openeded and plasmashell crashed
and restarted.

The crash can be reproduced sometimes.

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

Thread 9 (Thread 0x7fa388935700 (LWP 17033)):
#0  0x7fa43e9e5e67 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fa439c69edd in g_main_context_prepare
(context=context@entry=0x7fa37c000990, priority=priority@entry=0x7fa388934cc0)
at ././glib/gmain.c:3501
#2  0x7fa439c6a91b in g_main_context_iterate
(context=context@entry=0x7fa37c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909
#3  0x7fa439c6ab0c in g_main_context_iteration (context=0x7fa37c000990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7fa43e9e66fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7fa43e99007a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa43e7b20d3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa43e7b6d88 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa43d8cb464 in start_thread (arg=0x7fa388935700) at
pthread_create.c:333
#9  0x7fa43e0d19df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 8 (Thread 0x7fa389136700 (LWP 17032)):
#0  0x7fa43e7ae260 in QMutex::unlock() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7fa43e9e5e81 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7fa439c69edd in g_main_context_prepare
(context=context@entry=0x7fa384000990, priority=priority@entry=0x7fa389135ca0)
at ././glib/gmain.c:3501
#3  0x7fa439c6a91b in g_main_context_iterate
(context=context@entry=0x7fa384000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909
#4  0x7fa439c6ab0c in g_main_context_iteration (context=0x7fa384000990,
may_block=1) at ././glib/gmain.c:3990
#5  0x7fa43e9e66fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7fa43e99007a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7fa43e7b20d3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7fa389586a35 in  () at
/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#9  0x7fa43e7b6d88 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7fa43d8cb464 in start_thread (arg=0x7fa389136700) at
pthread_create.c:333
#11 0x7fa43e0d19df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7fa418e55700 (LWP 16824)):
#0  0x7fa43d8d118f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa41a7132ab in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7fa41a713107 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7fa43d8cb464 in start_thread (arg=0x7fa418e55700) at
pthread_create.c:333
#4  0x7fa43e0d19df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7fa41bfff700 (LWP 16816)):
#0  0x7fa43d8d118f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7fa4432452c4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7fa443245309 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7fa43d8cb464 in start_thread (arg=0x7fa41bfff700) at
pthread_create.c:333
#4  0x7fa43e0d19df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7fa426163700 (LWP 16815)):
#0  0x7fa43e0c45dd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7fa439caec40 in g_wakeup_acknowledge (__nbytes=16,
__buf=0x7fa426162bc0, __fd=) at
/usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x7fa439caec40 in g_wakeup_acknowledge (wakeup=0x7fa41c002390) at
././glib/gwakeup.c:210
#3  0x7fa439c6a4be in g_main_context_check
(context=context@entry=0x7fa414000990, max_priority=2147483647,
fds=fds@

[plasmashell] [Bug 373762] New: plasmashell crashed/restarted when quitting firefox and chromium

2016-12-17 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=373762

Bug ID: 373762
   Summary: plasmashell crashed/restarted when quitting firefox
and chromium
   Product: plasmashell
   Version: 5.8.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: arthur.ma...@internode.on.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.9.0+ x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
When quitting firefox and chromium, the plasmashell panel disappeared and
reappeared along with the crash bug symbol.

The crash can be reproduced sometimes.

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

Thread 13 (Thread 0x7f9a4affa700 (LWP 9072)):
#0  0x7f9b213dc18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9b222c3c6b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f9b255493f5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f9b25549cea in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f9b222c2da8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9b213d6464 in start_thread (arg=0x7f9a4affa700) at
pthread_create.c:333
#6  0x7f9b21bdc9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 12 (Thread 0x7f9a5526d700 (LWP 8135)):
#0  0x7f9b213dc18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9b222c3c6b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f9b255493f5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f9b25549cea in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f9b222c2da8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9b213d6464 in start_thread (arg=0x7f9a5526d700) at
pthread_create.c:333
#6  0x7f9b21bdc9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 11 (Thread 0x7f9a55feb700 (LWP 7954)):
#0  0x7f9b213dc18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f9b222c3c6b in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f9b255493f5 in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#3  0x7f9b25549cea in  () at /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5
#4  0x7f9b222c2da8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9b213d6464 in start_thread (arg=0x7f9a55feb700) at
pthread_create.c:333
#6  0x7f9b21bdc9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 10 (Thread 0x7f9a677fe700 (LWP 7933)):
#0  0x7ffe4bafa947 in  ()
#1  0x7ffe4bafabda in clock_gettime ()
#2  0x7f9b21be9886 in __GI___clock_gettime (clock_id=1, tp=0x7f9a677fdb60)
at ../sysdeps/unix/clock_gettime.c:115
#3  0x7f9b22368021 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f9b224e4bd9 in QTimerInfoList::updateCurrentTime() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f9b224e5185 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f9b224e652e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f9b1d563edd in g_main_context_prepare
(context=context@entry=0x7f9a58000990, priority=priority@entry=0x7f9a677fdcc0)
at ././glib/gmain.c:3501
#8  0x7f9b1d56491b in g_main_context_iterate
(context=context@entry=0x7f9a58000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909
#9  0x7f9b1d564b0c in g_main_context_iteration (context=0x7f9a58000990,
may_block=1) at ././glib/gmain.c:3990
#10 0x7f9b224e6f5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f9b224908da in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#12 0x7f9b222be0f3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x7f9b222c2da8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f9b213d6464 in start_thread (arg=0x7f9a677fe700) at
pthread_create.c:333
#15 0x7f9b21bdc9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 9 (Thread 0x7f9a67fff700 (LWP 7932)):
#0  0x7f9b21be91ff in __libc_enable_asynccancel () at
../sysdeps/unix/sysv/linux/x86_64/cancellation.S:67
#1  0x7f9b21bcf5d2 in

[plasmashell] [Bug 373795] New: plasmashell crashed and restarted when quitting firefox

2016-12-17 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=373795

Bug ID: 373795
   Summary: plasmashell crashed and restarted when quitting
firefox
   Product: plasmashell
   Version: 5.8.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: arthur.ma...@internode.on.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.8.0-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
After a video playback program, mpv was terminated due to lock-up, chromium
froze. When I quit firefox, chromium unfroze but plasmashell terminated and
restarted.

The crash can be reproduced sometimes.

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

Thread 9 (Thread 0x7f5d22c15700 (LWP 4615)):
#0  0x7f5dd83b156d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5dd3d429f6 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f5d14002e70, timeout=, context=0x7f5d14000990)
at ././glib/gmain.c:4228
#2  0x7f5dd3d429f6 in g_main_context_iterate
(context=context@entry=0x7f5d14000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924
#3  0x7f5dd3d42b0c in g_main_context_iteration (context=0x7f5d14000990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f5dd8cc4f5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5dd8c6e8da in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f5dd8a9c0f3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5dd8aa0da8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f5dd7bb4464 in start_thread (arg=0x7f5d22c15700) at
pthread_create.c:333
#9  0x7f5dd83ba9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 8 (Thread 0x7f5d23416700 (LWP 4614)):
#0  0x7f5dd83b156d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f5dd3d429f6 in g_main_context_poll (priority=,
n_fds=1, fds=0x7f5d1c0013c0, timeout=, context=0x7f5d1c000990)
at ././glib/gmain.c:4228
#2  0x7f5dd3d429f6 in g_main_context_iterate
(context=context@entry=0x7f5d1c000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3924
#3  0x7f5dd3d42b0c in g_main_context_iteration (context=0x7f5d1c000990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f5dd8cc4f5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f5dd8c6e8da in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f5dd8a9c0f3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f5d23866a35 in  () at
/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#8  0x7f5dd8aa0da8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f5dd7bb4464 in start_thread (arg=0x7f5d23416700) at
pthread_create.c:333
#10 0x7f5dd83ba9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7f5d2c301700 (LWP 4570)):
#0  0x7f5dd7bba18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5db87ea2bb in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f5db87ea117 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f5dd7bb4464 in start_thread (arg=0x7f5d2c301700) at
pthread_create.c:333
#4  0x7f5dd83ba9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7f5dba35d700 (LWP 4569)):
#0  0x7f5dd7bba18f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f5ddd5212c4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f5ddd521309 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f5dd7bb4464 in start_thread (arg=0x7f5dba35d700) at
pthread_create.c:333
#4  0x7f5dd83ba9df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7f5dbbfff700 (LWP 4562)):
#0  0x7f5dd3d88004 in g_mutex_unlock (mutex=0x7f5db990) at
././glib/gthread-posix.c:1348
#1  0x7f5dd3d41ed0 in g_main_context_prepare
(context=context@entry=0x7f5db990, priority=priority@entry=0x7f5dbbffeca0)
at ././glib/gmain.c:3499
#2  0x7f5dd3d4291b in g_main_context_iterate
(context=context@entry=0x7f5db990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909
#3  0x7f5dd3d42b0c in 

[plasmashell] [Bug 373815] New: plasmashell crashing when quitting firefox

2016-12-18 Thread Arthur Marsh
https://bugs.kde.org/show_bug.cgi?id=373815

Bug ID: 373815
   Summary: plasmashell crashing when quitting firefox
   Product: plasmashell
   Version: 5.8.4
  Platform: Debian unstable
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: arthur.ma...@internode.on.net
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.8.4)

Qt Version: 5.7.1
Frameworks Version: 5.28.0
Operating System: Linux 4.9.0+ x86_64
Distribution: Debian GNU/Linux unstable (sid)

-- Information about the crash:
when I quit firefox, plasmashell crashed and restarted, this may be a mesa
13.0.2 issue with my Radeon (Cedar) video card.

The crash can be reproduced sometimes.

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

Thread 9 (Thread 0x7f7bd3fff700 (LWP 4482)):
#0  0x7f7c8e5fc69e in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x7f7c89679edd in g_main_context_prepare
(context=context@entry=0x7f7bcc000990, priority=priority@entry=0x7f7bd3ffecc0)
at ././glib/gmain.c:3501
#2  0x7f7c8967a91b in g_main_context_iterate
(context=context@entry=0x7f7bcc000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3909
#3  0x7f7c8967ab0c in g_main_context_iteration (context=0x7f7bcc000990,
may_block=1) at ././glib/gmain.c:3990
#4  0x7f7c8e5fcf5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7f7c8e5a68da in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7f7c8e3d40f3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f7c8e3d8da8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f7c8d4ec464 in start_thread (arg=0x7f7bd3fff700) at
pthread_create.c:333
#9  0x7f7c8dcf29df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 8 (Thread 0x7f7bd8d4f700 (LWP 4481)):
#0  0x7f7c8dce55dd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f7c896bec40 in read (__nbytes=16, __buf=0x7f7bd8d4ebc0,
__fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x7f7c896bec40 in g_wakeup_acknowledge (wakeup=0x7f7c64002780) at
././glib/gwakeup.c:210
#3  0x7f7c8967a4be in g_main_context_check
(context=context@entry=0x7f7bd4000990, max_priority=2147483647,
fds=fds@entry=0x7f7bd40013c0, n_fds=n_fds@entry=1) at ././glib/gmain.c:3707
#4  0x7f7c8967a994 in g_main_context_iterate
(context=context@entry=0x7f7bd4000990, block=block@entry=1,
dispatch=dispatch@entry=1, self=) at ././glib/gmain.c:3926
#5  0x7f7c8967ab0c in g_main_context_iteration (context=0x7f7bd4000990,
may_block=1) at ././glib/gmain.c:3990
#6  0x7f7c8e5fcf5b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7f7c8e5a68da in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f7c8e3d40f3 in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#9  0x7f7bd919fa35 in  () at
/usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/XmlListModel/libqmlxmllistmodelplugin.so
#10 0x7f7c8e3d8da8 in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x7f7c8d4ec464 in start_thread (arg=0x7f7bd8d4f700) at
pthread_create.c:333
#12 0x7f7c8dcf29df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 7 (Thread 0x7f7c68865700 (LWP 4465)):
#0  0x7f7c8d4f218f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7c6a1232bb in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#2  0x7f7c6a123117 in  () at /usr/lib/x86_64-linux-gnu/dri/r600_dri.so
#3  0x7f7c8d4ec464 in start_thread (arg=0x7f7c68865700) at
pthread_create.c:333
#4  0x7f7c8dcf29df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 6 (Thread 0x7f7c6bbe0700 (LWP 4464)):
#0  0x7f7c8d4f218f in pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f7c92e592c4 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x7f7c92e59309 in  () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x7f7c8d4ec464 in start_thread (arg=0x7f7c6bbe0700) at
pthread_create.c:333
#4  0x7f7c8dcf29df in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:105

Thread 5 (Thread 0x7f7c75b6a700 (LWP 4462)):
#0  0x7f7c8dce55dd in read () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f7c896bec40 in read (__nbytes=16, __buf=0x7f7c75b69bc0,
__fd=) at /usr/include/x86_64-linux-gnu/bits/unistd.h:44
#2  0x7f7c896bec40 in g_wakeup_acknowledge (wakeup=0

  1   2   3   >