[plasmashell] [Bug 377137] New: Plasma crash

2017-03-02 Thread Polo
https://bugs.kde.org/show_bug.cgi?id=377137

Bug ID: 377137
   Summary: Plasma crash
   Product: plasmashell
   Version: 5.9.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: forz...@hotmail.com
CC: bhus...@gmail.com, plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.9.3)

Qt Version: 5.8.0
Frameworks Version: 5.31.0
Operating System: Linux 4.9.11-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed: Sometimes when I click on the
plasma applet on the top left corner Plasma crash completely and restarts.

The crash can be reproduced sometimes.

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

Thread 8 (Thread 0x7f416b430700 (LWP 717)):
#0  0x7f422d2a7ef9 in QTimerInfoList::repairTimersIfNeeded() () at
/usr/lib/libQt5Core.so.5
#1  0x7f422d2a7f83 in QTimerInfoList::timerWait(timespec&) () at
/usr/lib/libQt5Core.so.5
#2  0x7f422d2a963e in  () at /usr/lib/libQt5Core.so.5
#3  0x7f42277a3c8d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#4  0x7f42277a46cb in  () at /usr/lib/libglib-2.0.so.0
#5  0x7f42277a48bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#6  0x7f422d2aa06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#7  0x7f422d25389a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#8  0x7f422d075a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#9  0x7f416dd020a7 in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#10 0x7f422d07a6d8 in  () at /usr/lib/libQt5Core.so.5
#11 0x7f422bf45454 in start_thread () at /usr/lib/libpthread.so.0
#12 0x7f422c98f7df in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f417e2da700 (LWP 716)):
#0  0x7f42277e9e64 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f42277a475a in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f42277a48bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f422d2aa06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f422d25389a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f422d075a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f4230d62fd6 in  () at /usr/lib/libQt5Quick.so.5
#7  0x7f422d07a6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f422bf45454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f422c98f7df in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f4208d57700 (LWP 713)):
#0  0x7f422bf4b10f in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f4232a57234 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f4232a57279 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f422bf45454 in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f422c98f7df in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f420ad89700 (LWP 710)):
#0  0x7f422c98648d in poll () at /usr/lib/libc.so.6
#1  0x7f42277a47a6 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f42277a48bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f422d2aa06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f422d25389a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f422d075a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f42301af025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f422d07a6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f422bf45454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f422c98f7df in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f4218f08700 (LWP 649)):
#0  0x7f42277a3d9d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#1  0x7f42277a46cb in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f42277a48bc in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f422d2aa06b in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f422d25389a in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f422d075a73 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f42301af025 in  () at /usr/lib/libQt5Qml.so.5
#7  0x7f422d07a6d8 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f422bf45454 in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f422c98f7df in clone () at /usr/lib/libc.so.6

Thread 3 (Thread 0x7f421a950700 (LWP 625)):
#0  0x7f42277e9e49 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f42277a3670 in g_main_context_acquire () at
/usr/lib/libglib-2.0.so.0
#2  0x

[kate] [Bug 444768] New: Kate fails to open

2021-11-01 Thread Marco polo
https://bugs.kde.org/show_bug.cgi?id=444768

Bug ID: 444768
   Summary: Kate fails to open
   Product: kate
   Version: 19.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: application
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: rjmal...@gmail.com
  Target Milestone: ---

Created attachment 143090
  --> https://bugs.kde.org/attachment.cgi?id=143090&action=edit
"strace kate" - kate not opening

SUMMARY

Kate simply fails to open.

STEPS TO REPRODUCE

1. Start new kde session.
2. open same kate session in 2  instances
3. manually save session 
4. log out and log in
5. as 2nd kate opens dialog will come up asking if ' ...  reopen here or in
other instance ... '

on clicking no , kate is broken and wont open new instances.if i dont click
anything , kate works fine.

NOTE: not entirely sure the steps will reproduce the bug , i maybe hitting a
very very rare bug .

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

[kate] [Bug 444768] Kate fails to open

2021-11-08 Thread Marco polo
https://bugs.kde.org/show_bug.cgi?id=444768

--- Comment #3 from Marco polo  ---
(In reply to kde.org from comment #1)
> cannot confirm with kate 21.08.2
> Created new kate test-session 
> Saved kate session
> Exit kate
> start kate
> select kate test-session
> start another kate instance
> select kate test-session.
> select NO
> 
> result
> a second kate instance is running, as expected (on top of the first one).
> 
> Haven't tried to log in and out of KDE, but I don't think that should matter

Bug is only triggered when KDE session is started with "KDE session" saving
enabled.

Open 2 kate instances both running same kate session , then logout and login
into KDE 

on logging in , KDE will spawn 2 kate instances , both running same kate
session.

Maybe some sort of dead lock / race condidtion being triggered at this point.

Okay will try with 21.08.2.

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

[krita] [Bug 400427] New: 'mergedimage.png' and 'preview.png' inside .kra does not match final image.

2018-10-28 Thread Marco polo
https://bugs.kde.org/show_bug.cgi?id=400427

Bug ID: 400427
   Summary: 'mergedimage.png' and 'preview.png' inside .kra does
not match final image.
   Product: krita
   Version: 4.1.5
  Platform: Appimage
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: File formats
  Assignee: krita-bugs-n...@kde.org
  Reporter: rjmal...@gmail.com
  Target Milestone: ---

Created attachment 115950
  --> https://bugs.kde.org/attachment.cgi?id=115950&action=edit
krita kra image

Filter layers seems to be skipped while rendering 'mergedimage.png' and
'preview.png'.

plz check attached file.

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

[krita] [Bug 400427] 'mergedimage.png' and 'preview.png' inside .kra does not match final image.

2018-10-29 Thread Marco polo
https://bugs.kde.org/show_bug.cgi?id=400427

--- Comment #2 from Marco polo  ---
Created attachment 115961
  --> https://bugs.kde.org/attachment.cgi?id=115961&action=edit
new.kra

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

[krita] [Bug 400427] 'mergedimage.png' and 'preview.png' inside .kra does not match final image.

2018-10-29 Thread Marco polo
https://bugs.kde.org/show_bug.cgi?id=400427

--- Comment #3 from Marco polo  ---
i tried windows build on another pc and bug is there.

plz check out 'new.kra' attachment.its has a vector layer + guassian filter +
paint layer.if i reduce guassian filter radius size from 200 px to 20 px,
'mergedimage.png' will match final image othersize top 2 layers get skipped

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

[kdevelop] [Bug 409747] Crash + data loss

2019-08-02 Thread Marco polo
https://bugs.kde.org/show_bug.cgi?id=409747

Marco polo  changed:

   What|Removed |Added

 CC||rjmal...@gmail.com

--- Comment #1 from Marco polo  ---
Just encountered this bug.

kdevelop crashed with

'/tmp/.mount_KDevelL7pxbl/AppRun: line 36: 12625 Bus error(core dumped)
kdevelop $@'

the file that was been edited was zeroed out.

there was no call stack output.

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

[krita] [Bug 400427] 4.1 only: 'mergedimage.png' and 'preview.png' inside .kra does not match final image.

2018-10-31 Thread Marco polo
https://bugs.kde.org/show_bug.cgi?id=400427

--- Comment #5 from Marco polo  ---
bug is present in krita-4.1.5-1be40f6-x86_64.appimage (Krita Plus).

but not in krita-4.2.0-pre-alpha-9697760-x86_64.appimage (Krita Next).

krita-4.2.0-pre-alpha-9697760 is saving pngs correctly.

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

[dolphin] [Bug 387064] New: Dolphin high cpu usage when system has high IO activity

2017-11-18 Thread Marco polo
https://bugs.kde.org/show_bug.cgi?id=387064

Bug ID: 387064
   Summary: Dolphin high cpu usage when system has high IO
activity
   Product: dolphin
   Version: 16.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: rjmal...@gmail.com
CC: elvis.angelac...@kde.org
  Target Milestone: ---

High system IO activity (for ex running 'make -j 2 install') causes Dolphin cpu
usage to go up to 5%,so if i have 4 instances open,dolphin ends up taking 20 %,

it may be due to inotify watch events hammering dolphin,from the code it looks
like directory watches are added for counting directory items, -- but i could
be very wrong here,not familiar with the source.

any case plz fix this.its annoying to see dolphin taking up 10 - 20 % doing
nothing when doing something cpu intensive.

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

[abakus] [Bug 366641] New: i6788888888888888yyyyyyyyyyyyyyyyyyrrhhhhhhhhhhh

2016-08-11 Thread polo via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=366641

Bug ID: 366641
   Summary: i6788yyrrhhh
   Product: abakus
   Version: 0.90
  Platform: Other
OS: other
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k.h...@gmx.de
  Reporter: nik...@ov3u841.com

truyrr 
nntyhhh

Reproducible: Always

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