[Heaptrack] [Bug 486162] [Request] Extend Demangle support

2024-04-26 Thread Matheus Catarino
https://bugs.kde.org/show_bug.cgi?id=486162

--- Comment #1 from Matheus Catarino  ---
Comment on attachment 168922
  --> https://bugs.kde.org/attachment.cgi?id=168922
heaptrack show dlang mangled functions (druntime internal)

D code:
void main() {}

command: ldmd2 foo.d

For this print has used ldc2 (LLVM D Compiler), but same result on any D
compiler.

By default using extern(D) - D ABI '_D'
extern(C++) - C++ ABI, demangle works
extern(C) - like betterC, no issue

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

[Heaptrack] [Bug 486162] New: [Request] Extend Demangle support

2024-04-26 Thread Matheus Catarino
https://bugs.kde.org/show_bug.cgi?id=486162

Bug ID: 486162
   Summary: [Request] Extend Demangle support
Classification: Applications
   Product: Heaptrack
   Version: unspecified
  Platform: unspecified
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@milianw.de
  Reporter: matheus-catar...@hotmail.com
  Target Milestone: ---

Created attachment 168922
  --> https://bugs.kde.org/attachment.cgi?id=168922=edit
heaptrack show dlang mangled functions (druntime internal)

Similar references
- https://bugs.kde.org/show_bug.cgi?id=481485
- https://bugs.kde.org/show_bug.cgi?id=458175
- https://bugs.kde.org/show_bug.cgi?id=372182

Request to extend support also to other ABIs, like Rust, Swift, D and any
mangled ABI.

Following the attachment of this report, I'm trying to investigate a possible
case of DRuntimeGC memory leak on archlinux/glibc and cannot detect the same
problem on alpine/musl.

I don't know if it helps, but I do know that kdab/hotspot and kdab/perfparser
have support through 3rd party demangle-libraries to support Rust('_R') [v0
mangle] and D ('_D').
If this is a starting point to be added, great.
https://github.com/KDAB/hotspot/blob/1ac3ff2e885f381e0dfe86204eab0f9f82b84553/scripts/appimage/Dockerfile#L81-L100

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

[kwin] [Bug 464477] I can’t use 120 Hz refresh rate in Plasma anymore

2023-01-19 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=464477

--- Comment #3 from Matheus  ---
I ran drm_info again without the json flag and the output is a little
different.

$ drm_info
Node: /dev/dri/card0
├───Driver: amdgpu (AMD GPU) version 3.49.0 (20150101)
│   ├───DRM_CLIENT_CAP_STEREO_3D supported
│   ├───DRM_CLIENT_CAP_UNIVERSAL_PLANES supported
│   ├───DRM_CLIENT_CAP_ATOMIC supported
│   ├───DRM_CLIENT_CAP_ASPECT_RATIO supported
│   ├───DRM_CLIENT_CAP_WRITEBACK_CONNECTORS supported
│   ├───DRM_CAP_DUMB_BUFFER = 1
│   ├───DRM_CAP_VBLANK_HIGH_CRTC = 1
│   ├───DRM_CAP_DUMB_PREFERRED_DEPTH = 24
│   ├───DRM_CAP_DUMB_PREFER_SHADOW = 1
│   ├───DRM_CAP_PRIME = 3
│   ├───DRM_CAP_TIMESTAMP_MONOTONIC = 1
│   ├───DRM_CAP_ASYNC_PAGE_FLIP = 1
│   ├───DRM_CAP_CURSOR_WIDTH = 256
│   ├───DRM_CAP_CURSOR_HEIGHT = 256
│   ├───DRM_CAP_ADDFB2_MODIFIERS = 1
│   ├───DRM_CAP_PAGE_FLIP_TARGET = 0
│   ├───DRM_CAP_CRTC_IN_VBLANK_EVENT = 1
│   ├───DRM_CAP_SYNCOBJ = 1
│   └───DRM_CAP_SYNCOBJ_TIMELINE = 1
├───Device: PCI 1002:73df Advanced Micro Devices, Inc. [AMD/ATI] Navi 22
[Radeon RX 6700/6700 XT/6750 XT / 6800M]
│   └───Available nodes: primary, render
├───Framebuffer size
│   ├───Width: [0, 16384]
│   └───Height: [0, 16384]
├───Connectors
│   ├───Connector 0
│   │   ├───Object ID: 94
│   │   ├───Type: DisplayPort
│   │   ├───Status: connected
│   │   ├───Physical size: 600x340 mm
│   │   ├───Subpixel: unknown
│   │   ├───Encoders: {0}
│   │   ├───Modes
│   │   │   ├───2560x1440@59.95 preferred driver phsync nvsync 
│   │   │   ├───2560x1440@143.91 driver phsync nvsync 
│   │   │   ├───1920x1200@59.88 driver nhsync pvsync 
│   │   │   ├───1920x1080@60.00 driver phsync pvsync 16:9 
│   │   │   ├───1920x1080@59.94 driver phsync pvsync 16:9 
│   │   │   ├───1920x1080@50.00 driver phsync pvsync 16:9 
│   │   │   ├───1600x1200@60.00 driver phsync pvsync 
│   │   │   ├───1680x1050@59.95 driver nhsync pvsync 
│   │   │   ├───1280x1024@75.03 driver phsync pvsync 
│   │   │   ├───1280x1024@60.02 driver phsync pvsync 
│   │   │   ├───1440x900@59.95 driver phsync nvsync 
│   │   │   ├───1280x800@59.81 driver nhsync pvsync 
│   │   │   ├───1152x864@75.00 driver phsync pvsync 
│   │   │   ├───1280x720@60.00 driver phsync pvsync 
│   │   │   ├───1280x720@60.00 driver phsync pvsync 16:9 
│   │   │   ├───1280x720@59.94 driver phsync pvsync 16:9 
│   │   │   ├───1280x720@50.00 driver phsync pvsync 16:9 
│   │   │   ├───1024x768@75.03 driver phsync pvsync 
│   │   │   ├───1024x768@60.00 driver nhsync nvsync 
│   │   │   ├───800x600@75.00 driver phsync pvsync 
│   │   │   ├───800x600@60.32 driver phsync pvsync 
│   │   │   ├───720x576@50.00 driver nhsync nvsync 4:3 
│   │   │   ├───720x576@50.00 driver nhsync nvsync 16:9 
│   │   │   ├───720x480@60.00 driver nhsync nvsync 4:3 
│   │   │   ├───720x480@60.00 driver nhsync nvsync 16:9 
│   │   │   ├───720x480@59.94 driver nhsync nvsync 
│   │   │   ├───720x480@59.94 driver nhsync nvsync 16:9 
│   │   │   ├───720x480@59.94 driver nhsync nvsync 4:3 
│   │   │   ├───640x480@75.00 driver nhsync nvsync 
│   │   │   ├───640x480@60.00 driver nhsync nvsync 4:3 
│   │   │   ├───640x480@59.94 driver nhsync nvsync 
│   │   │   ├───640x480@59.94 driver nhsync nvsync 4:3 
│   │   │   └───720x400@70.08 driver nhsync pvsync 
│   │   └───Properties
│   │   ├───"EDID" (immutable): blob = 101
│   │   ├───"DPMS": enum {On, Standby, Suspend, Off} = On
│   │   ├───"link-status": enum {Good, Bad} = Good
│   │   ├───"non-desktop" (immutable): range [0, 1] = 0
│   │   ├───"TILE" (immutable): blob = 0
│   │   ├───"CRTC_ID" (atomic): object CRTC = 77
│   │   ├───"scaling mode": enum {None, Full, Center, Full aspect} = None
│   │   ├───"underscan": enum {off, on, auto} = off
│   │   ├───"underscan hborder": range [0, 128] = 0
│   │   ├───"underscan vborder": range [0, 128] = 0
│   │   ├───"max bpc": range [8, 16] = 10
│   │   ├───"HDR_OUTPUT_METADATA": blob = 0
│   │   ├───"vrr_capable" (immutable): range [0, 1] = 1
│   │   ├───"Content Protection": enum {Undesired, Desired, Enabled} =
Undesired
│   │   ├───"HDCP Content Type": enum {HDCP Type0, HDCP Type1} = HDCP Type0
│   │   └───"subconnector" (immutable): enum {Unknown, VGA, DVI-D, HDMI,
DP, Wireless, Native} = Native

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

[kwin] [Bug 464477] I can’t use 120 Hz refresh rate in Plasma anymore

2023-01-19 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=464477

--- Comment #2 from Matheus  ---
(In reply to Zamundaaa from comment #1)
> Please attach the output of drm_info
> (https://gitlab.freedesktop.org/emersion/drm_info)
> 

Driver: amdgpu (AMD GPU) version 3.49.0 (20150101) on Linux 6.1.6-arch1-3

DRM_CLIENT_CAP_ASPECT_RATIO supported
DRM_CLIENT_CAP_ATOMIC supported
DRM_CLIENT_CAP_STEREO_3D supported
DRM_CLIENT_CAP_UNIVERSAL_PLANES supported
DRM_CLIENT_CAP_WRITEBACK_CONNECTORS supported
DRM_CAP_ADDFB2_MODIFIERS = 1
DRM_CAP_ASYNC_PAGE_FLIP = 1
DRM_CAP_CRTC_IN_VBLANK_EVENT = 1
DRM_CAP_CURSOR_HEIGHT = 256
DRM_CAP_CURSOR_WIDTH = 256
DRM_CAP_DUMB_BUFFER = 1
DRM_CAP_DUMB_PREFERRED_DEPTH = 24
DRM_CAP_DUMB_PREFER_SHADOW = 1
DRM_CAP_PAGE_FLIP_TARGET = 0
DRM_CAP_PRIME = 3
DRM_CAP_SYNCOBJ = 1
DRM_CAP_SYNCOBJ_TIMELINE = 1
DRM_CAP_TIMESTAMP_MONOTONIC = 1
DRM_CAP_VBLANK_HIGH_CRTC = 1

Device: PCI 1002:73DF Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX
6700/6700 XT/6750 XT / 6800M]
Connectors

Connector 0
Object ID: 94
Type: DisplayPort
Encoders: {93}
Properties
"CRTC_ID" (atomic): object CRTC = 77
"Content Protection": enum {"Undesired", "Desired", "Enabled"} =
Undesired
"DPMS": enum {"On", "Standby", "Suspend", "Off"} = On
"EDID" (immutable): blob = 
"HDCP Content Type": enum {"HDCP Type0", "HDCP Type1"} = HDCP Type0
"HDR_OUTPUT_METADATA": blob = 
"TILE" (immutable): blob = 
"link-status": enum {"Good", "Bad"} = Good
"max bpc": range [8, 16] = 10
"non-desktop" (immutable): range [0, 1] = 0
"scaling mode": enum {"None", "Full", "Center", "Full aspect"} =
None
"subconnector" (immutable): enum {"Unknown", "VGA", "DVI-D",
"HDMI", "DP", "Wireless", "Native"} = Native
"underscan": enum {"off", "on", "auto"} = off
"underscan hborder": range [0, 128] = 0
"underscan vborder": range [0, 128] = 0
"vrr_capable" (immutable): range [0, 1] = 1

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

[kwin] [Bug 464477] New: I can’t use 120 Hz refresh rate in Plasma anymore

2023-01-18 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=464477

Bug ID: 464477
   Summary: I can’t use 120 Hz refresh rate in Plasma anymore
Classification: Plasma
   Product: kwin
   Version: 5.26.5
  Platform: Archlinux
OS: Linux
Status: REPORTED
  Severity: minor
  Priority: NOR
 Component: wayland-generic
  Assignee: kwin-bugs-n...@kde.org
  Reporter: matheuskiskiss...@gmail.com
  Target Milestone: ---

Created attachment 155411
  --> https://bugs.kde.org/attachment.cgi?id=155411=edit
System Settings/Display and Monitor

I have a Dell s2719dgf monitor connected to my GPU (AMD 6750 XT) via
DisplayPort. It’s a 2560x1440 144 Hz monitor but I always set it at 120 Hz in
Display and Monitor (KDE System Settings) since I feel it’s good balance for
gaming and desktop usage.

Since last week, the 120 Hz option is gone and I can only select 144 Hz or 60
Hz. Also, using the adaptive sync option on 'always on' with 144 Hz causes
heavy flickering on the desktop screen.

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

[kwin] [Bug 454219] New: KWin stop to work, show a message error and start working again

2022-05-22 Thread Paulo Matheus
https://bugs.kde.org/show_bug.cgi?id=454219

Bug ID: 454219
   Summary: KWin stop to work, show a message error and start
working again
   Product: kwin
   Version: unspecified
  Platform: Slackware Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kwin-bugs-n...@kde.org
  Reporter: dukeriul...@live.com
  Target Milestone: ---

Application: kwin_x11 (5.24.5)

Qt Version: 5.15.3
Frameworks Version: 5.94.0
Operating System: Linux 5.17.9 x86_64
Windowing System: X11
Distribution: Slackware 15.0 x86_64 (post 15.0 -current)
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
I was playing RuneScape via the open source client for Linux: RuneLite. It
crash only occurs when I am using RuneLite. The KWin's windows close, and
seconds later it comeback to normal, but with a crash window.

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted

[KCrash Handler]
#4  0x7f7ca578de3c in pthread_kill@@GLIBC_2.34 () at /lib64/libc.so.6
#5  0x7f7ca573ce72 in raise () at /lib64/libc.so.6
#6  0x7f7ca572449b in abort () at /lib64/libc.so.6
#7  0x7f7c9a6b0c44 in  () at /usr/lib64/dri/iris_dri.so
#8  0x7f7c9b29c079 in  () at /usr/lib64/dri/iris_dri.so
#9  0x7f7c9a888359 in  () at /usr/lib64/dri/iris_dri.so
#10 0x7f7ca8c73de4 in  () at /usr/lib64/libkwin.so.5
#11 0x7f7ca69f044d in  () at /usr/lib64/libQt5Core.so.5
#12 0x7f7ca8c4708c in KWin::Scene::paintScreen(QRegion const&, QRegion
const&, QRegion*, QRegion*, KWin::RenderLoop*, QMatrix4x4 const&) () at
/usr/lib64/libkwin.so.5
#13 0x7f7ca8d112da in KWin::SceneOpenGL::paint(KWin::AbstractOutput*,
QRegion const&, QList const&, KWin::RenderLoop*) () at
/usr/lib64/libkwin.so.5
#14 0x7f7ca8ba06ee in KWin::Compositor::composite(KWin::RenderLoop*) () at
/usr/lib64/libkwin.so.5
#15 0x7f7ca8ba0d4b in KWin::X11Compositor::composite(KWin::RenderLoop*) ()
at /usr/lib64/libkwin.so.5
#16 0x7f7ca69f044d in  () at /usr/lib64/libQt5Core.so.5
#17 0x7f7ca8b591b2 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*)
() at /usr/lib64/libkwin.so.5
#18 0x7f7ca8c35d33 in KWin::RenderLoopPrivate::dispatch() () at
/usr/lib64/libkwin.so.5
#19 0x7f7ca69f044d in  () at /usr/lib64/libQt5Core.so.5
#20 0x7f7ca69f412a in QTimer::timeout(QTimer::QPrivateSignal) () at
/usr/lib64/libQt5Core.so.5
#21 0x7f7ca69e6acf in QObject::event(QEvent*) () at
/usr/lib64/libQt5Core.so.5
#22 0x7f7ca5e59a8f in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib64/libQt5Widgets.so.5
#23 0x7f7ca69bc18a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib64/libQt5Core.so.5
#24 0x7f7ca6a0f18b in QTimerInfoList::activateTimers() () at
/usr/lib64/libQt5Core.so.5
#25 0x7f7ca6a0d71f in
QEventDispatcherUNIX::processEvents(QFlags) ()
at /usr/lib64/libQt5Core.so.5
#26 0x7f7ca17a57de in  () at /usr/lib64/libQt5XcbQpa.so.5
#27 0x7f7ca69bad0b in
QEventLoop::exec(QFlags) () at
/usr/lib64/libQt5Core.so.5
#28 0x7f7ca69c295c in QCoreApplication::exec() () at
/usr/lib64/libQt5Core.so.5
#29 0x0042c5b2 in  ()
#30 0x7f7ca5725a37 in __libc_start_call_main () at /lib64/libc.so.6
#31 0x7f7ca5725aec in __libc_start_main_impl () at /lib64/libc.so.6
#32 0x0042dcb1 in  ()
[Inferior 1 (process 4516) detached]

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

[valgrind] [Bug 449199] New: unhandled syscall 387 on ppc64le-linux

2022-01-26 Thread Matheus Castanho
https://bugs.kde.org/show_bug.cgi?id=449199

Bug ID: 449199
   Summary: unhandled syscall 387 on ppc64le-linux
   Product: valgrind
   Version: unspecified
  Platform: Fedora RPMs
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: m...@linux.ibm.com
  Target Milestone: ---

SUMMARY
valgrind issues a warning noting syscall number 387 is not implemented by
valgrind on ppc64le when using upstream glibc. This seems to be map to the rseq
syscall.

STEPS TO REPRODUCE
1. git clone git://sourceware.org/git/glibc.git
2. mkdir build && cd build
3. ../glibc/configure --prefix=/usr && make -j10 && make test
t=elf/tst-valgrind-smoke

OBSERVED RESULT

--2953886-- WARNING: unhandled ppc64le-linux syscall: 387
--2953886-- You may be able to write your own handler.
--2953886-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2953886-- Nevertheless we consider this a bug.  Please report
--2953886-- it at http://valgrind.org/support/bug_reports.html.

EXPECTED RESULT

No warning.

SOFTWARE/OS VERSIONS
Fedora 34
valgrind 3.18.1 (provided by distro)

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

[krunner] [Bug 439744] Krunner from the apps panel does not display website search plugins.

2021-08-03 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=439744

--- Comment #2 from Matheus  ---
I've tried changing the default separator to space, but it still doesn't work
in KDE Application Dashboard. I wrongly referred to Krunner, but the problem is
in the App Dashboard search. I'm sorry

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

[krunner] [Bug 439744] New: Krunner from the apps panel does not display website search plugins.

2021-07-10 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=439744

Bug ID: 439744
   Summary: Krunner from the apps panel does not display website
search plugins.
   Product: krunner
   Version: unspecified
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: webshortcuts
  Assignee: alexander.loh...@gmx.de
  Reporter: matheus.wx...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
Krunner from the apps panel does not display website search plugins.

EXPECTED RESULT
Krunner from the apps panel could allow the use of site search plugins just
like the original krunner plasmoid itself.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.22
(available in About System)
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.83.0
Qt Version: 5.15,3

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

[dolphin] [Bug 439649] Failed to run Shell Scripts on click

2021-07-08 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=439649

--- Comment #2 from Matheus  ---
Pois é falha minha...

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

[dolphin] [Bug 439649] New: Failed to run Shell Scripts on click

2021-07-08 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=439649

Bug ID: 439649
   Summary: Failed to run Shell Scripts on click
   Product: dolphin
   Version: 21.04.3
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: matheus.wx...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY
It is not possible to execute Shell Scripts, because the execution returns the
error "execvp: Error in exec format"

STEPS TO REPRODUCE
1.Run a ".sh" file with the click of the mouse or by a ".desktop" application.

OBSERVED RESULT
execvp: Error in exec format

EXPECTED RESULT
a execução norman do arquivo ".sh"

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:5.22
KDE Plasma Version: 5.22.3
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3

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

[systemsettings] [Bug 436019] New: failed to change the speed of the animations of the desktop effects.

2021-04-21 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=436019

Bug ID: 436019
   Summary: failed to change the speed of the animations of the
desktop effects.
   Product: systemsettings
   Version: 5.21.4
  Platform: Neon Packages
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: kcm_kwin_effects
  Assignee: kwin-bugs-n...@kde.org
  Reporter: matheus.wx...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: ---

SUMMARY
failed to change the speed of the animations of the desktop effects.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT

Changing the speed of the animation of the system in "Behavior of the
workspace: general behaviors", does not change the speed of the animations in
the effects of the workspace.;

EXPECTED RESULT

That the time of the animations of the effects of the working area corresponded
to the option of "speed of the animations"

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

ADDITIONAL INFORMATION

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

[Discover] [Bug 430219] Discover crashes shortly after opening

2021-02-04 Thread Matheus Catarino
https://bugs.kde.org/show_bug.cgi?id=430219

Matheus Catarino  changed:

   What|Removed |Added

 CC||matheus-catar...@hotmail.co
   ||m

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

[Discover] [Bug 430219] Discover crashes shortly after opening

2021-02-04 Thread Matheus Catarino
https://bugs.kde.org/show_bug.cgi?id=430219

--- Comment #2 from Matheus Catarino  ---
Created attachment 135419
  --> https://bugs.kde.org/attachment.cgi?id=135419=edit
New crash information added by DrKonqi

plasma-discover (5.20.5) using Qt 5.15.2

- What I was doing when the application crashed:
   The application freezes every time it launches updating search.
- Unusual behavior I noticed:
After initializing the system, the problem happens every time you open the
discoverer. I've already checked if there was a problem with the video driver,
but there was no problem with the driver (visibly detectable).

-- Backtrace (Reduced):
#5  0x7f41cabf0f1e in as_content_rating_set_value () at
/usr/lib/libappstream.so.4
[...]
#9  0x7f41cabf7125 in as_metadata_parse_file () at
/usr/lib/libappstream.so.4
#10 0x7f41cabfb49c in as_pool_load () at /usr/lib/libappstream.so.4
#11 0x7f41cc2b277a in AppStream::Pool::load() () at
/usr/lib/libAppStreamQt.so.2
[...]
#4  0x7f41ccece6fc in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5

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

[systemsettings] [Bug 430635] Unable to set custom shortcuts from the settings application

2020-12-21 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=430635

--- Comment #5 from Matheus  ---
I did exactly the same! Then I exported the group again and you can see that
your edit isn't there anymore, the key is empty.

I also tried editing ~/.config/khotkeysrc, which is where all custom shortcuts
seem to be stored at, but KDE isn't reloading this file and if I restart
plasmashell with `plasmashell --replace` the key gets empty again. 

Maybe I just don't know how to properly reload this shortcut daemon? I didn't
find much about it. Or maybe KDE's shortcut daemon is really completely broken
this time.

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

[systemsettings] [Bug 430635] Unable to set custom shortcuts from the settings application

2020-12-21 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=430635

--- Comment #3 from Matheus  ---
I tried many earlier versions of the systemsettings and had always the same
problem. I tried:  
   5.19.90  
   5.20.0   
   5.20.2   
   5.20.3  
   5.20.4

So this might be a problem or a compatibility with the KDE framework I'm
guessing.

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

[systemsettings] [Bug 430635] Unable to set custom shortcuts from the settings application

2020-12-20 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=430635

--- Comment #1 from Matheus  ---
Dec 20 19:17:13 arch-matheus systemsettings5[305190]: kf.guiaddons: Cannot
record without a window
Dec 20 19:17:13 arch-matheus systemsettings5[305190]: kf.guiaddons: Cannot
record without a window


That is logged when I click on the shortcut widget.

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

[systemsettings] [Bug 430635] Unable to set custom shortcuts from the settings application

2020-12-20 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=430635

Matheus  changed:

   What|Removed |Added

 CC||matheusfillip...@gmail.com

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

[systemsettings] [Bug 430635] New: Unable to set custom shortcuts from the settings application

2020-12-20 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=430635

Bug ID: 430635
   Summary: Unable to set custom shortcuts from the settings
application
   Product: systemsettings
   Version: 5.20.4
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: matheusfillip...@gmail.com
  Target Milestone: ---

SUMMARY
Since 5.20.4 it is no longer possible to set custom shortcuts on the settings
app.


STEPS TO REPRODUCE
1. Open the settings app, go to Shortcuts -> Custom Shortcuts.
2. Create a new one or go to the trigger tab for a existing one.
3. You will be unable to modify the shortcut with the little widget there.

OBSERVED RESULT
You try to type a shortcut an nothing is detected. This same widget still works
on another applications like setting a shortcut for applets.


SOFTWARE/OS VERSIONS
OS: Arch Linux x86_64, DE: KDE Plasma 5.20.2, CPU: Intel i7-7700HQ (8) @
3.800GHz, GPU: NVIDIA GeForce GTX 1050 Ti Mobile, GPU: Intel HD Graphics 630,
Memory: 15.5 GiB

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

[ark] [Bug 430373] New: Plasma: Blurred and poorly synchronized interface

2020-12-14 Thread Matheus Catarino
https://bugs.kde.org/show_bug.cgi?id=430373

Bug ID: 430373
   Summary: Plasma: Blurred and poorly synchronized interface
   Product: ark
   Version: 20.12.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: elvis.angelac...@kde.org
  Reporter: matheus-catar...@hotmail.com
CC: rthoms...@gmail.com
  Target Milestone: ---

Application: ark (20.12.0)

Qt Version: 5.15.2
Frameworks Version: 5.77.0
Operating System: Linux 5.9.13-arch1-1 x86_64
Windowing system: X11
Distribution: Arch Linux

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

- Unusual behavior I noticed:
When the operating system is turned on the plasma interface appears to be
broken in video synchronization since the taskbar appears blurred, although
this had never happened before.

- Custom settings of the application:
Default

The crash can be reproduced every time.

-- Backtrace:
Application: Ark (ark), signal: Segmentation fault

[KCrash Handler]
#4  0x7f3b7015e8f9 in QAction::setEnabled(bool) () from
/usr/lib/libQt5Widgets.so.5
#5  0x7f3b6f6ccdd6 in ?? () from /usr/lib/libQt5Core.so.5
#6  0x7f3b70253d53 in QAbstractButton::clicked(bool) () from
/usr/lib/libQt5Widgets.so.5
#7  0x7f3b702546dc in ?? () from /usr/lib/libQt5Widgets.so.5
#8  0x7f3b70256083 in ?? () from /usr/lib/libQt5Widgets.so.5
#9  0x7f3b70256263 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) ()
from /usr/lib/libQt5Widgets.so.5
#10 0x7f3b701a3b0e in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#11 0x7f3b70162752 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#12 0x7f3b7016987b in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#13 0x7f3b6f695a7a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#14 0x7f3b7016887e in QApplicationPrivate::sendMouseEvent(QWidget*,
QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) ()
from /usr/lib/libQt5Widgets.so.5
#15 0x7f3b701bc249 in ?? () from /usr/lib/libQt5Widgets.so.5
#16 0x7f3b701bf63f in ?? () from /usr/lib/libQt5Widgets.so.5
#17 0x7f3b70162752 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#18 0x7f3b6f695a7a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#19 0x7f3b6fa72594 in
QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
() from /usr/lib/libQt5Gui.so.5
#20 0x7f3b6fa47bb5 in
QWindowSystemInterface::sendWindowSystemEvents(QFlags)
() from /usr/lib/libQt5Gui.so.5
#21 0x7f3b6a86716c in ?? () from /usr/lib/libQt5XcbQpa.so.5
#22 0x7f3b6dc6a8f4 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#23 0x7f3b6dcbe821 in ?? () from /usr/lib/libglib-2.0.so.0
#24 0x7f3b6dc69121 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#25 0x7f3b6f6ee6e1 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#26 0x7f3b6f6943fc in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#27 0x7f3b7036620a in QDialog::exec() () from /usr/lib/libQt5Widgets.so.5
#28 0x7f3b70df8fff in Kerfuffle::OverwriteQuery::execute() () from
/usr/lib/libkerfuffle.so.20
#29 0x7f3b6f6ccdd6 in ?? () from /usr/lib/libQt5Core.so.5
#30 0x7f3b70dd8a93 in Kerfuffle::Job::userQuery(Kerfuffle::Query*) () from
/usr/lib/libkerfuffle.so.20
#31 0x7f3b6f6c2582 in QObject::event(QEvent*) () from
/usr/lib/libQt5Core.so.5
#32 0x7f3b70162752 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#33 0x7f3b6f695a7a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#34 0x7f3b6f698573 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib/libQt5Core.so.5
#35 0x7f3b6f6ef0a4 in ?? () from /usr/lib/libQt5Core.so.5
#36 0x7f3b6dc6a8f4 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#37 0x7f3b6dcbe821 in ?? () from /usr/lib/libglib-2.0.so.0
#38 0x7f3b6dc69121 in g_main_context_iteration () from
/usr/lib/libglib-2.0.so.0
#39 0x7f3b6f6ee6e1 in
QEventDispatcherGlib::processEvents(QFlags) ()
from /usr/lib/libQt5Core.so.5
#40 0x7f3b6f6943fc in
QEventLoop::exec(QFlags) () from
/usr/lib/libQt5Core.so.5
#41 0x7f3b6f69c894 in QCoreApplication::exec() () from
/usr/lib/libQt5Core.so.5
#42 0x55c77783a6b7 in ?? ()
#43 0x7f3b6f058152 in __libc_start_main () from /usr/lib/libc.so.6
#44 0x55c77783b95e in _start ()
[Inferior 1 (process 2773) detached]

Possible duplicates by query: bug 429973, bug 418660, bug 411774, bug 409252,

[dolphin] [Bug 427034] New: Dolphin freezes system completely (Wrestool)

2020-09-27 Thread Matheus Bastos
https://bugs.kde.org/show_bug.cgi?id=427034

Bug ID: 427034
   Summary: Dolphin freezes system completely (Wrestool)
   Product: dolphin
   Version: 19.12.3
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: view-engine: icons mode
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: matheusm...@gmail.com
CC: kfm-de...@kde.org
  Target Milestone: ---

SUMMARY

When observing KSysGuard (System Monitor) when opening a folder with several
.exe files, the use of the processor and RAM memory increases exponentially in
the "wrestool" process and freezes the system completely, being necessary to
shut down.

STEPS TO REPRODUCE
1. Save several .exe files to a directory.
2. Enable the viewing of these files in Dolphin > General > Views and select
the options: "Microsoft Windows executables” and “Microsoft Windows images”.
Click "Apply".
3. Close Dophin and open it again, go into that folder and watch the processes
running.

OBSERVED RESULT
Dolphin completely crashes the system (Wrestool).

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 20.04
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
DE: Plasma
WM: KWin
Kernel: 5.4.0-49-generic
CPU: Pentium E6500 (2) @ 2.936GHz
Memory: 4GB
GPU: Intel 4 Series Chipset

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

[kwin] [Bug 426083] New: Plasma keeps forgeting selected Alt+Tab effect

2020-09-01 Thread Matheus Candido
https://bugs.kde.org/show_bug.cgi?id=426083

Bug ID: 426083
   Summary: Plasma keeps forgeting selected Alt+Tab effect
   Product: kwin
   Version: 5.19.5
  Platform: Other
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: effects-window-management
  Assignee: kwin-bugs-n...@kde.org
  Reporter: matheu...@live.com
  Target Milestone: ---

SUMMARY
I frequently use "Large Icons" effect preference on Task Switcher and at random
moments it forgets my "Large Icons" preference and returns to "Breeze" being
selected.

STEPS TO REPRODUCE
1. Select Large Icons (or maybe some other effect)
2. Use Plasma for a while, maybe reboot or close and open the laptop, a regular
daily usage.
3. Alt+Tab

OBSERVED RESULT
It goes back to "Breeze" effect.

EXPECTED RESULT
Keep using the selected "Large Icons" effect.

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

ADDITIONAL INFORMATION

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

[dolphin] [Bug 260266] Allow assigning keyboard shortcuts to service menu actions

2020-06-21 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=260266

Matheus  changed:

   What|Removed |Added

 CC||matheusfillip...@gmail.com

--- Comment #8 from Matheus  ---
Oh this is still not possible? After 10 years, would be such a nice feature. I
would like to use this to copy a file full path string with ctrl+shift+c :(

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

[plasmashell] [Bug 422673] Plasma monitor doesn't show anything.

2020-06-17 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=422673

--- Comment #13 from Matheus  ---
Working on 5.19.1 after reinstalling the widgets.

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

[plasmashell] [Bug 422712] New: Not able to use "Edit application" from right click menu from the search list.

2020-06-09 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=422712

Bug ID: 422712
   Summary: Not able to use "Edit application" from right click
menu from the search list.
   Product: plasmashell
   Version: 5.19.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Application Launcher (Kickoff)
  Assignee: k...@davidedmundson.co.uk
  Reporter: matheusfillip...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

SUMMARY

Not able to use "Edit application" from right click menu from the search list. 

STEPS TO REPRODUCE
1. Open the application launcher or application dashboard menu
2. Search for any app and right click on it
3. Click on "Edit application" from the popup menu.

OBSERVED RESULT

Nothing happens but that is not a problem with kmenuedit since it still
launches and it also works if i just got to my app tab or recent and right
click on them. The problem only happens for applications in the search results
list.


EXPECTED RESULT

A window for editing the app should appear.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version:  5.19
KDE Frameworks Version: 5.70
Qt Version: 5.15

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

[kdeplasma-addons] [Bug 422710] New: Disk Quota and Network Quota widgets are not working anymore

2020-06-09 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=422710

Bug ID: 422710
   Summary: Disk Quota and Network Quota widgets are not working
anymore
   Product: kdeplasma-addons
   Version: 5.19.0
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Disk Quota
  Assignee: plasma-b...@kde.org
  Reporter: matheusfillip...@gmail.com
  Target Milestone: ---

SUMMARY
After the 5.19 upgrade the system monitor applets/widgets are showing totally
blank. They were working on 5.18.5. 


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 5.19
KDE Frameworks Version: 5.70
Qt Version: 5.15

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

[plasmashell] [Bug 422705] New: Plasma

2020-06-09 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=422705

Bug ID: 422705
   Summary: Plasma
   Product: plasmashell
   Version: 5.18.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Severity: crash
  Priority: NOR
 Component: generic-crash
  Assignee: plasma-b...@kde.org
  Reporter: matheusfillip...@gmail.com
  Target Milestone: 1.0

Created attachment 129174
  --> https://bugs.kde.org/attachment.cgi?id=129174=edit
Crash dump

SUMMARY
Plasma randomly crashes. Not sure why, usually when opening an application but
happened three times with me already with different applications so I can't
quite see any pattern. 

Maybe the attached crash dump tells something useful I hope.



SOFTWARE/OS VERSIONS

Linux: Arch linux
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.70
Qt Version: 5.15

ADDITIONAL INFORMATION

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

[KAccounts] [Bug 415089] Dolphin Kio-gdrive authentication with Google account fails

2020-04-12 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=415089

Matheus  changed:

   What|Removed |Added

 CC||matheusfillip...@gmail.com

--- Comment #22 from Matheus  ---
I also have the same issue on arch, kaccounts-providers-19.12.3-1.

After the authentication it even opens my drive folders for a while but then
fails in less then 5 minutes or so, and I'm unable to see anything anymore
besides the "you need yo set up authentication again" notification.

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

[print-manager] [Bug 326289] plasma-desktop crashed after configuring printer applet [JobModel::updateJob]

2020-02-13 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=326289

--- Comment #57 from Matheus  ---
Is there any workaround? I'm on 5.18.9? I was trying to use a wifi printer

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

[plasmashell] [Bug 417601] plasmashell crashing, unable to launch

2020-02-13 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=417601

--- Comment #2 from Matheus  ---
(gdb) r
Starting program: /usr/bin/plasmashell 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe1ca4700 (LWP 32369)]
[New Thread 0x7fffdb713700 (LWP 32370)]
[New Thread 0x7fffd9cce700 (LWP 32372)]
Aborting shell load: The activity manager daemon (kactivitymanagerd) is not
running.
If this Plasma has been installed into a custom prefix, verify that its D-Bus
services dir is known to the system for the daemon to be activatable.
org.kde.plasmaquick: Applet preload policy set to 1
[New Thread 0x7fffd3bb5700 (LWP 32377)]
[New Thread 0x7fffd181e700 (LWP 32378)]
Warning: all files used by qml by the plasmoid should be in ui/. The file in
the path
"file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/LayoutManager.js"
was expected at
QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/LayoutManager.js")
Warning: all files used by qml by the plasmoid should be in ui/. The file in
the path
"file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/FolderTools.js"
was expected at
QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderTools.js")
[New Thread 0x7fff3d7e2700 (LWP 32386)]
trying to show an empty dialog
org.kde.plasmaquick: New Applet  "Application Launcher" with a weight of 100
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
org.kde.plasmaquick: New Applet  "Digital Clock" with a weight of 50
Warning: all files used by qml by the plasmoid should be in ui/. The file in
the path
"file:///usr/share/plasma/plasmoids/org.kde.panel/contents/code/LayoutManager.js"
was expected at
QUrl("file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/LayoutManager.js")
trying to show an empty dialog
Failed to find service for Unity Launcher "application://Mailspring.desktop"
[New Thread 0x7fff2de39700 (LWP 32423)]
org.kde.plasmaquick: Delayed preload of  "Application Launcher" after 0 seconds
KAStatsFavoritesModel::setFavorites is ignored
KActivities: Database connection: 
"kactivities_db_resources_140737353435136_readonly" 
query_only:  QVariant(qlonglong, 1) 
journal_mode:QVariant(QString, "wal") 
wal_autocheckpoint:  QVariant(qlonglong, 100) 
synchronous: QVariant(qlonglong, 0)
Entry is not valid "org.kde.kontact.desktop" 0x57890270
Entry is not valid "org.kde.kontact.desktop" 0x57824400
Closing SQL connection:  "kactivities_db_resources_140737353435136_readonly"
trying to show an empty dialog
org.kde.plasmaquick: Applet "Application Launcher" loaded after 343 msec
org.kde.plasmaquick: New Applet  "Audio Volume" with a weight of 50
org.kde.plasmaquick: New Applet  "Clipboard" with a weight of 50
org.kde.plasmaquick: New Applet  "Device Notifier" with a weight of 50
org.kde.plasmaquick: New Applet  "KDE Connect" with a weight of 50
Warning: all files used by qml by the plasmoid should be in ui/. The file in
the path
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/code/uiproperties.js"
was expected at
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/uiproperties.js")
org.kde.plasmaquick: New Applet  "Notifications" with a weight of 50
[New Thread 0x7fff2116b700 (LWP 32527)]
libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
org.kde.plasmaquick: New Applet  "Printers" with a weight of 50
libkcups: Get-Jobs last error: 0 successful-ok
libkcups: Get-Jobs last error: 0 successful-ok
[New Thread 0x7fff1a3b2700 (LWP 32530)]
[New Thread 0x7fff19bb1700 (LWP 32531)]
[New Thread 0x7fff193b0700 (LWP 32532)]
[New Thread 0x7fff18baf700 (LWP 32533)]

(process:32335): OSTree-WARNING **: 20:39:49.331: Invalid proxy URI ''

(process:32335): OSTree-WARNING **: 20:39:49.331: Invalid proxy URI ''
[New Thread 0x7fff0bfff700 (LWP 32534)]
org.kde.plasmaquick: New Applet  "Updates" with a weight of 50
[New Thread 0x7fff0b7fe700 (LWP 32535)]
org.kde.plasmaquick: New Applet  "Vaults" with a weight of 50
Plasma Shell startup completed
[New Thread 0x7fff0addc700 (LWP 32536)]
[New Thread 0x7fff0a5db700 (LWP 32537)]
libkcups: 6

Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault.
0x7fff23ae5556 in JobMo

[plasmashell] [Bug 417601] New: plasmashell crashing, unable to launch

2020-02-13 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=417601

Bug ID: 417601
   Summary: plasmashell crashing, unable to launch
   Product: plasmashell
   Version: 5.12.9
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: grave
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: matheusfillip...@gmail.com
  Target Milestone: 1.0

SUMMARY

I am not able to launch plasmashell anymore. It keep crashing on every attempt,
not sure what is the matter. This is the output of kstart4 plasmashell from a
konsole instance.

kstart5 plasmashell
Omitting both --window and --windowclass arguments is not recommended
Aborting shell load: The activity manager daemon (kactivitymanagerd) is not
running.
If this Plasma has been installed into a custom prefix, verify that its D-Bus
services dir is known to the system for the daemon to be activatable.
org.kde.plasmaquick: Applet preload policy set to 1
Warning: all files used by qml by the plasmoid should be in ui/. The file in
the path
"file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/LayoutManager.js"
was expected at
QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/LayoutManager.js")
Warning: all files used by qml by the plasmoid should be in ui/. The file in
the path
"file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/code/FolderTools.js"
was expected at
QUrl("file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/FolderTools.js")
trying to show an empty dialog
org.kde.plasmaquick: New Applet  "Application Launcher" with a weight of 100
Connecting to deprecated signal
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
Both point size and pixel size set. Using pixel size.
trying to show an empty dialog
org.kde.plasmaquick: New Applet  "Digital Clock" with a weight of 50
Warning: all files used by qml by the plasmoid should be in ui/. The file in
the path
"file:///usr/share/plasma/plasmoids/org.kde.panel/contents/code/LayoutManager.js"
was expected at
QUrl("file:///usr/share/plasma/plasmoids/org.kde.panel/contents/ui/LayoutManager.js")
trying to show an empty dialog
Failed to find service for Unity Launcher "application://Mailspring.desktop"
org.kde.plasmaquick: Delayed preload of  "Application Launcher" after 0 seconds
KAStatsFavoritesModel::setFavorites is ignored
KActivities: Database connection: 
"kactivities_db_resources_140080309827584_readonly" 
query_only:  QVariant(qlonglong, 1) 
journal_mode:QVariant(QString, "wal") 
wal_autocheckpoint:  QVariant(qlonglong, 100) 
synchronous: QVariant(qlonglong, 0)
Entry is not valid "kontact.desktop" 0x56109847f2b0
Entry is not valid "ktp-contactlist.desktop" 0x56109847f2b0
Entry is not valid "kontact.desktop" 0x56109847f2b0
Entry is not valid "ktp-contactlist.desktop" 0x56109847f2b0
Closing SQL connection:  "kactivities_db_resources_140080309827584_readonly"
trying to show an empty dialog
org.kde.plasmaquick: Applet "Application Launcher" loaded after 156 msec
org.kde.plasmaquick: New Applet  "Audio Volume" with a weight of 50
org.kde.plasmaquick: New Applet  "Clipboard" with a weight of 50
org.kde.plasmaquick: New Applet  "Device Notifier" with a weight of 50
org.kde.plasmaquick: New Applet  "KDE Connect" with a weight of 50
Warning: all files used by qml by the plasmoid should be in ui/. The file in
the path
"file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/code/uiproperties.js"
was expected at
QUrl("file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/uiproperties.js")
org.kde.plasmaquick: New Applet  "Notifications" with a weight of 50
libkcups: Create-Printer-Subscriptions last error: 0 successful-ok
org.kde.plasmaquick: New Applet  "Printers" with a weight of 50
libkcups: Get-Jobs last error: 0 successful-ok
libkcups: Get-Jobs last error: 0 successful-ok

(process:18916): OSTree-WARNING **: 18:38:14.214: Invalid proxy URI ''

(process:18916): OSTree-WARNING **: 18:38:14.214: Invalid proxy URI ''
org.kde.plasmaquick: New Applet  "Updates" with a weight of 50
org.kde.plasmaquick: New Applet  "Vaults" with a weight of 50
Plasma Shell startup completed
Registering "org.kde.StatusNotifierItem-13204-1/StatusNotifierItem"
libkcups: 6
KCrash: Attempting to start /usr/bin/plasmashell from kdeinit
sock_file=/run/user/1000/kdeinit5__0
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasmashell path = /usr/bin pid = 18916
KCrash: Arguments: /usr/bin/plasmashell 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from
kdeinit

[plasmashell] [Bug 416215] plasmashell crahsed beim login.

2020-01-15 Thread Matheus Catarino
https://bugs.kde.org/show_bug.cgi?id=416215

--- Comment #1 from Matheus Catarino  ---
Created attachment 125142
  --> https://bugs.kde.org/attachment.cgi?id=125142=edit
New crash information added by DrKonqi

plasmashell (5.17.5) using Qt 5.14.0

- What I was doing when the application crashed:

During system upgrade using discover with package-qt5.

- Unusual behavior I noticed:

After trying to open another application from the start menu, the desktop
crashed momentarily.

- Custom settings of the application:

Desktop displays wallpapers as random slides.

-- Backtrace (Reduced):
#6  0x7fc3a8ba81f5 in QV4::QObjectWrapper::wrap(QV4::ExecutionEngine*,
QObject*) () at /usr/lib/libQt5Qml.so.5
#7  0x7fc3a8b9f128 in QV4::ExecutionEngine::fromVariant(QVariant const&) ()
at /usr/lib/libQt5Qml.so.5
#8  0x7fc3a8c28293 in  () at /usr/lib/libQt5Qml.so.5
#9  0x7fc3a8c48027 in  () at /usr/lib/libQt5Qml.so.5
#10 0x7fc3a8c4d30f in  () at /usr/lib/libQt5Qml.so.5

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

[plasmashell] [Bug 416215] plasmashell crahsed beim login.

2020-01-15 Thread Matheus Catarino
https://bugs.kde.org/show_bug.cgi?id=416215

Matheus Catarino  changed:

   What|Removed |Added

 CC||matheus-catar...@hotmail.co
   ||m

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

[plasmashell] [Bug 415351] New: Plasmashell crash in Bentoo v0.1 (funtoo based)

2019-12-19 Thread Matheus Catarino
https://bugs.kde.org/show_bug.cgi?id=415351

Bug ID: 415351
   Summary: Plasmashell crash in Bentoo v0.1 (funtoo based)
   Product: plasmashell
   Version: 5.17.4
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: matheus-catar...@hotmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.17.4)

Qt Version: 5.13.2
Frameworks Version: 5.65.0
Operating System: Linux 5.3.16-gentoo x86_64
Distribution: Linux

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

This system is very unstable;
Plasma-workspace glitch and black window;

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

Thread 15 (Thread 0x7fbf3a6cf700 (LWP 4614)):
[KCrash Handler]
#6  0x7fbf8233d0a7 in _XPutPixel32 () at /usr/lib/libX11.so.6
#7  0x7fbf8233d6f0 in _XSetImage () at /usr/lib/libX11.so.6
#8  0x7fbf82339487 in XGetSubImage () at /usr/lib/libX11.so.6
#9  0x7fbf72cc459f in swrastGetImage2 () at /usr/lib64/libGLX_mesa.so.0
#10 0x7fbf72cc45f2 in swrastGetImage () at /usr/lib64/libGLX_mesa.so.0
#11 0x7fbf7206d505 in swrastSetTexBuffer2 () at
/usr/lib64/dri/swrast_dri.so
#12 0x7fbf70c8b336 in Plasma::WindowThumbnail::bindGLXTexture() () at
/usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
#13 0x7fbf70c8cc8d in
Plasma::WindowThumbnail::windowToTextureGLX(Plasma::WindowTextureNode*) () at
/usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
#14 0x7fbf70c8d82a in
Plasma::WindowThumbnail::windowToTexture(Plasma::WindowTextureNode*) () at
/usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
#15 0x7fbf70c8db5f in Plasma::WindowThumbnail::updatePaintNode(QSGNode*,
QQuickItem::UpdatePaintNodeData*) () at
/usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so
#16 0x7fbf81f30170 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) ()
at /usr/lib/libQt5Quick.so.5
#17 0x7fbf81f30a2b in QQuickWindowPrivate::updateDirtyNodes() () at
/usr/lib/libQt5Quick.so.5
#18 0x7fbf81f31f32 in QQuickWindowPrivate::syncSceneGraph() () at
/usr/lib/libQt5Quick.so.5
#19 0x7fbf81ed7968 in QSGRenderThread::sync(bool) () at
/usr/lib/libQt5Quick.so.5
#20 0x7fbf81ed8c64 in QSGRenderThread::syncAndRender() () at
/usr/lib/libQt5Quick.so.5
#21 0x7fbf81edc4f8 in QSGRenderThread::run() () at
/usr/lib/libQt5Quick.so.5
#22 0x7fbf802c5c62 in QThreadPrivate::start(void*) () at
/usr/lib/libQt5Core.so.5
#23 0x7fbf7f778427 in start_thread () at /lib/libpthread.so.0
#24 0x7fbf7ff5577f in clone () at /lib/libc.so.6

Thread 14 (Thread 0x7fbf3affd700 (LWP 4521)):
#0  0x7fbf7f77ef15 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib/libpthread.so.0
#1  0x7fbf802cb2f3 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7fbf802cb379 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7fbf69646ae0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fbf6964a3fa in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fbf69645d4e in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fbf6964863b in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fbf802c5c62 in QThreadPrivate::start(void*) () at
/usr/lib/libQt5Core.so.5
#8  0x7fbf7f778427 in start_thread () at /lib/libpthread.so.0
#9  0x7fbf7ff5577f in clone () at /lib/libc.so.6

Thread 13 (Thread 0x7fbf3b7fe700 (LWP 4520)):
#0  0x7fbf7f77ef15 in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib/libpthread.so.0
#1  0x7fbf802cb2f3 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7fbf802cb379 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7fbf69646ae0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fbf6964a3fa in
ThreadWeaver::WorkingHardState::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fbf69645d4e in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fbf6964863b in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fbf802c5c62 in QThreadPrivate::start(void*) () at
/usr/lib/libQt5Core.so.5
#8  0x7f

[knotes] [Bug 413458] New: Can't remove alarm

2019-10-25 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=413458

Bug ID: 413458
   Summary: Can't remove alarm
   Product: knotes
   Version: unspecified
  Platform: Debian stable
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-b...@kde.org
  Reporter: matheus...@infonet.com.br
CC: myr...@kde.org
  Target Milestone: ---

SUMMARY
An alarm keeps showing up even with the note deleted.

STEPS TO REPRODUCE
1. Create a note.
2. Configure an alarm to it.
3. Remove the alarm when it appears on screen.

OBSERVED RESULT
The alarm keeps showing up many times during the day, probably one hour after.

EXPECTED RESULT
The alarm should never show up again, since the note had been deleted and the
alarm removed.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian 10 Stable
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION
kernel 4.19.0-6-amd64

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

[apper] [Bug 413282] New: Apper crash on finish update

2019-10-21 Thread Matheus Catarino
https://bugs.kde.org/show_bug.cgi?id=413282

Bug ID: 413282
   Summary: Apper crash on finish update
   Product: apper
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: dantt...@gmail.com
  Reporter: matheus-catar...@hotmail.com
  Target Milestone: ---

Application: apper (1.0.0)

Qt Version: 5.13.1
Frameworks Version: 5.63.0
Operating System: Linux 5.3.7-arch1-1-ARCH x86_64
Distribution: Arch Linux

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

 Whenever you update any package, after finishing apper stops working. It does
not appear to affect the installation of the update, but it becomes a nuisance
to see the tool failing.

- Custom settings of the application:

I use the aur qt5-autoupdater-packagekit package due to the need for discover.
Then I ended up installing apper to manage the packages installed on the
system.

Using Plasma DE (last version)

The crash can be reproduced every time.

-- Backtrace:
Application: Apper (apper), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f9d7ea82d00 (LWP 50833))]

Thread 3 (Thread 0x7f9d75d67700 (LWP 50835)):
#0  0x7f9d7d17c9ef in poll () at /usr/lib/libc.so.6
#1  0x7f9d7c1e4180 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9d7c1e4251 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f9d7d728a1c in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f9d7d6cf4ec in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f9d7d501385 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f9d7d9fdb37 in  () at /usr/lib/libQt5DBus.so.5
#7  0x7f9d7d5025b0 in  () at /usr/lib/libQt5Core.so.5
#8  0x7f9d7c7714cf in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f9d7d1872d3 in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7f9d77c7f700 (LWP 50834)):
#0  0x7f9d7d17c9ef in poll () at /usr/lib/libc.so.6
#1  0x7f9d7b36c630 in  () at /usr/lib/libxcb.so.1
#2  0x7f9d7b36e2db in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x7f9d786bb101 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x7f9d7d5025b0 in  () at /usr/lib/libQt5Core.so.5
#5  0x7f9d7c7714cf in start_thread () at /usr/lib/libpthread.so.0
#6  0x7f9d7d1872d3 in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7f9d7ea82d00 (LWP 50833)):
[KCrash Handler]
#6  0x7f9d7f310873 in  () at /usr/lib/apper/libapper_private.so
#7  0x7f9d7f3094eb in PackageModel::clearSelectedNotPresent() () at
/usr/lib/apper/libapper_private.so
#8  0x5614585c9b2b in  ()
#9  0x7f9d7d6fcb70 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#10 0x7f9d7f05de70 in
PackageKit::Transaction::finished(PackageKit::Transaction::Exit, unsigned int)
() at /usr/lib/libpackagekitqt5.so.1
#11 0x7f9d7f062c96 in  () at /usr/lib/libpackagekitqt5.so.1
#12 0x7f9d7f060536 in  () at /usr/lib/libpackagekitqt5.so.1
#13 0x7f9d7d6fca11 in QMetaObject::activate(QObject*, int, int, void**) ()
at /usr/lib/libQt5Core.so.5
#14 0x7f9d7f072985 in  () at /usr/lib/libpackagekitqt5.so.1
#15 0x7f9d7f074e46 in  () at /usr/lib/libpackagekitqt5.so.1
#16 0x7f9d7da0a300 in  () at /usr/lib/libQt5DBus.so.5
#17 0x7f9d7d6fd44a in QObject::event(QEvent*) () at
/usr/lib/libQt5Core.so.5
#18 0x7f9d7e1c94f5 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() at /usr/lib/libQt5Widgets.so.5
#19 0x7f9d7e1d2e11 in QApplication::notify(QObject*, QEvent*) () at
/usr/lib/libQt5Widgets.so.5
#20 0x7f9d7d6d09c2 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() at /usr/lib/libQt5Core.so.5
#21 0x7f9d7d6d3739 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#22 0x7f9d7d729404 in  () at /usr/lib/libQt5Core.so.5
#23 0x7f9d7c1e23fe in g_main_context_dispatch () at
/usr/lib/libglib-2.0.so.0
#24 0x7f9d7c1e4211 in  () at /usr/lib/libglib-2.0.so.0
#25 0x7f9d7c1e4251 in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#26 0x7f9d7d728a03 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#27 0x7f9d7d6cf4ec in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#28 0x7f9d7d6d7326 in QCoreApplication::exec() () at
/usr/lib/libQt5Core.so.5
#29 0x5614585ba3ab in  ()
#30 0x7f9d7d0af153 in __libc_start_main () at /usr/lib/libc.so.6
#31 0x5614585ba49e in _start ()
[Inferior 1 (process 50833) detached]

Possible duplicates by query: bug 413205, bug 413201, bug 413024, bug 412864,
bug 412691.

Reported using DrKonqi

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

[plasmashell] [Bug 411720] New: Crashed plasma

2019-09-08 Thread Matheus Catarino
https://bugs.kde.org/show_bug.cgi?id=411720

Bug ID: 411720
   Summary: Crashed plasma
   Product: plasmashell
   Version: 5.16.5
  Platform: Archlinux Packages
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: matheus-catar...@hotmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.16.5)

Qt Version: 5.13.0
Frameworks Version: 5.61.0
Operating System: Linux 5.2.13-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

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

- Unusual behavior I noticed:

Arch Linux x86_64 Linux-5.2.13 w/ NVidia proprietary

Programs opened:
vscode;
firefox;

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

Thread 27 (Thread 0x7fd54b7fe700 (LWP 13895)):
#0  0x7fd5d246f415 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd5d2fe05a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7fd5d2fe0692 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7fd5b4bbe309 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fd5b4bc1d8b in  () at /usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fd5b4bc1de1 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fd5b4bbfecc in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7fd5d2fda520 in  () at /usr/lib/libQt5Core.so.5
#10 0x7fd5d246957f in start_thread () at /usr/lib/libpthread.so.0
#11 0x7fd5d2c640e3 in clone () at /usr/lib/libc.so.6

Thread 26 (Thread 0x7fd54bfff700 (LWP 13894)):
#0  0x7fd5d246f415 in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fd5d2fe05a0 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/usr/lib/libQt5Core.so.5
#2  0x7fd5d2fe0692 in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#3  0x7fd5b4bbe309 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fd5b4bc1d8b in  () at /usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fd5b4bc1de1 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fd5b4bc1de1 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#9  0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#10 0x7fd5b4bc1de1 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#11 0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#12 0x7fd5b4bc1de1 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#13 0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#14 0x7fd5b4bc1de1 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#15 0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#16 0x7fd5b4bc1de1 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#17 0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#18 0x7fd5b4bc1de1 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#19 0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#20 0x7fd5b4bc1de1 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#21 0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#22 0x7fd5b4bc1de1 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#23 0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#24 0x7fd5b4bc1de1 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#25 0x7fd5b4bbd4fe in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#26 0x7fd5b4bbfecc in ThreadWeaver::Thread::run() () a

[plasmashell] [Bug 410144] Session restoring not reordering applications (feature request)

2019-07-23 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=410144

--- Comment #2 from Matheus  ---
OH please Nate Graham! They me more, how soon and how??

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

[plasmashell] [Bug 410144] New: Session restoring not reordering applications (feature request)

2019-07-23 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=410144

Bug ID: 410144
   Summary: Session restoring not reordering applications (feature
request)
   Product: plasmashell
   Version: 5.12.8
  Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: Task Manager
  Assignee: h...@kde.org
  Reporter: matheusfillip...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

It would be a nice feature to have the windows order on the default task
manager  restored when restoring plasmashell sessions. Or maybe just adding a
way to keep the windows order under special window/application settings. Or
either having the task manager the option to remember the manually set order so
that applications are always automatically put in the set order.

Is that possible in any way?

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

[neon] [Bug 369077] Issues with UEFI dual booting with other Ubuntu OS's

2019-06-16 Thread Francisco Matheus
https://bugs.kde.org/show_bug.cgi?id=369077

Francisco Matheus  changed:

   What|Removed |Added

 CC||francisco.matheus.souza@gma
   ||il.com

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

[plasmashell] [Bug 408722] New: KDE Plasmashell desktop randomly crashes when opening a new window.

2019-06-15 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=408722

Bug ID: 408722
   Summary: KDE Plasmashell desktop randomly crashes when opening
a new window.
   Product: plasmashell
   Version: 5.12.7
  Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: matheusfillip...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Created attachment 120884
  --> https://bugs.kde.org/attachment.cgi?id=120884=edit
syslog of the crash

SUMMARY
After the most recent upgrade for ubuntu 18.04.2, using nvidia propretary
drivers, plasmashell randomly crashes, closing all applications and going back
to sddm.

STEPS TO REPRODUCE

Just normal usage, after some time the crash occurs when a new window is about
to open. I just a see a black screen and back to sddm, looking on htop from a
remote session all applications closed.

ERROR LOG

XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"

org.kde.runners.baloo[5103]: The X11 connection broke (error 1). Did the X11
server die?

http://dpaste.com//384TBYR


SPECIAL / WEIRD SPECIFIC THINGS RUNNING ON THIS MACHINE WHILE THE CRASH

I have an i3 X2GO session being hosted on the machine on display :50 and a
client running on display :0, where the crash occurs. Also have jack2 running.
I have set opengl 2.1 in the settings of kde and I have a universal scaling
greater than 1.



SUSPICIOUS

The driver recomendation gui is not working, with the error "importError:
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.12' not found "

SOFTWARE/OS VERSIONS
$ inxi -F   
System:Host: matheus-Inspiron-15-7000-Gaming Kernel: 4.18.0-17-generic
x86_64 bits: 64 Desktop: N/A
   Distro: Ubuntu 18.04.2 LTS   
Machine:   Device: laptop System: Dell product: Inspiron 15 7000 Gaming serial:
N/A 
   Mobo: Dell model: 0P84C9 v: A01 serial: N/A UEFI: Dell v: 1.8.1
date: 08/15/2018
BatteryBAT0: charge: 64.9 Wh 100.0% condition: 64.9/74.0 Wh (88%)   
CPU:   Quad core Intel Core i7-7700HQ (-MT-MCP-) cache: 6144 KB 
   clock speeds: max: 3800 MHz 1: 3400 MHz 2: 3400 MHz 3: 3400 MHz 4:
3401 MHz 5: 3407 MHz 6: 3400 MHz
   7: 3400 MHz 8: 3406 MHz  
Graphics:  Card-1: Intel Device 591b
   Card-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile]   
   Display Server: X.Org 1.19.6 drivers: modesetting,nvidia (unloaded:
fbdev,vesa,nouveau) 
   Resolution: 1920x1080@60.01hz
   OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 version: 4.6.0
NVIDIA 430.26   
Audio: Card-1 Intel CM238 HD Audio Controller driver: snd_hda_intel Sound:
ALSA v: k4.18.0-17-generic
   Card-2 Corsair driver: USB Audio
   Card-3 Roland UM-ONE driver: USB Audio
Network:   Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
Controller driver: r8169
   IF: enp2s0 state: down mac: 8c:ec:4b:0a:f7:d9
   Card-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
driver: ath10k_pci
   IF: wlp3s0 state: up mac: d4:6a:6a:fe:20:9f
   Card-3: Atheros
   IF: null-if-id state: N/A speed: N/A duplex: N/A mac: N/A
Drives:HDD Total Size: 3256.6GB (39.1% used)
   ID-1: /dev/sda model: LITEON_CV3 size: 256.1GB
   ID-2: /dev/sdb model: TOSHIBA_MQ01ABD1 size: 1000.2GB
   ID-3: USB /dev/sdc model: Elements_SE_25FE size: 2000.4GB
Partition: ID-1: / size: 88G used: 70G (85%) fs: ext4 dev: /dev/sda7
   ID-2: /home size: 457G used: 425G (99%) fs: ext4 dev: /dev/sdb3
   ID-3: swap-1 size: 25.47GB used: 1.70GB (7%) fs: swap dev: /dev/sda8
RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 61.0C mobo: N/A gpu: 53C
   Fan Speeds (in rpm): cpu: N/A
Info:  Processes: 464 Uptime: 12:15 Memory: 7404.1/15906.3MB Client: Shell
(bash) inxi: 2.3.56 


NVIDIA DRIVER

430.26

PLASMA

$ plasmashell --version
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-matheus'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-matheus'
plasmashell 5.12.7


LOOKING FOR TEMPORARY WO

[Discover] [Bug 403858] New: Central de aplicativos fevhando sozinha

2019-02-02 Thread Matheus Novais
https://bugs.kde.org/show_bug.cgi?id=403858

Bug ID: 403858
   Summary: Central de aplicativos fevhando sozinha
   Product: Discover
   Version: 5.14.5
  Platform: unspecified
OS: Linux
Status: REPORTED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: discover
  Assignee: lei...@leinir.dk
  Reporter: matheus.novais...@gmail.com
CC: aleix...@kde.org
  Target Milestone: ---

Application: plasma-discover (5.14.5)

Qt Version: 5.11.2
Frameworks Version: 5.54.0
Operating System: Linux 4.15.0-45-generic x86_64
Distribution: KDE neon User Edition 5.14

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

Toda vez que tento abrir para instalar um app ou fazer uma atualização ela
simplemente fecha

The crash can be reproduced every time.

-- Backtrace:
Application: Discover (plasma-discover), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f05280c9200 (LWP 3951))]

Thread 18 (Thread 0x7f04aeffd700 (LWP 3978)):
#0  0x7f051fd2f9f3 in futex_wait_cancelable (private=,
expected=0, futex_word=0x55b9fe2a6ba0) at
../sysdeps/unix/sysv/linux/futex-internal.h:88
#1  __pthread_cond_wait_common (abstime=0x0, mutex=0x55b9fe2a6b50,
cond=0x55b9fe2a6b78) at pthread_cond_wait.c:502
#2  __pthread_cond_wait (cond=0x55b9fe2a6b78, mutex=0x55b9fe2a6b50) at
pthread_cond_wait.c:655
#3  0x7f04fd66223b in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#4  0x7f04fd661f67 in ?? () from
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
#5  0x7f051fd296db in start_thread (arg=0x7f04aeffd700) at
pthread_create.c:463
#6  0x7f052363088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 17 (Thread 0x7f04af7fe700 (LWP 3977)):
#0  0x7f051dbd3064 in g_mutex_unlock () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f051db8ca88 in g_main_context_prepare () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f051db8d46b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f051db8d64c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f0523f5e04b in QEventDispatcherGlib::processEvents
(this=0x7f049c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#5  0x7f0523f0230a in QEventLoop::exec (this=this@entry=0x7f04af7fdda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#6  0x7f0523d2dbba in QThread::exec (this=) at
thread/qthread.cpp:525
#7  0x7f0523d38adb in QThreadPrivate::start (arg=0x55b9fade2f40) at
thread/qthread_unix.cpp:367
#8  0x7f051fd296db in start_thread (arg=0x7f04af7fe700) at
pthread_create.c:463
#9  0x7f052363088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 16 (Thread 0x7f04c219d700 (LWP 3971)):
#0  0x7f0523623bf9 in __GI___poll (fds=0x7f04a80024c0, nfds=2, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f051db8d539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f051db8d64c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f0523f5e04b in QEventDispatcherGlib::processEvents
(this=0x7f04bb20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x7f0523f0230a in QEventLoop::exec (this=this@entry=0x7f04c219cda0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x7f0523d2dbba in QThread::exec (this=) at
thread/qthread.cpp:525
#6  0x7f0523d38adb in QThreadPrivate::start (arg=0x55b9fc587660) at
thread/qthread_unix.cpp:367
#7  0x7f051fd296db in start_thread (arg=0x7f04c219d700) at
pthread_create.c:463
#8  0x7f052363088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 15 (Thread 0x7f04c3fff700 (LWP 3969)):
#0  0x7f0523623bf9 in __GI___poll (fds=0x55b9fb01a850, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f051db8d539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f051db8d8d2 in g_main_loop_run () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f04ce04d026 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x7f051dbb5105 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f051fd296db in start_thread (arg=0x7f04c3fff700) at
pthread_create.c:463
#6  0x7f052363088f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7f04c8d0f700 (LWP 3968)):
#0  0x7f051dbd3049 in g_mutex_lock () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f051db8d51f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f051db8d64c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f051db8d691 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f051dbb5105 in ?? () from 

[systemsettings] [Bug 395575] New: It's not possible to lower the DPI to values smaller than 96

2018-06-18 Thread Matheus Gritz
https://bugs.kde.org/show_bug.cgi?id=395575

Bug ID: 395575
   Summary: It's not possible to lower the DPI to values smaller
than 96
   Product: systemsettings
   Version: 5.13.0
  Platform: Manjaro
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: kcm_fonts
  Assignee: unassigned-b...@kde.org
  Reporter: matheusgr...@gmail.com
CC: unassigned-b...@kde.org
  Target Milestone: ---

Distro: Manjaro KDE Edition 17.1.10
Qt: 5.11.0
KDE Plasma: 5.13.0
KDE Frameworks: 5.47.0
systemsettings5 version: 5.13.0

Steps to Reproduce:
1. Open System Settings
2. Select "Fonts"
3. Toggle "Force Fonts DPI"
4. Try to lower the DPI to a value smaller than 96.
5. Writing the number greys out the "Apply" button and the down arrow is not
clickable.

Ever since the 5.13 update, I'm no longer able to lower the font DPI to values
smaller than 96. Using the default DPI scaling makes windows, buttons, widgets
and other elements too big in my laptop, taking most of the space of the
screen.

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

[plasmashell] [Bug 394351] New: Plasma suddenly crashes as pointer moves to system tray

2018-05-16 Thread Matheus Marques
https://bugs.kde.org/show_bug.cgi?id=394351

Bug ID: 394351
   Summary: Plasma suddenly crashes as pointer moves to system
tray
   Product: plasmashell
   Version: 5.12.5
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: System Tray
  Assignee: plasma-b...@kde.org
  Reporter: martr...@gmail.com
  Target Milestone: 1.0

Created attachment 112697
  --> https://bugs.kde.org/attachment.cgi?id=112697=edit
Log report.

Application: plasmashell (5.12.5)

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

-- Information about the crash:
- What I was doing when the application crashed:
(I'm filling this on browser as bug reporter had error 410)
Using Waterfox 56.1.0 (64-bit) version, moved my pointer to system tray to
switch wireless on / off (connection was down) and then there's a crash.
Redshift turned off in the meantime.

- Unusual behavior I noticed:
Redshift suddenly turned off, but I think its a side effect of Plasma crashing.
Albeit it, nothing was unusual.

- Custom settings of the application:
I'm using 'Icons-only Task Manager' as my default bottom bar.  As I'm using
Arch and KDE, I have lots of custom and don't know what else I can provide.
Some light would be helpful.

The crash does not seem to be reproducible.

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

Thread 26 (Thread 0x7fc5217fa700 (LWP 14128)):
#0  0x7fc65a8e7ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fc65b730f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fc59399b149 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fc59399f029 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fc59399a20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fc59399f082 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fc59399a20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fc59399d079 in ThreadWeaver::Thread::run() () at
/usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fc65b72fabd in  () at /usr/lib/libQt5Core.so.5
#9  0x7fc65a8e2075 in start_thread () at /usr/lib/libpthread.so.0
#10 0x7fc65b03353f in clone () at /usr/lib/libc.so.6

Thread 25 (Thread 0x7fc521ffb700 (LWP 14127)):
#0  0x7fc65a8e7ffc in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7fc65b730f9c in QWaitCondition::wait(QMutex*, unsigned long) () at
/usr/lib/libQt5Core.so.5
#2  0x7fc59399b149 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /usr/lib/libKF5ThreadWeaver.so.5
#3  0x7fc59399f029 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#4  0x7fc59399a20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#5  0x7fc59399f082 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#6  0x7fc59399a20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#7  0x7fc59399f082 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#8  0x7fc59399a20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#9  0x7fc59399f082 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#10 0x7fc59399a20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#11 0x7fc59399f082 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#12 0x7fc59399a20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#13 0x7fc59399f082 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#14 0x7fc59399a20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#15 0x7fc59399f082 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#16 0x7fc59399a20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#17 0x7fc59399f082 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#18 0x7fc59399a20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#19 0x7fc59399f082 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#20 0x7fc59399a20d in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/usr/lib/libKF5ThreadWeaver.so.5
#21 0x7fc59399f082 in  () at /usr/lib/libKF5ThreadWeaver.so.5
#22 

[systemsettings] [Bug 392979] settings crash

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

--- Comment #9 from Matheus <matheusfillip...@gmail.com> ---
Okay thanks!

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

[systemsettings] [Bug 392979] settings crash

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

--- Comment #7 from Matheus <matheusfillip...@gmail.com> ---
You mean fixed in Qt 5.9.5 right. Okay I hope it gets fixed for the lts
release! But does it have any relationship with this lagging on some
applications sometimes?

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

[systemsettings] [Bug 392979] settings crash

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

--- Comment #5 from Matheus <matheusfillip...@gmail.com> ---
Is this a widespread problem with kde? I've experiencing some lagging behaviors
on most applications that works fine on the other DE's I have installed.

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

[systemsettings] [Bug 392979] New: settings crash

2018-04-10 Thread Matheus
https://bugs.kde.org/show_bug.cgi?id=392979

Bug ID: 392979
   Summary: settings crash
   Product: systemsettings
   Version: 5.12.4
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: matheusfillip...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.12.4)

Qt Version: 5.9.4
Frameworks Version: 5.44.0
Operating System: Linux 4.15.0-13-generic x86_64
Distribution: Ubuntu Bionic Beaver (development branch)

-- Information about the crash:
I was searching for the name draw and it simply crashed. I have nvidia-384
installed and its a laptop i15 7567.

-- 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 0x7ff87352c800 (LWP 32479))]

Thread 8 (Thread 0x7ff81f732700 (LWP 10734)):
#0  0x7ff86ef720b4 in __GI___libc_read (fd=34, buf=0x7ff81f731cd0,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7ff868e21960 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff868ddcf27 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff868ddd3e0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff868ddd7d2 in g_main_loop_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ff8242b9e16 in  () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6  0x7ff868e04e05 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7ff86b12d6db in start_thread (arg=0x7ff81f732700) at
pthread_create.c:463
#8  0x7ff86ef8388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 7 (Thread 0x7ff825cb5700 (LWP 10733)):
#0  0x7ff86ef76bf9 in __GI___poll (fds=0x55cbddb88370, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff868ddd439 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff868ddd54c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff868ddd591 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff868e04e05 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ff86b12d6db in start_thread (arg=0x7ff825cb5700) at
pthread_create.c:463
#6  0x7ff86ef8388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7ff836bb8700 (LWP 8452)):
#0  0x7ff86ef720b4 in __GI___libc_read (fd=29, buf=0x7ff836bb7b70,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7ff868e21960 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff868ddcf27 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff868ddd3e0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff868ddd54c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7ff86f8c24fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ff86f86761a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x7ff86f68622a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ff86d1d9a45 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#9  0x7ff86f68b16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x7ff86b12d6db in start_thread (arg=0x7ff836bb8700) at
pthread_create.c:463
#11 0x7ff86ef8388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 5 (Thread 0x7ff840da1700 (LWP 987)):
#0  0x7ff86ef76bf9 in __GI___poll (fds=0x7ff83c003ce0, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7ff868ddd439 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff868ddd54c in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff86f8c24fb in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7ff86f86761a in
QEventLoop::exec(QFlags) () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x7ff86f68622a in QThread::exec() () at
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x7ff86d1d9a45 in  () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x7ff86f68b16d in  () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7ff86b12d6db in start_thread (arg=0x7ff840da1700) at
pthread_create.c:463
#9  0x7ff86ef8388f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 4 (Thread 0x7ff849211700 (LWP 608)):
#0  0x7ff86ef720b4 in __GI___libc_read (fd=12, buf=0x7ff849210b70,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27
#1  0x7ff868e21960 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7ff868ddcf27 in g_main_context_check () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7ff868ddd3e0 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7ff868ddd54c in 

[krita] [Bug 392526] Isometric grid has several drawing issues(with openGL disabled)

2018-03-31 Thread Matheus Pesegoginski
https://bugs.kde.org/show_bug.cgi?id=392526

--- Comment #2 from Matheus Pesegoginski <pese.ek...@outlook.com> ---
(In reply to wolthera from comment #1)
> Huh, that's peculiar. Does it also happen with openGL enabled?

I can't try it, my computer do not have opengl support, unfortunatly.

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

[krita] [Bug 392526] Bug at isometric grid

2018-03-30 Thread Matheus Pesegoginski
https://bugs.kde.org/show_bug.cgi?id=392526

Matheus Pesegoginski <pese.ek...@outlook.com> changed:

   What|Removed |Added

   Platform|Other   |Windows CE
 OS|Linux   |MS Windows

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

[krita] [Bug 392526] New: Bug at isometric grid

2018-03-30 Thread Matheus Pesegoginski
https://bugs.kde.org/show_bug.cgi?id=392526

Bug ID: 392526
   Summary: Bug at isometric grid
   Product: krita
   Version: 4.0
  Platform: Other
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: Tool/Assistants
  Assignee: krita-bugs-n...@kde.org
  Reporter: pese.ek...@outlook.com
  Target Milestone: ---

I'm not so good at explaining bugs, so i leave bellow a short video of the bug
occuring:
https://youtu.be/zrlPF1om8fc


Krita
  Version: 4.0.0

OS Information
  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 6.1.7601
  Pretty Productname: Windows 7 SP 1 (6.1)
  Product Type: windows
  Product Version: 7sp1

OpenGL Info
  **OpenGL not initialized**

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

[plasmashell] [Bug 385865] Plasma crashed after switching activities using shortcut

2017-10-17 Thread Matheus Marques
https://bugs.kde.org/show_bug.cgi?id=385865

--- Comment #1 from Matheus Marques <martr...@gmail.com> ---
After the afternoon update of some packages on Oct. 17, I think the issue is
solved. I've tried it now and there is no sign of the bad behaviour. Everything
working properly.

Thanks.

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

[plasmashell] [Bug 385865] New: Plasma crashed after switching activities using shortcut

2017-10-17 Thread Matheus Marques
https://bugs.kde.org/show_bug.cgi?id=385865

Bug ID: 385865
   Summary: Plasma crashed after switching activities using
shortcut
   Product: plasmashell
   Version: 5.11.0
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: k...@davidedmundson.co.uk
  Reporter: martr...@gmail.com
CC: plasma-b...@kde.org
  Target Milestone: 1.0

Application: plasmashell (5.11.0)

Qt Version: 5.9.2
Frameworks Version: 5.39.0
Operating System: Linux 4.13.7-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
Fresh reboot. Tried to change activity using shortcut (meta + 2; meta + 3; for
example). Plasma suddenly crashed and bug report option showed up. Plasma then
starts working again.

- Unusual behavior I noticed:
Redshift makes weird colors, after the second crash, plasmashell won't load
again on its own. I need to open console and load it.

- Custom settings of the application:
Lots of changes on shortcuts and widgets. I don't know what kind of info could
be useful here. Any help would be appreciated.

The crash can be reproduced every time.

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

Thread 8 (Thread 0x7f97ba58f700 (LWP 3280)):
#0  0x7f9885e85664 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x7f9885e5dd6e in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9885e5dfae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f988be9ccf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f988be4048b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f988bc5927e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f97bcf2d1aa in KCupsConnection::run() () at /usr/lib/libkcupslib.so
#7  0x7f988bc5dfcb in  () at /usr/lib/libQt5Core.so.5
#8  0x7f988ae1708a in start_thread () at /usr/lib/libpthread.so.0
#9  0x7f988b56a24f in clone () at /usr/lib/libc.so.6

Thread 7 (Thread 0x7f97cd08e700 (LWP 3180)):
#0  0x7f9885e5c53a in  () at /usr/lib/libglib-2.0.so.0
#1  0x7f9885e5c701 in g_main_context_check () at /usr/lib/libglib-2.0.so.0
#2  0x7f9885e5de76 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f9885e5dfae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f988be9ccf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f988be4048b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f988bc5927e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f988f97929b in  () at /usr/lib/libQt5Quick.so.5
#8  0x7f988bc5dfcb in  () at /usr/lib/libQt5Core.so.5
#9  0x7f988ae1708a in start_thread () at /usr/lib/libpthread.so.0
#10 0x7f988b56a24f in clone () at /usr/lib/libc.so.6

Thread 6 (Thread 0x7f97cf2e7700 (LWP 3058)):
#0  0x7f988b55fd4b in poll () at /usr/lib/libc.so.6
#1  0x7f9885e5ded3 in  () at /usr/lib/libglib-2.0.so.0
#2  0x7f9885e5dfae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#3  0x7f988be9ccf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#4  0x7f988be4048b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#5  0x7f988bc5927e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#6  0x7f988bc5dfcb in  () at /usr/lib/libQt5Core.so.5
#7  0x7f988ae1708a in start_thread () at /usr/lib/libpthread.so.0
#8  0x7f988b56a24f in clone () at /usr/lib/libc.so.6

Thread 5 (Thread 0x7f9866fd5700 (LWP 2990)):
#0  0x7f988ae1d38d in pthread_cond_wait@@GLIBC_2.3.2 () at
/usr/lib/libpthread.so.0
#1  0x7f9891697ef7 in  () at /usr/lib/libQt5Script.so.5
#2  0x7f9891697f39 in  () at /usr/lib/libQt5Script.so.5
#3  0x7f988ae1708a in start_thread () at /usr/lib/libpthread.so.0
#4  0x7f988b56a24f in clone () at /usr/lib/libc.so.6

Thread 4 (Thread 0x7f987133a700 (LWP 2954)):
#0  0x7f9885e855f9 in g_mutex_lock () at /usr/lib/libglib-2.0.so.0
#1  0x7f9885e5d77d in g_main_context_prepare () at
/usr/lib/libglib-2.0.so.0
#2  0x7f9885e5ddf6 in  () at /usr/lib/libglib-2.0.so.0
#3  0x7f9885e5dfae in g_main_context_iteration () at
/usr/lib/libglib-2.0.so.0
#4  0x7f988be9ccf4 in
QEventDispatcherGlib::processEvents(QFlags) ()
at /usr/lib/libQt5Core.so.5
#5  0x7f988be4048b in
QEventLoop::exec(QFlags) () at
/usr/lib/libQt5Core.so.5
#6  0x7f988bc5927e in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x7f988edccbc9 in  () at /usr/lib/libQt5Qml.so.5
#8  0x7f988bc5dfcb in  () at /usr/lib/libQt5Core.so.5
#9  0x7f988ae1708a in start_thread 

[krita] [Bug 364984] group not editable at new window view.

2016-07-03 Thread Matheus Pesegoginski via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364984

--- Comment #2 from Matheus Pesegoginski <pese.ek...@outlook.com> ---
Yeah, it happens every time. But sometimes it takes some time to happen.

My version of Krita is the 3.0 git (f0cbffc)
I use Windows 10 64. 

And sorry for anything mistaken cause english is not my main language.

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


[krita] [Bug 364984] group not editable at new window view.

2016-07-01 Thread Matheus Pesegoginski via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364984

Matheus Pesegoginski <pese.ek...@outlook.com> changed:

   What|Removed |Added

   Keywords||usability
 CC||pese.ek...@outlook.com

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


[krita] [Bug 364984] New: group not editable at new window view.

2016-07-01 Thread Matheus Pesegoginski via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=364984

Bug ID: 364984
   Summary: group not editable at new window view.
   Product: krita
   Version: 3.0
  Platform: MS Windows
   URL: http://i.imgur.com/ZflkyHE.png
OS: MS Windows
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: general
  Assignee: krita-bugs-n...@kde.org
  Reporter: pese.ek...@outlook.com

When i open a new window view, it shows up that i can't draw inside it, because
there is a group layer not editable, but it doesn't have any group layer..


Reproducible: Always

Steps to Reproduce:
1.Open a file
2. After Open the file, click in the Window -> New Window
3. In the Window that poped out, go to Window -> New View -> "File Name"
4. Try to draw something at this window.

Actual Results:  
Print a message at screen: "group not editable"

Expected Results:  
I Expected that i can draw at the new window.

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


[ksplash] [Bug 363042] Splash screen frozen for ~20-30 seconds

2016-06-15 Thread Matheus Felipe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363042

--- Comment #4 from Matheus Felipe <matheusfbr...@gmail.com> ---
(In reply to Natenom from comment #3)
> No change on my system after the update.
> KDE Plasma 5.6.5, KDE Frameworks 5.22.0, Qt 5.6.1 on Arch Linux;

First boot after update went ok ( no idea why ), and after that same error.

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


[ksplash] [Bug 363042] Splash screen frozen for ~20-30 seconds

2016-06-15 Thread Matheus Felipe via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363042

--- Comment #2 from Matheus Felipe <matheusfbr...@gmail.com> ---
plasmashell 5.6.5

first boot, seems fixed

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


[kate] [Bug 356473] Crashes after trying to open c/c++ files

2015-12-10 Thread Matheus via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356473

--- Comment #2 from Matheus <matheusfillip...@gmail.com> ---
As I'm running on ubuntu, I've installed kdevelop throught apt-get
install kdevelop. I have allready tryied to run apt-get remove --purge
kdevelop* and reinstall it, install using the .deb package and I'm
allways getting the same error. Now I discovered that this only
happens with a single file Isn't it quite interesting?  I guess I
mentioned in the report that it happens with all cpp codes, but
testing it now I didn't had any issue. The code was actually that
large, about 40 lines of code. I is a test code and don't do anything
because its totally incomplete and buggy. It's attached to this
reply(named generator.cpp). Try yourself and see if you can open it.

2015-12-10 14:02 GMT-02:00 Milian Wolff via KDE Bugzilla
<bugzilla_nore...@kde.org>:
> https://bugs.kde.org/show_bug.cgi?id=356473
>
> Milian Wolff <m...@milianw.de> changed:
>
>What|Removed |Added
> 
>  Status|UNCONFIRMED |NEEDSINFO
> Version|4.7.1   |unspecified
> Product|kdevelop|kate
>  Resolution|--- |WAITINGFORINFO
>Assignee|kdevelop-bugs-n...@kde.org  |kwrite-bugs-n...@kde.org
>   Component|general |part
>
> --- Comment #1 from Milian Wolff <m...@milianw.de> ---
> Crash in KSycocaEntry, this means your environment is probably misconfigured.
> Do you compile KDevelop yourself? If so, where do you install it to? Do you
> setup KDEDIRS properly, and run kbuildsycoca4?
>
> Furthermore, can you get more debug symbols for katepart, including file/line
> numbers?
>
> --
> You are receiving this mail because:
> You reported the bug.

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


[kdevelop] [Bug 356473] New: Crashes after trying to open c/c++ files

2015-12-10 Thread Matheus via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356473

Bug ID: 356473
   Summary: Crashes after trying to open c/c++ files
   Product: kdevelop
   Version: 4.7.1
  Platform: Ubuntu Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: kdevelop-bugs-n...@kde.org
  Reporter: matheusfillip...@gmail.com

Application: kdevelop (4.7.1)
KDE Platform Version: 4.14.13
Qt Version: 4.8.6
Operating System: Linux 4.2.0-19-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
I was trying to open a c++ file. It allways craches when I try to do so and
then I have to restart the application or reboot system. I only happens with
c++ or c files.

The crash can be reproduced every time.

-- 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 0x7f098ba75840 (LWP 10138))]

Thread 10 (Thread 0x7f096f03d700 (LWP 10139)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x7f098487eb5a in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x7f098487eb89 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x7f09874d66aa in start_thread (arg=0x7f096f03d700) at
pthread_create.c:333
#4  0x7f0988193eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 9 (Thread 0x7f08edbbf700 (LWP 10140)):
#0  0x7f0982241869 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f09821fca9e in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f09821fd190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f09821fd2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f098899420e in QEventDispatcherGlib::processEvents
(this=0x7f08e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x7f09889620d1 in QEventLoop::processEvents
(this=this@entry=0x7f08edbbed40, flags=...) at kernel/qeventloop.cpp:149
#6  0x7f0988962445 in QEventLoop::exec (this=this@entry=0x7f08edbbed40,
flags=...) at kernel/qeventloop.cpp:204
#7  0x7f09888514f9 in QThread::exec (this=this@entry=0x1fd5680) at
thread/qthread.cpp:538
#8  0x7f0988942133 in QInotifyFileSystemWatcherEngine::run (this=0x1fd5680)
at io/qfilesystemwatcher_inotify.cpp:265
#9  0x7f0988853d1c in QThreadPrivate::start (arg=0x1fd5680) at
thread/qthread_unix.cpp:349
#10 0x7f09874d66aa in start_thread (arg=0x7f08edbbf700) at
pthread_create.c:333
#11 0x7f0988193eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 8 (Thread 0x7f08ec9ca700 (LWP 10141)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at
../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
#1  0x7f0988854264 in QWaitConditionPrivate::wait (time=1000,
this=0x3ac7620) at thread/qwaitcondition_unix.cpp:84
#2  QWaitCondition::wait (this=this@entry=0x3ac6968,
mutex=mutex@entry=0x3ac6970, time=time@entry=1000) at
thread/qwaitcondition_unix.cpp:158
#3  0x7f09852ed526 in KDevelop::DUChainPrivate::CleanupThread::run
(this=0x3ac6950) at
/build/buildd/kdevplatform-1.7.1/language/duchain/duchain.cpp:283
#4  0x7f0988853d1c in QThreadPrivate::start (arg=0x3ac6950) at
thread/qthread_unix.cpp:349
#5  0x7f09874d66aa in start_thread (arg=0x7f08ec9ca700) at
pthread_create.c:333
#6  0x7f0988193eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 7 (Thread 0x7f08dd51b700 (LWP 10142)):
#0  0x7f098818449d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f09822404e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f09821fccd4 in g_main_context_check () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f09821fd190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f09821fd2fc in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x7f098899420e in QEventDispatcherGlib::processEvents
(this=0x7f08d80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#6  0x7f09889620d1 in QEventLoop::processEvents
(this=this@entry=0x7f08dd51ad90, flags=...) at kernel/qeventloop.cpp:149
#7  0x7f0988962445 in QEventLoop::exec (this=this@entry=0x7f08dd51ad90,
flags=...) at kernel/qeventloop.cpp:204
#8  0x7f09888514f9 in QThread::exec (this=) at
thread/qthread.cpp:538
#9  0x7f0988853d1c in QThreadPrivate::start (arg=0x4371898) at
thread/qthread_unix.cpp:349
#10 0x7f09874d66aa in start_thread (arg=0x7f08dd51b700) at
pthread_create.c:333
#11 0x7f0988193eed in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 6 (Thread 0x7f08cfdd5700 (LWP 10152)):
#0  0x7f09881888dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x7f09821fd1ec in ?? () from